Recurring Payment: How to Set One Up and Actually Get Paid Globally

Recurring Payment: How to Set One Up and Actually Get Paid Globally

Get recurring payments right and revenue becomes predictable. Get them wrong and you spend your weekends chasing failed cards.

Cards expire and banks decline. Each failed renewal leaves you two jobs: recover the payment and decide what happens to access.

This guide covers what a recurring payment actually is, how to set one up, where founders lose money, and how to handle the part nobody warns you about: sales tax and VAT across dozens of countries.

TL;DR

• A recurring payment charges a customer automatically on a fixed schedule (weekly, monthly, annually) using stored card or bank details.
• You need three things to run one: a payment method on file, a billing schedule, and a system to retry failed charges.
• Failed charges can end subscriptions customers still want. Retries can recover temporary payment failures before they become involuntary churn.
• If you sell software across borders, your sales can create sales tax or VAT obligations in the buyer's country. Local rules, thresholds, and whether the buyer is a business determine what you owe. That is the part that turns a simple charge into a compliance project.
• A Merchant of Record like Creem runs the recurring payment, the retries, and the tax filings for you, so you keep building instead of bookkeeping.

What Is a Recurring Payment?

A recurring payment is an agreement where a customer authorizes you to charge them repeatedly without asking each time.

Your payment provider saves a reusable payment token or supported bank mandate, and your billing system uses it for scheduled charges.

Recurring charges can be fixed or variable.

Fixed recurring payments charge the same amount every cycle. Think Netflix Standard at $19.99 a month in the US. Predictable for you, predictable for the customer.

Variable recurring payments change based on usage. Think an AWS bill, a per-seat SaaS plan that grows with the team, or a usage-based API product billed per 1,000 calls. The schedule is fixed but the number moves.

Both rely on the same plumbing: a saved payment method, a tokenized card or mandate, and a scheduler that fires the charge. The customer sees a line on their statement. You see money in your account after settlement and payout. That is the whole promise.

How to Set Up a Recurring Payment

You have two real paths, and they are very different amounts of work.

Path 1: Wire it up yourself with a payment gateway

The DIY route starts with a payment gateway. At its core, a gateway processes payments: it charges the card and moves the money, and you reach it through an API.

Some gateways also sell optional subscription billing and retry tools. You configure those and connect them to your own business logic instead of coding every billing feature from scratch.

Here is what you still own on this path:

1. Show the terms, then collect the card. Get explicit agreement to the price or pricing basis, the billing interval, and the cancellation terms, then collect the card through the gateway's hosted fields or SDK.

   Never store raw card numbers yourself unless you enjoy PCI DSS audits.

2. Create a customer object and save the payment method through the gateway's setup flow for future off-session charges. The agreement from step 1 is what authorizes renewals, so keep a record of it with the payment method.

   On EEA and UK cards, Strong Customer Authentication (SCA) can ask the customer to authenticate at setup, and some later renewals can still need them to step in.

3. Define your products, plan tiers, and prices, including any free trial, then create a subscription that ties the customer to a price and a billing interval.

4. Handle webhooks. When a charge succeeds, fails, or a card expires, the gateway sends an event. You need code listening for every one of them.

5. Set up dunning. When a payment fails, retry on a smart schedule and email the customer to update their card, using the gateway's recovery tools if it has them or your own code if not.

6. Handle proration, upgrades, downgrades, cancellations, and refunds.

7. Then, and this is the big one, work out where your sales create sales tax or VAT obligations. That depends on the customer's location, what you sell, and whether they buy as a business, and every renewal needs the matching treatment.

This gives you total control. It also gives you a project that never really finishes, because tax rules change and cards keep failing.

Budget weeks of engineering for a custom billing and tax integration, then keep someone maintaining it after launch.

Billing add-ons leave you as the legal seller, so the tax obligations and the compliance upkeep stay with you.

Path 2: Use a Merchant of Record

The second path hands the whole stack to a Merchant of Record (MoR). You define the plan and the price. The MoR becomes the legal seller, runs the recurring payment, handles the retries, and files the taxes under its own registrations.

With Creem, setting up a recurring payment comes down to a short checklist:

1. Complete identity or business verification at onboarding.
2. Create the product and set its price and billing interval, from daily to yearly or a custom cadence.
3. Connect checkout with a hosted checkout link or the API.
4. Point Creem's subscription webhooks at your app so payment status grants or revokes access.
5. Decide what a customer keeps after cancelling, or after a failed payment that never resolves.
6. Run a checkout in test mode and confirm your app reacts to each subscription event before you go live.

Creem runs the subscription, the failed-payment recovery, and the tax compliance.

You still build and deliver the product. You are not wiring card-expiry handling at midnight.

Creem charges 3.9% + $0.40 per successful transaction, with no monthly or setup fee. That rate covers transaction-tax handling, invoicing, compliance, and dispute handling.

