Depending on your business needs, you may have to send a payment request to your customer by email. A link in this email will redirect the customer to our Checkout in order to complete a payment form.
- How does it work
- Send a payment link through Dashboard
- Send a payment link through API
- Send multiple payment links
How does it work
When you send a Card by Link request to your customers, they will receive an email containing information about their identity and the transaction that you want them to complete. The logo can be customized to your needs, and you will receive a notification when they complete the Checkout process.
Here is an example of the email they will receive in case of a one-off payment:
After clicking on the Checkout button, the customer will be redirected to a SlimPay hosted Checkout, where they will enter their card details to complete the transaction:
Send a payment link through Dashboard
- Login to your Dashboard
- Select Orders. Under the blue drop down button select Card payment by link.
- Fill out the form. You will need to specify:
- Subscriber reference (the client reference)
- First name
- Last name
- Payment reference
- Amount
- Label (optional)
- Execution Date
- Type (a payment can be unique or recurring)
In case of a recurring payment, you will also need to specify: - First card payment date
- Frequency
- Number of recurrent card payments (optional)
- Confirm by clicking the Send the link button
Send a payment link through API
Create an order (https://dev.slimpay.com/hapi/reference/orders#create-orders) containing the type of payment you want and make sure to specify:
- In the subscriber object:
- familyName
- givenName
- sendUserApproval (set it to true)
Send multiple payment links
We currently do not have a way to integrate multiple payment links inquiries in a single file.
However, you can develop a script on your own, calling our API in a repetitive manner in order to send a payment link to multiple customers. If you are developing such script, make sure the API answers after each request, and that each order is indeed created.