Payment services account - Cybersource
21 minutes to read
🛈 Important This topic applies only when processing payments using Cybersource |
These are the specific to the Payment service account tab. The items in bold are the fields relevant to Payment services. You will need to obtain merchant specific settings from the payment provider in order to complete these settings.
Field |
Description |
Required |
Auto set |
Sample value |
Card mapping |
See the article on Card mapping to correctly configure this field. |
Yes |
Yes |
Default:VISA;VISA:VISA;MASTERCARD:MASTER; |
Merchant Id |
Enter the Merchant id provided by Cybersource. |
Yes |
No |
70XXXXXX00 |
Test Mode |
Enter 1 for Test Mode and Enter 0 for Live Mode. |
Yes |
Yes |
Auto populated for Test Mode. |
Profile id |
Enter the Profile id provided by Cybersource. |
Yes |
No |
2E979851-XXX-XXXX-XXXX-A2B98D62330E |
Accesskey |
Enter the Access key provided by Cybersource. You must use separate keys for the test and production environments. |
Yes |
No |
40c683XXXXXXXX7ca37166XXXXXXXXac |
Secretkey 1 |
Enter the Secret key provided by Cybersource. You must use separate keys for the test and production environments. Split the Secret Key into two parts. Enter part 1 into this field. Ensure the length of Part 1 is <= 200 characters. Enter the remainder of the Secret key in the field below (Cybersource secretkey 2). |
Yes |
No |
Field is limited to 200 characters |
Secretkey 2 |
Enter the remainder of the Cybersource Secret key. Note – this portion must be less than or equal to 200 characters. |
Yes |
No |
Field is limited to 200 characters |
Soapkey 1 |
Enter the Soap key provided by Cybersource. You must use separate keys for the test and production environments. Split the Soap Key into multiple parts. Enter part 1 into this field. Ensure the length of Part 1 is <= 200 characters. Carry the remainder over to Cybersource soapkey 2. You must use separate keys for the test and production environments. |
Yes |
No |
Field is limited to 200 characters |
Soapkey 2 |
Enter the reminder of the Soap key into this field. If the remainder is > 200 characters, split the remainder into two parts and enter part 1 into this field. Carry the remainder over to Cybersource soapkey 3. |
Yes |
No |
Field is limited to 200 characters |
Soapkey 3 |
Enter the final remainder of the Soapkey into this field. If there is no remainder, leave this field blank/Null. |
No |
No |
Field is limited to 200 characters |
Server url |
Enter the URL for the server url • Test Environment: https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor • Production Environment: |
Yes |
Yes |
Auto populated for Test |
Tokenized authorization support for ecom |
Leave this field as it is. |
No |
Yes |
0 |
Payment accept web url |
Refer the MAX Pay Global - cybersource_NotificationSiteDeployment document. Once you followed the step 6 from document, we got below URL https://rrconnector.azurewebsites.net How to get Payment accept web URL? Copy the note down URL: URL is: https://rrconnector.azurewebsites.net So, here is your payment accept URL: https://paymentconnector.azurewebsites.net/cybersource/CardPage.html You need to configure this URL in PS |
Yes |
No |
https://paymentconnector.azurewebsites.net/cybersource/CardPage.html |
Using multiple connectors in ecom |
This is not used. Leave this field as it is. |
No |
Yes |
0 |
Show payment token list in ecom |
This is not used. Leave this field as it is. |
No |
Yes |
0 |
|
Address verification |
|
|
|
Address Verification |
This standard Microsoft setting is not supported. Leave this option disabled. AVS support is configured and decided by the Payment provider. |
No |
No |
|
|
Card verification value |
|
|
|
Card Verification Value |
Enable this option to Prompt CVV option while authorizing sales order |
No |
No |
|
Allow blank card verification value |
Enable CVV to allow blank CVV while authorizing sales order. |
No |
No |
|