The main API

Core API

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

The following is the list of the following:https://api.iopay.com.br/api/
AuthenticationBearer token
The following table is inserted:JSON

Overview

The API Base focuses on the main stream of payments: 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 on new journeys.

Transactions

Create and track payments.

Pix, card and boleto enter the same transaction cycle as API.

Tokenization

Less exposure.

Associate payment instruments with customer for recurring journeys and repurchase.

Authentication

Send a valid token to the header Authorization and use JSON in the integration payloads.

Example of authentication
curl --request GET \
  --url https://api.iopay.com.br/api/v1/customer/get/:customerId \
  --header 'Authorization: Bearer seu_token' \
  --header 'Content-Type: application/json'
Ambientes. Separate development/testing and production credentials. Do not display tokens in the frontend, repository or public logs.

Basic flow

Access to the InternetAutentique.

Choose the environment and send the Bearer token.

The following is the list of the following:Create the buyer.

You get a reusable ID for the trip.

03 · TransactionHe's running the payroll.

Create Pix, card or boleto associated with customer.

04 · StateSincronize.

Use ID and webhooks to keep up with changes.

Creating a customer

POST /api/v1/customer/new
curl --request POST \
  --url https://api.iopay.com.br/api/customer/new \
  --header 'Authorization: Bearer seu_token' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Maria Oliveira",
    "email": "[email protected]",
    "document": "12345678909",
    "phone_number": "+5511999999999"
  }'

Creating Pix transaction

POST /api/v1/transaction/new/:CustomerID
curl --request POST \
  --url https://api.iopay.com.br/api/v1/transaction/new/:CustomerID \
  --header 'Authorization: Bearer seu_token' \
  --header 'Content-Type: application/json' \
  --data '{
    "amount": 12990,
    "payment_method": "pix",
    "reference_id": "order_102938"
  }'
Examples of integration. Keep routes, fields and examples in sync with current implementation before posting changes.

Features

AreaUseNext reference
CustomersRegister, check and identity of the payer.Core API
Card / tokenizationInstruments associated with the customer and buy back.Core API
TransactionsCreation, consultation, capture and cancellation.Core API
PixCharge, identification and status tracking.The basic API + webhooks
BoletoCreation and cycle of bank collection.The basic API + webhooks
SellersPlatform/marketplace participants.Sellers API →
SplitDistribution between participants.Split API