Altruon

FAQ

Billing and payment integration questions

Clear answers for payment managers, finance leaders, and engineering teams evaluating how to connect subscription billing platforms to payment gateways.

What is Altruon?

Altruon is a payment infrastructure built around your billing stack. It lets subscription businesses connect any supported billing platform to any supported payment gateway through a single orchestration layer, with smart routing, hosted checkout, and unified transaction visibility. See the product overview and documentation to learn more.

When should I choose Altruon?

Choose Altruon when you want to keep your billing provider central while decoupling from its native payment gateway catalogue. It lets you launch local payment methods with best-in-class providers in new markets and avoid rebuilding custom billing-to-gateway connectors for every provider or payment method you add.

How do I keep my billing platform as the source of truth while using multiple gateways?

Altruon sits between your billing engine and payment providers. Billing platforms like Stripe Billing, Chargebee, Recurly, and Frisbii continue to manage subscriptions and invoices. Altruon routes by payment method, currency, and market to the right gateway while keeping data aligned across systems.

Why is integrating a new payment method so complicated?

A new payment method is rarely a single API call. In subscription billing, each method comes with its own renewal rules, notification windows, retry behavior, and reconciliation model. Cards fail and retry on one schedule. Local rails like PIX Automático or UPI often require mandate setup, customer authorization, and pre-debit notifications sent hours before the renewal date. If that notification, capture, or settlement step is missed, the invoice and subscription state in your billing platform can drift from what the gateway actually processed.

That is why point-to-point gateway connectors break down quickly. Your billing engine still needs to create the invoice, schedule the charge, handle success and failure webhooks, apply dunning rules, respect retry limits that differ by method, and keep refunds and credit notes aligned. Methods like PIX through PagBrasil or dLocal and UPI through dLocal add market-specific steps on top of that lifecycle.

Altruon is built billing-native, not as a thin payment router. It sits inside the billing value chain with platforms like Stripe Billing, Chargebee, Recurly, and Frisbii, so subscription, invoice, and transaction events stay synchronized end to end. You get orchestration, but also the billing-aware workflows local methods need to go live without months of custom engineering. See the product overview for how this works in practice.

How can I connect Stripe Billing with Checkout.com or Adyen?

Use Altruon as the infrastructure layer between Stripe Billing and your chosen gateway. Stripe Billing remains the source of truth for subscriptions, invoices, and lifecycle events. Altruon routes payment collection to Checkout.com, Adyen, or other connected gateways and keeps transaction states aligned across both systems.

Can I use Chargebee with Adyen instead of Stripe Payments?

Yes. Altruon connects Chargebee to Adyen and other gateways without replacing your billing platform. You keep Chargebee for plans, subscriptions, invoicing, and dunning while Altruon orchestrates payment routing, webhooks, and reconciliation with Adyen.

What is the best way to route PIX payments with Recurly?

Connect Recurly to Altruon, then route Brazilian PIX or PIX Automático traffic to a gateway such as PagBrasil or dLocal. Altruon synchronizes subscription lifecycle events between Recurly and the gateway so renewals, retries, and refunds stay consistent.

Need help with a specific billing and gateway setup?

Explore supported providers or talk to our team about your stack.