Create a credit card payment

⚠️

Warning

Authorization responses are subject to the addition of new fields from card brands/issuers.
Integrate in a way that anticipates this behavior by properly using serialization and deserialization techniques.

ℹ️

The capture of the credit transaction can be automatic or later.

• For automatic capture, send the Payment.Capture `parameter in the request as “true”;
• For later capture, send the parameter as "false" and subsequently make the capture after authorization.

Warning

• It is not possible to perform a transaction with an Amount of 0. To verify the validity of a card, use Zero Auth;
• Mastercard credit transactions with stored credentials: Mastercard requires the Transaction Initiation Indicator for credit and debit card purchases using stored card data. The goal is to indicate whether the transaction was initiated by the cardholder (Cardholder-Initiated Transaction - CIT) or by the merchant (Merchant-Initiated Transaction - MIT). In this scenario, it is mandatory to send the InitiatedTransactionIndicator node with the Category and SubCategory parameters for Mastercard transactions, within the Payment node. Check the example of the node and the list of categories and subcategories in Mastercard Transaction Initiator Indicator .
• The Payment.ServiceTaxAmount field is exclusive to airlines, allowing them to charge the boarding fee separately from the airfare.
• To validate if the authentication was accepted in the authorization response, consider the ECI outside the Payment.ExternalAuthentication node.

⚠️

The Hipercard card brand was discontinued on June 30 2025.

⚠️

Identification of transactions originating from payment links for Elo cards

Starting October 17, 2025, it will be mandatory to identify transactions originating from payment links for Elo-branded cards. Send the parameter Payment.SolutionType = "ExternalLinkPay".

The parameter Payment.SolutionType will be available in the API starting September 15, 2025.