Choose how to pay
Buyers can pay from an InFlow balance, charge a supported card, or make a supported blockchain payment. Sellers choose which options to accept for their products and services. This section explains what each option provides and what both sides need to set up.
MPP and x402 describe how applications request and submit payments. They do not identify the source of the money by themselves. For example, either protocol can carry a payment from an InFlow balance or a linked card.
Compare the payment options
Start with how the buyer wants to fund the purchase, then check the seller requirements. Each guide below covers the corresponding dashboard setup and application configuration.
| Payment option | Buyer setup | Seller setup |
|---|---|---|
| InFlow balance | Fund an InFlow account in the purchase currency. Payments spend from that balance through MPP or x402. | Use an InFlow Seller account and offer balance payments. Proceeds are credited to the seller’s InFlow balance, less applicable fees. |
| Linked cards | Save a supported card in InFlow and select instrument payments through MPP or x402. The purchase charges the card in USD. | Connect a Stripe account that can accept payments, then offer instrument payments. |
| Stripe payments | Use a compatible external buyer that supplies a Stripe Shared Payment Token for a one-time USD purchase. | Connect a payment-enabled Stripe account, create its Stripe Profile, and offer the MPP Stripe method. |
| Visa CARD | Link an eligible Visa card to InFlow and verify a spending allowance. Use MPP CARD for a one-time USD purchase. | Connect a payment-enabled Stripe account, complete Seller business details, and offer the MPP CARD method. |
All seller integrations above use an InFlow Seller account. Complete the setup in the same environment as your application. Accounts and environments explains account roles, API keys, and Sandbox testing.
Distinguish the card payment methods
A seller’s Stripe connection can receive several kinds of card payments, but the buyer setup differs. Choose the guide that matches how the buyer provides permission to use the card:
- Linked cards: InFlow charges a card saved in the buyer’s account. This is called an instrument payment and does not require a Visa CARD allowance.
- Stripe payments: A compatible external wallet supplies a Shared Payment Token authorizing card use for the purchase. The InFlow buyer SDK does not create this token.
- Visa CARD: The buyer’s linked Visa card needs a verified allowance. InFlow uses its Visa integration to obtain an encrypted payment credential for the purchase.
An ordinary linked-card payment is not automatically a CARD payment. Likewise, the Stripe Profile required for MPP Stripe is separate from CARD’s merchant details. Follow the selected method’s guide rather than treating all card payments as one setup.
Know when a blockchain is involved
Funding an InFlow balance can involve a blockchain deposit. Spending that balance transfers funds within InFlow; each purchase does not require another on-chain payment. USD card purchases also do not require the buyer to choose a blockchain or hold a payment token.
Direct on-chain payments are another option: x402 uses the exact scheme, and MPP supports the Tempo method. These payments identify a blockchain network and token. A buyer paying from an external wallet must hold the accepted token on the required network.
Networks and currencies lists supported combinations, Sandbox networks, and payment-token faucets. It is a reference for configuring these choices, not an additional payment method.
Match the seller’s offer to the buyer
Sellers can offer more than one supported payment option. For example, a report could accept an InFlow balance payment and a linked-card payment. The buyer selects one advertised option for the purchase; offering both does not require paying twice.
Choose options your intended buyers can use, then configure the corresponding MPP or x402 integration. Accept both protocols explains how one resource can accept either protocol.
Buyers must support the advertised payment method and meet its funding requirements. A saved card cannot pay a balance-only offer, and a funded balance cannot pay a Stripe-only offer. Choose payment options explains selection and spending limits.
Funding and permission are separate. InFlow buyer payments still follow the applicable approvals and allowances flow. Enough funds or a saved card does not by itself authorize a purchase.
Continue your integration
Accept a payment
Build a seller endpoint and test a balance-funded purchase before adding the payment options you need.
Make a payment
Configure a buyer application and complete a controlled Sandbox purchase.
Networks and currencies
Find supported currencies, blockchain networks, and test funding sources.
