Real-Time Account Updater Testing
Ensure your Real-Time Account Updater integration works correctly by simulating Account Updater responses in the sandbox.
You can use the following test values and responses in the sandbox for both Batch and Real-Time Account Updater.
Step 1: Request Access
The sandbox is not available for self-signup at this time.
If you’re interested in Real-Time Account Updater, contact us to request a demo. The Pagos Accounts team will email you with an invitation to our sandbox environment. Follow the link in the invitation to confirm your email address, create a Sandbox password, and complete your account setup.
Step 2: Generate Your Sandbox API Keys
When you first onboard with Real-Time Account Updater, open the Pagos Sandbox Service Panel to generate an API Key pair:
These API Keys are universal across the sandbox and will be used for testing both Account Updater and Network Tokenization. If you have already created an API key, you don’t need to create a new one.
Click your profile icon at the bottom of the main navigation.
Under Developers, click API Keys.
Click the Action API tab.
Under the Action API Keys header, click Create API Key to add a new key pair to your account. A side panel will open with the new Client and Private key values.
Copy your new API key pair and store it somewhere secure. You can only view this value one time.
Click I’ve Copied My Keys to confirm and exit the side panel.
Step 3: Request Your Real-Time Account Updater Sandbox Encryption Keys
In the sandbox, follow the same steps outlined in our Real-Time Account Updater Encryption guide to create your RequestEncryptionKey, ResponseDecryptionKey, and associated Key IDs.
Step 4: Test Real-Time Account Updater
You’re ready to begin testing the full capabilities of Real-Time Account Updater! Follow the instructions in our Real-Time Account Updater Overview Overview guide to perform the following actions in the sandbox using our sandbox testing values:
-
Authenticate and Encrypt to confirm your access
-
Submit a card inquiry using our test values.
-
Check response of the inquiry.
Keep in Mind:
-
The sandbox is a stateless system that responds with simulated responses and processes in a synchronous manner
-
When you submit test values, you’ll receive the expected response and corresponding webhook immediately
Test Values
Visa
| Visa Test Card Details | Response Code | Error Code | Response Code Description | Updated Card Details (If Applicable) |
|---|---|---|---|---|
| LAE | Change in account number or change in account number and expiration date |
| |
| LAE | Change in account number or change in account number and expiration date |
| |
| LCA | Closed account | ||
| LED | Change in expiration date |
| |
| LCC | Contact cardholder | ||
| LNB | Non-participating BIN | ||
| LNM | Participating BIN - No match | ||
| LNC | No change in account details | ||
| LCO | Card holder opt-out | ||
| LE02 | Account number invalid | ||
| LE03 | Account number format invalid | ||
| LE04 | Expiration date invalid | ||
| LE05 | Merchant not registered |
Mastercard
| Short Code | Description | |||
|---|---|---|---|---|
| Mastercard Test Card Details | Response Code | Error Code | Response Code Description | Mastercard Updated Card Details (If Applicable) |
| LAE | Change in account number or change in account number and expiration date |
| |
| LAE | Change in account number or change in account number and expiration date |
| |
| LCA | Closed account | ||
| LED | Change in expiration date |
| |
| LNB | Non-participating BIN | ||
| LNM | Participating BIN - No match | ||
| LNC | No change in account details | ||
| LNC | No change in account details | ||
| LE03 | Account number format invalid | ||
| LE04 | Expiration date invalid | ||
| LE05 | Merchant not registered | ||
| LE06 | Sub-merchant not registered |
Real-Time Account Updater Testing
Ensure your Real-Time Account Updater integration works correctly by simulating Account Updater responses in the sandbox.
You can use the following test values and responses in the sandbox for both Batch and Real-Time Account Updater.
Step 1: Request Access
The sandbox is not available for self-signup at this time.
If you’re interested in Real-Time Account Updater, contact us to request a demo. The Pagos Accounts team will email you with an invitation to our sandbox environment. Follow the link in the invitation to confirm your email address, create a Sandbox password, and complete your account setup.
Step 2: Generate Your Sandbox API Keys
When you first onboard with Real-Time Account Updater, open the Pagos Sandbox Service Panel to generate an API Key pair:
These API Keys are universal across the sandbox and will be used for testing both Account Updater and Network Tokenization. If you have already created an API key, you don’t need to create a new one.
Click your profile icon at the bottom of the main navigation.
Under Developers, click API Keys.
Click the Action API tab.
Under the Action API Keys header, click Create API Key to add a new key pair to your account. A side panel will open with the new Client and Private key values.
Copy your new API key pair and store it somewhere secure. You can only view this value one time.
Click I’ve Copied My Keys to confirm and exit the side panel.
Step 3: Request Your Real-Time Account Updater Sandbox Encryption Keys
In the sandbox, follow the same steps outlined in our Real-Time Account Updater Encryption guide to create your RequestEncryptionKey, ResponseDecryptionKey, and associated Key IDs.
Step 4: Test Real-Time Account Updater
You’re ready to begin testing the full capabilities of Real-Time Account Updater! Follow the instructions in our Real-Time Account Updater Overview Overview guide to perform the following actions in the sandbox using our sandbox testing values:
-
Authenticate and Encrypt to confirm your access
-
Submit a card inquiry using our test values.
-
Check response of the inquiry.
Keep in Mind:
-
The sandbox is a stateless system that responds with simulated responses and processes in a synchronous manner
-
When you submit test values, you’ll receive the expected response and corresponding webhook immediately
Test Values
Visa
| Visa Test Card Details | Response Code | Error Code | Response Code Description | Updated Card Details (If Applicable) |
|---|---|---|---|---|
| LAE | Change in account number or change in account number and expiration date |
| |
| LAE | Change in account number or change in account number and expiration date |
| |
| LCA | Closed account | ||
| LED | Change in expiration date |
| |
| LCC | Contact cardholder | ||
| LNB | Non-participating BIN | ||
| LNM | Participating BIN - No match | ||
| LNC | No change in account details | ||
| LCO | Card holder opt-out | ||
| LE02 | Account number invalid | ||
| LE03 | Account number format invalid | ||
| LE04 | Expiration date invalid | ||
| LE05 | Merchant not registered |
Mastercard
| Short Code | Description | |||
|---|---|---|---|---|
| Mastercard Test Card Details | Response Code | Error Code | Response Code Description | Mastercard Updated Card Details (If Applicable) |
| LAE | Change in account number or change in account number and expiration date |
| |
| LAE | Change in account number or change in account number and expiration date |
| |
| LCA | Closed account | ||
| LED | Change in expiration date |
| |
| LNB | Non-participating BIN | ||
| LNM | Participating BIN - No match | ||
| LNC | No change in account details | ||
| LNC | No change in account details | ||
| LE03 | Account number format invalid | ||
| LE04 | Expiration date invalid | ||
| LE05 | Merchant not registered | ||
| LE06 | Sub-merchant not registered |