![]() The fields you will need to add to the Crypt string:įIRST = You are storing Credential to File. Once you have upgraded to protocol 4.00, you will need to submit extra fields to Opayo, in order to let us know that you will be processing transactions from a stored card including any REPEAT transactions that you will take via My Sage Pay or the Shared protocol. This is due to the payment card industry tightening standards, and introducing new processing procedures. TRANSTYPE 3.0 2 UPGRADEIf you wish to store a card number for possible future use, you will need to upgrade to protocol 4.00 - if you do not, unfortunately you will find increasing numbers of transactions decline. This field is ignored for PayPal transactions. Only use when you can provide a valid SCA Exemption reason ThreeDSExemptionIndicator.ģ = Force 3D-Secure checks for this transaction when possible and ALWAYS send for Authorisation, irrespective of rulebase and if the cardholder has failed Authentication. When 3D-Secure checks are possible and rules allow, perform the checks and apply the Authorisation rules.ġ = Force 3D-Secure challenge flow when possible and apply rules for Authorisation.Ģ = Do not perform 3D-Secure checks for this transaction and always Authorise. This is useful when direct and trusted customer contact is established, and you want to override the default security check level.Ġ = Default value. Set this flag to fine tune the 3D Secure checks and ruleset you have defined at a transaction level. Specifically, if you are using Appl圓DSecure=2 to suppress 3D secure checking, this will need to be accompanied by an SCA Exemption: The behaviour of this field has changed in Protocol 4.00. Important: All of these fields are optional Appl圓DSecure field TRANSTYPE 3.0 2 ISOValues derived from the 8583 ISO Standard. Identifies the type of transaction being authenticated. Your assessment of the level of fraud risk for the specific authentication for both the cardholder and the authentication being conducted.įor example, are you delivering goods to the cardholder’s billing address, is this a first-time order or reorder? The account ID, if applicable, of your customer’s account on your website. Information about how you authenticated the cardholder as part of a previous 3DS transaction.įor example, were they authenticated via frictionless authentication or did a cardholder challenge occur?Īdditional information about the cardholder’s account that has been provided by you.įor example, how long has the cardholder had the account on your website? Information about how you authenticated the cardholder before or during the transaction.įor example, did your customer log into their online account on your website, using two-factor authentication, or did they log in as a guest? Simply add these fields to your Crypt string. This includes SCA Exemption and account level information, that will help us ensure your transactions are as frictionless as possible. Once you have upgraded to protocol 4.00, you will be able to submit optional fields to the 3D Secure process. See the API Reference section for more information. DeliveryAddress3, maximum length 50 characters. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |