Create scheduled payment - V1
PUT /order/v1/banking/subscriptions/{id}/payments
Schedule a payment for an existing subscription.
NOTE: Please, to authenticate use the scope: “api://app-order-hml”
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The subscription ID (UUID)
Header Parameters
Section titled “Header Parameters ”Request Body required
Section titled “Request Body required ”object
Account ID associated with the scheduled payment
Example
133e4567-e89b-12d3-a456-426614174000Due date in ISO 8601 format (YYYY-MM-DD). If not provided, system calculates automatically within cycle and D+2 to D+10 window.
Example
2025-02-10External identifier for the scheduled payment
Example
scheduled-payment-12345Payment amount object
object
Currency code
Example
BRLAmount value as a numeric string. A JSON number is also accepted.
Example
10.00Example
{ "currency": "BRL", "value": "199.90"}Scheduled payment description
Example
Monthly subscription chargePurpose of the scheduled payment.
- FIRST_ATTEMPT: the original charge for the cycle.
- NEW_ATTEMPT_AFTER_DUE_DATE: a further attempt at a charge that was not settled by its due date, such as one canceled for insufficient balance. Accepted only on subscriptions created with allowChargeAfterDueDate. Bacen rules: from the day after the request (dueDate defaults to tomorrow), at most 7 days after the original due date and inside its cycle, on at most 3 dates, one at a time, with the amount of the original charge. It refers to the charge in originalScheduledPaymentId or, when omitted, to the last FIRST_ATTEMPT of the subscription.
Example
FIRST_ATTEMPTOnly for NEW_ATTEMPT_AFTER_DUE_DATE: the scheduled payment to retry (a FIRST_ATTEMPT, or one of its retries). When omitted, the last FIRST_ATTEMPT of the subscription.
Example
7c3f2e2a-5b3a-4f7e-9a0a-2e2f9d0c1a2bWebhook URL to receive status updates
Example
https://example.com/webhooks/scheduled-paymentResponses
Section titled “ Responses ”The resource was returned successfully
object
The unique identifier of the scheduled payment
Example
123e4567-e89b-12d3-a456-426614174000The end-to-end identifier for the payment
Example
E1234567820250116150012345ABCDEFConciliation ID of the scheduled payment
Example
A298FE4B49A1408685311891FC557584The status of the scheduled payment
Example
PENDINGDue date of the scheduled payment
Example
2025-02-10Payment amount
object
The three-character ISO currency code.
https://en.wikipedia.org/wiki/ISO_4217Example
BRLThe amount of the transaction, in minor units.
Minor Units Format
------------------
All amount values must be formatted in that currency’s smallest unit.
Two-decimal currency (for example Real): R$ 10,95 BRL, amount will be "10.95".
Two-decimal currency (for example US Dollars): $10.95 USD, amount will be "10.95".
Zero-decimal currency (for example Japanese Yen): ¥1095 JPY, amount will be "1095".
Click here to download the latest official ISO 4217 Currency Table, with Minor Units (number of decimal places) per currency. Example
10.95Example
{ "currency": "BRL", "value": "199.90"}Scheduled payment description
Example
Monthly subscription chargeSubscription ID
Example
033bb7f8-f744-418b-852b-c6e2d7afc428Purpose of the scheduled payment
Example
FIRST_ATTEMPTExternal identifier for the scheduled payment
Example
scheduled-payment-12345object
Example
INVALID_REQUESTobject
Example
[ { "field": "field_name", "issue": "INVALID", "description": "Field is invalid" }]Unauthorized Request
object
Example
UNAUTHORIZEDExample
Unauthorized Requestobject
Example
[]object
Example
FORBIDDEN_ERRORobject
Example
[]Resource not found
object
Example
NOT_FOUNDExample
Resource not foundobject
Example
[]object
Example
INTERNAL_ERRORobject
Example
[]