The three gateway specific fields are stored_credential_usage, stored_credential_transaction_id, and stored_credential_initiated_reason. Using gateway specific fields will give you more fine grain control over what it sent, however you will need to store additional data from the gateway that is returned from the gateway in a gateway specific response field. You can either use Spreedly’s native support which is less hands on, or use gateway specific fields. Your Merchant Code (may be called Merchant ID)įor Worldpay there are two options for sending stored credential fields. Order_id is used to populate the required attribute orderCode of the element for Worldpay. More information can be found in step 7 of the 3DS 2.0 guide During 3DS 2.0 transactions you may need to pass additional parameters with completion calls. Worldpay may give you these values as API key, API ID and Org Unit ID respectively.
#WORLDPAY INSTALLATION ID UPDATE#
After successfully completing this step you will need to update your gateway fields to include hmac_secret, issuer_id and org_unit_id. Using Visa and Mastercard cards retained with Spreedly falls under Stored Credentials regulations.īefore using Worldpay for 3DS 2.0 transactions you must first onboard through Worldpay.
#WORLDPAY INSTALLATION ID FULL#
In addition, if you tell WorldPay you are working with Spreedly you can usually bypass the need toĭo a full test transaction before being pushed into production. You’ll need to login and turn that setting off. There is a setting in your WorldPay Merchant Interface called Capture Delay which is set to on byĭefault within Worldpay. For US based acquiring accounts, see WorldPay US.
0 kommentar(er)
