Findock v1 and v2

Estimated reading: 2 minutes

Findock is available in version 1 and version 2. The main difference between the versions is mainly in the speed of handling an API request.

Findock v1

The image above shows the flow of an API request to Findock v1. In summary, it means that all flows and actions within Salesforce are executed immediately after the API request. This includes processing the Contact and Account, storing transaction objects and submitting and processing the request to the Payment Service Provider. This ensures that it can take a long time before CampaignSuite receives a response from the API.

Findock v2

With Findock v2, CampaignSuite receives a response from Findock as soon as possible so that the API call can be completed very quickly. While the donor is paying, all necessary actions are performed behind the scenes in SalesForce, including creating / adjusting Contacts and Accounts. As soon as these actions are completed, Findock sends a signal to CampaignSuite via a Webhook so that all necessary IDs can be stored there.

Schematically it would look like this:

Contact your Salesforce implementation party to do a migration from v1 to v2 in SalesForce. Within CampaignSuite you can easily switch between v1 and v2 without additional settings.

Webhook

Findock v1 and v2 both use Webhooks. This means that they both give a signal back to the website when a status of a payment changes. CampaignSuite receives these signals and processes them in the submissions of Gravity Forms. This way you will always see the correct status of a payment with the submissions.