Start with a payment link
For a published product, this is enough to create a hosted payment link:productId identifies a product with a published version. slug is your
tenant’s checkout slug, not the provider name.
Follow the quickstart to create a sandbox and a published
product before running this example.
How the money arrives
In Brazil (you and the buyer in Brazil), a Pix or card (single payment) charge lands on your own receiving account at the payment provider, opened by Infi once its team approves your registration. Both methods are in test environment. You do not bring a provider key: registration starts from the dashboard. Outside Brazil (in beta, with a waiting list): Infi UK Ltd is the merchant of record for the buyer abroad. It charges the card, works out the sales tax and sends the receipt; your share is paid every 15 days in dollars, euros or pounds into an international account in your name, or in reais if you prefer. Crypto withdrawal is on the roadmap. Boleto, installments (2× to 12×) and Brazilian NFS-e are coming soon. The fee per charge depends on the method. The schedule is in going to production. Sandbox sales use the payment provider’s test environment. Billing, subscriptions, metering, credits and checkout use the same underlying infrastructure. Infi has its own financial ledger; a provider is an execution adapter, not the financial model of your application.Early access
The Stripe-compatible SDK is in Early access. Compatibility is being finalized; do not assume full Stripe API parity or automatic migration. Contact us to confirm the available flows before integrating.Choose your next step
- Quickstart: sandbox, key and your first payment link.
- TypeScript SDK: install and use the existing SDK.
- HTTP API: authentication, requests and route reference.
- Webhooks: verify events and track deliveries.