MMNWEB charges through your gateway account — and each provider connects in its own way. The most important difference in this section: with Cielo you register credentials in the system; with Stripe and Mercado Pago you never hand over any keys — the connection happens through authorization (OAuth).
| Cielo | Stripe | Mercado Pago | |
|---|---|---|---|
| Connection model | Customer registers credentials | OAuth (Connect Standard) | OAuth (marketplace) |
| Do you hand over keys? | Yes (your Cielo store's) | Never | Never |
| What MMNWEB stores | the merchant's credentials | only the acct_… identifier | access_token + refresh_token (encrypted) |
| Native split | — | application_fee_amount | application_fee |
| Typical use | cards (store) | cards | PIX |
With every split-enabled provider, the charge happens on your account and the platform fee is separated by the gateway's own native mechanism. This is not an accounting detail: it's what keeps the operation outside the regulatory requirements that apply to anyone holding third-party funds — the payment settles directly to you, with no intermediary in the money flow.
Cielo — which credential works with which version (Webservice 1.5 × API 3.0) and why the other version's won't work.
Stripe — how to connect your account without sending any keys, and what "account ready to sell" means.
Mercado Pago — OAuth, credential types, and the 6-month token deadline nobody warns you about.
Want to see checkout charging through your gateway?