Customer initiated payments with saved cards

When charging a customer, where the customer is present in the payment flow (Customer Initiated Transaction), coming PSD2 regulations require that the card holder is strongly authenticated (e.g. 3D Secure), except for some exemption cases. Read more about PSD2 here: https://blog.reepay.com/psd2-strong-customer-authentication/ This will affect the use of saved cards for easy checkouts, as the card cannot be used without Strong Customer Authentication (SCA) in the card holder present scenario.

To remedy this, Reepay Checkout now offers an option to start a checkout charge session with a saved card (card-on-file). The customer will be sent directly to Strong Customer Authentication and directly back afterwards with success or error indication. In some cases SCA is not necessary, so the customer will not be prompted with any request for information during the payment session. See: https://docs.reepay.com/reference#card-on-file

Notice that Merchant Initiated Transactions, that is payments initiated by the merchant (or a party acting on behalf of the merchant - e.g. Reepay), where the customer is not present in the payment flow, are out-of-scope for SCA. In this scenario payments with saved cards can still be performed using the Charge API (https://reference.reepay.com/api/#charge).

Cheers, Reepay

PayPal

Reepay now supports PayPal as a payment method for one-off payments.

According to several surveys, 59% of PayPal users have abandoned a transaction because PayPal wasn’t there.

Businesses can establish trust with consumers by offering preferred payment methods; 44% are more likely to trust and shop with businesses with a preferred payment provider and good payments process.

To setup PayPal follow this help article: https://intercom.help/reepay/en/articles/3315950-how-to-configure-paypal

Cheers, 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.

Dunning grace period

Dunning plans can now be configured with an optional grace period before the dunning process starts. During the grace period retrying will be performed if the payment method has suffered a potentially recoverable soft decline, e.g. insufficient funds. It can be configured if dunning should start immediately for irrecoverable hard declines, e.g. expired credit card.

The grace period can be configured for dunning plans in the Administration: Configuration → Dunning Management

Cheers, Reepay

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.

Support for Klarna Pay Later and Klarna Pay Now

Reepay now supports Klarna Pay Later and Klarna Pay Now as payment types for one-off payments. Contact Reepay support at support@reepay.com to get started with Klarna payments.

Cheers, Reepay

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

Webhook overview select all

In the Administration webhook overview it is now possible to select all (only up to 100 though) webhooks and perform update, resend or disable operation.

Webhook disable bug

A bug preventing to disable retrying webhooks has been squashed.

Show Previous Entries