|
|
|
|
|
|
To make sure that your requests are processed correctly, you need to test the basic success and error conditions for each ICS service you plan to use. This chapter explains how to test the Credit Card Services and covers these topics:
Important Before you can test, you must contact CyberSource Customer Support to activate Credit Card Services and configure your account for testing. You must also contact your processor to set up your processor account.
• Use your regular CyberSource merchant ID to perform testing.
• Unless otherwise specified, use test credit card numbers, not real ones. See Table 34.
• Use a real combination for the city, state, and postal code.
• Use a real combination for the area code and telephone number.
• Use a non-existent account and domain name for the customer’s email address.
• When testing a Global Payment Service country-specific bank card, such as Italy’s Carta Si or Ireland’s Laser card, specify the appropriate country code when sending the customer’s address and specify the currency used in that country.
• When testing the SCMP API, use the CyberSource test server ics2test.ic3.com.
• When testing the Simple Order API, use the test URL
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor.
Note If you are using the Global Payment Service and are testing captures, make sure to capture the full amount of the authorization. Although a capture request for a partial amount will not be rejected during testing, it will be rejected by the processor in production.
Use the credit card numbers in Table 34 to test the authorization, capture, and credit services. Do not use real credit card numbers.
To test card types not listed in Table 34, use an account number that is within the card’s bin range.
For best results, try each test with a different ICS service request and with different test credit card numbers.
|
Credit Card Type |
Test Account Number—remove spaces when sending to CyberSource |
|---|---|
|
American Express |
3782 8224 6310 005 |
|
Discover |
6011 1111 1111 1117 |
|
JCB |
3566 1111 1111 1113 |
|
Laser |
6304 9850 2809 0561 515 |
|
Maestro (International) |
5033 9619 8909 17 5868 2416 0825 5333 38 |
|
Maestro (UK Domestic) |
Issue number not required: 6759 4111 0000 0008 One-digit issue number required: 6759 5600 4500 5727 054 Two-digit issue number required: 5641 8211 1116 6669 |
|
MasterCard |
5555 5555 5555 4444 |
|
Solo |
Issue number not required: 6334 5898 9800 0001 One-digit issue number required: 6767 8200 9988 0077 06 Two-digit issue number required: 6334 9711 1111 1114 |
|
UATP |
1354 1234 5678 911 |
|
Visa |
4111 1111 1111 1111 |
Using Amounts to Simulate Errors
You can simulate the CyberSource error messages by requesting authorization, capture, or credit services with specific amounts that trigger the error messages. These triggers work only on the test server, not on the production server. Each payment processor uses its own error messages.
To see the list of trigger amounts and responses for each processor, go to the Testing Information page at the Support Center.
Testing American Express Card Verification
If you want to use card verification with American Express, follow these steps:
1 Contact American Express to register to use the feature.
2 Contact Customer Support after you are confirmed with American Express to use the feature. Until CyberSource configures your account to use the card verification number, you will receive a 1 in the reply field ccAuthReply_cvCode for the Simple Order API, or in the field auth_cv_result for the SCMP API.
3 Test your system in production using a small dollar amount, such as one dollar. Instead of using the test account numbers, use a real credit card account number, and send an incorrect card verification number in the request for authorization.
The card should be refused and the request declined. If it is not, contact American Express to confirm that your account is correctly configured to use the card verification feature.
You must go live with CyberSource before you begin to accept customers. When you go live, your CyberSource account is updated so that you can send transactions to the CyberSource production server. If you have not already done so, you will need to provide your banking information to CyberSource so that your processor can deposit funds to your merchant bank account.
To go live:
1 Go to the CyberSource Knowledgebase at http://www.cybersource.com/esupport.
2 Submit a question—click the Submit a Question link.
3 Log in with your CyberSource merchant ID and password. Use the same merchant ID and password that you use to log in to the Business Center.
4 On the Submit a Question page, fill in the contact information.
5 For the General Topic, select Getting Set Up on CyberSource.
6 For the Specific Topic, select Go Live.
7 For the Subject, enter "Go Live".
8 In the question field, indicate that you would like to go live.
9 If you have not already submitted your banking information to CyberSource, include the information in the question field and select the check box for This question contains sensitive banking information.
10 Click Submit question.
You will receive an email with your support ticket number and a CyberSource representative will contact you to complete the process.
11 After CyberSource has confirmed that you are live, update your system to send requests to the production server and instead of the test server. See the documentation for your client SDK for instructions.
After you go live, use real card numbers and other data to test every card type, currency, and CyberSource application that your integration supports. Because these are real transactions, use small amounts, such as one dollar, to do the tests. If you have more than one CyberSource merchant ID, test each one separately. Process an authorization, capture, and credit for each configuration. Use your bank statements to verify that money is deposited into and withdrawn from your merchant bank account.
|
|
|
|
|
|