Main API

Base API

Internal reference to organize the main IOPAY API flow: authentication, customers, payment instruments and transactions.

Base URLhttps://api.iopay.com.br/api
AuthenticationBearer token
FormatJSON

Overview

The Base API concentrates the main payment flow: authentication, customers, cards/tokenization and transactions. Sellers and Split have their own surfaces because they serve platform and distribution operations.

Customers

Reusable identity.

Create the buyer once and reuse the context in new journeys.

Transactions

Create and track payments.

Pix, cards and boleto enter the same transactional cycle of the API.

Tokenization

Less exposure.

Associate payment instruments with the customer for recurring and repurchase journeys.

Authentication

Send email, secret and io_seller_id to obtain the access_token. Use the returned token in the Authorization header of the next requests.

POST /auth/login
curl --request POST \
  --url https://api.iopay.com.br/api/auth/login \
  --header 'Content-Type: application/json' \
  --data '{
    "email": "your_email",
    "secret": "your_secret",
    "io_seller_id": "<IO_SELLER_ID>"
  }'
Bearer Token. Authentication returns access_token, token_type, token_scope and expires_in. Use the access token as Authorization: Bearer your_token in the next calls and don't expose credentials or tokens in the frontend, repository or public logs.

Basic flow

01 · AccessAuthenticate.

Send your credentials and get the access token.

02 · CustomerCreate the buyer.

Receive a reusable identifier for the journey.

03 · TransactionGenerate the payment.

Create Pix, card or boleto associated with the customer.

04 · StateSynchronize.

Use queries by ID and webhooks to track changes.

Create customer

POST /v1/customer/new
curl --request POST \
  --url https://api.iopay.com.br/api/v1/customer/new \
  --header 'Authorization: Bearer your_token' \
  --header 'Content-Type: application/json' \
  --data '{
    "first_name": "Maria",
    "last_name": "Oliveira",
    "customer_type": "person_natural",
    "email": "[email protected]",
    "taxpayer_id": "12345678909",
    "phone_number": "+5511999999999",
    "address": {
      "line1": "Av. Paulista, 1000",
      "line2": "Apto 101",
      "neighborhood": "Bela Vista",
      "city": "São Paulo",
      "state": "SP",
      "postal_code": "01310100",
      "country_code": "BR"
    }
  }'

Create Pix transaction

POST /v1/transaction/new/:CustomerID
curl --request POST \
  --url https://api.iopay.com.br/api/v1/transaction/new/:CustomerID \
  --header 'Authorization: Bearer your_token' \
  --header 'Content-Type: application/json' \
  --data '{
    "amount": 12990,
    "currency": "BRL",
    "description": "Order #102938",
    "statement_descriptor": "IOPAY STORE",
    "io_seller_id": "<IO_SELLER_ID>",
    "payment_type": "pix",
    "reference_id": "order_102938"
  }'
Integration examples. Keep routes, fields and examples in sync with the current implementation before publishing changes.

Resources

AreaUseNext reference
CustomersRegistration, queries and payer identity.Base API
Cards / tokenizationInstruments associated with the customer and repurchase.Base API
TransactionsCreation, query, capture and cancellation.Base API
PixCharging, identifiers and status tracking.Base API + Webhooks
BoletoCreation and lifecycle of bank slip charges.Base API + Webhooks
SellersPlatform / marketplace participants.Sellers API →
SplitDistribution among participants.Split API →