What gets in the way
Your invoices are global. Your payments are not.
01
Your billing vendor decides your payment coverage
A method your acquirer already supports can still be missing from your billing engine's connector, so your customers never see it.
02
One acquirer for every market
Card-heavy markets often approve better with a second or a local acquirer, yet every invoice goes to the same one.
03
Every new market is an engineering project
Each new acquirer or local method means another integration, another checkout flow and another reconciliation job for your team.
How Altruon fits
Your billing engine issues the invoice. Altruon collects it.
Plans, seats and usage stay where they are. Altruon adds the checkout, acquirers and methods around them and writes every result back to the invoice.
Local methods
Markets your billing engine can't reach yet
Add a local acquirer or method per market. Your billing engine keeps issuing the invoices, and Altruon collects them where your customers pay.
India INR
UPI via dLocal, with recurring mandates and a pre-debit notice sent before each debit.
South Korea KRW
KakaoPay via Checkout.com, the country's leading mobile wallet, alongside cards.
Europe and UK EUR · GBP · SEK
SEPA Direct Debit via Trustly, Bacs via Trustly and Autogiro with Trustly.
Japan JPY
Local card acquiring via Checkout.com, Adyen and dLocal.
Usage-based invoices are collected like any other invoice your billing engine issues.






