CyberSource Resources - Extensions
Shopify Plugin
Overview
Installation
Dispute Notifications
Testing
Traffic Review
Payment Method Review
SFCC Cartridge
Overview
Installation
Historical Data Export
Front-end Integration
Mobile Integration
Fraud Management
Abuse Prevention
3DS Recommendations
Accounts
Testing
Testing Overview
Common Errors
Credit Card Tests
Processor Decline/No Auth Testing
Alternative Payment Methods (Non-Credit Card) Tests
PayPal Testing
Native Mobile App Tests
Phone and Offline Order Tests
Testing Resources
Adyen Resources
Braintree Resources
CyberSource Resources
Releases
Testing Resources
CyberSource Resources
Below are some links to the official CyberSurce developer documentation as well as test card and numbers provided by the publicly available developer documentation. These testing resources are maintained regularly by the Forter team, but please visit CyberSource's official test card page for the most up-to-date information and additional gateway-specific resources.
Testing a Valid Card Testing a Valid Card
Please use the following card numbers in sandbox with any valid expiration date and card Owner name to generate an authorized response from Cybersource in your sandbox environment:
| Card Brand | Test Input |
|---|---|
| American Express | 3782 8224 6310 005 |
| Discover | 6011 1111 1111 1117 |
| JCB | 3566 1111 1111 1113 |
| Maestro (International) | 5033 9619 8909 175868 2416 0825 5333 38 |
| Maestro (UK Domestic) | 6759 4111 0000 00086759 5600 4500 5727 054 5641 8211 1116 6669 |
| Mastercard | 2222 4200 0000 11132222 6300 0000 1125 5555 5555 5555 4444 |
| UATP | 1354 1234 5678 911 |
| Visa | 4111 1111 1111 1111 |
CyberSource No-Auth Testing CyberSource No-Auth Testing
CyberSource provides general test cases that include no auth, 2XX responses. Please note that details required in order to test different errors in your checkout flow using CyberSource. For Processor-specific testing with CyberSource, please see the Processor-Specific No-Auth Testing section below.
| Input | Expected Response |
|---|---|
| Input: purchaseTotals_grandTotalAmount = 1 Info = Valid Transaction | decision=ACCEPT reasonCode=100 ccAuthReply_processorResponse=00 |
| Input: purchaseTotals_grandTotalAmount = -1 Info = Invalid Amount < $0 | decision=REJECT reasonCode=102 ccAuthReply_processorResponse= |
| Input: purchaseTotals_grandTotalAmount = 100000000000 Info = Invalid Amount; amount too large | decision=REJECT reasonCode=102 ccAuthReply_processorResponse= |
| Input: card_accountNumber = Info = Empty credit card number | decision=REJECT reasonCode=101 ccAuthReply_processorResponse= |
| Input: card_accountNumber = 4111111111111112 Info = Invalid Luhn Mod 10 | decision=REJECT reasonCode=231 ccAuthReply_processorResponse= |
| Input: card_accountNumber = 412345678912345678914 Info = 21-digit credit card number; Mod 10 OK | decision=REJECT reasonCode=231 ccAuthReply_processorResponse= |
| Input: card_expirationMonth = 13 Info = Invalid expiration month | decision=REJECT reasonCode=102 ccAuthReply_processorResponse= |
| Input: card_expirationYear = 1998 Info = Expiration date passed | decision=REJECT reasonCode=202 ccAuthReply_processorResponse= |
Processor-Specific No-Auth Testing Processor-Specific No-Auth Testing
CyberSource provides processor specific testing scenarios. Select your relevant processor link to see specific amounts used to test different processor decline responses in your sandbox environment.
Example No-Auth Testing Example No-Auth Testing
The below chart represents the amounts used in sandbox in order to generate different processor decline responses from CyberSource in your sandbox environment specifically for the First Data payment processor.
| Input | Expected Response |
|---|---|
| Input: purchaseTotals_grandTotalAmount=1005.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D05 |
| Input: purchaseTotals_grandTotalAmount=1012.00 | decision=REJECT reasonCode=233 ccAuthReply_processorResponse=D12 |
| Input: purchaseTotals_grandTotalAmount=1014.00 | decision=REJECT reasonCode=231 ccAuthReply_processorResponse=D14 |
| Input: purchaseTotals_grandTotalAmount=1015.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D15 |
| Input: purchaseTotals_grandTotalAmount=1025.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D25 |
| Input: purchaseTotals_grandTotalAmount=1051.00 | decision=REJECT reasonCode=204 ccAuthReply_processorResponse=D51 |
| Input: purchaseTotals_grandTotalAmount=1055.00 | decision=REJECT reasonCode=233 ccAuthReply_processorResponse=D55 |
| Input: purchaseTotals_grandTotalAmount=1057.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D57 |
| Input: purchaseTotals_grandTotalAmount=1062.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D62 |
| Input: purchaseTotals_grandTotalAmount=1075.00 | decision=REJECT reasonCode=233 ccAuthReply_processorResponse=D75 |
| Input: purchaseTotals_grandTotalAmount=1093.00 | decision=REJECT reasonCode=203 ccAuthReply_processorResponse=D93 |
| Input: purchaseTotals_grandTotalAmount=1097.00 | decision=REJECT reasonCode=211 ccAuthReply_processorResponse=D97 |
| Input: purchaseTotals_grandTotalAmount=2200.00 | decision=REJECT reasonCode=201 ccAuthReply_processorResponse=R |
| Input: purchaseTotals_grandTotalAmount=2950.00 | decision=ERROR reasonCode=150 ccAuthReply_processorResponse=E |
CyberSource Reason Codes CyberSource Reason Codes
Refer to CyberSource's documentation.