Worldpay processes a recurring charge the same way it processes any other card transaction. It doesn't run a native subscription product that tracks plans, prorates upgrades, or retries a failed renewal on its own, so a business billing on a schedule through Worldpay has to build or buy that logic separately. We build the subscription logic Worldpay doesn't provide: the schedule, the retry, and the sync back into billing and accounting once a charge succeeds or fails.
Worldpay supports recurring and tokenized transactions, meaning a card can be securely stored as a token and charged again later without asking the customer to re-enter their details. What it does not do on its own is decide when that charge should happen, what to do if it fails, or how a plan change like an upgrade or downgrade should be prorated.
That logic usually lives in a separate billing system, whether that is a dedicated subscription platform, a custom scheduler a business built itself, or in some setups, little more than a recurring calendar reminder for someone to run a charge manually.
A missed renewal date, a retry that never happens, or a cancelled subscription that keeps getting charged anyway are the three most common failure points once recurring billing depends on a person remembering to run it. None of them show up until a customer notices, usually as a complaint, not a quiet internal flag.
Keeping a subscription's status in sync with accounting or a CRM is its own separate gap. A card that fails and eventually gets fixed, a plan that gets upgraded mid-cycle, none of that updates anywhere else unless something's built to push it there.
A declined recurring charge can trigger an automatic retry on its own schedule and a customer notice if it keeps failing, instead of quietly dropping the renewal until someone notices revenue is off.
When a plan changes, cancels, or a card gets updated, that status reaches your accounting system and CRM automatically, so finance isn't reconciling against a billing spreadsheet someone updates by hand.
A calendar reminder, a manual charge run, a spreadsheet of who's due: tell us what it actually looks like today and we'll look at what of it can run on its own.
Worldpay will process the charge; it won't decide when to run it, retry it, or tell your other systems what happened. Recurring billing is just the gap this page covers. n-frames builds the same kind of missing logic anywhere a tool processes something but stops short of managing the process around it.
Let's talk →Worldpay supports recurring and tokenized card transactions, so a card can be charged again later without the customer re-entering it. It doesn't include a built-in subscription product that manages plans, proration, or retry scheduling the way a dedicated billing platform does; that logic has to come from elsewhere.
Worldpay reports the decline back to whatever system initiated the charge. What happens next, a retry, a dunning email, suspending the account, isn't handled by Worldpay itself. It depends entirely on the billing logic built around the integration.
Yes. A dedicated subscription or billing platform can be built to use Worldpay as the underlying processor for the actual card charge, while the subscription platform, or custom logic standing in for one, manages plans, schedules, and retries.
Worldpay's API supports tokenizing a card so it can be charged again without re-entering the details, and the actual recurring charge gets triggered by whatever system holds the billing schedule, whether that's a subscription platform, your own backend, or, for smaller volumes, someone manually running it on a calendar.