To find out more about FinDock PayLinks, please visit our website.
Once you have configured PayLinks, using payment links is very simple.
To use payment links, just:
- Copy the payment link from the installment Pay URL field.
- Share the payment link with the payer.
- After the payer completes the payment, successfully or unsuccessfully, FinDock automatically updates the installment in Salesforce.
The payment link can be shared through any online channel, e.g. email, SMS, messaging apps, etc. using Salesforce CRM out-of-the-box features and additional solutions like Pardot and Marketing Cloud.
A payment link is unique for a given installment and can only be used once for payment.
Payment link URL details
The payment link URL has three components:
- Base URL (depending on type of org)
- Hashed Salesforce Org ID
- Installment GUID
- Base URL:
- Hashed Salesforce Org ID:
- Installment GUID:
The payment link takes the payer to your PayLinks landing page. This page is populated with data from your PayLinks configuration and the installment:
|Installment Field||Payment form field||Description||Example|
|GUID||(embedded in URL)||Generated by FinDock|
|Due date||Due Date||Due date for the payment||15-04-2021|
|Amount Open||Amount||Pre-filled amount to be paid||10.00|
|Amount Open||-||If the value is 0, a specific message is shown to the user.||Payment already completed. (Message can be customized)|
|CurrencyISOCode||Amount||Currency used on the payment form||€|
|Payment Method||Select a payment method||If the installment has a payment method, that method is pre-selected but can be changed by the payer.||Credit Card|
|Bank Statement Description||Description||Payment purpose. With most payment processors, this value also appears on the payer’s bank account record.||Membership fee for Your Organization for March 2021|
PayLinks and the Payment API
The PayLink URL is included in the
GET /Installment response and follow-up status notifications for one-time installments as well as future installments of recurring payments. For further information, see the API reference guide.