Intelligent Routing

Reepay's Intelligent Routing makes it possible for you to minimize your acquiring costs. You may have one acquirer agreement with low prices for domestic cards while another agreement gives you lower prices for international cards. By using Reepay Intelligent Routing the payment is automatically routed to the acquirer with the lowest cost. The Intelligent Routing is based on our new Fee Configuration, where you easily can configure your acquiring fees.

If you are interested in using this functionality, please contact your Reepay contact person or ask in the chat, to get more details and pricing on this new feature.


Checkout optional save card

It is now possible to let the customer choose whether to save card in a charge session instead of fixing this for the session with the recurring parameter. When creating a session the following parameters can now be used:

  • recurring_optional - If defined it will be the default selection for a save card checkbox. That is, if set to true the option will be default selected, and vice versa for false.
  • recurring_optional_text - Can be used to control the label for the checkbox. The default is "Save card".

Example with recurring_optional=true and the default label:

If the customer chooses to save card, the payment_method parameter will be returned from the session and the charge object (https://reference.reepay.com/api/#the-charge-object) will have the attribute recurring_payment_methodFor details see the create charge session API call: https://docs.reepay.com/reference#createchargesession

Cheers, Reepay

Card verification

We are happy to announce a new great feature called Card Verification.

The Card Verification operation checks the validity of a stored card without making an actual authorisation on the card. That is, the check will not be visible to the cardholder on their bank statement.

This allows you to check a card's validity before doing an actual charge on the card.

Currently this operation is only supported for the following acquirers: Nets, Swedbank, Bambora and Valitor. The operation is supported by our API, read more here: 

https://reference.reepay.com/api/#card-verification

Best regards
The Reepay Team

Resurs Bank Integration

We have partnered with Resurs Bank and are now ready with an integration. Resurs Bank is a Nordic finance company that offers attractive installment payment solutions. Do you want to hear about the opportunities? Contact Michael Abild at michael.Abild@resurs.dk or Thomas Petersen at thomas.Petersen@resurs.dk from Resurs Bank.

Subscription trial for fixed period scheduling

It is now possible to use trial for fixed day scheduling, e.g. billing on the first of every month. If trial is used the subscription will be in trial and billed at the end of the trial period. The billing at the end of the trial period depends on the configured partial period handling. If proration is used, a prorated invoice will be made for the remaining billing period until the fixed scheduling day.

As an example consider a subscription plan with billing every first of the month and a seven day trial period. If a customer signs-up on the 14th, the trial will run until the 21st where the customer will be billed prorated for the period 21st to end-of-month.

To configure trial on a plan go to: Configuration → Plans → Create/supersede → Trial.

Cheers, Reepay

API TLS upgrade

If you have an API integration to Reepay, this information might be important to you.

To keep your API integration with Reepay secure, we have planned to phase out support for old technologies: SHA-1, TLS 1.0, and TLS 1.1. (These protocols and TLS 1.2 power the 'Secure' in 'HTTPS'.)

Why

SHA-1 is one of the algorithms you can use to authenticate who you’re talking to. It’s now considered dangerously weak, and might allow an adversary to spoof their identity. This is why all modern browsers have stopped accepting SHA-1 certificates.

TLS 1.0 and 1.1 ensure that your communications stay private. In order to do this, they generate a series of random bytes used to encrypt your connection. TLS 1.0 provides two ways of doing this (CBC and RC4), but several vulnerabilities have been discovered in both of them (including BEAST and the RC4 biases). If you kept using old versions of TLS, someone could theoretically sniff your connection.

As a result the internet is moving towards SHA-2 and TLS 1.2. These technologies have few known attacks and were subject to more rigorous security design than their predecessors.

What this means to you

The upgrade process will be seamless for most users. Most frameworks and operating systems support TLS 1.2 out of the box without any changes required, but older clients might be affected, e.g. Java 6. To test if your client supports TLS 1.2, you can make a test HTTPS GET request for the following url:

https://sandbox.reepay.com/api/helloworld

If your client supports TLS 1.2 you will receive the a text response with content Hello world. Otherwise an error will be raised by the client.

If your client does not support TLS 1.2, you will need to make the necessary upgrades to your environment.

Don't hesitate to contact us at support@reepay.com if you have any questions.

Timeline

Reepay will only support TLS 1.2 by the 7th of May 2020

Show Previous EntriesShow Previous Entries