Simple Order API Field: payerAuthEnrollService_challengeCode=04.REST API Field: consumerAuthenticationInformation.challengeCode=04.To minimise declines from Issuers, we suggest that you pass the following field within your Payer Authentication Enrolment 2.0 requests: Your customer will see a Payer Authentication window and will be prompted to enter the One-Time Password. Step-up Challenged: where the issuer will be requesting a step-up and would also be sending a One-Time Password (OTP) to your customer.You will be able to see a successful example of this behaviour in the Business Center by seeing a Payer Authentication Validation in green (pa_validate.reason_code=100, pa_validate_eci=05 or 02). Your customer will see a Payer Authentication window but will not ultimately be challenged. Step-up Frictionless: where the issuer will be requesting a step-up but would ultimately not send a One-Time Password (OTP) to your customer.You will be able to see a successful example of this behaviour in the Business Center by seeing a Payer Authentication Enrollment call in green ( pa_enroll.reason_code=100, pa_enroll_eci=05 or 02). Your customer will not see any Payer Authentication windows through their checkout experience. Frictionless: where the issuer simply do not wish to step-up the customer.Note: Payer Authentication provides three types of experience to the customers as follows: If the "Establishment of the Relationship" was performed with Payer Authentication 2.0, you will be able to use your token (or Network Transaction ID) for both CIT and MIT transactions.You will only be allowed to perform CIT transactions up until October 2022. If the "Establishment of the Relationship" was performed with Payer Authentication 1.0, you should not be using your token (or Network Transaction ID) for any MIT transactions.If the "Establishment of the Relationship" was performed without Payer Authentication, you should expect to receive a decline by the issuer.If you intend to use your token for MIT transactions, then you will need to be using Payer Authentication 2.0 during the "Establishment of the Relationship".įailure to be compliant will generate an increase of soft declines with a Reason Code 478 (Strong Customer Required) and of Hard Declines with a Reason Code 203 (General Decline by the Processor).As such, we would highly recommend to proactively update your implementation as soon as possible to Payer Authentication 2.0. However, note that Payer Authentication 1.0 will no longer be available by October 2022. 0 during the "Establishment of the Relationship". If you intend to solely use your token for CIT transactions (when the customer is initiating the transaction), then you may use Payer Authentication 1.0 or Payer Authentication 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |