Test Your Solution
To conduct tests with PayU, use the credentials provided below in your requests, depending on the country your account is associated with.
Argentina |
Brazil |
Chile |
Colombia |
Mexico |
Panama |
Peru |
|
---|---|---|---|---|---|---|---|
Account ID | 512322 | 512327 | 512325 | 512321 | 512324 | 512326 | 512323 |
Merchant ID | 508029 | ||||||
API Login | pRRXKOl8ikMmt9u | ||||||
API Key | 4Vj8eK4rloUd272L48hsrarnUA | ||||||
Public Key | PKaC6H4cEDJD919n705L544kSU |
Notes
- Refer to the PayU-Handled 3DS Authentication documentation to find the credentials for testing 3DS.
- The test environment does not replicate data from your production account.
Test Cards
You can use the following cards for testing:
Argentina
Card | Number |
---|---|
AMEX Credit Card | 376414000000009 |
ARGENCARD Credit Card | 5011050000000001 |
CABAL Credit Card | 5896570000000008 |
CENCOSUD Credit Card | 6034930000000005 - 5197670000000002 |
DINERS Credit Card | 36481400000006 |
MASTERCARD Credit Card | 5399090000000009 |
NARANJA Credit Card | 5895620000000002 |
SHOPPING Credit Card | 6034880000000051 |
VISA Credit Card | 4850110000000000 - 4036820000000001 |
VISA Debit Card | 4517730000000000 |
Brazil
Card | Number | Expiration Date | CVV |
---|---|---|---|
AMEX Credit Card | 371341553758128 | 2035/01 | 1234 |
DINERS Credit Card | 36490101441625 | 2035/01 | 123 |
ELO Credit Card | 4389351648020055 4389358876174389 |
2035/01 | 123 |
HIPERCARD Credit Card | 6062825624254001 | 2035/01 | 123 |
MASTERCARD Credit Card | 5448280000000007 2223020000000005 2223000250000004 |
2035/01 | 123 |
VISA Credit Card | 4235647728025682 4895370010000005 |
2035/01 | 123 |
Chile
Card | Number | Cardholder | CVV | Expiration date |
---|---|---|---|---|
AMEX Credit Card | 377825000000005 | Follow the testing values according to the expected result. | ||
DINERS Credit Card | 36525200000002 | |||
MASTERCARD Credit Card | 5457210001000019 | BKN_DMC_001 | 300 | 12/25 |
MASTERCARD Debit Card | 5204730000001003 | BKN_MCS_001 | 100 | 12/25 |
MASTERCARD Prepaid Card | 5185540320000012 | BKN_DMC_001 | 001 | 12/25 |
VISA Credit Card | 4761340000000035 | VISA_GLOBAL_3 | 846 | 12/27 |
VISA International Card | 4005520000000129 | VISA_ECOMMERCE_03 | 921 | 12/27 |
VISA Dedit Card | 4761340000000050 | VISA_GLOBAL_5 | 846 | 12/27 |
Colombia
Card | Number |
---|---|
AMEX Credit Card | 377813000000001 - 377847626810864 - 376402004977124 - 376414000000009 |
CODENSA Credit Card | 5907120000000009 |
CRM Credit Card | 5282096712463427 |
DAVIVIENDA Credit Card | 5247081012761500 |
DINERS Credit Card | 36032400000007 - 36032404150519 - 36032440201896 |
MASTERCARD Credit Card | 5471300000000003 - 5120697176068275 |
NEQUI Credit Card | 4093551018099251 |
VISA Credit Card | 4097440000000004 - 4037997623271984 - 4111111111111111 |
VISA Debit Card | 4509420000000008 |
Mexico
Card | Number |
---|---|
AMEX Credit Card | 376675000000005 |
MASTERCARD Credit Card | 5491380000000001 |
MASTERCARD Debit Card | 5256780000000007 |
VISA Credit Card | 4268070000000002 |
VISA Debit Card | 4415490000000004 |
Panama
Card | Number |
---|---|
MASTERCARD Credit Card | 5455040000000005 |
VISA Credit Card | 4723030000000005 |
Peru
Card | Number |
---|---|
AMEX Credit Card | 377753000000009 |
DINERS Credit Card | 36239200000000 |
MASTERCARD Credit Card | 5491610000000001 |
MASTERCARD Debit Card | 5236930000000003 |
VISA Credit Card | 4907840000000005 - 4634010000000005 |
VISA Debit Card | 4557880000000004 |
Testing Statuses
When testing payments, make sure to include the following values in the request according to the desired status:
- To obtain approved transactions:
- Include
APPROVED
in the cardholder’s name. - Use 777 as the card’s CVV (for AMEX, use 7777).
- The
test
parameter and the description also influence the status. If it does not work withtest
set to false, change its value to true. - When entering the card’s expiration date, ensure the month is less than
6
and the year is later than the current year. For example:05/202_
.
- Include
- To obtain declined transactions:
- Include
REJECTED
in the cardholder’s name. - Use 666 as the card’s CVV (for AMEX, use 666).
- The
test
parameter and the description also influence the status. If it does not work withtest
set to false, change its value to true. - When entering the card’s expiration date, ensure the month is greater than
6
and the year is later than the current year. For example:07/202_
.
- Include
-
For the card number, use a valid number corresponding to the brand sent in the request. You can use an online credit card generator or select one of the cards for your country mentioned earlier.
-
To test bank transfers through PSE (available in Colombia) in the PayU Sandbox environment, refer to the PSE Test Guide (PDF).
-
To test cards in Chile, use the cardholder name, CVV, and expiration date values shown in the example cards.
Importing the Collection
Click the button below to import our collection in Postman (you may need to refresh the page if the button does not work for you). Note that we create a new environment each time you import the collection.
After you run the collection, you need to set the environment variables and the globals.
Setting Your Environment Variables
Our collection has one environment named PayU API Sandbox
. We recommend you invoke the collection’s API requests in a Sandbox environment only.
If you want to change the PayU’s testing accounts, configure the api_key
, api_login
, merchant_id
and account-[country]
variables. You can leave all the other variables unchanged.
Importing Globals
Globals are the variables required to process transactions in our Payment gateway such as currency, transaction amount, confirmation and response pages and more.
Import the globals for the collection to configure the values sent to the requests.
-
Download the globals file here.
-
In the Postman collection, click Import next to your workspace name and locate the json file recently downloaded.
-
When finish, click Import.
To change the amount of a transaction, update the value for the tx_value_[Country]
according to the country you want to test.
Running the Requests in the Correct Order
Beware that the order in which you run the requests is important, since some of the data returned by one request may be used in the next invocation.