Creates a new payment linked to a customer in the Asaas account.
Use this operation for one-time or installment payments via bank slip (boleto), Pix or credit card. When billingType is UNDEFINED, the payer can choose among the payment methods enabled on the account when accessing the payment page.
For one-time payments, provide value. For installment payments, use installmentCount with only one of installmentValue and totalValue. When using totalValue, Asaas calculates the installment amount and applies any rounding difference to the last installment. In this scenario, the response represents the first payment generated and includes the installment ID.
If the account has global fine and interest settings and they should be kept, do not send interest and fine. Sending these objects with null or empty values may override the configuration for the created payment.
For bank slip (boleto) payments, daysAfterDueDateToRegistrationCancellation defines for how many days after the due date the registration will remain available for payment. The value 0 cancels the registration when the payment changes to OVERDUE; when the field is omitted, the account's default setting applies. This setting cannot be changed after the payment is created.
When creating recurring Automatic Pix payments in MANUAL mode, provide the pixAutomaticAuthorizationId of an ACTIVE authorization. The payment instruction must be created between 2 and 10 business days before the due date. Without this field, the PIX payment is created as a conventional Pix.
Payment trackingCreating the payment does not represent payment confirmation. Track status changes through the payment Webhooks.
For Pix payments on individual (natural person) accounts,
CONFIRMEDmay be temporary during a precautionary block, for up to 72 hours. After the review, the payment may move toRECEIVEDorREFUNDED.