---- dataentry gateway ----
type                   : gateway # do not change this line
name                   : CyberSource Secure Acceptance Web/Mobile
countries              : 
support-added          : 1.1
support-removed        : 
auth-net-emulation     : no # enter "yes" or "no" (without quotes)
supports-3dsecure      : yes # enter "yes" or "no" (without quotes)
supports-multicurrency : yes # enter "yes" or "no" (without quotes)
gateway_url            : http://www.cybersource.com/products/payment_security/secure_acceptance_web_mobile/
----




====== CyberSource Secure Acceptance Web/Mobile ======
<WRAP center round important 90%>
Subscriptions are not supported with CyberSource SA Web/Mobile at this time. If you intend to sell subscriptions with your FoxyCart store, you will need to make use of another payment gateway.
</WRAP>
===== Setting Up CyberSource Secure Acceptance Web/Mobile for FoxyCart =====

<WRAP center round important 90%>
**Important:** Ensure all the following steps are completed for your CyberSource account, as without it transactions could fail to complete correctly.
</WRAP>

  - Login to the **CyberSource Business Center**: https://ebc.cybersource.com/ebc/login/Login.do
  - Navigate to **Tools & Settings** -> **Secure Acceptance** -> **Profiles**
  - Create a new profile. If you already have a profile set up, open it and continue to the next step.\\ {{ :gateways:cybersource-create-profile.png?direct&300 |}}
  - From within your profile, copy the **Profile ID** found towards the top of the page into the **Profile ID** field in FoxyCart administration payment settings section.\\ {{ :gateways:cybersource-profile.png?direct&300 |}}
  - Go to the **Payment Settings** section and select the card types and currencies you need.\\ {{ :gateways:cybersource-payment-settings.png?direct&300 |}}
  -  Go to the **Notifications** settings and set the **Merchant Post URL** to be ''https://YOUR-FOXYCART-STORE-DOMAIN/ipn.php'' - changing it to match your own FoxyCart store domain. For example, if your FoxyCart store domain was ''example.foxycart.com'', you would set the Merchant Post URL to be ''https://example.foxycart.com/ipn.php''. If it was a custom subdomain like ''secure.example.com'' the URL would be ''https://secure.example.com/ipn.php''. \\ {{ :gateways:cybersource-notifications.png?direct&300 |}} \\ If you're letting FoxyCart send your receipts for you, you'll also want to ensure the "Email Receipt To Customer" checkbox is unchecked.
  - In the **Security** section, create a new key. If you already have an existing key, open it and proceed to the next step.\\ {{ :gateways:cybersource-create-new-key.png?direct&300 |}}
  - Looking at your key, copy the **Access Key** and **Secret Key** into the matching fields within the payments section of the FoxyCart administration.\\ {{ :gateways:cybersource-key-created.png?direct&300 |}}
  - From the **Profile** section, click the "Promote to Active" button in the top right hand corner to make it active.
===== Testing =====
==== Obtaining a Test Account ====
Contact CyberSource Secure Acceptance Web/Mobile for info. <wrap help>Know more? Feel free to edit this page with info.</wrap>
==== Test Card Numbers ====

  * Visa: ''4111 1111 1111 1111''
  * MasterCard: ''5555 5555 5555 4444''
  * American Express: ''3782 822463 10005''
  * Discover: ''6011 1111 1111 1117''
  * JCB: ''3566 1111 1111 1113''
  * Diners Club: ''3800 0000 0000 06''
  * Maestro International: ''6000 3400 0000 9859''
  * Maestro Domestic: ''6759 1800 0000 5546''

To simulate processor-specific error messages, choose your payment processor here:
http://www.cybersource.com/developers/test_and_manage/testing/legacy_scmp_api/



===== Troubleshooting & Interpreting Response Codes =====
Contact CyberSource Secure Acceptance Web/Mobile for info. <wrap help>Know more? Feel free to edit this page with info.</wrap>



===== Important Notes and Caveats =====

==== Possible Action: Datafeed Handling ====

At the time of the customer completing the transaction - we don't necessarily know whether the transaction was completed yet or not. We instead rely on a notification from the gateway after the checkout has been completed to confirm whether the transaction was approved or not. To handle this, transactions are initially marked as pending, and when we get a confirmation from the gateway on the result of the transaction, we update it accordingly. Each time the status changes, a datafeed will be sent to your endpoint if configured with the transaction details and the ''status'' node will be present.

The ''status'' node can contain one of three different values: ''pending'', ''approved'' or ''rejected''. Depending on the types of actions you're needing to perform at your datafeed endpoint, you need to make sure the appropriate status value is present first.

===== User Notes and Experiences =====
<wrap tip>If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date.</wrap> We reserve the right to edit or remove comments that don't add value to this page.