Using FinDock PayLinks

Once you have configured PayLinks, using payment links is very simple.

To use payment links, just:

1. Copy the link from the Pay URL field on the one-time (installment) or the Setup URL field on a recurring payment (Recurring Payment, Recurring Donation, or Gift Commitment).
2. Share the link with the payer.
3. After the payer completes the request, successfully or unsuccessfully, FinDock automatically updates the related data in Salesforce.

The payment link can be shared through any online channel, e.g. email, SMS, messaging apps, etc. using out-of-the-box Salesforce features and additional solutions like Pardot and Marketing Cloud.

A payment link is unique for a given record, and for installments, the payment link can only be used once to pay the open amount on the installment.

PayLink use cases

For one-time payments, PayLinks deliver a personalized and pleasant payment experience. Leveraging data directly from Salesforce CRM, you can be sure the payer is presented with meaningful (and correct) information about the payment. The PayLink itself also opens up a number of possible deliver channels, giving your payment operations more flexibility in delivery.

For the payer, a one-time PayLink eliminates much of the common frictions around completing payments. Pre-filled details and pre-selected options remove uncertainty. And when the payment link arrives in the payer's preferred channel, it's even easier to get the payment done.

This personalized, smooth experience is also a part of the recurring PayLink use case. For recurring payments, however, the PayLink purpose is quite different compared to one-time payments. With recurring PayLinks, you are proving an easy way for the payer to update an existing recurring payment.

Why would a payer want to update a recurring payment? One of the primary uses cases for updates is expired cards. For example, you can use Salesforce automation to trigger send a recurring PayLink when the payer's credit card is close to expiration (based on the expiration details on the payer's Payment Profile record).

Recurring PayLinks can also be used in scenarios like:

• Payer wants to switch bank accounts for a recurring direct debit
• Payer wants to use a different card
• Organization wants to encourage switch to a different payment method or processor

Payment link URL details

The payment link URL has three components:

• Base URL (depending on type of org)
• Hashed Salesforce Org ID
• Record GUID

For example, let's use this PayLink: https://link.test.findock.com/pay/1xyzzabcd2/b3f1a221-1234-fc0c-e13f-abeee5b3509d

In that example, we have:

• Base URL: https://link.test.findock.com (sandbox org)
• PayLink type: payfor one-time and setup for recurring
• Hashed Salesforce Org ID: 1xyzzabcd2
• Record GUID: b3f1a221-1234-fc0c-e13f-abeee5b3509d

The payment link takes the payer to your configured PayLinks page. This page is populated with data from your PayLinks configuration and the link-specific Salesforce record.

PayLink mapping for Installment

PayLink page field mapping for one-time payments using Installment records.

PayLink mapping for Recurring Payment

PayLink page field mapping for FinDock Standalone as source.

PayLink mapping for Recurring Donation

PayLink page field mapping for Salesforce Nonprofit Success Pack as source.

PayLink mapping for Gift Commitment

PayLink page field mapping for Salesforce Fundraising as source. The field mapping uses both Gift Commitment and Gift Commitment Schedule.

PayLinks and the Payment API

The PayLink URL is included in the response for GET /Installment and GET /Recurring, as well as in follow-up status notifications for one-time installments and future installments of recurring payments. For further information, see the API spec.