What gets in the way
Local methods stall at the billing connector
01
Your billing vendor's connector decides what you can offer
You can only sell with the methods your billing engine's payment connectors support. If a market's method is missing, you wait for the vendor to ship it.
02
Recurring local methods come with mandates and scheme rules
PIX Automático, UPI and direct debit need a mandate at signup, notices before a debit and retry rules of their own. Card logic does not carry over.
03
Each market is a new integration
A new acquirer per country means a new API, new webhooks and a new reconciliation, repeated for every launch.
How Altruon fits
One integration for every market you add
Global coverage
Local payment methods where your subscribers pay
Each method runs on an acquirer you contract with, and every result is written back to the invoice in your billing engine.
Brazil BRL
Recurring PIX and local card acquiring through dLocal and PagBrasil.
India INR
UPI through dLocal, including recurring mandates, with pre-debit notices handled for you.
South Korea KRW
KakaoPay in KRW through Checkout.com, alongside cards.
Europe and UK EUR · GBP · SEK
SEPA Direct Debit and Bacs via Trustly, Autogiro with Trustly, and card acquiring through Adyen and Checkout.com.
Japan JPY
Local card acquiring through Checkout.com, Adyen and dLocal.
Recurring by design
Local methods are set up for renewals from the first checkout, not bolted on after.
Mandates at checkout
The subscriber approves the PIX Automático, UPI or direct debit mandate in the checkout session, including free-trial setups that charge nothing up front.
Pre-debit notices
Before each PIX Automático and UPI debit, Altruon sends the pre-debit notice and emits subscription.pre_debit_notification.sent.
Method-aware retries
PIX and PIX Automático retry on platform schedules, while UPI and direct debit follow their own scheme rules. Every retry is claimed once, so it never charges twice.



