Book a Demo

T1Pagos - Cards

Suggest Edits

This page presents all information related to the T1Pagos 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

Production Environment

Connecting with Yuno

Mandatory fields when integrating via Yuno:

first_name
last_name
*The provider may request additional fields according to the merchant or to improve the approval rate.

General information

Countries:

mexico-flag
Mexico

Currencies:

MXN

Payment methods:

Credit card
Credit card
debit card
Debit card

TRX without CVV:

Yes

Purchase TRX in 1-Step:

Yes

Purchase TRX in 2-Step:

Yes

Support for recurrency:

Yes

Webhooks:

Yes. Some processes are automatically executed, like suscription charges, to maintain the systems synchronized, an endpoint can be configured to receive notifications of some events such as new charges, suscription renovations and others.

Captures

Partial capture:

Yes

Refunds

Refund support:

Yes

Partial refunds:

Yes

Voids

Void support:

Yes

Void to authorization:

Yes

Void to refund:

No

Installments

Capability to define the installments when creating the payment:

Yes

Conditions or restrictions:

Installments can be 3, 6, 9, 12, 15, 18, or 24.
Supports different payment plans:
  • normal
  • msi
  • mci
  • diferido
  • diferido_msi
  • diferido_mci

Deferral date availability:

Yes

Minimum number of Installments (#months):

3

Maximum number of Installments (#months):

24

Security

E3DS v2:

Yes

Testing guidelines for sandbox environment

Necessary fields for testing:

Access Token.

General observations for testing cards:

You can use random transactions IDs (transactionId) for all testing cases.

Test cards:

Case PAN Status Code Description
Use of 3DS 5555555555554444 Accepted or Rejected Variable Reply with profile "3d_secure" to make use of profile selector.
Rejected card 4222222222222220 Rejected do_not_honor The transaction was declined for an unknown reason.
Stolen card 4000000000000119 Rejected tarjeta_robada The bank has reported the card as stolen.

Test cards Amex:

Case PAN Status Code Description
Approved 341111111111111 Completed cargo_exitoso The charge was successful.
Rejected 340000000000009 Rejected do_not_honor The transaction was declined for an unknown reason.
Insufficient funds 370000000000002 Rejected fondos_insuficientes The card does not have enough balance to complete the purchase.
Stolen card 342969003866921 Rejected
Ciber card 343434343434343 Completed

Test cards Mastercard:

Case PAN Status Code Description
Approved 5105105105105100 Completed cargo_exitoso The charge was successful.
Rejected 5559156876003462 Rejected
Insufficient funds 5175152167874418 Rejected
Stolen card 5294369875991708 Rejected

Test cards Visa:

Case PAN Status Code Description
Approved 4111111111111111 Completed cargo_exitoso The charge was successful.
Inssuficient funds 4444444444444448 Rejected fondos_insuficientes The card does not have enough balance to complete the purchase.
Ciber card 4000000000000044 Completed
Ciber card 4242424242424242 Completed

Integration configuration

Credentials and steps to obtain them:

In the Admin system (Sandbox and Production), in the left menu, click Tokens. See to your list of Access Tokens.

Dashboard configuration:

  1. Log in to dashboard.y.uno.
  2. Click Connections and then select T1Pagos.
  3. Click Connect.
  4. Introduce Name and Access Token.
  5. Click Connect

Configuration of webhooks in partner:

The register is made from the Admin system (Sandbox and Production), in the left menu, click Webhooks. More than one endpoint can be included and notifications can be channeled to each new route.

Production environment

Specific procedure for a merchant to go live:

-



Send feedback

Updated 3 months ago