On a $100 sale, that leaves you $95.70.

What you buy with that fee is not having to become a tax filer. Creem collects and remits VAT, GST, and sales tax as merchant of record.

A bare gateway has a lower processing rate, but tax tooling, filings, and the engineering to run billing sit on top of it.

For most software and digital-product sellers, that is the better trade by a wide margin.

Check the plans at creem.io/pricing.

Renewal revenue reaches you on a set calendar. Creem processes payouts on the 1st and 15th of each month, and arrival depends on the payout method.

You need at least 50 USD or 50 EUR available to withdraw. Payments can be held for 7 to 12 days before they become available.

Bank payouts carry a transfer fee, plus partner FX if your bank currency differs. USDC payouts on Polygon cost 2% of payout volume.

Side by side, the two paths split the work like this:

Payment methods and currencies to offer for recurring billing

The method a buyer picks decides how you collect the next renewal. Some store a reusable token, some need a mandate, and some can't renew on their own.

Creem checkout accepts cards, PayPal, Apple Pay, Google Pay, and AliPay. Offer a method on a subscription plan only when it can carry renewals, or the customer ends up paying by hand.

Two currencies matter on every charge. Presentment currency is what the buyer sees and pays, and settlement currency is what lands in your account.

Creem charges buyers in their own currency.

On a gateway path, conversion and cross-border card fees come from your gateway's terms, and they come out of your margin.

Where Recurring Payments Leak Money

Failed renewals stay quiet until you look. A card can decline with no cancellation request, and if it never resolves, your access policy ends the subscription.

Involuntary churn is revenue you lose to failed payments, not to unhappy customers. Cards expire, banks flag charges as suspicious, balances run short. That is recurring revenue lost for a payment problem, not a product problem.

Three mechanisms can help address failed payments. Availability, configuration, and coverage depend on your provider.

Smart retries. Do not retry a failed card five minutes later five times in a row. Space attempts across days and align them with paydays. Retries can resolve temporary declines without customer action; the available retry controls depend on your provider.

Card account updater. Networks like Visa and Mastercard offer services that can refresh eligible stored-card details when a card is reissued. Where your provider supports these services, they can reduce expiry-driven failures. Availability, configuration, and coverage depend on your provider.

Dunning emails. A short, clear "your payment didn't go through, update your card here" email with a one-click link brings back customers who would otherwise vanish. Timing and tone matter more than volume.

If you build recurring payments yourself, you build or configure these recovery tools yourself.

Creem includes dunning in its subscription billing, so failed payments go through recovery instead of silent churn.

When a renewal fails, work through it in order:

1. Retry the charge on your recovery schedule.
2. If retries don't clear it, email the customer a link to update the payment method.
3. When the recovery window ends, apply your access policy: pause access or end the subscription.

The payment-update email can be this short: "Your Pro plan renewal didn't go through. Update your card in one click to keep your access."

Preventing chargebacks and voluntary cancellations

Some lost renewals start with a surprised customer rather than a failed card. A customer who doesn't recognize a charge can dispute it with their bank.

On the gateway path, a chargeback can cost you the payment plus a dispute fee. Five habits reduce the surprises that lead to disputes:

• Charge what you promised. Bill the amount and interval the customer agreed to, so the statement matches what they expect.
• Use a billing descriptor they recognize. The name on the card statement should match your product, so the charge doesn't look like fraud.
• Show the next charge date. Put it on the account page and in receipts, so customers know when to expect a renewal.
• Make cancelling easy to find. Let customers cancel from their account page rather than leaving a bank dispute as their easiest way out.
• Send renewal reminders. Remind customers before an annual renewal and before a trial converts to paid.

On a merchant of record, the provider fights the dispute. Creem carries chargeback liability and gives buyers a customer portal to manage payment methods and cancellations.

The Tax Trap Behind Every Cross-Border Recurring Payment

Here is the thing that turns your tidy monthly charge into tax work. When you sell software across borders, destination-based tax follows the customer's location.

What you owe depends on product taxability, whether the customer buys as a business or consumer, and local registration or nexus rules.

Say your monthly plan costs $20 before tax. For applicable consumer sales, Germany's standard VAT rate of 19% adds $3.80 per renewal, while the UK's standard VAT rate of 20% adds $4 to the same plan.

A non-UK business that is the legal seller must register for VAT from its first taxable UK sale for which it is liable for VAT, regardless of value.

Sell to a customer in Texas and state sales tax can apply once you cross an economic nexus threshold.

Each renewal needs the applicable tax treatment, so compliance continues after signup. Taxability follows the sale and the jurisdiction's rules.

Doing this yourself means owning the tax work wherever your sales create obligations:

