Payment Methods
Connect Stripe, PayPal, Polar, Mollie, Kelviq, Razorpay, Paystack, Skrill, CoinPayments, CeyPay, access codes or a native method so your project can take subscriptions.
By the end of this page, you'll have added at least one payment method to your project so it can start accepting subscriptions. Each method has its own setup guide linked below.
A payment method is a gateway connection — Stripe, PayPal, Razorpay, etc. — that processes subscriber payments on your behalf. Subscriby supports eleven payment options, and you can enable as many as you like per project. Subscribers see the ones you've enabled and pick the one that suits them.
Navigating to Payment Methods. Select a project first (top-left project picker or Select as Current on the All Projects page), then open Payment Methods from the sidebar.
Add a new payment method
Open Setup a Payment Method
Click Setup a Payment Method at the top-right of the Payment Methods page.
Pick a provider and mode
Pick a provider from the grid (Stripe, PayPal, etc.) and select a mode:
- Live — production, real money flowing.
- Test / Sandbox — testing, no real money.
Some providers don't have a Test mode — native platform payments and Access Codes are Live-only.
Enter the provider's configuration
Enter the provider's API keys, secret keys, merchant IDs, depending on the provider. Keys must match the mode: live keys (e.g. sk_live_…) for Live mode, test keys (e.g. sk_test_…) for Test mode. Subscriby validates the prefixes for most providers.
The exact fields for each provider are documented in the per-provider setup guides below.
Mark the method Active
Toggle Mark Payment Method as Active to make it immediately available to your subscribers. Leave it off while you're still validating the connection.
Save changes
Click Save Changes (or Connect for Stripe, which redirects through Stripe's own onboarding flow).
Provider setup guides
Each provider has its own config fields and instructions. Click through for the step-by-step:
Stripe
42 countries, direct charges, 150+ currencies. Handled via Stripe Connect — Subscriby automates key exchange so you won't paste any keys yourself.
PayPal
200+ countries, 24 currencies, supports recurring subscriptions. Requires a Client ID and Secret from the PayPal Developer portal.
Polar
Merchant of record in 120+ countries, 36 currencies, supports recurring. Needs one organization access token; the webhook registers itself.
Mollie
Europe's rails — iDEAL, SEPA Direct Debit, Bancontact, cards and PayPal — in
29 currencies, supports recurring. Needs the profile's API key
(live_… / test_…).
Kelviq
Merchant of record in 90+ countries, 137 currencies, supports recurring and chases a failed renewal itself. Needs one Server API Key; the webhook registers itself.
Skrill
131 countries, e-wallet and card payments, one-time charges only. Requires your Skrill merchant email and a secret word.
CoinPayments
Bitcoin and USD stablecoins. Needs a Client ID, Client Secret, and an API domain (a-api or b-api).
Paystack
Seven African countries — Nigeria, Ghana, South Africa, Kenya, and more.
Requires an API key (pk_live_… / pk_test_…) and a secret
(sk_live_… / sk_test_…).
Razorpay
India-exclusive, 80+ currencies, supports recurring. Needs a Key ID
(rzp_live_… / rzp_test_…) and Key Secret.
CeyPay
Sri Lanka-exclusive crypto gateway (USDT variants). Requires API key
(ak_live_… / ak_test_…) and Secret key (sk_live_… / sk_test_…).
Native platform payment
The in-app payment a connector brings, priced in its platform's own currency. Live only, one-time only — no recurring subscriptions.
Access Codes
Single-use codes you generate and hand out — for free giveaways or manual sales. No external gateway needed. For one string many people redeem for money off, see coupon codes instead.
Sync subscription plans (for providers with product catalogues)
Some providers keep their own product / plan catalogue, and Subscriby needs to push your plans to that catalogue before subscribers can transact through them. This applies to Stripe, PayPal, Polar, Kelviq, CoinPayments, and Razorpay. The other providers don't need this step.
Subscriby does this push on its own whenever a plan that is on sale is created, saved or published, so in day-to-day use you never run it by hand. Only plans that are on sale are pushed: a draft is pushed the moment you publish it. The manual sync below re-pushes every plan at once, which is what you want after linking a new provider, after reconnecting one, or whenever the bot or the portal says a plan is not available for a provider.
Confirm plans are configured
Make sure your subscription plans are created and configured.
Locate the provider's row
On the Payment Methods page, find the provider's row.
Choose Sync Subscription Plans
Click the options menu (three-dots icon) and choose Sync Subscription Plans.
Wait for the sync job
Subscriby queues a sync job. Behind the scenes, it creates matching products and pricing entries inside the provider's dashboard — Stripe products and prices, PayPal plans, Polar products, Kelviq plans, Razorpay plans, and so on.
Check the provider's dashboard
When the sync completes, plans become available through that provider, and each one shows up in the provider's own dashboard as a product with a price. Plans you add, edit or publish afterwards are pushed automatically; re-run the sync only when a plan is missing on the provider's side.
Recurring vs. one-time support. Separate from sync, providers differ in whether they support automatic recurring billing for subscriptions. The ones that do: Stripe, PayPal, Polar, Mollie, Kelviq, Paystack, Razorpay. The ones that don't — only one-time charges: Skrill, CoinPayments, CeyPay, native platform payments, Access Codes.
Validation rule to be aware of: Subscriby blocks you from saving a plan with Recurring = on if the plan's currency is crypto (BTC, USDT, USDC, and so on) or a platform's native currency. For fiat currencies, the form doesn't block the save — so you could configure a recurring plan in USD with Skrill attached, but there'd be no actual auto-renewal at runtime because Skrill doesn't have a recurring mechanism. Always match your plan's recurring setting to what the payment methods you intend to accept can actually deliver.
Choosing providers wisely
Rather than enabling every provider on day one, pick based on your audience.
Global audience
Stripe for the broadest fiat reach (138+ currencies, cards, Apple Pay, Google Pay, Link and the wallets your Stripe account enables, such as Amazon Pay, Cash App Pay, Revolut Pay, Samsung Pay and GrabPay). Pair with PayPal if part of your audience prefers not entering card numbers.
Polar when you would rather not handle sales tax and VAT yourself: Polar is the merchant of record, collects the tax and pays you out in 120+ countries, including where Stripe will not onboard you.
Kelviq for the same reason, with failed renewals chased for you: Kelviq is a merchant of record too, pays you out in 90+ countries, and emails the member a payment link and retries a failed card up to eight times over fourteen days.
Regional providers
- India-only → Razorpay (UPI, netbanking, Indian cards, and wallets locals expect).
- Africa (Nigeria, Ghana, Kenya, South Africa) → Paystack (local cards, mobile money, USSD, bank transfers).
- Europe → Mollie (iDEAL, SEPA Direct Debit, Bancontact, cards and PayPal, with renewals on the mandate the first payment leaves).
Crypto-first audience
CoinPayments globally (BTC, ETH, stablecoins on many chains) or CeyPay for Sri Lankan-settled USDT.
Platform-native
A connector may bring its platform's own in-app payment — instant, no redirect, store-compliant, one-time charges only, and only reachable through the bot (not the portal). It is not a gateway Subscriby integrates: the option, its explainer and the checkout card come from the connector, and a project whose connector declares no native payment never sees it. See Native payment methods.
Offline sales, gifting, influencer giveaways
Access Codes — no gateway at all, you generate codes and hand them out.
See Choosing a payment provider for a decision tree walkthrough.
Editing or removing a payment method
Edit
Update keys, rename, or toggle active. Click the method's row on the Payment Methods page, adjust the fields, save.
Deactivate
Flip Active off. Existing subscribers on this method keep their renewals; new signups won't see it on the checkout list.
Delete
Permanent. Existing subscriptions tied to this method are left without a gateway to bill from, and their next renewal will fail. Only delete methods that were mistakes or are truly retired.
Changing a provider's keys mid-flight can interrupt renewals for subscribers signed up under the old keys. When rotating credentials, coordinate closely with the provider's documentation — some providers keep legacy product IDs valid across key changes, others require a re-sync.
Frequently asked
Related
- Choosing a payment provider — decision guide.
- Subscription plans — where payment methods and plans come together.
- Transaction fees — how Subscriby charges on top of gateway fees.
How is this guide?
Last updated on