Card aliases and tokens replace sensitive data such as a bank card number with references (aliases/tokens). The card data authorized to be stored is saved in an encrypted format in a secure SlimPay environment.
The SlimPay electronic signature module sets up aliases.
This article has all the information on:
The customer path
To streamline the application process, SlimPay has invested heavily in its customer interfaces to provide a friction-free application experience.
There are two steps in the card alias setup process:
Step 1 – Entering bank information
The account holder is asked to enter the number, expiry date and CVC on their bank card.
Step 2 – Validating the data sent to the merchant
SlimPay Checkout informs the debtor that the bank information has been sent to the merchant and the alias card has been set up.
NB: The alias card reference cannot be generated by the merchant. This reference can only be provided by SlimPay.
When creating an alias via Checkout, your client is informed in the event of an invalid entry of the card number or CVC. Other technical errors may arise, for example when the card has been declared stolen.
Request for information
When a card alias is created, in most cases your customers will not see any transaction line on their bank account statement with the exception neo-banks customers (Boursorama, Revolut, N26 ...). Those should see a 1 euro authorization on their bank statement. This purpose of this authorization is to verify the existence of the used card, and should eventually disappear after 7 days.
You can also opt for a 0 euro authorization, also called request for information, to avoid the situation where the card is rejected for insufficient funds at the time of the verification. The card alias creation will trigger a request for information, and an amount of 0 euro will replace the 1 euro default amount. To enable this feature, please reach out to our support team.
Card update request
For merchants with a subscription-based business model, ensuring the continuity of their recurring revenues is crucial. When accepting payment by card, merchants are exposed to passive churn, as cards expire. To avoid that type of churn, SlimPay allows merchants to send a « card update request » to their clients, so that they can update their card details.
How does it work?
Merchants can customize the communication sent to their clients either by providing a text, or by providing SlimPay with a template to be used (HTML or CSS) to follow their graphic charter. It is also possible to customize the email sender by delegating a sub-domain name to SlimPay. (ex: checkout.mymerchant.com)
Each month, SlimPay identifies all cards that have been used in the past 12 months and that will expire at the end of the month. Once identified, SlimPay sends on behalf of the merchant an email to all concerned cardholders, inviting them to update their card details. The email contains a link to the Checkout where they can enter their new card numbers. SlimPay will then create a new card alias that will be used for the future recurring payments.
SlimPay is planning one email at the beginning of the month and two reminders (middle and end of the month) prior to the card expiration to increase chances to get the updated card number.
What are the benefits?
- No revenue losses as there is no discontinuity in the recurring payments collection
- No passive churn due to the card expiration
- Client satisfaction is ensured as the service provided by the merchant is not stopped
Card alias migration
For merchants already accepting card payments via their previous payment service provider, SlimPay can migrate all the card aliases to ensure service and payment continuity.
For the merchant, this means gathering all the card payment data from its previous supplier, then combining it with the other information in its possession (e.g. card holder name) and sending it to SlimPay in a specified format.
Once SlimPay has received all of the required information, the files are checked and if they meet the criteria, the card aliases are then set up in the SlimPay base. This will allow merchants to quickly collect payments from their customers.
Please note that SlimPay only deals with card alias migration and not payment schedules which are handled by the merchant’s individual system.
How does it work?
Below you’ll find the description of card alias migration flows:
- No disruption to service: Easily migrate all of your customers’ existing card aliases to ensure that future payments associated with the card aliases are collected.
- Power: Migrate all of your customers’ card data with no restrictions on volume.
- Fast migration: Four weeks is all it takes to migrate card aliases, from reception of the data from your previous PSP.
- A secure process: The security of customer card data is guaranteed
- Bank cards, Visa and MasterCard are supported.