InfinitePay data API: NSU captures, Pix and wallets
InfinitePay Tap, Conta, Cartão is CloudWalk's Brazilian merchant app (on-device InfinitePay) that turns an Android 10+ NFC phone into a free InfiniteTap card reader and pairs it with a PF/PJ digital account, Pix at zero fee, payment links, billing, POS inventory and a no-annual-fee smart card. Shopkeepers, MEI, CNPJ firms and delivery riders accept debit, credit and wallets by tap — sales over R$200 ask for the customer's PIN — then choose to receive in the moment or in one business day, with rates that already bundle prepayment. Team Mode installs a sales-only client on as many phones as the shop needs; the same login generates installment links up to 12× for WhatsApp and DMs, issues Pix or card cobranças, runs an online catalog, compares MDR in-app, and can open an instant loan paid from sales. The smart card pays 1.5% cashback and sits in the phone wallets. Published for Brazil only (CloudWalk Payment Institution CNPJ 18.189.547/0001-42, Rua Eugênio de Medeiros 303, São Paulo), it holds a 4.87 rating across 1.04 million Google Play reviews, 10 million-plus installs and a #7 free-finance slot, sitting next to Stone, PagBank, Cielo, Mercado Pago Point, SumUp and Ton for the same SoftPOS-plus-conta slot.
CNPJ document_number lands on the same signed-in merchant session as wallets, cardholder and products_allowed, with identity_validation status and account_kind (MerchantPj versus a CPF seller) deciding which till is a company. SoftPOS and delivery taps then key each card capture by nsu; Pix outflows are tracked beside current_tpv, while active_loan and card credit_statement rows reuse the same handle.
ERP and courier stacks reconcile those receipts against receivables reference_id and BACEN validation state so a shop that takes NFC on Android 10, Pix at zero fee and a no-annual-fee card can close the day without a separate acquirer file. openData Studio turns that merchant session into callable open data.
Screenshots
API surface
The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.
Check password credentials
POST
/v1/merchants/sign-inopendataConfirms the merchant password and returns the jwt_token plus payload.message profile used as Bearer on later first-party calls.
Auth: Unauthenticated. CPF/CNPJ handle plus password. On success a jwt_token is returned and sent as a Bearer token on later calls.
- handle
- password
- device_authenticated
- jwt_token
- payload.message
- id
- has_password
- is_company
POST /v1/merchants/sign-in HTTP/1.1 Content-Type: application/json { "handle": "loja.centro", "password": "********", "device_authenticated": true }{ "jwt_token": "<jwt_token>", "payload": { "message": { "id": 88412019, "handle": "loja.centro", "has_password": true, "is_company": true } } }List active auth sessions
GET
/v1/merchants/me/devicesopendataLists live devices on the merchant login so Team Mode phones and the owner's till can be revoked from the security settings.
Auth: Authorization: Bearer jwt_token from password or QR sign-in.
- sessions
- id
- handle
- device_authenticated
- ip_address
- received_at
GET /v1/merchants/me/devices HTTP/1.1 Authorization: Bearer <jwt_token>{ "sessions": [ { "id": "sess-1a2b", "handle": "loja.centro", "device_authenticated": true, "ip_address": "203.0.113.10", "received_at": "2026-10-17T11:02:01Z" } ] }Current merchant session
GET
/v1/merchants/me/profileopenfinanceLoads the signed-in PF/PJ merchant — wallets, cardholder, CNPJ document_number, products_allowed and legal_representative — for the home conta and till.
Auth: Authorization: Bearer jwt_token from the password or QR sign-in.
- include
- payload.message
- id
- handle
- user_handle
- phone_number
- is_company
- avatar_url
- cover_url
- products_allowed
- identity_validation
- wallets
- currency
- amount
- cardholder
- merchant
- document_number
- legal_representative
GET /v1/merchants/me/profile?include=wallets,cardholder,merchant HTTP/1.1 Authorization: Bearer <jwt_token>{ "payload": { "message": { "id": 88412019, "handle": "loja.centro", "user_handle": "loja.centro", "phone_number": "11987654321", "is_company": true, "avatar_url": "https://static.example.com/avatars/88412019.png", "cover_url": "https://static.example.com/covers/88412019.png", "products_allowed": ["tap", "pix", "payment_links", "card"], "identity_validation": {"status": "approved"}, "wallets": [{"id": "wal-brl", "currency": "BRL", "amount": "18450.20"}], "cardholder": {"name": "Ana Souza"}, "merchant": {"document_number": "12345678000195"}, "legal_representative": {"document_number": "12345678901"} } } }BACEN validation status
GET
/v1/merchants/me/compliance/statusosintReads BACEN / identity_validation status for the merchant so Pix, lending and card products unlock after KYC.
Auth: Authorization: Bearer jwt_token from password or QR sign-in.
- identity_validation
- status
- bacen_validations
- invalid_data
- document_number
GET /v1/merchants/me/compliance/status HTTP/1.1 Authorization: Bearer <jwt_token>{ "identity_validation": { "status": "approved" }, "bacen_validations": { "status": "approved", "invalid_data": false }, "document_number": "12345678000195" }Legal entity with merchant include
GET
/v1/entities/{entity_id}osintReturns the legal entity and nested merchant document_number, including account_kind MerchantPj versus PF, for CNPJ/CPF switching and select-account.
Auth: Authorization: Bearer jwt_token from password or QR sign-in.
- id
- account_kind
- handle
- user_id
- status
- roles
- merchant
- document_number
- accounts
GET /v1/entities/88412019?include=merchant HTTP/1.1 Authorization: Bearer <jwt_token>{ "id": 88412019, "account_kind": "MerchantPj", "handle": "loja.centro", "user_id": 88412019, "status": "active", "roles": ["owner"], "merchant": { "document_number": "12345678000195" }, "accounts": [ { "user_id": 88412019, "account_kind": "MerchantPj", "handle": "loja.centro", "status": "active", "roles": ["owner"] } ] }Capture InfiniteTap NFC sale
POST
/v1/payments/contactless/captureopenbankingAuthorizes an InfiniteTap contactless capture on an Android 10+ NFC phone and returns the nsu the sales screens key on.
Auth: Authorization: Bearer jwt_token with a payments-write scope.
- amount
- currency
- installments
- entry_mode
- handle
- nsu
- status
- instant_transactions
- transaction_info
- brand
POST /v1/payments/contactless/capture HTTP/1.1 Authorization: Bearer <jwt_token> Content-Type: application/json { "amount": "199.90", "currency": "BRL", "installments": 1, "entry_mode": "nfc", "handle": "loja.centro" }{ "nsu": "314159265", "status": "approved", "amount": "199.90", "currency": "BRL", "instant_transactions": true, "transaction_info": { "entry_mode": "nfc", "brand": "mastercard" } }Index captured sales
GET
/v1/sales/dailyopendataPages the merchant's captured volume (current_tpv) and per-nsu sales for the day, analytics and fees screens.
Auth: Authorization: Bearer jwt_token with a financial read scope.
- date
- handle
- current_tpv
- currency
- sales
- nsu
- amount
- status
- received_at
GET /v1/sales/daily?date=2026-10-17&handle=loja.centro HTTP/1.1 Authorization: Bearer <jwt_token>{ "current_tpv": "18450.20", "currency": "BRL", "sales": [ { "nsu": "314159265", "amount": "199.90", "status": "approved", "received_at": "2026-10-17T14:02:11Z" } ] }Sale receipt by NSU
GET
/v1/receipts/{nsu}openbankingReturns one captured sale by nsu for the receipt, chargeback and fees drill-down.
Auth: Authorization: Bearer jwt_token.
- nsu
- amount
- currency
- status
- handle
- transaction_info
- entry_mode
- brand
- received_at
GET /v1/receipts/314159265 HTTP/1.1 Authorization: Bearer <jwt_token>{ "nsu": "314159265", "amount": "199.90", "currency": "BRL", "status": "approved", "handle": "loja.centro", "transaction_info": { "entry_mode": "nfc", "brand": "mastercard" }, "received_at": "2026-10-17T14:02:11Z" }Pix cash-out
POST
/v1/transfers/pixopenbankingSends a Pix cash-out from the PF/PJ wallets on the merchant session, the zero-fee unlimited Pix rail advertised next to InfiniteTap.
Auth: Authorization: Bearer jwt_token. Requires identity_validation approved.
- amount
- currency
- handle
- pix_key
- status
- reference_id
- received_at
POST /v1/transfers/pix HTTP/1.1 Authorization: Bearer <jwt_token> Content-Type: application/json { "amount": "350.00", "currency": "BRL", "handle": "loja.centro", "pix_key": "[email protected]" }{ "status": "sent", "amount": "350.00", "currency": "BRL", "reference_id": "pix-9f21", "received_at": "2026-10-17T14:08:00Z" }Receivable by reference
GET
/v1/settlements/{reference_id}openfinanceReads one receivable (1-business-day prepayment or installment plan) keyed by reference_id for the recebimentos screens.
Auth: Authorization: Bearer jwt_token.
- reference_id
- nsu
- amount
- currency
- status
- receivables_details
- settle_in_days
- allow_payment_after_due_date
GET /v1/settlements/recv-8841 HTTP/1.1 Authorization: Bearer <jwt_token>{ "reference_id": "recv-8841", "nsu": "314159265", "amount": "199.90", "currency": "BRL", "status": "prepaid", "receivables_details": { "settle_in_days": 1, "allow_payment_after_due_date": false } }List issued cards
GET
/v1/cards/issuedopenfinanceLists the no-annual-fee smart card (1.5% cashback) and nested credit_statement rows for the Cartão Inteligente screens.
Auth: Authorization: Bearer jwt_token with a card-issuing scope.
- cards
- id
- cardholder
- products_allowed
- cashback_rate
- credit_statement
- amount
- currency
GET /v1/cards/issued HTTP/1.1 Authorization: Bearer <jwt_token>{ "cards": [ { "id": "crd-1", "cardholder": {"name": "Ana Souza"}, "products_allowed": ["virtual", "physical"], "cashback_rate": "0.015", "credit_statement": { "id": "stmt-10", "amount": "620.00", "currency": "BRL" } } ] }Sales-backed lending snapshot
GET
/v1/financing/instant-loanopenfinanceReads the instant loan (Empréstimo Inteligente) sized off captured current_tpv for the two-click in-app offer.
Auth: Authorization: Bearer jwt_token with a lending scope.
- handle
- account_kind
- current_tpv
- active_loan
- id
- amount
- currency
- status
GET /v1/financing/instant-loan HTTP/1.1 Authorization: Bearer <jwt_token>{ "handle": "loja.centro", "account_kind": "MerchantPj", "current_tpv": "18450.20", "active_loan": { "id": "loan-22", "amount": "5000.00", "currency": "BRL", "status": "open" } }
Data categories
- accounts
- kyc
- balances
- sales
- pix
- receivables
- cards
- lending
Where teams use this data
SoftPOS and delivery NSU reconciliation
A shop or dark-kitchen ERP pulls each InfiniteTap capture by nsu, matches amount and current_tpv to the courier's phone, and flags Team Mode tills that settled off-shift.
Pix cash-out versus wallet headroom
Treasury bots read wallets on the merchant session, send Pix cash-outs to suppliers, and stop the drain when identity_validation is still pending.
Receivables and MDR close
Finance stacks walk receivables by reference_id against the daily sales listing so 1-business-day prepayment and installment plans land in the same ledger as the till.
Sales-backed lending watch
A credit desk reads active_loan next to current_tpv and account_kind so a CNPJ merchant's instant loan is sized off captured volume, not a bureau file alone.
Frequently asked questions
What merchant fields does the signed-in session return?
GET /v1/merchants/me/profile returns wallets, cardholder, merchant.document_number, products_allowed, legal_representative, identity_validation, handle, is_company, phone_number and avatar_url once the sign-in JWT is attached.
How are InfiniteTap card sales identified?
Each capture is stored under nsu. GET /v1/sales/daily lists them for the day together with current_tpv; GET /v1/receipts/{nsu} returns the receipt the till, Team Mode phone or delivery rider just took, and receivables are keyed separately by reference_id.
Does the surface cover Pix and the digital account?
Yes. Wallets on the merchant profile hold the PF/PJ conta; POST /v1/transfers/pix sends Pix out; current_tpv is the captured volume the instant loan and cash-out limits sit against. Pix in on the till is the zero-fee sales rail advertised next to NFC.
How does InfinitePay authenticate merchants?
A password check at POST /v1/merchants/sign-in, or a QR sign-in from an already paired phone. The issued jwt_token is sent as a Bearer Authorization header on later first-party calls; GET /v1/merchants/me/devices lists live devices.
Apps similar to InfinitePay Tap, Conta, Cartão
- Ton: maquininha, tap e conta — Stone Pagamentos' merchant app for Brazilian MEI and small shops pairs a physical Ton card machine and TapTon NFC on the phone with a free Conta Ton, Pix on the till, payment links and a no-annual-fee card.
- Stone — Stone's TapStone turns an NFC phone into a card reader at the same rates as a Stone maquininha, sitting on a free Conta PJ with Pix, payment links, boletos and working-capital credit for larger Brazilian shops.
- PagBank — PagBank Tap On accepts contactless debit and credit on the phone at no hardware cost, next to Moderninha card machines, a free PF/PJ digital account and unlimited Pix for Brazilian merchants.
- Mercado Pago Point Tap — Mercado Pago Point Tap turns an Android 10+ NFC phone or iPhone 11+ into a contactless till, alongside Point card machines, Pix QR and a Mercado Pago digital account for in-person Brazilian sales.
- Cielo Tap — Cielo Tap, inside the Cielo Gestão app, takes contactless debit, credit and wallets on the phone with no monthly fee, next to Cielo Flash and Smart terminals and instant Pix.
- SumUp — SumUp Brazil lets sellers take contactless payments on the phone at no hardware cost, sell on a physical maquininha, and run free Pix through a SumUp digital account.
- Getnet Get Tap — Santander's Getnet Get Tap turns a smartphone into a till for debit, credit in up to 12x and Pix, with Get Mini and Smart terminals and a free Get Conta that settles in two business days.
Topics
- InfinitePay API
- InfiniteTap NSU
- CloudWalk merchant session
- Pix cash-out
- Brazilian SoftPOS
- CNPJ document_number
- wallets cardholder
- active_loan TPV
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.
- NDA + SOW on every engagement
- Delivery in 3–7 days
- Payment only after acceptance
- Work scoped to authorized use