Online card acquiring
Every declined card was a customer who already said yes.
Visa and Mastercard acceptance for online businesses, run with the operational discipline that decides whether a payment stack pays for itself or quietly costs you money.
What you get
Acceptance, and the work that keeps it working
Anyone can connect you to a card network. The difference shows up three months later, in the numbers nobody demoed.
Card acceptance
Visa and Mastercard for card-not-present traffic, across one-off and recurring purchases.
Approval monitoring
Decline reasons broken out and reviewed, so drops get diagnosed rather than absorbed.
Dispute handling
Chargebacks and representments handled by someone whose name you know.
Settlement reporting
Files and views built for month-end close, not for a screenshot in a pitch deck.
Approval rates
Where the money actually goes missing
Roughly two thirds of a typical decline profile has nothing to do with the customer's balance. It's friction, timing and data — all three of which are somebody's job.
Authentication that finishes
3-D Secure 2 with exemption handling where it applies, so low-risk buyers aren't sent through a challenge they'll abandon on a phone.
Retries that respect the issuer
Soft declines get a second attempt on a schedule issuers tolerate. Retrying badly is worse than not retrying at all.
Clean data at authorisation
Descriptors, MCC, address and currency sent correctly the first time. Unglamorous, and consistently worth more than it sounds.
Recurring revenue
Subscriptions fail quietly. We'd rather they failed loudly.
A subscription business doesn't lose customers at checkout — it loses them at renewal, one expired card at a time. Involuntary churn is a payments problem long before it becomes a retention problem.
- Card-on-file and credential-on-file flows set up correctly from the start
- Network updates so an expired card doesn't end the relationship
- Dunning windows you control, not ones we impose
- Renewal failure reporting that names the reason, not just the count
Where subscriptions leak
Renewal
Settlement and reporting
Numbers your finance team can close on
Reconciliation is where most payment relationships turn sour. Not because the money is wrong, but because nobody can prove it's right without a week of spreadsheet work.
- Settlement on a T+3 rhythm, with the reserve terms stated up front
- Transaction-level detail that ties back to your order IDs
- Fees itemised per transaction rather than netted into a lump sum
- Exports that go straight into your accounting system
Settlement cycle
0
Fit
We'd rather say no early than sorry later
Acquiring relationships end badly when nobody was honest at the start. Here is roughly where we sit today.
A good fit
- Registered online businesses with a trading history we can review
- Clear delivery, refund and support processes
- Sectors that sit inside our current licensing scope
- Teams that can supply proper documentation without a fight
Not a fit today
- Models where delivery of goods or services can't be evidenced
- Aggressive rebilling or unclear subscription terms
- Sectors outside the scope of our current authorisation
- Anyone looking to go live before onboarding is finished
Onboarding
What happens between the first call and the first authorisation
Qualification
Volumes, markets, business model. We tell you at this stage whether it's worth continuing.
KYB review
Company documents, ownership, and how your business actually operates. Thorough, and finite.
Integration and live
Sandbox first, then production with monitoring in place from the first transaction.
Questions
The ones people actually ask
How long does onboarding take?
It depends almost entirely on how quickly documentation arrives. A prepared business with clean corporate records moves fast; one still assembling its ownership chain does not. We tell you what we need in one list rather than in five emails.
What does pricing look like?
Pricing depends on your volumes, markets and risk profile, so we quote after we understand the business rather than before. What we commit to is a structure you can read once and explain to your CFO without a decoder ring.
Do you hold a rolling reserve?
Sometimes, depending on the model and the risk profile. Where a reserve applies, the percentage and release period are stated in the agreement before you sign, not discovered afterwards.
Can we keep our existing gateway?
In many cases yes. If you already have an integration that works, replacing it should be your decision rather than a condition of the relationship.
What happens when a chargeback comes in?
You get notified with the reason code and the evidence window, and a named person on our side works the case with you. Disputes are not a portal you shout into.
Get started
Send us your decline report. We'll tell you what's fixable.
Volumes, markets, timeline — and if you have it, a month of authorisation data. You'll get a straight answer about fit and a realistic view of what changes.