Create Open Finance Enrollment
POST/open-finance/enrollments
Create a new Open Finance enrollment.
Request
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
- application/json
Body
required
Client redirect URL.
Open Finance participant id.
Client logged user document. In case of the user is a business entity, it is the document of the business entity representative.
Client logged user document when the user is a business entity.
Enrollment permissions. PAYMENTS_INITIATE: Permission to initiate payments RECURRING_PAYMENTS_INITIATE: Permission to initiate recurring payments
Enrollment name.
client logged user bank ISPB.
client logged user branch number.
client logged user bank account number.
client logged user bank account type.
Enrollment is linked to a optmized journey.
Enrollment link id to a optmized journey. Required if is_linked is true.
Responses
- 201
- 400
- 401
- 422
The enrollment created successfully.
- application/json
- Schema
- Example (from schema)
Schema
Enrollment id.
Possible values: [PENDING, ERROR, FAILED, AWAITING_DEVICE_RISK_SIGNALS, AWAITING_ACCOUNT_OWNER_VALIDATION, AWAITING_ENROLLMENT, AWAITING_DEVICE_REGISTRATION, PENDING_REVOKE, AUTHORIZED, REVOKED, REJECTED]
Enrollment status.
Enrollment expiration date time.
Enrollment created at.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"status": "PENDING",
"expiration_date_time": "2026-04-27T21:25:47.779Z",
"created_at": "2026-04-27T21:25:47.779Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.