Pagar.me - Cards
This page presents all information related to the Pagar.me connection using Cards as payment. Use the following buttons to navigate to the desired section.
General Information
Captures
Refunds
Voids
Installments
Chargebacks
Security
Testing Guidelines
Integration Configuration
Connecting with Yuno
Mandatory fields when integrating via Yuno:
last_name
items.id
General information
Countries:
![brazil-flag](https://raw.githubusercontent.com/writechoiceorg/yuno-images/main/flags/brazil.png)
Currencies:
BRL.
Payment methods:
![Credit card](https://icons.prod.y.uno/card_logosimbolo.png)
![debit card](https://icons.prod.y.uno/card_logosimbolo.png)
![Prepaid card](https://icons.prod.y.uno/card_logosimbolo.png)
Minimum amount:
Maximum amount:
It depends on the payment method.
TRX limit:
200 per minute.
Support of international BIN:
Yes
TRX without CVV:
Yes
Purchase TRX in 1-Step:
Yes
Purchase TRX in 2-Step:
Yes
Support for recurrency:
No
Type of integration:
B2B
Webhooks:
Yes (Optional)
Captures
Partial capture:
Yes
Multiple captures:
Yes
Maximum time to capture an authorization:
7 days.
Captures over the amount of authorization:
No
Maximum amount:
100% of the authorization.
Refunds
Refund support:
Yes
Partial refunds:
Yes
Multiple refunds:
No
Voids
Void support:
Yes
Void to authorization:
Yes
Void to refund:
No
Installments
Capability to define the installments when creating the payment:
Yes
GET endpoint available for retrieving the permitted BIN for the installments:
No
Possibility to choose who will be responsible for financing installments:
No
Chargebacks
Notifications of chargebacks:
No
Security
Address verification service:
No
Support for 0Auth:
No
3DS v2:
Yes
Testing guidelines for sandbox environment
Necessary fields for testing:
Test cards:
Card Number | Scenario |
---|---|
4000000000000010 | Success card. Any operation with this card is successful. |
4000000000000028 | Failure card. Any transaction return unauthorized status. |
4000000000000036 | Processing card -> Success. The transaction receives an error status and is later confirmed by the acquirer. |
4000000000000044 | Processing card -> Failure. The transaction receives an error status and is later not found by the acquirer, characterized as a failure. |
4000000000000077 | Success card -> Processing -> Success. The transaction receives a success status and, upon performing a second action later, an issue occurs in the operation being characterized as processing. At the end, the transaction will be updated with the success of the second operation. |
4000000000000093 | Success card -> Processing -> Success (first operation). The transaction receives a success status and, upon performing a second action later, an issue occurs in the operation being characterized as processing. At the end, the transaction will be updated with the success of the first operation. |
4000000000000051 | Processing card -> Canceled. The transaction receives a processing status and finally the transaction will be updated with the cancellation of the first operation. |
4000000000000069 | Paid card -> Chargedback. The transaction receives a paid status and, later, changes the status to chargeback. |
Any other card | Any transaction returns as unauthorized. |
Check the oficial Pagarme documentation if the operations does not happend as expected.
Integration configuration
Credentials and steps to obtain them:
Before accessing the Pagarme dashboard, contact the Pagarme support team to obtain the credentials.
- Log in to Pagarme dashboard.
- Access Development and then select keys.
- Click Generate Secret Key.
Dashboard configuration:
- Log in to dashboard.y.uno.
- Click Connections and then find the Pagarme card.
- Click Connect.
- Introduce Name and Secret Key.
- Click Add.
Updated about 1 month ago