Strong Customer Authentication

Riverty Strong Customer Authentication

In order to reduce the number of fraud transactions and making only payments more secure, Riverty introduced Strong Customer Authentication (SCA).
SCA adds an extra layer of security by using a third party like a bank to verify the end-customer prior or during an online payment. Riverty currently offers this functionality in Sweden, Norway, Denmark, Finland, and Netherlands.
You will find an overview of the eID methods used per country below

Riverty Strong Authentication is not a standard feature and could be enabled upon request. Please contact support for more information.

Once it has been enabled, the existing flow looks slightly different.
As per the current flow you could expect either a status ‘success’ or ‘rejected’
For Strong Customer Authentication a 3rd status will be added to the flow. The status is called ‘pending processing.’
For this solution, Riverty will decide for which orders and customers SCA will be triggered. This decision is based on a number of parameters, such as order amount, shipping address and other fraud and risk related variables.

1. Customer selects Riverty in the checkout and clicks ‘Pay’ to finalize a purchase
2. Merchant does a Authorize payment request to Buckaroo with customer and order details
3. Riverty API decides based on merchant configuration if SCA is required to finalize the purchase. If SCA needs to be performed Riverty API sends a response with “outcome” : “Pending processing”
4. Buckaroo returns a redirect URL, where the Merchant will have to redirect the consumer to with a page with further instructions to complete verification
5. After verification is completed the end-customer is redirected back to Merchant’s web page.
6. The Merchant will automatically receive an updated status push message either ‘success’ or ‘rejected’
   o If the order status is accepted, order is finalized
   o If the order status is cancelled, expired or pending - order is not finalized. After 15 minutes the pending order times out, so a new try with a new order number is required.

Example of a Pending Processing Status

{
  "Key": "6B39EAFD858949EAAA5************",
  "Status": {
    "Code": {
      "Code": 791,
      "Description": "Pending processing"
    },
    "SubCode": null,
    "DateTime": "2023-12-20T15:16:13"
  },
  "RequiredAction": {
    "RedirectURL": https://checkout.buckaroo.nl/html/redirect.ashx?r=8DE0DE55F7C24DF0BBC7C***********,
    "RequestedInformation": null,
    "PayRemainderDetails": null,
    "Name": "Redirect",
    "TypeDeprecated": 0
  },
  "Services": null,
  "CustomParameters": null,
  "AdditionalParameters": null,
  "RequestErrors": null,
  "Invoice": "BMSWH6TK1***********",
  "ServiceCode": "afterpay",
  "IsTest": true,
  "Currency": "EUR",
  "AmountDebit": 501.0,
  "TransactionType": "I038",
  "MutationType": 3,
  "RelatedTransactions": null,
  "ConsumerMessage": null,
  "Order": null,
  "IssuingCountry": "NL",
  "StartRecurrent": false,
  "Recurring": false,
  "CustomerName": "John Doe",
  "PayerHash": null,
  "PaymentKey": null
}

}