Credit Card
Create Credit Card Payment
Creates a credit card payment with configurable installments.
POST
The Bearer authentication token is required to access this endpoint.
Defines how customer data is handled. -
noNeedToSpecify: No customer data
required. - fillDataNow: Customer data must be provided now. -
requestCheckout: Customer data will be collected via checkout.Payment amount.
Expiration date and time in ISO 8601 format.
Number of installments (1 to 24).
Response
Unique ID of the created transaction.
Payment amount.
Payment description.
Customer data handling mode.
Redirect URL after payment.
Customer email.
Customer phone number.
Customer document type.
Transaction expiration date and time.
Customer document.
Customer document type.
Customer name.
Transaction ID (UUID).
Card EMV data (when applicable).
Receiver name.
International transaction status. Possible values: -
WAITING_PAYMENT:
Waiting for payment - PAID: Paid - DENIED: Denied - CANCELED: Canceled -
REFUNDED: RefundedTransaction status in Portuguese.
Generated checkout ID.
Checkout URL where the customer can fill in card details.
Transaction creation date and time (ISO 8601).
Last update date and time (ISO 8601).
Configured number of installments.
Important Notes
Transaction Status
After creation, the transaction is in statusWAITING_PAYMENT (Waiting for payment). Possible statuses are:
- WAITING_PAYMENT: Waiting for payment
- PAID: Payment approved and processed
- DENIED: Payment declined
- CANCELED: Transaction canceled
- REFUNDED: Payment refunded
Checkout URL
The returnedcheckout_url can be used to direct the customer to a hosted checkout page, where they can securely enter card details.
Installments
- Available installments: 1 to 24 installments
- Minimum amount: Check your account-specific configuration
- Fees: Automatically calculated based on configuration and number of installments
Client Mode
TheclientMode field defines how customer data will be handled:
- noNeedToSpecify: No customer data required at creation
- fillDataNow: Customer data must be provided in the payload
- requestCheckout: Customer data will be collected via checkout
Expiration
The expiration date (expire_at) must be provided in ISO 8601 format. After expiration, the transaction can no longer be paid.
HTTP Status Codes
- 201: Payment created successfully
- 400: Invalid payload data
- 401: Missing or invalid authentication token
- 500: Internal error creating payment
Validations
- Amount: Must be greater than 0
- Installments: Must be between 1 and 24
- Expiration Date: Must be a future date