Skip to main content
Answers to the questions merchants and developers ask most. Each answer links to the full guide if you need more detail.

Getting started

Onboarding, timelines, and going live

Checkout

Shopify, headless, and mobile apps

Payments

Gateways, credentials, and webhooks

Billing

Prepaid credits, tiers, and GST

Dashboard

Coupons, upsells, RTO, customization

Developers

Webhooks, retries, and API keys

​
Getting started and onboarding

Typically 24–48 hours. Onboarding is fully managed — you share Shopify collaborator access, our team builds the integration on a duplicate of your theme, and you approve a preview before going live. See Shopify onboarding.
Your Shopify collaboration code and store URL, your business and GST details, team members, and payment gateway credentials for the gateways you want enabled. Full checklist in the Shopify guide.
No. We integrate on a duplicate of the theme you nominate (your live theme if you don’t specify one), and you review a preview/testing link before anything goes live.
Regenerating it revokes our access mid-integration. Don’t click Generate New Code until your FlexyPe checkout integration is fully completed.
Yes — Shopify onboarding is mandatory first. Your store must be onboarded and your domain registered with FlexyPe before you can integrate on Hydrogen/headless or mobile apps.

​
Checkout and platforms

  • Shopify — managed theme integration (guide)
  • Hydrogen and other headless/React storefronts on Shopify — browser SDK (guide)
  • Mobile apps backed by a Shopify store — hosted checkout in a webview (guide)
On headless storefronts, FlexyPe detects your store from the domain the script runs on, which must match the domain you registered during onboarding. On localhost, add data-shop-domain to the script tag. See store detection.
The most common cause is a domain mismatch — the domain serving the script isn’t the one registered with FlexyPe. Confirm the registered domain, and in local development set data-shop-domain explicitly. Remove that attribute in production.
Create a checkout session from your backend, then load https://checkout.flexype.io/?session={session_id} in a webview. Creating the session server-side keeps your API key out of the app binary. See Mobile Apps.
Yes. Checkout Customization covers general styling, and the login, address, and payment steps individually.

​
Payments and gateways

Razorpay, Easebuzz, Cashfree, PayU, XPay, PhonePe, Snapmint, and CCAvenue. See Payment Providers for per-gateway setup.
PayU, Cashfree, XPay, and Easebuzz require webhook setup. Razorpay requires account authorization and no webhook setup. PhonePe requires sharing your MID with our team — mapping is manual and can take up to a week.
Yes. Configure them any time from Settings → Payment Settings.
Your gateway’s own support team. We can refer you to a provider if you don’t have an account yet, but technical questions about the gateway itself go to them.
Yes — Payment Offers creates payment-method-specific discounts, for example prepaid-only offers to shift volume away from COD.

​
Billing and credits

FlexyPe bills from a prepaid credit balance. Charging starts with your first processed order, cumulative sales determine your tier, and charges are deducted daily. Full detail in Billing and Payments.
No. Your selling plan, tiers, and rates are unchanged — only when charges are calculated and collected. See what changed.
Settings → Billing & Usage → Add Credits, or the Available Credits shortcut in the left navigation. Step-by-step.
No — 18% GST is added on top. A ₹1,000 recharge is billed at ₹1,180 and adds ₹1,000 to your balance. Add your GSTIN in Store Details to claim input credit. See GST and taxes.
Your estimated monthly charges plus a buffer of about 4–5 days of expected charges. Watch days of credit left and the projected balance on the Billing & Usage balance strip. See billing analytics.
Crossing a tier threshold triggers reconciliation — the cycle is recalculated at the new tier and the difference posts as a credit or a debit. See how it works.
No. The plan amount is divided across the days of the month and you’re charged only for days used. Worked example.

​
Dashboard and features

Go to Coupons and pick a type — Amount Off, Buy X Get Y, Purchase Driven, Exclusive Free Gift, Free Shipping, or Bundle. Configure the rules and activate.
Enable the RTO Suite for OTP verification, address validation, and fraud signals so risky orders are caught before fulfillment.
The Abandoned Cart dashboard lists incomplete checkouts, and you can wire recovery flows to the ACR webhook to trigger your own messaging.
Yes — Smart Upsells supports pre- and post-purchase offers.
Assign roles in Users & Permissions and audit actions in Activity Logs.
Taxes & Duties — add your GSTIN, choose inclusive or exclusive pricing, and define regional rules.

​
Webhooks and API

Abandoned Checkout Recovery, Abandoned Session Recovery, Collection Viewed, Product Viewed, and New Customer. See available events and event triggers for exact firing conditions.
Compare the X-Flexype-Authorization header against the secret you set when creating the endpoint, before processing anything. See verifying webhooks.
FlexyPe retries three times — after 1 minute, 5 minutes, and 15 minutes. After that the delivery is marked failed, and you can retry it manually from the dashboard. See retry logic.
Retries reuse the original X-Event-Id. Deduplicate on that header and persist processed IDs so it survives restarts. See idempotency.
Return HTTP 200 within 10 seconds. Acknowledge first, then process asynchronously in a queue or background job.
Dashboard → Settings → API Keys. Rotate them regularly, keep them in environment variables, and revoke any key you suspect is exposed. Authentication details are in the API Reference.

​
Still stuck?

Contact Support

Reach the FlexyPe support team

WhatsApp community

Product updates, tips, and other merchants