PSD2 and Strong Customer Authentication

The deadline for PSD2 is approaching, which means Strong Customer Authentication (SCA) will become mandatory within the EU. Danish issuers will require SCA by January 11, 2021. For details on PSD2 and SCA see: https://docs.reepay.com/reference#strong-customer-authentication

Reepay will make sure all accounts are ready for SCA by enabling 3D Secure and/or Secured by Nets on those accounts not already using SCA.

The newest version of 3D Secure (version 2) supports a frictionless authentication flow, where the customer is not presented with any challenges (two-factor authentication). For issuing banks to make a decision on whether a frictionless authentication can be granted, they will need information about the customer and the context of the payment. Some of this data is provided by Reepay, e.g. customer browser information, but some of the data needs to be provided by you the merchant. 

The data is not mandatory, but we urge you to consider sending the additional information to maximize the chance of a frictionless authentication flow. For details on sending SCA data see: https://docs.reepay.com/reference#strong-customer-authentication

Merry Christmas, Reepay

SCA support in hosted pages and Reepay Token

In preparation for the coming PSD2 regulatory changes (September 14th), Reepay hosted pages and Reepay Token now supports Strong Customer Authentication (SCA) (3D Secure and Dankort Secured by Nets).

No action is required by you as a merchant. SCA will be enabled by us for all merchants, not already using SCA for Checkout, before September 14th.

New user groups

User groups in the administration have been changed to better accommodate for the needs of our customers. The new user groups are more intuitive as they more closely relates to the functionality accessible in the left menu. It is also possible to define more fine grained permissions, e.g. whether specifically refunding is allowed. The screendump below shows the new user group edit dialog.

Metadata in mails

It is now possible to access metadata in mail templates. E.g. if customer metadata contains shoe_size key and value it can be accessed in the template as:

{{customer.metadata.shoe_size}}

Metadata is available as

customer.metadata
subscription.metadata
plan.metadata
invoice.metadata

and add-on metadata as a parameter in the list of subscription add-ons subscription.add_ons[].metadata. Example iterating through subscription add-ons:

{{#subscription.add_ons}}
Name: {{name}}<br/>
License plate: {{metadata.plate}}<br/>
{{/subscription.add_ons}}

For details on Mustache templating see: https://mustache.github.io/mustache.5.html

New payment method added event type

A new event type (`customer_payment_method_added`) has been added for the event that a new payment method has been added to customer. The event can be used with webhook to register payment method after a Checkout recurring session flow, or a charge flow, with the option to store payment method for later use.

To receive the webhook the event type must be selected in webhook configuration. This can be done either in the Administration or using the API.

Show Previous EntriesShow Previous Entries