Cybersource

Setting up Cybersource

1. 1

   Set up your Cybersource account.

2. 2

   Log in to the Test Business Center.

3. 3

   In the left nav, click Payment Configuration > Key Management.

4. 4

   Generate a new key by clicking Generate Key. Select Transaction Processing on the first screen, and SOAP on the second.

5. 5

   Copy the key that appears, and download it for safekeeping if you'd like — it won't be shown again.

6. 6

   Log in to your Foxy admin and go to your payment settings. Set your payment method to Cybersource.com.

7. 7

   Switch to the Live Server option. If it's disabled, you'll need to start your Foxy subscription first.

8. 8

   Enter your Merchant ID, the same one you use to log in to Cybersource, and the Transaction Key you just copied.

9. 9

   If your store needs to verify that a credit card is valid for certain amounts, set the card verification mode field, live or test. Use this if you want to save a credit card for the customer and verify it's valid without charging it at the time of entry. See the ? to the right of the field for help on the options.

10. 10

    Click Update Payment Gateway.

11. 11

    Back in your Cybersource account, click Account Management > SmartAuth Settings and set your checkboxes to look like this:

    • UK users can skip this step — CVN is not available and is covered by the Decision Manager settings.

    • Cybersource puts basic fraud screening in place via Decision Manager even in the basic setup package.

    • Foxy always sends the CVN unless the customer is using a saved card, or it's processing a subscription. This is very common: the first transaction between your store and your customer validates using the CVN, and subsequent transactions validate using other services such as address verification.

12. 12

    Test. Your account may already be in test mode — contact Cybersource support to make sure everything's ready to go.

13. 13

    Test more. Test with a real credit card and make sure everything works as expected, all the way up to the money actually being deposited into your merchant account.

Note that using a test card on a live account generates account configuration errors. We're calling that out because it's unusual — normally the cards would just be rejected with a normal declined-style error message.

Payment tokenization

To be able to charge a customer again, you need to create a customer profile at Cybersource.

You'll get the subscription ID as paySubscriptionCreateReply__subscriptionID in your data feed application. The customer profile is created at Cybersource, so you can access it using the Cybersource Business Center.

Activation

Version 1.1

1. 1

   Choose Cybersource.com (Payment Tokenization) as your payment gateway.

2. 2

   Activate the Payment Token Required option.

Version 2.0+

1. 1

   Choose Cybersource.com as your payment gateway.

2. 2

   Activate the Payment Token Required option.

Overriding the merchant reference number

As of Foxy v2.0, the Merchant Reference Number that Foxy passes to Cybersource — normally the Foxy transaction ID — can be overridden. This is advanced functionality and is only relevant for very specific use cases, such as complex fulfillment processes where multiple authorizations and captures need to be grouped by the Merchant Reference Number.

To override the default Foxy transaction ID, add an attribute via the API named fx_transaction_id_gateway_override to the cart resource. The value of that attribute is passed to Cybersource as the Merchant Reference Number, also known as the Merchant Reference Code.

For reference, here's the field in the Cybersource portal:

Testing

Obtaining a test account

• Cybersource testing guide

• Cybersource technical documentation

Test card numbers

• Cybersource test card numbers — the testing guide lists the card numbers to use in the test environment.

• Cybersource getting started documentation, which covers simulating error responses using specific order total amounts.

Important notes and caveats

Cybersource limits the number of characters we can send in payment requests, while Foxy's character limits on the checkout are more permissive. When the customer fills out the checkout form, some information may be cut off or special characters removed before being sent to Cybersource. The original data remains in Foxy.

Our view is that it's more important to let the customer check out, with data intact in Foxy, than to reject on an error because the customer put "ext" instead of "x" in their phone field, or included a disallowed character in their company name.

If you'd rather validate the checkout data entry than have values automatically replaced or truncated, you can do so using JavaScript validation.