Create an Automatic Pix Recurrence
POSTTag: api-baas-create-pix-automatic-recurrenceDescription: Creates an automatic pix recurrence to be able to send payment schedules to the payer/debtor./v1/pix/scheduled-payments/automatic-recurrences
Request
Header Parameters
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.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
The product ID is a UUID (v4) used to identify the Z.ro product configuration.
The product target user ID is a UUID (v4) used to identify what user account this request must be executed. Require: x-product-uuid.
- application/json
Body
required
Possible values: [JOURNEY_1, JOURNEY_2, JOURNEY_3, JOURNEY_4]
Automatic pix journey. JOURNEY_1: An automatic pix recurrence will be created and a notification to the payer will be sent. JOURNEY_4: A QRCode will be generated to be shared with the payer to pay or schedule the payment of the charge and approve (optional) the automatic pix recurrence.
Possible values: [WEEKLY, MONTHLY, QUARTERLY, SEMI_ANNUALLY, ANNUALLY]
Frequency
Date of the first payment of the automatic pix recurrence
Date for when the automatic pix recurrence will be ended
Recurrence fixed value for the charges.
Maximum floor value.
Possible values: non-empty and <= 8 characters
Owner (payer) Bank ISPB
Owner (payer) name (required if journey 4)
Owner (payer) document (CPF or CNPJ)
Possible values: non-empty and <= 5 characters
Owner (payer) Bank branch (required if journey 1)
Owner (payer) Bank account number (required if journey 1)
Debtor document (CPF or CNPJ) (required if journey 4)
Debtor name (required if journey 4)
Contract number or reference code
Contract description
Tags (max: 5)
Expiration date (required if journey 1)
Pix key ID (required if journey 4)
Charge value (required if journey 4)
Charge due date (required if journey 4)
Responses
- 200
- 400
- 403
Recurrence successfully created.
- application/json
- Schema
- Example (from schema)
Schema
Recurrence ID.
Possible values: [PENDING, CREATED, FAILED, APPROVED, REJECTED, CANCELED, EXPIRED, FINISHED]
Recurrence status
Possible values: [PENDING_CONFIRMED, CREATED_CONFIRMED, CREATED_FAILED, APPROVED_CONFIRMED, REJECTED_CONFIRMED, CANCELED_CONFIRMED, CANCELED_FAILED, EXPIRED_CONFIRMED, FINISHED_CONFIRMED]
Recurrence status
{
"id": "d1952c4b-9348-41ab-99a3-05b11459aded",
"status": "PENDING",
"state": "PENDING_CONFIRMED"
}
If any required params are missing or has invalid format or type.
If user person type is not Legal Person