A payments stack,
not a checkout button.

Every transaction Centrobill touches moves through a decisioning engine before it reaches an acquirer, so a decline isn't the end of the story, it's a signal to try the next best path. Orchestration evaluates card type, issuing bank, customer location, and each acquirer's live performance, then routes the transaction down the path most likely to approve. That smart routing runs through Centrobill MAX.

When the first attempt fails, decline cascading automatically retries it through a backup acquirer instead of letting the sale disappear. Underneath all of it sits BIN optimization, which learns which banks approve which kinds of transactions and adjusts routing continuously, and real-time velocity rules that keep every account within the thresholds acquirers and card schemes actually enforce.

A single acquiring relationship is a single point of failure. Centrobill maintains direct acquiring relationships across five regions, with 100+ currencies and cards plus local payment methods per market, so a business processing internationally isn't routing every transaction through one bank in one country.

That matters twice over for the businesses we serve. It improves approval rates because local acquirers approve local transactions more readily than a foreign one does, and it builds in the redundancy that protects a merchant when one relationship changes overnight.

A merchant identification number is what an acquiring bank assigns to identify a business's transactions, and relying on just one means every transaction, every dispute, and every regulatory threshold funnels through a single account. Centrobill gives merchants access to multiple MIDs, with volume distributed automatically across them so no single account absorbs more volume or risk than it should.

We monitor account health continuously, so a reserve increase, a rising chargeback ratio, or an approaching threshold gets caught and addressed before it becomes an account closure.

Subscription businesses lose revenue two ways: customers who cancel on purpose, and payments that fail by accident. Centrobill's billing engine handles trials, upgrades, downgrades, and dunning automatically, and pairs that with smart retry logic that reattempts a failed payment at the moment it's statistically most likely to succeed, rather than on a fixed schedule that ignores why the card declined in the first place.

Centrobill MAX's Rebill Optimizer routes failed recurring transactions to alternate acquirers before writing the payment off, which is often the difference between a saved subscription and lost customer.

Chargebacks cost more than the disputed transaction. Enough of them and an acquirer starts questioning the whole account. Centrobill combines real-time transaction scoring, 3D Secure authentication, and chargeback alert integrations, including Ethoca and Verifi, to catch disputes before they escalate, plus representment support for the ones that do happen anyway.

The goal isn't zero fraud, since that's not achievable for any business at scale. It's keeping chargeback ratios inside the thresholds that keep an account in good standing with its acquirers and the card schemes.

One REST API surface covers checkout, tokenization, recurring billing, smart routing, payment recovery, and reporting, with SDKs for Node, Python, PHP, and Go. Sandbox parity with production means what works in testing works in production without surprises.

Webhooks are signed, writes are idempotent, and retries use exponential backoff, the details that matter to whoever actually has to build and maintain the integration, not just demo it.

Full developer documentation