• Register where local VAT or sales-tax rules require it.
• Charge the applicable rate and retain customer-location records.
• Validate business tax IDs and apply B2B reverse charge where its conditions are met.
• File and remit on the schedules required by each jurisdiction.

It is a full back-office function.

This is the single strongest reason software sellers use a merchant of record. Creem is the legal seller for covered transactions.

Creem calculates and collects transaction tax at checkout, remits it to the authority, and files the returns.

Your recurring payments keep running. Creem carries the transaction-tax registrations for those sales, while you retain your other business tax duties.

Recurring Payment vs Subscription vs Installment

These terms get mixed up, so here is the clean version.

A recurring payment is the mechanism: an automatic charge on a schedule.

A subscription is a business model built on recurring payments, where ongoing access to a product is exchanged for ongoing charges.

An installment plan is a fixed number of recurring payments that pay off a single purchase, like a $600 course split into 6 payments of $100. Once the total is paid, the charges stop.

All three run on the same payment rails. The recurring payment does the charging, and the other two describe what those charges pay for.

A subscription can bill a fixed amount each cycle or a variable one. An API product that charges for the calls used each month is still a subscription.

Choosing a Recurring Payment Provider: Checklist

Three kinds of provider can sit behind a recurring charge, and each one leaves different work on your desk.

• Processor: moves the card charge. You stay the legal seller, so tax, invoices and disputes stay with you.
• Billing tool: runs plans, renewals and retries on top of a processor. Tax and chargebacks still sit with you.
• Merchant of record: becomes the legal seller, so it collects and remits VAT and sales tax and handles chargebacks. You still build, deliver and support the product.

Before you commit, check each of these with the provider:

• PCI scope: find out whether card data ever touches your servers. A hosted or embedded checkout keeps it off them and shrinks your compliance work.
• Billing setup: check which intervals, trials, seat counts and usage meters you can configure without writing your own billing logic.
• Methods and currencies: list the cards, wallets and local methods your buyers use, then confirm each can carry a repeat charge in the buyer's currency.
• Failed-payment recovery: ask which retries, card updates and dunning emails run by default, and which ones you would have to build.
• Tax responsibility: ask who the legal seller is. If it is you, you register, collect, file and remit wherever you owe tax.
• Payout availability: ask when a successful charge becomes money you can withdraw, including any risk holds and minimum balances.
• Fraud screening: check who screens risky payments and who pays when a fraudulent charge turns into a chargeback.
• Identity and business verification: expect to verify yourself or your company before live payments switch on, and ask how long review takes.

Then compare the total cost instead of the headline rate. Add processing and FX fees to the engineering hours for billing and recovery, plus tax registrations and filings if you are the seller.

FAQ

How do I set up a recurring payment for my business?

Set up recurring payments by creating a billing plan, getting customer authorization, and connecting checkout to your product's subscription status.

With a processor, you configure billing and keep the seller obligations.

With Creem, set the price and interval and connect checkout. Creem runs recurring charges, recovery, and transaction taxes for covered sales.

What is the difference between a recurring payment and a subscription?

A recurring payment is the automatic charge itself. A subscription is a business model that sells ongoing access.

Paid subscriptions commonly use recurring payments. Installment plans use recurring payments too, so the charging mechanism extends beyond subscriptions.

Why do recurring payments fail?

Recurring payments fail because of expired cards, insufficient funds, or bank fraud flags. These failures account for a large slice of subscription churn.

Retries address temporary declines, while supported account-updater services refresh eligible stored-card details. Dunning emails ask customers to resolve payment problems, such as replacing a card.

Do I have to charge tax on recurring payments?

Usually yes, and in the customer's country. The product, customer location and business status, and registration or nexus rules determine whether you must charge tax.

Apply that tax treatment to each renewal. When Creem is the legal seller, Creem calculates, collects, files, and remits transaction taxes.

Is a payment gateway enough to run recurring payments?

No, basic gateway processing alone does not manage subscriptions. Optional billing and recovery services handle those features when configured.

You still integrate your product and maintain the setup. Payment and billing software leave legal-seller and transaction-tax obligations with you.

A merchant of record such as Creem takes the legal-seller role and handles billing and transaction taxes for covered sales. Choose based on how much of that stack you want to own.

Stop Babysitting Your Billing

A recurring payment should be the most boring part of your business.

Money arrives on schedule, failed cards get retried automatically, and the taxman gets paid without you filing a VAT or sales-tax return.

That is exactly what Creem does. As your Merchant of Record, Creem runs the recurring payments and the recovery on failed charges.

It also collects, files and remits VAT, GST, and sales tax on every sale where it is the legal seller.

Seats, usage meters, and prepaid credits match how your product charges. Creem takes chargeback liability, and buyers manage cards and cancellations in the customer portal.

You set the price and build the product. Creem handles getting paid.

Start selling with Creem.