Migrating from Secure Acceptance
CyberSource is retiring Secure Acceptance, which the Direct Post and Hosted Page methods depend on. See KA-11531. CyberSource sends each merchant its own sunset date, after which shoppers cannot add a new card with Direct Post or Hosted Page.
This page explains how to move a store to the Microform or Unified Checkout method without shoppers losing the cards that they already saved.
Choosing a method
| Microform | Unified Checkout | |
|---|---|---|
| Card form | The storefront keeps its own payment form, where CyberSource fields replace only the card number and security code inputs. | CyberSource builds the card form and shows it inline on the storefront page. |
| Look and feel | You control the layout and style of the whole form. | CyberSource controls the form. |
| Closest to | Direct Post | Hosted Page |
| Later | The path to digital wallets in a later release. |
Business Center prerequisites
Make sure that Microform or Unified Checkout, Token Management Service and zero-amount authorizations are enabled for your merchant ID. For more information, see Generating Credentials.
Upgrading the plugin
Upgrade the CyberSource plugin to version 3.x or later. For more information, see Backend Integration.
Upgrade the plugin before you change the storefront, because the new storefront needs the Microform or Unified Checkout method, which only version 3.x has. Version 3.x keeps Direct Post and Hosted Page working, so the current storefront keeps working after the upgrade.
Creating the new configuration
In Commerce Manager, create a payment configuration with the provider CYBERSOURCE and the method MICROFORM_CREDIT_CARD or UNIFIED_CHECKOUT_CREDIT_CARD, then activate it and associate it with the store. For the steps and the configuration keys, see Configuring the Plugin.
For Unified Checkout, also set up the card form in the CyberSource Business Center. For more information, see Setting up Unified Checkout.
Changing the storefront
For the code samples, see Frontend Integration.
From Direct Post to Microform
- Replace the card number and the security code inputs with the Microform containers, such as
#number-containerand#securityCode-container. - Keep the expiry date inputs.
- Remove the form post to CyberSource and the parsing of its response.
- Load the library from the instructions, call
createTokenwhen the shopper submits the form, and post the transient token topaymentinstrumentformastransient-token, with the billing address inbilling-address.
From Hosted Page to Microform
- Remove the redirect to the CyberSource page.
- Remove the pages for
return-hrefandcancel-href, and the receipt handling. - Add a card form with the Microform containers.
- Load the library from the instructions, call
createTokenwhen the shopper submits the form, and post the transient token topaymentinstrumentformastransient-token, with the billing address inbilling-address.
From Direct Post or Hosted Page to Unified Checkout
- Remove the card fields (Direct Post), or the redirect and its
return-hrefandcancel-hrefpages (Hosted Page). - Submit
requestinstructionsformwith the shopper's country incountryinstead of the billing address. - Add two containers, one for the payment button and one for the card form, such as
#uc-buttonsand#uc-form. - Load the library from the instructions, call
mount, and post the transient token topaymentinstrumentformastransient-token. The card form collects the billing address.
Content Security Policy
If the storefront sets a Content Security Policy, allow the CyberSource JavaScript library from the client-library URL. For more information, see Frontend Integration.
Moving saved cards to the new configuration
Run this step after the new storefront goes live. It moves the cards that shoppers saved with Direct Post or Hosted Page to the new configuration. Those cards and orders that are still in progress then reserve, charge and refund through it. Shoppers do not enter their cards again.
Find the
UIDPKof the old and the new configuration, by name or by GUID:SELECT UIDPK, GUID, CONFIGURATION_NAME, PAYMENT_PROVIDER_PLUGIN_ID FROM TPAYMENTPROVIDERCONFIG WHERE CONFIGURATION_NAME IN ('<old configuration name>', '<new configuration name>');SELECT UIDPK, CONFIGURATION_NAME FROM TPAYMENTPROVIDERCONFIG WHERE GUID = '<configuration GUID>';Move the saved cards:
UPDATE TPAYMENTINSTRUMENT SET PAYMENTPROVIDERCONFIG_UID = <new config UIDPK> WHERE PAYMENTPROVIDERCONFIG_UID = <old config UIDPK>;
These statements run on every database that Self-Managed Commerce supports. Cards saved with Direct Post or Hosted Page keep working under the new configuration, because plugin 3.0.0 sends their tokens the same way as before.
Disabling the old configuration
After you move the saved cards, you can disable the old configuration in Commerce Manager.
Rolling back
Point the saved cards back to the old configuration:
UPDATE TPAYMENTINSTRUMENT SET PAYMENTPROVIDERCONFIG_UID = <old config UIDPK> WHERE PAYMENTPROVIDERCONFIG_UID = <new config UIDPK>;Assign the old configuration to the store again.
What shoppers see
| From | To | What changes for the shopper |
|---|---|---|
| Direct Post | Microform | The card number and security code fields come from CyberSource and are styled like the rest of the form. |
| Hosted Page | Microform | The shopper enters the card on the storefront instead of on a CyberSource page. |
| Direct Post | Unified Checkout | The shopper enters the card in a form that CyberSource builds, within the storefront payment page. |
| Hosted Page | Unified Checkout | The CyberSource card form shows within the storefront payment page instead of redirecting the user to a separate CyberSource page. |
In every case, shoppers keep their saved cards.