Use transaction simulators to troubleshoot future customer payment issues with realistic responses. These simulators prepare you for handling potential errors in the Sandbox before going live. By simulating errors and edge cases, you can prepare for real-world scenarios and ensure your system responds appropriately.
Get Started
Each simulator is triggered by entering a specific transaction amount. These amounts simulate different error responses, such as insufficient funds or expired cards.
To activate any transaction simulator, always use the following test card data:
Number: 4242 4242 4242 4242
CVV: Any three-digit number. For example, 123.
Expiration: Any valid future date values in MMYY format. For example, 1234.
Activate Transaction Simulators
Trigger each simulator by entering a specific test transaction amount. Enter the associated trigger amount to simulate the platform error using the following Portal methods:
These values simulate different transaction error response outcomes by platform:
Vantiv transaction simulators use Sale transaction types to simulate different responses at different points of the transaction lifecycle without changing the transaction type.
Use each amount as the transaction amount to trigger each simulator. For example, using $500.04 returns an “Insufficient Funds” simulator response message.
To trigger a Vantiv transaction simulator:
Set the transaction type to Sale.
Enter the test card data.
Provide one of the following trigger amounts and process the transaction to simulate a potential Vantiv platform credit card sale processing error:
Trigger Amount
Simulator Response Message
$95.87
Declined
$500.01
Exceeds Approval Amount Limit
$500.04
Insufficient Funds
$565.56
Transaction not supported by issuer.
$566.56
Blocked by cardholder/contact cardholder.
$848.00
Processing Network Unavailable
$848.01
Issuer Unavailable
$848.02
Re-submit Transaction
$848.03
Call Issuer
$848.04
Merchant not certified/enabled for IIAS.
$848.05
Issuer Generated Error
$848.06
Restricted Card
$848.07
Card Not Active
$848.08
Illegal Transaction
$848.09
Duplicate Transaction
$848.10
System Error
$848.11
System Error (cannot process)
$848.12
Lost/Stolen Card
$848.13
Expired Card
$848.14
Restricted Card
$848.15
No such issuer
$848.16
Transaction not allowed at terminal.
$848.17
Cardholder transaction not permitted.
$848.18
Cardholder requested that recurring or installment payment be stopped.
$848.19
Do Not Honor
$848.20
Decline - Request Positive ID
$848.21
Processing Network Error
$848.22
Soft Decline - Primary Funding Source Failed
$848.23
Soft Decline - Auto Recycling In Progress
$848.24
Internal System Error - Call Vantiv
$848.25
Generic Decline
Result: The transaction simulator returns the platform simulator response message aligned with the amount.
VCore transaction simulators are divided into Authorization (Auth) and Capture transaction categories:
Auth: Credit card authorization responses.
Capture: Credit card sale or authorization transaction settlement batching responses.
Sale transactions combine the Auth and Capture processes into one step. This process seeks immediate authorization while assigning the transaction to the daily batch. Using Sale transactions works for VCore simulators and eliminates the need for a second manual capture after a prior Authorization transaction.
Trigger Auth Transaction Simulators
Merchants use Auth transactions to collect payment information and get approval from a cardholder's financial institution to hold and capture funds.
To trigger a VCore Auth transaction simulator:
Set the transaction type to Authorization Only.
Enter the test card data.
Provide one of the following trigger amounts and process the transaction to simulate a potential VCore platform credit card authorization error:
Authorization Amount
Simulated Authorization Error
$101.03
Invalid Merchant ID
$101.05
Generic Authorization Decline
$101.13
Invalid Amount
$101.14
Invalid Account Number
$101.30
Message Format Error
$101.39
No Credit Account
$101.51
Insufficient Funds
$101.54
Expired Card
$101.82
Invalid CVV
$101.83
Unable to Verify PIN
$101.96
System Error
Result: The Auth transaction simulator returns the platform simulator response message aligned with the amount shown in the table.
Trigger Capture Transaction Simulators
Merchants use Capture transactions to collect payment after a prior Auth approval from a cardholder's financial institution.
To trigger a VCore Capture transaction simulator:
Set the transaction type to Sale.
Enter the test card data.
Provide one of the following trigger amounts and process the transaction to simulate a potential VCore platform credit card capture error:
Authorization Amount
Simulated Authorization Error
$201.02
Invalid authorization source code.
$201.04
Invalid or missing entry mode.
$201.10
Invalid or missing merchant category code (MCC).
$201.11
Invalid or missing transaction number.
$201.12
Invalid or missing merchant number presented by the merchant.
$201.14
Test card rejected for settlement.
$201.20
Transaction Amount Exceeds Network Limit.
$201.21
The transaction amount exceeds the internal limit. Transaction pending further review.
$201.22
Non-Debit Merchant USB
$201.23
Blocked Merchant
$201.30
Transaction Declined
Result: The Capture transaction simulator returns the platform simulator response message aligned with the amount shown in the table.
Important!
You can’t view Capture simulator responses until the transaction status is Captured. Capture simulator responses appear after the daily settlement batch closes at 9:30 PM Eastern Time.
Do not use values outside the specified triggers to activate Sandbox simulators. Non-trigger values return standard successful server responses for normal testing.
Important!
Do not use values outside the specified triggers to activate Sandbox simulators. Non-trigger values return standard successful server responses for normal testing.
Check Simulator Responses
When triggering the transaction simulator with a relevant amount, an artificial platform response is returned with a message explaining the reason.
To find the platform transaction simulator response messages:
Select Payment History in the left navigation panel.
Select the relevant transaction to access the Transaction Details page.
Select Alerts on the Transaction Details left menu.
Result: The Alerts menu displays a list of all platform responses to the transaction. For transactions using simulator trigger amounts, the Alerts menu shows the simulator response message from the applicable platform.