Creates a payment with credit card as the payment method.
Use this operation to create the payment and redirect the payer to the invoiceUrl, or to process the card directly through the API. For direct processing, provide the card and cardholder data or a creditCardToken valid for the customer.
When the card is processed during creation, the attempt occurs immediately, regardless of dueDate. If the transaction is not authorized, the payment is not persisted and the API returns HTTP 400.
The creditCardToken replaces creditCard and creditCardHolderInfo and can only be used in payments of the customer for which it was generated. In Production, tokenization must be enabled for the account.
Set a minimum timeout of 60 seconds for this request when the card is processed, reducing the risk of duplicate attempts if the response is delayed.
For installment payments, up to 21 installments are allowed for Visa and Mastercard, and up to 12 installments for other card brands.
When authorizeOnly is true, the amount is only reserved on the card limit and the payment gets the AUTHORIZED status. The capture must be performed later through the pre-authorization capture endpoint. The default reservation period is 3 days and, for eligible accounts, it can be configured for up to 25 days; after this period, the reservation is automatically reversed.
Direct card processingIf your application captures card data, use HTTPS. Without SSL, the account may be blocked for credit card transactions.
Provide in
remoteIpthe IP of the payer's device, not the IP of the integration server.
Payment trackingCreating the payment does not mean the amount is definitively available. Track processing through the payment Webhooks, including risk analysis, confirmation, receipt or capture refusal scenarios.