CONTENT

Overview

In order to be complaint with the PSD2, Amazon Pay introduced SCA for their transactions.

The SCA Upgrade introduces a “Confirmation Flow” to handle Multi-Factor Authentication (MFA) when it is required.

When MFA is required, the Confirmation Flow shows the credit card issuer’s MFA challenge to the buyer. After the buyer interacts with the Confirmation Flow (for example, completes the MFA challenge), the buyer is returned to the merchant’s site (for example, order confirmation page).

Please update the AmazonPay checkout workflow after a buyer initiates their order completion and before you call the Authorize Operation.

Changes

New JavaScript function confirmationFlow()

Due to MFA, it is necessary after a succesful confirmation of an order to start a new call, the ConfirmationFlow.

To start the workflow, please

• execute a Confirm on the order on the BNP Payment platform, after you receive a result

• start the confirmationFlow in case of success with "confirmationFlow.success()"

• in case of failure "confirmationFlow.error()" aborts the process.

Implementation of the new Javascript call is shown below. This has been optimized for our BNP merchants.

function confirmationFlow()
{
	// Get resultCode from BNP call AmazonAPA.aspx, EventToken: COD
	var resultCode_BNP = Payment platform call to get the ResultCode from the Confirm, AP call COD or SCO.
	// Your AmoazonSellerID / AmazonMerchantID
	var amazonSellerId = 'Your_SellerID';
	// Amazon order reference generated by Address Widget
	var orderReferenceId = 'Your_Order_Reference';
	//Initiate confirmation flow
	OffAmazonPayments.initConfirmationFlow(amazonSellerId, orderReferenceId, function (confirmationFlow)
		{
			if(resultCode_BNP = '00000000')
			{
				confirmationFlow.success(); 
			}
			else
			{
				confirmationFlow.error();
			}
		}
	);
}

Please also refer to https://developer.amazon.com/de/docs/eu/amazon-pay-onetime/sca-upgrade.html for additional guidance.

Merchant should be able to handle BNP's redirection ( URLSuccess / URLFailure ) with the result of the MFA Challenge.

URLSuccess / URLFailure for ConfirmOrderDetails (COD) and SetOrderDetails and ConfirmOrder (SCO) call

On "Order Now" the merchant has to send the URLSuccess and URLFailure in the calls (EventToken=SCO | COD), because the redirect is executed after the MFA challenge.

After "Order Now" the Confirm (EventToken=SCO | COD) is executed on the payment and then the redirect to the challenge takes place using the JavaScript code shown above.

AmazonAPA.aspx

The following event calls at the BNP Payment platform are affected by the changes. Please make sure to include the new parameters.

User Flow and Sequences

Flow

1. Clicks on AmazonPay button to sign-in

2. Chooses an address from the widget

3. Chooses payment method from the widget

4. Confirms the order

Option 1: SCO

This is the recommended option.

Option 2: SOD and COD

1. The first call is to be made to ConfirmationFlow - with this, AmazonPay can handle the MFA if required. Here is confirmationFlow error/success to be set. Reference to the Amazon Pay Widgets.js file already used for the other widgets.

2. Call SetOrderDetails (SOD) including OrderTotal

3. Call ConfirmOrderDetails (COD) set URLSuccess/URLFailure parameter with a returnURL value

Option 3: MFA Failure

Status =>Abandoned:

Status =>Failure:

1. If the customer fails or abandons the challenge, the customer is redirected to the URLFailure.

2. Logout the user.

3. Cancel the order by calling “Reverse.aspx”

Cancel Order by Calling “Reverse.aspx“

In order to reverse a complete order with Amazon Pay with the function „CancelOrderReference“, please request to https://paymentpage.axepta.bnpparibas/reverse.aspx

More and detailed information is found in the official BNP documentation here: Amazon Pay Manual

Status

If the MFA is successful, the redirection is done to URLSuccess , if not the redirection is done to URLFailure .