One API for every payment.

Infi connects your application to payments through one API. Every charge goes through the payment provider on your receiving account. Your application works with Infi's payment and event model.

Start with a payment link

For a published product, this is enough to create a hosted payment link:

import { Infi } from "@beinfi/sdk";
 
const infi = new Infi({
  secretKey: process.env.INFI_SECRET_KEY!
});
 
const { url } = await infi.links.create(productId, {
  slug: "acme"
});

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

Charges go through Infi. Pix and card go through the payment provider, and each sale is split on the spot: your share goes to your recipient and Infi's fee to Infi's. You sell before verification (KYC); it is only required to withdraw.

Accounts of your own at other providers (Stripe, Asaas, Efí, Woovi, Adyen) can be connected, but they only keep data: nothing is charged, refunded or withdrawn through them.

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.

The blog and the legal documents are currently available in Portuguese only.