# FinDock Knowledge Base

> The knowledge base provides comprehensive product documentation for system integrators, administrators and end users.

## Table of contents

 - [Can I accept donations from organizations through Giving Pages?](https://docs.findock.com/faq/can-i-accept-donations-from-organizations-through-giving-pages.md)
 - [Can I deploy Giving Pages from sandbox to production?](https://docs.findock.com/faq/can-i-deploy-giving-pages-to-a-production-org.md)
 - [Can I replace an existing target?](https://docs.findock.com/faq/can-i-replace-an-existing-target.md)
 - [Do PCI-DSS 4.0 requirements apply to FinDock Giving Pages?](https://docs.findock.com/faq/do-pci-dss-4-0-requirements-apply-to-giving-pages.md)
 - [Does FinDock support Enhanced Domains?](https://docs.findock.com/faq/does-findock-support-enhanced-domains.md)
 - [Does FinDock support translations?](https://docs.findock.com/faq/does-findock-support-translations.md)
 - [Integrating with Experience Cloud](https://docs.findock.com/api/integrating-with-experience-cloud.md)
 - [Can I change the time when automated payment schedules run?](https://docs.findock.com/faq/can-i-change-when-auto-collect-payment-schedules-are-run.md)
 - [Can I use the free Salesforce Integration user license with FinDock?](https://docs.findock.com/faq/can-i-use-the-free-salesforce-integration-user-license-with-findock.md)
 - [Choosing a Bacs Direct Debit solution](https://docs.findock.com/faq/choosing-a-bacs-dd-solution.md): FinDock provides several options for collecting Bacs Direct Debit payments
 - [Does a sandbox refresh or renewal impact FinDock?](https://docs.findock.com/faq/does-a-sandbox-refresh-or-renewal-impact-findock.md)
 - [Does FinDock support eFaktura?](https://docs.findock.com/faq/does-findock-support-efaktura.md)
 - [API integration checklist](https://docs.findock.com/api/api-integration-checklist.md)
 - [How to use the Payment API v2](https://docs.findock.com/api/how-to-use-the-payment-api-v2.md)
 - [Troubleshooting the Payment API](https://docs.findock.com/api/troubleshooting-the-payment-api-v2.md)
 - [Getting started with the Payment API v2](https://docs.findock.com/api/getting-started-with-the-payment-api-v2.md)
 - [How the Payment API works](https://docs.findock.com/api/how-the-payment-api-works.md)
 - [Initial payments for recurring payments](https://docs.findock.com/api/initial-payments-for-recurring-payments.md): For some payment method and processor combinations, you can or must collection an initial payment for new recurring payments.
 - [Using the API test app](https://docs.findock.com/api/using-the-api-test-app.md)
 - [Does FinDock support UTM tracking?](https://docs.findock.com/faq/does-findock-support-utm-tracking.md)
 - [Does FinDock work with Person Accounts?](https://docs.findock.com/faq/does-findock-work-with-person-accounts.md)
 - [Does Salesforce IP session locking impact FinDock?](https://docs.findock.com/faq/does-salesforce-ip-session-locking-impact-findock.md)
 - [Does updating the security token for the integration user affect ProcessingHub and WebHub connections?](https://docs.findock.com/faq/does-updating-integration-user-security-token-impact-connections.md)
 - [Feature maturity stages FAQs](https://docs.findock.com/faq/feature-maturity-stages-faqs.md)
 - [How are IBANs validated on Payment Profile?](https://docs.findock.com/faq/how-are-ibans-validated-on-payment-profile.md)
 - [How can I find the installment for a Stripe charge?](https://docs.findock.com/faq/how-can-i-find-the-installment-for-a-stripe-charge.md)
 - [How can I set up team-based fundraising?](https://docs.findock.com/faq/how-can-i-set-up-team-based-fundraising.md)
 - [How can I update card details for an active recurring payment?](https://docs.findock.com/faq/how-can-i-update-card-details-for-an-active-recurring-payment.md)
 - [How do I grant login access in Salesforce?](https://docs.findock.com/faq/how-do-i-grant-login-access-in-salesforce.md)
 - [How does FinDock manage Salesforce release compatibility?](https://docs.findock.com/faq/how-does-findock-manage-salesforce-release-compatibility.md)
 - [How is FinDock handling the move to external client apps?](https://docs.findock.com/faq/how-is-findock-handling-the-move-to-external-client-apps.md)
 - [How is FinDock handling Wero?](https://docs.findock.com/faq/how-is-findock-handling-wero.md)
 - [How should I use Guided Review?](https://docs.findock.com/faq/how-should-i-use-guided-review.md)
 - [Frequently asked questions](https://docs.findock.com/faq.md)
 - [November 24 release announcement](https://docs.findock.com/faq/november-24-release-announcement.md)
 - [Salesforce Security Update announcement](https://docs.findock.com/faq/salesforce-security-update.md)
 - [Salesforce Shield Platform Encryption](https://docs.findock.com/faq/salesforce-shield-platform-encryption.md)
 - [What are deleted stage records?](https://docs.findock.com/faq/what-are-deleted-staging-records.md)
 - [What are the correct image dimensions for a Giving Page?](https://docs.findock.com/faq/what-are-image-dimensions-for-giving-pages.md)
 - [What causes the MUTUAL AUTHENTICAtION FAILED error?](https://docs.findock.com/faq/what-causes-mutual-authentication-failed-error.md)
 - [What is my Salesforce Org Id?](https://docs.findock.com/faq/what-is-my-salesforce-org-id.md)
 - [Why did I get notified by Salesforce about ICU locale formats?](https://docs.findock.com/faq/why-did-i-get-notified-about-icu-locale-formats.md)
 - [Why do I get an invalid session error with Deploy Config?](https://docs.findock.com/faq/why-do-i-get-an-invalid-session-error-with-deploy-config.md)
 - [Why does a PSP show collected at the PSP but not in FinDock?](https://docs.findock.com/faq/why-does-a-payment-show-collected-at-psp-but-not-findock.md)
 - [Why does Guided Matching get Apex heap size errors?](https://docs.findock.com/faq/why-does-guided-matching-get-apex-heap-size-errors.md)
 - [Feature maturity stages](https://docs.findock.com/release-notes/feature-maturity-stages.md)
 - [FinDock releases](https://docs.findock.com/release-notes.md): FinDock product release practices
 - [Release Notes - April '20](https://docs.findock.com/release-notes/release-notes-april-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - April '21](https://docs.findock.com/release-notes/release-notes-april-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - February '20](https://docs.findock.com/release-notes/release-notes-february-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '20](https://docs.findock.com/release-notes/release-notes-january-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - February '21](https://docs.findock.com/release-notes/release-notes-february-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '21](https://docs.findock.com/release-notes/release-notes-january-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '22](https://docs.findock.com/release-notes/release-notes-january-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '23](https://docs.findock.com/release-notes/release-notes-january-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '24](https://docs.findock.com/release-notes/release-notes-january-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '25](https://docs.findock.com/release-notes/release-notes-january-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - January '26](https://docs.findock.com/release-notes/release-notes-january-26.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '20](https://docs.findock.com/release-notes/release-notes-july-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '21](https://docs.findock.com/release-notes/release-notes-july-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '22](https://docs.findock.com/release-notes/release-notes-july-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '23](https://docs.findock.com/release-notes/release-notes-july-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '24](https://docs.findock.com/release-notes/release-notes-july-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '25](https://docs.findock.com/release-notes/release-notes-july-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - June '20](https://docs.findock.com/release-notes/release-notes-june-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - June '21](https://docs.findock.com/release-notes/release-notes-june-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '20](https://docs.findock.com/release-notes/release-notes-march-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '21](https://docs.findock.com/release-notes/release-notes-march-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '22](https://docs.findock.com/release-notes/release-notes-march-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '23](https://docs.findock.com/release-notes/release-notes-march-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '24](https://docs.findock.com/release-notes/release-notes-march-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '25](https://docs.findock.com/release-notes/release-notes-march-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - March '26](https://docs.findock.com/release-notes/release-notes-march-26.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '20](https://docs.findock.com/release-notes/release-notes-may-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '21](https://docs.findock.com/release-notes/release-notes-may-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '22](https://docs.findock.com/release-notes/release-notes-may-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '23](https://docs.findock.com/release-notes/release-notes-may-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - July '26](https://docs.findock.com/release-notes/release-notes-july-26.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '24](https://docs.findock.com/release-notes/release-notes-may-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '25](https://docs.findock.com/release-notes/release-notes-may-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '20](https://docs.findock.com/release-notes/release-notes-november-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '21](https://docs.findock.com/release-notes/release-notes-november-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '22](https://docs.findock.com/release-notes/release-notes-november-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '23](https://docs.findock.com/release-notes/release-notes-november-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '24](https://docs.findock.com/release-notes/release-notes-november-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - November '25](https://docs.findock.com/release-notes/release-notes-november-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - May '26](https://docs.findock.com/release-notes/release-notes-may-26.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - October '20](https://docs.findock.com/release-notes/release-notes-october-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - October '21](https://docs.findock.com/release-notes/release-notes-october-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '20](https://docs.findock.com/release-notes/release-notes-september-20.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '21](https://docs.findock.com/release-notes/release-notes-september-21.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '22](https://docs.findock.com/release-notes/release-notes-september-22.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '23](https://docs.findock.com/release-notes/release-notes-september-23.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '24](https://docs.findock.com/release-notes/release-notes-september-24.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release Notes - September '25](https://docs.findock.com/release-notes/release-notes-september-25.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Release schedule](https://docs.findock.com/release-notes/release-schedule.md): FinDock schedule for upcoming releases
 - [FinDock Docs overview](https://docs.findock.com/docs.md)
 - [Audit Trail](https://docs.findock.com/docs/data-model/audit-trail.md): Audit Trail records save information about changes made to FinDock packages.
 - [Bank Feed Account](https://docs.findock.com/docs/data-model/bank-feed-account.md): Bank Feed Account records save information about bank accounts that have a Bank Feed connection.
 - [Bank Feed Authorization Account](https://docs.findock.com/docs/data-model/bank-feed-authorization-account.md): Bank Feed Authorization Account records save information about...
 - [Release Notes - September '26](https://docs.findock.com/release-notes/release-notes-september-26.md): Our release communication aims to inform you early of upcoming releases. The scope of a release may change prior to the production release date.
 - [Bank Feed Authorization](https://docs.findock.com/docs/data-model/bank-feed-authorization.md): Bank Feed Authorization records store authorization parameters for a bank account connected to Bank Feed.
 - [FinDock data model](https://docs.findock.com/docs/data-model/findock-data-model.md): The FinDock data model added custom objects with native relationships to standard Salesforce objects.
 - [Guided Matching Setup](https://docs.findock.com/docs/data-model/guided-matching-setup.md): Guided Matching Records store the match rules used in an execution plan for a specific target or inbound report type and subtype.
 - [Inbound Report](https://docs.findock.com/docs/data-model/inbound-report.md): Inbound Report records capture incoming payment data from integrated payment processors and used for reconciliation through Guided Matching.
 - [FinDock components](https://docs.findock.com/docs/data-model.md): FinDock packages, objects and settings
 - [Installment](https://docs.findock.com/docs/data-model/installment.md): Installment records capture details for a single inbound (receivable) or outbound (payable) payment. Installments may represent one-time payments or individual collections of recurring payments.
 - [Log](https://docs.findock.com/docs/data-model/logs.md): FinDock logs capture details about system events. They are a valuable source of information for advanced root cause analysis.
 - [Mandate History](https://docs.findock.com/docs/data-model/mandate-history.md): Mandate History records capture changes to mandate that need to be tracked for certain payment methods.
 - [Mandate Schedule](https://docs.findock.com/docs/data-model/mandate-schedule.md): Mandate schedules are used to register mandates as required by direct debit schemes supported by FinDock as a native processor, and by certain 3rd party processors.
 - [Mandate](https://docs.findock.com/docs/data-model/mandate.md): Mandate records store the authorization from payers to collection recurring payments.
 - [Message](https://docs.findock.com/docs/data-model/message.md): Message records capture the raw data of inbound or outbound API calls and put job into a processing queue.
 - [Payment Profile](https://docs.findock.com/docs/data-model/payment-profile.md): Payment profile records store the essential information about a payment method used by the payer to allow the method to be used again.
 - [Payment Request Generator Run](https://docs.findock.com/docs/data-model/payment-request-generator-run.md): Payment Request Generator Run records store the configuration of a bulk generation run.
 - [Payment Schedule](https://docs.findock.com/docs/data-model/payment-schedule.md): Payment schedules are used to collection one-time payments for certain payment method-processor combinations and all recurring payments. Payment Schedule records represent individual collections that are manually or automatically run.
 - [Payment](https://docs.findock.com/docs/data-model/payment.md): Payment records represent the exchange of money between two parties. The Payment record can have a positive or negative amount, representing a credit (inbound payment) or debit (outbound payment) accordingly.
 - [PaymentHub File](https://docs.findock.com/docs/data-model/paymenthub-file.md): PaymentHub File records store details about bank files processed for reconciliation.
 - [Recurring Mandate Schedule](https://docs.findock.com/docs/data-model/recurring-mandate-schedule.md): Recurring Mandate Schedule records define the frequency and scope mandate schedules that need to be created and run over a certain period.
 - [Recurring Payment Schedule](https://docs.findock.com/docs/data-model/recurring-payment-schedule.md): Recurring Payment Schedule records define the frequency and scope payment schedules that need to be created and run over a certain period.
 - [Recurring Payment](https://docs.findock.com/docs/data-model/recurring-payment.md): Recurring Payment records define the amount, frequency, payment method and so forth for recurring payments.
 - [Refund](https://docs.findock.com/docs/data-model/refund.md): Refund records represent refund payments to payers triggered from Salesforce.
 - [Target Property](https://docs.findock.com/docs/data-model/target-property.md): Target Property records store information about merchant and bank accounts used for collection and reconciliation.
 - [Transaction Set, Transaction, Transaction Sub Element](https://docs.findock.com/docs/data-model/transaction-sets-transactions.md): Transaction sets and transactions store incoming payment data for reconciliation.
 - [Preparing a project](https://docs.findock.com/docs/getting-started/preparing-a-project.md): Get an overview of requirements and best practices for planning a FinDock implementation project.
 - [Quick start](https://docs.findock.com/docs/getting-started/quick-start.md): This quick start takes you through a basic setup of FinDock with Stripe as a payment processor.
 - [Adyen](https://docs.findock.com/docs/payment-processors/adyen.md): Add the Adyen for FinDock payment extension to process payments through Adyen.
 - [Authorize.net](https://docs.findock.com/docs/payment-processors/authorize-net.md): Add the Authorize.net for FinDock payment extension to process payments through Authorize.net.
 - [Autogiro mandate file](https://docs.findock.com/docs/payment-processors/autogiro-mandate-file.md): The Autogiro mandate file is generated by FinDock to register to new Autogiro direct debit mandates.
 - [Autogiro Direct Debit](https://docs.findock.com/docs/payment-processors/autogiro-direct-debit.md): Add the Nordic Payments extension to natively accept, process and reconcile Autogiro direct debits.
 - [Autogiro payment initiation](https://docs.findock.com/docs/payment-processors/autogiro-payment-initiation.md): The Autogiro payment initiation file is generated by FinDock to collect Autogiro direct debit payments.
 - [AvtaleGiro direct debit](https://docs.findock.com/docs/payment-processors/avtalegiro-direct-debit.md): Add the Nordic Payments extension to natively accept, process and reconcile AvtaleGiro direct debit payments with FinDock.
 - [Axerve](https://docs.findock.com/docs/payment-processors/axerve.md): Add the Axerve for FinDock payment extension to process card payments through Axerve.
 - [Bacs Direct Debit collection file](https://docs.findock.com/docs/payment-processors/bacs-dd-collection-file.md): The Bacs Direct Debit collection file is generated by FinDock to collect Bacs Direct Debit payments.
 - [Bacs notifications and FinDock](https://docs.findock.com/docs/payment-processors/bacs-dd-notifications-and-findock.md): The Bacs Direct Debit scheme requires payers to be notified of specific events. Here we describe how those requirements should be handled when using FinDock as a native Bacs processor.
 - [Bacs Direct Debit Instruction](https://docs.findock.com/docs/payment-processors/bacs-ddi.md): The Bacs Direct Debit Instruction file is generated by FinDock to register and updated Bacs Direct Debit mandates.
 - [Bollettino Postale processing](https://docs.findock.com/docs/payment-processors/bollettino-postale-processing.md): FinDock supports native processing of Bollettino Postale payslips through payment reference generation and payment reconciliation.
 - [Buckaroo](https://docs.findock.com/docs/payment-processors/buckaroo.md): Add the Buckaroo for FinDock payment extension to process payments through Buckaroo.
 - [Checkout.com](https://docs.findock.com/docs/payment-processors/checkout-com.md): Add the Checkout.com for FinDock payment extension to process payments through Checkout.com.
 - [SEPA Credit Transfer](https://docs.findock.com/docs/payment-processors/configuring-and-using-sepa-credit-transfer.md): SEPA Credit transfer is an add-on feature of the SEPA payment extension for native processing through FinDock.
 - [Configuring Bacs Manual](https://docs.findock.com/docs/payment-processors/configuring-bacs-manual.md)
 - [Configuring GoCardless](https://docs.findock.com/docs/payment-processors/configuring-gocardless.md): Add the GoCardless for FinDock payment extension to process direct debit payments through GoCardless.
 - [Configuring PayPal](https://docs.findock.com/docs/payment-processors/configuring-paypal.md): Add the PayPal for FinDock payment extension to process PayPal wallet payments through PayPal.
 - [Configuring SEPA Direct Debit](https://docs.findock.com/docs/payment-processors/configuring-sepa-dd.md): Add the SEPA for FinDock extension to natively accept, process and reconcile SEPA Direct Debit, SEPA Credit Transfer, Bollettino Postale and other payment methods.
 - [Configuring Access PaySuite](https://docs.findock.com/docs/payment-processors/configuring-smartdebit.md): Add the SmartDebit payment extension to process Bacs Direct Debit payments through Access PaySuite.
 - [Configuring Swish for FinDock](https://docs.findock.com/docs/payment-processors/configuring-swish.md): Add the Swish for FinDock payment extension to process Swish mobile payments.
 - [Configuring Tikkie](https://docs.findock.com/docs/payment-processors/configuring-tikkie.md): Add the Tikkie for FinDock payment extension to generate Tikkies and process Tikkie payments.
 - [Configuring Vipps MobilePay](https://docs.findock.com/docs/payment-processors/configuring-vipps.md): Add the Vipps MobilePay payment extension to process Vipps and MobilePay payments.
 - [Credit transfer security](https://docs.findock.com/docs/payment-processors/credit-transfer-security.md): This article outlines the security measures you should take when using FinDock to processing SEPA Credit Transfer payments.
 - [E-mandates for Autogiro](https://docs.findock.com/docs/payment-processors/e-mandates-for-autogiro.md): FinDock e-mandates for Autogiro enables organizations to set up mandates with payers using electronic identification (eID).
 - [E-mandates for SEPA Direct Debit](https://docs.findock.com/docs/payment-processors/e-mandates-for-sepa-direct-debit.md): This article outlines e-mandates can be used with native SEPA Direct Debit processing in FinDock.
 - [File types generated by FinDock](https://docs.findock.com/docs/payment-processors/file-types-generated-by-findock.md): When FinDock is used as a native payment processor, payment instructions often come in the form of standard file types that transferred to financial institutions for processing.
 - [FinDock for Norway](https://docs.findock.com/docs/payment-processors/findock-for-norway.md): The FinDock for Norway processor enables native processing of Norwegian payment methods such as AvtaleGiro direct debit.
 - [FinDock for Sweden](https://docs.findock.com/docs/payment-processors/findock-for-sweden.md): The FinDock for Sweden processor enables native processing of Swedish payment methods such as Autogiro direct debit.
 - [FinDock native payment methods](https://docs.findock.com/docs/payment-processors/findock-native-payment-methods.md): FinDock natively supports processing several different payment methods include direct debit schemes, bank transfers and payment requests.
 - [GoCardless credit transfer](https://docs.findock.com/docs/payment-processors/gocardless-credit-transfer.md)
 - [Stripe recurring credit card migration](https://docs.findock.com/docs/payment-processors/guide-stripe-recurring-credit-card-migration.md): This guide outlines specific migration steps needed for migrating existing card payments to FinDock.
 - [Migrating AvtaleGiro agreements](https://docs.findock.com/docs/payment-processors/migrating-avtalegiro-agreements.md): This guide outlines specific steps needed for migrating existing AvtaleGiro agreements to FinDock.
 - [Mollie](https://docs.findock.com/docs/payment-processors/mollie.md): Add the Mollie for FinDock payment extension to process payments through Mollie.
 - [Multi-Merchant accounts for PSPs](https://docs.findock.com/docs/payment-processors/multi-merchant-accounts-for-psps.md): FinDock payment extensions support multi-merchant setups so you can have several merchant accounts for the same payment processor.
 - [Multiple currency support in FinDock](https://docs.findock.com/docs/payment-processors/multiple-currency-support-in-findock.md): Multi-currency support in FinDock is dependent on the Salesforce setup and the currencies supported by the given payment processor-method combination.
 - [FinDock native processing](https://docs.findock.com/docs/payment-processors/native-processing.md): FinDock natively supports processing several different payment methods include direct debit schemes, bank transfers and payment requests.
 - [Pain.001](https://docs.findock.com/docs/payment-processors/pain-001.md): The pain.001 file is generated by FinDock to disburse SEPA Credit Transfer payments.
 - [Pain.008](https://docs.findock.com/docs/payment-processors/pain-008.md): The pain.008 file is generated by FinDock to collect direct debit payments according to the SEPA, SEDA, CH-DD or LSV+ direct debit schemes.
 - [Pain.009](https://docs.findock.com/docs/payment-processors/pain-009.md): The pain.009 file is generated by FinDock to register mandates according to the SEDA variation of SEPA Direct Debit.
 - [Pain.010](https://docs.findock.com/docs/payment-processors/pain-010.md): The pain.010 file is generated by FinDock to submit mandate changes according to the SEDA variation of SEPA Direct Debit.
 - [Pain.011](https://docs.findock.com/docs/payment-processors/pain-011.md): The pain.011 file is generated by FinDock to submit mandate cancellations according to the SEDA variation of SEPA Direct Debit.
 - [Paya](https://docs.findock.com/docs/payment-processors/paya.md): Add the Paya for FinDock payment extension to process payments through Paya (Nuvei).
 - [QR-bill with FinDock](https://docs.findock.com/docs/payment-processors/qr-bill-with-findock.md)
 - [Redsys](https://docs.findock.com/docs/payment-processors/redsys.md): Add the Redsys for FinDock payment extension to process card and Bizum payments through Redsys.
 - [Saferpay](https://docs.findock.com/docs/payment-processors/saferpay.md): Add the Saferpay for FinDock payment extension to process payments through Saferpay by Worldline.
 - [SEDA for SEPA](https://docs.findock.com/docs/payment-processors/seda-for-sepa.md): Add the SEPA for FinDock extension to natively accept, process and reconcile SEDA direct debits with FinDock.
 - [Stripe](https://docs.findock.com/docs/payment-processors/stripe.md): Add the Stripe for FinDock payment extension to process payments through Stripe.
 - [Swiss CH-DD](https://docs.findock.com/docs/payment-processors/swiss-ch-dd.md): Add the Swiss Payments extension to natively accept, process and reconcile CH-DD direct debits and ESR payments with FinDock.
 - [Swiss LSV+](https://docs.findock.com/docs/payment-processors/swiss-lsv.md): Add the Swiss Payments extension to natively accept, process and reconcile LSV+ direct debits and ESR payments with FinDock.
 - [Using Bacs Manual](https://docs.findock.com/docs/payment-processors/using-bacs-manual.md): With Bacs Manual, you use FinDock to generate Standard 18 files for DDI lodgement and payment collection. Uploaded Bacs reports are automatically parsed for reconciliation.
 - [Payment processors and methods](https://docs.findock.com/docs/payment-processors.md): FinDock integrates with many payment service providers through payment extension packages.
 - [Using GoCardless direct debit](https://docs.findock.com/docs/payment-processors/using-gocardless-dd.md)
 - [Using GoCardless Instant Bank Pay](https://docs.findock.com/docs/payment-processors/using-gocardless-instant-bank-pay.md)
 - [Using SEPA Direct Debit](https://docs.findock.com/docs/payment-processors/using-sepa-dd.md): With FinDock's native processing capabilities, you can create highly customized self-managed business processes for accepting, collecting and reconciling SEPA Direct Debit payments.
 - [Using Access PaySuite](https://docs.findock.com/docs/payment-processors/using-smartdebit.md): With Access PaySuite (formerly SmartDebit) as your Bacs service bureau, you can easily create direct debit payments, register DDIs and reconcile Bacs reports through FinDock.
 - [Using Swish](https://docs.findock.com/docs/payment-processors/using-swish.md): Accept and collect both one-time and recurring Swish payments with FinDock.
 - [Using Tikkie](https://docs.findock.com/docs/payment-processors/using-tikkie.md): Generate Tikkie QRs and URLs for one-off payments are generate Tikkies in bulk for campaigns and other initiatives for easy payment collection and reconciliation.
 - [Using Vipps Mobile Donations](https://docs.findock.com/docs/payment-processors/using-vipps-donations.md): Fetch and reconcile Vipps MobilePay Donations with FinDock.
 - [Using Vipps MobilePay](https://docs.findock.com/docs/payment-processors/using-vipps.md): Accept and collect both one-time and recurring Vipps MobilePay payments through FinDock.
 - [Worldpay Business Gateway 350](https://docs.findock.com/docs/payment-processors/worldpay-business-gateway-350.md): Add the Worldpay for FinDock payment extension to process one-time card payments through Worldpay Business Gateway 350.
 - [Worldpay Corporate Gateway](https://docs.findock.com/docs/payment-processors/worldpay-corporate-gateway.md): Add the Worldpay for FinDock payment extension to process card payments through Worldpay Payment Gateway (formerly Corporate Gateway).
 - [Abandoned payments](https://docs.findock.com/docs/payments/abandoned-payments.md): You can use FinDock payment data to identify abandoned payment intents for reporting and follow-up business processes.
 - [Accepting payments with FinDock](https://docs.findock.com/docs/payments/accepting-payments-with-findock.md): FinDock provides several options for accepting payments online as well as directly from Salesforce.
 - [Automate payment schedules](https://docs.findock.com/docs/payments/auto-collect-payments.md): You can automate payment schedules to varying degrees up to full automation using a combination of recurring schedules and the auto-run and auto-create options.
 - [Building payment Experiences](https://docs.findock.com/docs/payments/building-payment-experiences.md): FinDock's managed components for Payment Experiences can be easily used with Salesforce Flows custom Experience Could sites and orchestrating business processes.
 - [Choosing a digital experience option](https://docs.findock.com/docs/payments/choosing-a-digital-experience-option.md): FinDock provides several options, from no-code to pro-code, for building digital payment experiences.
 - [Configuring FinDock MOTO](https://docs.findock.com/docs/payments/configuring-findock-moto.md): The configurable FinDock Payments component can be placed on Salesforce record type layouts as well as embedded in custom workflows. Please note PCI compliance is mandatory for card payments.
 - [Configuring FinDock PayLinks](https://docs.findock.com/docs/payments/configuring-findock-paylinks.md): FinDock PayLinks include a fully integrated payment form with configurable payment options as well as branding, labelling and advanced options such as custom webhooks.
 - [Configuring Giving Pages](https://docs.findock.com/docs/payments/configuring-giving-pages.md): Before you can create and publish Giving Pages, you need to adjust some Salesforce settings and define a subdomain on givingpage.org where the pages are hosted by FinDock.
 - [Configuring the Payment Request Generator](https://docs.findock.com/docs/payments/configuring-the-payment-request-generator.md): To use the Payment Request Generator, users need specific permissions and access to the generator Lightning component.
 - [Creating and updating Giving Pages](https://docs.findock.com/docs/payments/creating-and-updating-giving-pages.md): Create, publish and manage Giving Pages, as well as leverage advanced options to customize the payer experience.
 - [Approval processes for collection runs](https://docs.findock.com/docs/payments/creating-approval-processes-for-bulk-collection-runs.md): You can use Salesforce tooling to create approval steps for different payment schedule stages.
 - [Custom domains](https://docs.findock.com/docs/payments/custom-domains.md): In addition to the free subdomain from FinDock, you can create a custom domain for hosting Giving Pages.
 - [Data quality requirements](https://docs.findock.com/docs/payments/data-quality-requirements.md): Data quality is an essential ingredient of successful payment collection. The FinDock Data Quality component helps you ensure required data is present and valid before payment instructions are sent.
 - [Disbursement Options with FinDock](https://docs.findock.com/docs/payments/disbursement-options-with-findock.md): FinDock supports payment disbursements through native SEPA Credit Transfer processing.
 - [FinDock Data Quality](https://docs.findock.com/docs/payments/findock-data-quality.md): Use the FinDock Data Quality component to validate payment data before collection runs.
 - [FinDock e-mandates](https://docs.findock.com/docs/payments/findock-e-mandates.md): The FinDock e-mandate feature enables organizations to set up mandates with payers using electronic identification (eID).
 - [FinDock Payment Experiences](https://docs.findock.com/docs/payments/findock-payment-experiences.md): FinDock Payment Experiences combines our payments on Salesforce capabilities with native Salesforce Digital Experiences to deliver compelling online payment journeys.
 - [finDock Payment Objects](https://docs.findock.com/docs/payments/findock-payment-objects.md): FinDock adds custom objects to Salesforce enabling you to accept process and reconcile payments.
 - [Getting started with Payment Experiences](https://docs.findock.com/docs/payments/getting-started-with-payment-experiences.md): FinDock Payment Experiences is a pilot feature that requires a few steps to get started.
 - [Payments with FinDock](https://docs.findock.com/docs/payments.md): Use FinDock to accept, collect and process payments
 - [Integrating Refunds from Salesforce](https://docs.findock.com/docs/payments/integrating-refunds-from-salesforce.md): FinDock supports initiating refunds directly from Salesforce through different integration patterns.
 - [Introduction to mandate handling](https://docs.findock.com/docs/payments/introduction-to-mandate-handling.md): FinDock includes a mandate service for creating, registering and managing mandates for several direct debit schemes.
 - [Introduction to payment schedules](https://docs.findock.com/docs/payments/introduction-to-payment-schedules.md): Payment schedules are the key tool for bulk payment collection. The payment schedule process results in a generated payment instruction file or instruction messages to PSPs depending on the selected payment method and processor.
 - [Monitor payment schedule progress](https://docs.findock.com/docs/payments/monitor-payment-schedule-progress.md): The Payment Schedule Path component on payment schedules provides details you can use to follow schedule progress.
 - [Payment collection use cases](https://docs.findock.com/docs/payments/payment-collection-use-cases.md): Here are a few examples of how FinDock collects payments.
 - [Payment Form configuration options](https://docs.findock.com/docs/payments/payment-form-configuration-options.md): Here you can find details about each payment form setting to help you configure the form to precisely meet your needs.
 - [Payment requests with FinDock](https://docs.findock.com/docs/payments/payment-requests-with-findock.md): With FinDock you can easily generate individual and bulk payment references for payment request. The references ensure paid requests are easily matched during reconciliation.
 - [PCI compliance and security](https://docs.findock.com/docs/payments/pci-compliance-and-security.md): If you use a virtual terminal to collect card payments, such as FinDock MOTO, your organization needs to follow PCI standards and ensure compliance.
 - [Pro-code payment experiences](https://docs.findock.com/docs/payments/pro-code-payment-experiences.md): FinDock's managed components for Payment Experiences can embedded in custom Lighting Web Components (LWCs) for custom pro-code solutions with maximum control over the user experience.
 - [Insights via ProcessingHub Manager](https://docs.findock.com/docs/payments/insights-via-processinghub-manager.md): Use the ProcessingHub Manager app to monitor and troubleshooting PaymentHub processes such as payment schedule runs.
 - [Reconciling payments](https://docs.findock.com/docs/payments/reconciling-payments.md): Introduction to payment reconciliation with FinDock.
 - [Refunds from Salesforce](https://docs.findock.com/docs/payments/refunds-from-salesforce.md): FinDock supports initiating refunds directly from Salesforce.
 - [Payment requests](https://docs.findock.com/docs/payments/requesting-payments.md): Get a quick overview of what payment requests are and how they can be used.
 - [Retry data load via ProcessingHub Manager](https://docs.findock.com/docs/payments/retry-data-load-via-processinghub-manager.md): For batch errors, you can use ProcessingHub Manger to retry the data in a similar way to Salesforce Dataloader.
 - [Using data quality validation](https://docs.findock.com/docs/payments/using-data-quality-validation.md): Learn how to use the FinDock Data Quality component to validate payment data.
 - [Using FinDock MOTO](https://docs.findock.com/docs/payments/using-findock-moto.md): Learn how to use the FinDock Payments component to collect MOTO payments.
 - [Using FinDock PayLinks](https://docs.findock.com/docs/payments/using-findock-paylinks.md): Using FinDock PayLinks is easy - you just need to share generated Pay URL from the installment or recurring payment.
 - [Using mandate schedules](https://docs.findock.com/docs/payments/using-mandate-schedules.md): For mandates that need to be registered before payments can be collection, mandate schedules enable you to run bulk registration and update actions.
 - [Using payment schedules](https://docs.findock.com/docs/payments/using-payment-schedules.md): Payment schedules can be created and run manually or fully automated. The default page layout includes components to help you follow and monitor the schedule run.
 - [Using a recurring payment schedule](https://docs.findock.com/docs/payments/using-recurring-payment-schedules.md): With recurring payment schedules, you can easily create and run payment schedules at fixed intervals over period of time.
 - [Using the Payment Request Generator](https://docs.findock.com/docs/payments/using-the-payment-request-generator.md): Define a Payment Request Generate run to generate payment references in bulk for campaigns and reports.
 - [What is the Payment Request Generator?](https://docs.findock.com/docs/payments/what-is-the-payment-request-generator.md): The Payment Request Generator enables you to generate unique payment references in bulk and stamp campaign records or report rows bulk payment request operations without needs to creating Installment records.
 - [Bank permissions for FinDock Bank Feed](https://docs.findock.com/docs/reconciliation/bank-permissions-for-bank-feed.md): Bank Feed is based on open banking (PSD2). Every bank has rules, roles and permissions for open banking connections. This article outlines common approaches and considerations for authorization Bank Feed connections.
 - [Bulk process failed inbound reports](https://docs.findock.com/docs/reconciliation/bulk-process-failed-inbound-reports.md): If many inbound reports failed, you can re-run them in bulk rather than retrying Guided Matching one by one.
 - [Configuring Guided Matching](https://docs.findock.com/docs/reconciliation/configuring-guided-matching.md): In addition to creating Guided Matching rules, there are related components that need to be added to page layouts.
 - [Configuring Manual Review](https://docs.findock.com/docs/reconciliation/configuring-manual-review.md)
 - [FinDock Bank Feed](https://docs.findock.com/docs/reconciliation/findock-bank-feed.md): FinDock Bank Feed automates bank statement reconciliation by connecting directly with your bank accounts and importing transactions for matching and updating Salesforce data.
 - [Guided Matching managed and suggested rules](https://docs.findock.com/docs/reconciliation/guided-matching-managed-and-suggested-rules.md): FinDock provides Guided Matching setups with managed and suggested rules to help simplify and optimize reconciliation.
 - [Guided Matching FAQs](https://docs.findock.com/docs/reconciliation/guided-matching-questions.md)
 - [Guided Matching rule types](https://docs.findock.com/docs/reconciliation/guided-matching-rule-types.md): Guided Matching setups define execution plans that include multiple matching rules. FinDock provides several matching rule types for matching and enriching Salesforce data to address a wide range of reconciliation use cases.
 - [Handling standing orders](https://docs.findock.com/docs/reconciliation/handling-standing-orders.md): Standing orders are used in the UK for recurring bank transfers. Payers set up the standing order, and FinDock gathers the payment details through reconciliation.
 - [Reconciliation](https://docs.findock.com/docs/reconciliation.md): FinDock supports automated and customizable payment matching to efficiently keep Salesforce data up to date.
 - [Batch reconciliation](https://docs.findock.com/docs/reconciliation/preparing-an-installment-batch-for-reconciliation.md): FinDock supports batch reconciliation of payments that were collected or processed by a 3rd part system.
 - [Processing and reconciling online payments](https://docs.findock.com/docs/reconciliation/processing-and-reconciling-online-payments.md): FinDock automatically matches and reconciles online payments collected through integrated payment service providers.
 - [Processing Bacs reports](https://docs.findock.com/docs/reconciliation/processing-bacs-reports.md): FinDock supports file-based reconciliation of Bacs reports.
 - [Processing and reconciling bank files](https://docs.findock.com/docs/reconciliation/processing-bank-statements.md): FinDock supports reconciling incoming payment data through a wide range of standard bank files and statements.
 - [Processing BGMax files](https://docs.findock.com/docs/reconciliation/processing-bgmax-files.md): FinDock supports BGMax file-based reconciliation.
 - [Processing C72 files](https://docs.findock.com/docs/reconciliation/processing-c72-files.md): FinDock supports C72 file-based reconciliation.
 - [Processing camt.053 files](https://docs.findock.com/docs/reconciliation/processing-camt-053-files.md): FinDock supports camt.053 file-based reconciliation.
 - [Processing camt.054 files](https://docs.findock.com/docs/reconciliation/processing-camt-054-files.md): FinDock supports camt.054 file-based reconciliation.
 - [Processing CODA files](https://docs.findock.com/docs/reconciliation/processing-coda-files.md): FinDock supports CODA file-based reconciliation.
 - [Processing MT 940 files](https://docs.findock.com/docs/reconciliation/processing-mt-940-files.md): FinDock supports MT 940 file-based reconciliation.
 - [Processing N43 files](https://docs.findock.com/docs/reconciliation/processing-n43-files.md): FinDock supports N43 file-based reconciliation.
 - [Processing OCR files](https://docs.findock.com/docs/reconciliation/processing-ocr-files.md): FinDock supports OCR file-based reconciliation.
 - [Processing pain.002 files](https://docs.findock.com/docs/reconciliation/processing-pain-002-files.md): FinDock supports pain.002 file-based reconciliation.
 - [Processing pain.012 files](https://docs.findock.com/docs/reconciliation/processing-pain-012-files.md): FinDock supports pain.012 file-based reconciliation.
 - [Processing Swish reports](https://docs.findock.com/docs/reconciliation/processing-swish-reports.md): FinDock supports Swish reports file-based reconciliation.
 - [Processing Total IN files](https://docs.findock.com/docs/reconciliation/processing-total-in-files.md): FinDock supports Total IN file-based reconciliation.
 - [Guided Matching rule type - Constant](https://docs.findock.com/docs/reconciliation/rule-type-constant.md): The Constant rule type is used to a constant value for incoming payment record field that should be used for matching.
 - [Guided Matching rule type - Create Campaign Member](https://docs.findock.com/docs/reconciliation/rule-type-create-campaign-member.md): The Create Campaign Member rule type is used to create campaign members based on incoming payment data.
 - [Guided Matching rule type - Create Record](https://docs.findock.com/docs/reconciliation/rule-type-create-record.md): The Create Record rule type is used to create a Salesforce record based on incoming payment data.
 - [Guided Matching rule type - Data360 Query](https://docs.findock.com/docs/reconciliation/rule-type-data360-query.md): The Data360 Query rule type is used to improve reconciliation success by querying data from Salesforce Data 360 objects.
 - [Guided Matching rule type - Find Duplicate](https://docs.findock.com/docs/reconciliation/rule-type-find-duplicate.md): The Find Duplicate rule type is used to extend the automatic deduplication rules of Salesforce.
 - [Guided Matching rule type - Fixed Width Extract](https://docs.findock.com/docs/reconciliation/rule-type-fixed-width-extract.md): The Fixed Width Extract rule type is used to enrich Salesforce data for matching when the incoming payment data has a fixed-width format.
 - [Guided Matching rule type - Guided Review](https://docs.findock.com/docs/reconciliation/rule-type-guided-review.md): The Guided Review rule type defines how the Guided Review component is used when automated matching needs manual intervention.
 - [Guided Matching rule type - Keyword Search](https://docs.findock.com/docs/reconciliation/rule-type-keyword-search.md): The Keyword Search rule type is used to match incoming payment records to Salesforce records based on keywords.
 - [Guided Matching rule type - Manage Source](https://docs.findock.com/docs/reconciliation/rule-type-manage-source.md): The Manage Source rule type is part of every Guided Matching setup and takes care of updating source-specific records if a source, like NPSP, is used.
 - [Guided Matching rule type - Normalize](https://docs.findock.com/docs/reconciliation/rule-type-normalize.md): The Normalize rule type is used to modify incoming payment data so that it matches the expected capitalization and whitespace used in Salesforce field values.
 - [Guided Matching rule type - Process Installment](https://docs.findock.com/docs/reconciliation/rule-type-process-installment.md): The Process Installment rule type is part of every Guided Matching setup. The rule determines how FinDock updates the matched Installment record.
 - [Guided Matching rule type - Query](https://docs.findock.com/docs/reconciliation/rule-type-query.md): The Query rule type is used to improve reconciliation success by querying Salesforce data.
 - [Guided Matching rule type - Regular Expression](https://docs.findock.com/docs/reconciliation/rule-type-regular-expression.md): The Regular Expression rule type allows you to extract unique data from an incoming payment for matching or enriching.
 - [Guided Matching rule type - Update Record](https://docs.findock.com/docs/reconciliation/rule-type-update-record.md): The Update Record rule type is used to update a Salesforce record based on incoming payment data.
 - [Using Manual Review](https://docs.findock.com/docs/reconciliation/using-manual-review.md)
 - [Using Guided Matching](https://docs.findock.com/docs/reconciliation/using-guided-matching.md): FinDock provides visual components to help you process incoming data through Guided Matching.
 - [What is Guided Matching?](https://docs.findock.com/docs/reconciliation/what-is-guided-matching.md): Guided Matching is a powerful toolset for matching and enriching Salesforce data with incoming payment data.
 - [Add payment extensions](https://docs.findock.com/docs/setup/add-payment-extensions.md): Payment extensions are optional packages you add to FinDock for processing payments natively or through Payment Service Providers (PSPs).
 - [Add source connectors](https://docs.findock.com/docs/setup/add-source-connectors.md): Add a source connector package to enable FinDock to sync payment data to industry-specific solutions.
 - [Automatic Chatter file upload with email](https://docs.findock.com/docs/setup/automatic-chatter-file-upload-with-email.md): Use Salesforce tooling to automatically upload incoming bank files to Chatter for processing.
 - [Configure FinDock Core](https://docs.findock.com/docs/setup/configure-findock-core.md): The FinDock Core settings determine how FinDock handles general payment management and orchestration features.
 - [Configure ProcessingHub](https://docs.findock.com/docs/setup/configure-processinghub.md): A connection from Salesforce to FinDock ProcessingHub is required for FinDock to function properly and is used for processing-heavy jobs such as generating and parsing bank files.
 - [Configure WebHub](https://docs.findock.com/docs/setup/configure-webhub.md): A connection from Salesforce to FinDock WebHub is required for online payment features such as PayLinks, while Notification Gateway is used to capture API messages from integrated PSPs.
 - [Custom payment methods](https://docs.findock.com/docs/setup/custom-payment-methods.md): Use custom payment methods to store payments in Salesforce that are not processed through FinDock or other PSPs.
 - [FinDock heartbeats](https://docs.findock.com/docs/setup/findock-heartbeats.md): The settings for individual heartbeat jobs can be adjusted to fit specific business process requirements.
 - [General permission guidance](https://docs.findock.com/docs/setup/general-permission-guidance.md): Standard and custom Salesforce permissions are required for FinDock admins and other users.
 - [Overview](https://docs.findock.com/docs/setup.md): Install and configure FinDock
 - [Install FinDock](https://docs.findock.com/docs/setup/install-findock.md): Install FinDock Core and ProcessingHub and learn about your setup options.
 - [Special considerations for data migrations](https://docs.findock.com/docs/setup/migrating-payment-data-special-considerations.md): Some payment processors have dedicated fields and other special considerations.
 - [Migrating payment data to FinDock](https://docs.findock.com/docs/setup/migrating-payment-data.md): Learn about the scope and details need to prepare for migrating existing payment data to FinDock.
 - [Permission set groups](https://docs.findock.com/docs/setup/permission-set-groups.md): FinDock provides permission set groups for common user types that you can modify by adding custom permission sets and muting specific permissions.
 - [Advanced Gift Aid options](https://docs.findock.com/docs/source-connectors/advanced-gift-aid-options.md): Advanced options enable charities to make claims on partial donated amounts, refine the scope of Gift Aid claim schedules and customize declaration handling.
 - [Configuring FinDock for Fundraising](https://docs.findock.com/docs/source-connectors/configuring-findock-for-fundraising.md): In addition to configuring the source connector, to use FinDock for Fundraising, you need to modify page layouts and create custom Flows.
 - [Configuring FinDock for NPSP](https://docs.findock.com/docs/source-connectors/configuring-findock-for-npsp.md): To use FinDock for NPSP, adust the source connector settings, default mappings and modify page layouts as needed.
 - [FAQs about Gift Aid](https://docs.findock.com/docs/source-connectors/faqs-about-gift-aid.md): Here we answer a few common questions about how to use FinDock to claim Gift Aid.
 - [FinDock for NPSP data model](https://docs.findock.com/docs/source-connectors/findock-for-npsp-data-model.md): When the FinDock for NPSP package is installed, several custom fields are added to NPSP to enable FinDock to sync payment data to NPSP.
 - [FinDock Standalone](https://docs.findock.com/docs/source-connectors/findock-standalone.md): FinDock Standalone means FinDock is the source of payment data for business logic in the org. Installment and Recurring Payment records are the source of truth for payment status and other details.
 - [For admins and SIs - Gift Aid setup](https://docs.findock.com/docs/source-connectors/for-admins-and-sis-gift-aid-setup.md): The Gift Aid package is both a source connector and native processor for Gift Aid. The setup includes source and processing-related settings, as well as managed components for Gift Aid management.
 - [For Gift Aid managers](https://docs.findock.com/docs/source-connectors/for-gift-aid-managers.md): Learn how to obtain and manage Gift Aid declarations and make Gift Aid claims to HMRC.
 - [Gift Aid data model](https://docs.findock.com/docs/source-connectors/gift-aid-data-model.md): The FinDock for Gift Aid package adds to orgs custom objects, fields and an Installment record type for managing and auditing Gift Aid declarations and claims.
 - [Gift Transaction - Installment Field Mapper](https://docs.findock.com/docs/source-connectors/gift-transaction-installment-field-mapper.md): Use the Field Mapper to define how FinDock should sync data between Installment records and related Gift Transaction records.
 - [How Gift Aid works](https://docs.findock.com/docs/source-connectors/how-gift-aid-works.md): Get a quick introduction to the Gift Aid tax relief scheme available to charities operating in the UK.
 - [Source connectors](https://docs.findock.com/docs/source-connectors.md): Add a source connector to integrate FinDock with industry solutions.
 - [Introduction to FinDock for Fundraising](https://docs.findock.com/docs/source-connectors/introduction-to-findock-for-fundraising.md): The FinDock for Fundraising source connector integrated FinDock to the Salesforce core Fundraising feature that is part of industry solutions such as Nonprofit Cloud and Education Cloud.
 - [NPSP FAQs](https://docs.findock.com/docs/source-connectors/npsp-faqs.md): Here we answer a few common questions about how to use FinDock with Salesforce NPSP.
 - [NPSP Status Mapping](https://docs.findock.com/docs/source-connectors/npsp-status-mapping.md): FiDock provides default mapping between Installment states and Opportunity stages. Please modify the mappings to ensure every Opportunity stage used by the organization has an Installment status mapping.
 - [NPSP workflows and recommendations](https://docs.findock.com/docs/source-connectors/npsp-workflows-and-recommendations.md): Here are some best practices for using FinDock with NPSP to collect and manage donation payments.
 - [Opportunity-Installment Field Mapper](https://docs.findock.com/docs/source-connectors/opportunity-installment-field-mapper.md): Use the Opportunity-Installment mappings to define how FinDock should sync data between Installment records and the related Opportunity records.
 - [Failed file reconciliation](https://docs.findock.com/docs/troubleshooting/failed-file-reconciliation.md): File-based reconciliation extracts bank files and matches data on ProcessingHub.
 - [Troubleshooting failed installments in successful payment schedule](https://docs.findock.com/docs/troubleshooting/failed-installments-in-schedule.md): Payment schedules can complete successfully with individual installments that failed.
 - [Failed online reconciliation](https://docs.findock.com/docs/troubleshooting/failed-online-reconciliation.md): Online reconciliation involves matching and updating Salesforce data through Guided Matching based on incoming PSP notifications.
 - [Failed payment intents](https://docs.findock.com/docs/troubleshooting/failed-payment-intents.md): Payment intents capture the details required to set up and collection a new payment.
 - [Troubleshooting failed payment schedule runs](https://docs.findock.com/docs/troubleshooting/failed-schedule-runs.md): Payment schedules can fail for different reasons depending on the phase of the schedule run.
 - [How to troubleshoot FinDock](https://docs.findock.com/docs/troubleshooting/how-to-troubleshoot-findock.md): Overview of the essential information and methods for troubleshooting payments in FinDock.
 - [Troubleshooting payments](https://docs.findock.com/docs/troubleshooting.md)
 - [Information sources for troubleshooting](https://docs.findock.com/docs/troubleshooting/information-sources-for-troubleshooting.md): Salesforce features and custom FinDock options are primary sources of information to troubleshooting payments.
 - [Troubleshooting payment schedules](https://docs.findock.com/docs/troubleshooting/troubleshooting-payment-schedules.md): Payment schedules determine collection of recurring payments as well as some one-time payments.
 - [Troubleshooting reconciliation](https://docs.findock.com/docs/troubleshooting/troubleshooting-reconciliation.md): Reconciliation involves matching and updating Salesforce data with incoming payment data from bank files and PSP notifications.
 - [Acceptgiro](https://docs.findock.com/docs/payment-processors/payment-methods/acceptgiro.md): Acceptgiro is a discontinued service. However, the payment reference format is still used in the Netherlands.
 - [ACH Direct Debit](https://docs.findock.com/docs/payment-processors/payment-methods/ach-direct-debit.md): ACH is a direct debit scheme used in the United States.
 - [Apple Pay](https://docs.findock.com/docs/payment-processors/payment-methods/apple-pay.md): Apple Pay is a digital wallet payment method popular worldwide.
 - [Autogiro](https://docs.findock.com/docs/payment-processors/payment-methods/autogiro.md): Autogiro is a direct debit scheme used in Sweden.
 - [AvtaleGiro](https://docs.findock.com/docs/payment-processors/payment-methods/avtalegiro.md): AvtaleGiro is a direct debit scheme used in Norway.
 - [Bacs Direct Debit](https://docs.findock.com/docs/payment-processors/payment-methods/bacs-direct-debit.md): Bacs Direct Debit is a direct debit scheme used throughout the UK.
 - [Bancontact](https://docs.findock.com/docs/payment-processors/payment-methods/bancontact.md): Bancontact is an online banking payment method used in Belgium.
 - [Bank Transfer](https://docs.findock.com/docs/payment-processors/payment-methods/bank-transfer.md): Bank transfer is a broad category of payment methods for bank-to-bank payments.
 - [Bizum](https://docs.findock.com/docs/payment-processors/payment-methods/bizum.md): Bizum is a popular mobile payment method in Spain.
 - [BLIK](https://docs.findock.com/docs/payment-processors/payment-methods/blik.md): BLIK is an online banking payment method popular in Poland.
 - [Bollettino Postale](https://docs.findock.com/docs/payment-processors/payment-methods/bollettino-postale.md): Bollettino Postale is a payment method used for payment requests in Italy.
 - [Cards](https://docs.findock.com/docs/payment-processors/payment-methods/cards.md): The card payment method includes both credit and debit cards from national and international card networks.
 - [CH-DD Direct Debit](https://docs.findock.com/docs/payment-processors/payment-methods/ch-dd-direct-debit.md): CH-DD is a direct debit scheme used in Switzerland.
 - [ESR](https://docs.findock.com/docs/payment-processors/payment-methods/esr.md): ESR is a payment method used for payment requests in Switzerland.
 - [Gift Card](https://docs.findock.com/docs/payment-processors/payment-methods/gift-card.md): The Gift card payment method is a card type with a stored, redeemable value.
 - [Giro](https://docs.findock.com/docs/payment-processors/payment-methods/giro.md): Giro is a payment method used for bank transfers and for payment references with regional format variations, for example, between Sweden and Norway.
 - [Google Pay](https://docs.findock.com/docs/payment-processors/payment-methods/google-pay.md): Google Pay is a digital wallet payment method popular worldwide.
 - [iDEAL QR | Wero](https://docs.findock.com/docs/payment-processors/payment-methods/ideal-qr.md): Wero is a payment method that replaces several regional methods for payment requests used throughout the EU. Wero generates both paylinks and QR codes.
 - [iDEAL | Wero](https://docs.findock.com/docs/payment-processors/payment-methods/ideal.md): Wero is a payment method that replaces several regional methods for payment requests used throughout the EU. Wero generates both paylinks and QR codes.
 - [Instant Bank Pay](https://docs.findock.com/docs/payment-processors/payment-methods/instant-bank-pay.md): Pay by Bank (Instant Bank Pay) is a online banking payment method offered by GoCardless.
 - [LSV+ Direct Debit](https://docs.findock.com/docs/payment-processors/payment-methods/lsv-direct-debit.md): LSV+ is a direct debit scheme used in Switzerland.
 - [MobilePay](https://docs.findock.com/docs/payment-processors/payment-methods/mobilepay.md): MobilePay is a digital wallet payment method used in Finland and Denmark that is part of the Vipps MobilePay service.
 - [OGM](https://docs.findock.com/docs/payment-processors/payment-methods/ogm.md): OGM is a payment method used for payment requests in Belgium.
 - [Payment methods overview](https://docs.findock.com/docs/payment-processors/payment-methods/payment-methods-overview.md): FinDock supports dozens of payment methods through integrated Payment Service Providers and native payment processing capabilities.
 - [PayPal](https://docs.findock.com/docs/payment-processors/payment-methods/paypal.md): PayPal is a payment method as well as a payment service provider. The payment method is a digital wallet widely supported around the world.
 - [PostFinance e-finance](https://docs.findock.com/docs/payment-processors/payment-methods/postfinance-efinance.md): PostFinance e-finance was a payment method used in Switzerland which has been replaced by PostFinance Pay.
 - [PostFinance Pay](https://docs.findock.com/docs/payment-processors/payment-methods/postfinance-pay.md): PostFinance Pay is an online banking payment method used in Switzerland.
 - [PostFinance PostCard](https://docs.findock.com/docs/payment-processors/payment-methods/postfinance-postcard.md): PostFinance PostCard was a payment method used in Switzerland which has been replaced by PostFinance Pay.
 - [Pre-authorized Debit (PAD)](https://docs.findock.com/docs/payment-processors/payment-methods/pre-authorized-debit.md): Pre-authorized Debit is a direct debit scheme used in Canada.
 - [Przelewy24](https://docs.findock.com/docs/payment-processors/payment-methods/przelewy24.md): Przelewy24 is an online banking payment method aggregator in Poland.
 - [QR-bill](https://docs.findock.com/docs/payment-processors/payment-methods/qr-bill.md): QR-bill is a payment method based on the ESR payment reference and used for payment payment requests in Switzerland.
 - [Satispay](https://docs.findock.com/docs/payment-processors/payment-methods/satispay.md): Satispay is a digital wallet payment method used in Italy.
 - [SEPA Credit Transfer](https://docs.findock.com/docs/payment-processors/payment-methods/sepa-credit-transfer.md): SEPA, the Single Euro Payments Area, includes a credit transfer scheme widely used throughout Europe.
 - [SEPA Direct Debit](https://docs.findock.com/docs/payment-processors/payment-methods/sepa-direct-debit.md): SEPA, the Single Euro Payments Area, includes a direct debit scheme widely used throughout Europe.
 - [Sofort](https://docs.findock.com/docs/payment-processors/payment-methods/sofort.md): Sofort was an online payment method for payment requests made as instant bank transfers in Germany. The payment method is now part of the Klarna Pay Now service.
 - [Standing Order](https://docs.findock.com/docs/payment-processors/payment-methods/standing-order.md): Standing orders are recurring bank transfers used in the UK.
 - [Swish](https://docs.findock.com/docs/payment-processors/payment-methods/swish.md): Swish is a digital wallet payment method used in Sweden.
 - [Tikkie](https://docs.findock.com/docs/payment-processors/payment-methods/tikkie.md): Tikkie is a popular payment method in the Netherlands used for sharing payment requests as links or QR codes.
 - [TWINT](https://docs.findock.com/docs/payment-processors/payment-methods/twint.md): TWINT is online banking payment method used in Switzerland.
 - [Vipps MobilePay Donations payment method](https://docs.findock.com/docs/payment-processors/payment-methods/vipps-mobilepay-donations.md): Vipps MobilePay Donations is payment method and service for nonprofits that is part of the Vipps MobilePay service.
 - [Vipps payment method](https://docs.findock.com/docs/payment-processors/payment-methods/vipps.md): Vipps is a digital wallet payment method used in Norway that is part of the Vipps MobilePay service.
 - [FinDock Payment API](https://docs.findock.com/api/payment-api-v2.md): The FinDock Payment API is a REST API for handling one-time and recurring payments. The API also provides informational endpoints you can use to build dynamic front-end applications that are not dependent on a specific Salesforce of FinDock configuration. Alongside primitive data types such as `string`, the Payment API uses data types that might be unfamiliar to you if you have not worked with Salesforce. These data types are Salesforce objects, record types and fields. ## Objects, record types and fields Salesforce objects (sObjects) are stored as records in the Salesforce database. These records are persistent representations of data. Some API resources accept, or even require, sObjects. The Payer block, for example, requires sObjects such as Contact and Account. The API allows you to define these objects in payloads. FinDock sObjects like Inbound Report can be included as well, but they require you to specify the object fields as Salesforce fields. **Record types** let Salesforce administrators offer specific business processes, picklist values, and page layouts to different users. Organizations can, for example, differentiate between `Account` object records by assigning them an `Organization` or `Household` record type. This facilitates the application of different types of page layouts or possible field values based on what record type an `Account` is. **Fields** are defined at the object level in Salesforce. Next to the out-of-the-box fields from Salesforce, custom fields can be added to objects. Use the Object Manager in Salesforce Setup to see available fields. Implementations of Salesforce can use different fields for a value like `email`. Custom fields for *standard Salesforce objects* like `Contact` and `Account` are passed with "__c" at the end of the field name. In the example below, you see the standard fields `FirstName` and `LastName` and a custom field `TwitterHandle` for the Contact object. ```json { "Payer":{ "Contact":{ "SalesforceFields":{ "FirstName":"Test", "LastName":"Payer", "TwitterHandle__c": "@TestPayerFamily" } } } } ``` Custom fields for **custom FinDock objects** like `Installment` and `Recurring Payment` can also be passed in a `SalesforceFields` object. `SalesforceFields` passed in the `OneTime` object are copied to the `Installment` record in Salesforce and `SalesforceFields` passed in the `Recurring` object are copied to the `Recurring` object in Salesforce. To which `Recurring` object the values are stored depends on the FinDock configuration. ```json { "OneTime":{ "Amount": 10.0, "SalesforceFields": { "Sales_Invoice__c": "a506E0000009TfL" } } } ``` ## Working with payer details Salesforce provides two objects to define the Payer: - Account: usually an organization - Contact: an individual Added to that simple split is [Person Account](https://help.salesforce.com/s/articleView?id=sf.account_person.htm&type=5), which stores information about individual people by combining certain Account and Contact fields into a single record. It is not its own object, but can be stored as an Account with a specific record type (see below). Some features of Salesforce - like Fundraising used in NonProfit Cloud (NPC) - *require* Person Account. The payer details are a Person Account record rather than a Contact. Make sure to always check with your Salesforce admin whether they are enabled and used. To send Person Account details to the Payment API, use an Account object with a `RecordTypeName` (API name) of the type Person Account. By default the API name is `PersonAccount`, but there can be customized or the org (Salesforce environment may have multiple Person Account record types. Always consult your Salesforce admin regarding record types. Whether an Account or Contact record, you always need to take into consideration how the payer is deduplicated. Every organization has [configured deduplication rules](https://help.salesforce.com/s/articleView?id=sales.managing_duplicates_overview.htm&type=5) that define the information the payment intent message needs to include for deduplication, bearing in mind that the more data points you have, the more effective deduplication is. ```json { "Account":{ "RecordTypeName": "person-account-record-type", "SalesforceFields":{ "Name":"Test Payer", "BillingStreet":"Any Street", "BillingCity":"Any City", "BillingPostalCode":"00000" } } } ``` For Person Accounts the following exceptions for (custom) field notations apply: - Standard Account fields can be passed as regular fields: `"BillingStreet":"Any Street"`. - Custom Account fields can be passed with the regular `__c` suffix: `"Custom_Street__c":"Any Street"`. - Standard Contact fields need to be prefixed with `Person`, with the exception of FirstName, LastName, Salutation which are passed as regular fields: `"PersonEmail" : "test@findock.com"`. - Custom Contact fields need to be suffixed with `__pc`: `"Custom_email__pc":"test@findock.com"` ```json { "Account":{ "RecordTypeName": "person-account-record-type", "SalesforceFields":{ "FirstName": "John", "LastName": "Payer", "PersonEmail": "test@findock.com", "BillingStreet": "Any Street", "Custom_account_field__c": "Apartment Name", "Custom_contact_field__pc": "Middle Name" } } } ``` For the FinDock for Fundraising source connector used with NonProfit Cloud (NPC), for example, the following exception applies: Since the "Recurring" object (Gift Commitment) is split in two objects (Gift Commitment & Gift Commitment Schedule), a prefix `GiftCommitment` is required to set SalesforceFields on this object. Fields without prefix are assumed to be set on the Gift Commitment Schedule object. Example: `GiftCommitment.GiftVehicle`. You can check which Source Connectors are available by performing a GET operation on the [Source Connector](/api/payment-api-v2/source-connectors) endpoint. ## Authentication Authentication is accomplished through an [Oauth2.0 authorization flow](https://help.salesforce.com/articleView?id=remoteaccess_oauth_web_server_flow.htm&type=5). Each Salesforce environment requires its own token. A [refresh token](https://help.salesforce.com/articleView?id=remoteaccess_oauth_flows.htm&type=5) can be used to acquire a new access token if the current token has expired. Read more on how to authenticate to Salesforce in the [Salesforce developer guide](https://help.salesforce.com/articleView?id=remoteaccess_oauth_flows.htm&type=5). Both `client_id` and `client_secret` can be acquired from the Salesforce 'Setup' from a 'Connected App'. - The `Authorization` token can be passed as a Bearer token in the request Header. - To Acquire a new `Authorization` token with the returned `Refresh` token, please make sure to pass the right `grant_type`, `client_id`, `client_secret` and `refresh_token` as specified in the Salesforce documentation referenced above. To get up and running quickly, use the (unofficial-but-provided-by) [Salesforce Postman Collection](https://github.com/scolladon/postman-salesforce-apis), as explained in this [blog](https://developer.salesforce.com/blogs/2020/03/explore-the-salesforce-apis-with-a-postman-collection.html) and look for the 'auth' folder. ## Error and response codes IF the API is not called successfully, you receive a HTTP Status Code `4xx` or `500`. A `422` code is returned when the message was well-formed, but could not be processed because of, for instance, wrong data. In the response you find additional information on how to prevent or handle the error through an array of `Errors` with an `error_code` and `error_message`, like in the following example. ```json { "Errors": [ { "error_message": "Amount can't be 0 or negative", "error_code": "200" } ] } ``` Below are some of the possible error codes: | Code | Description | | --- | --- | | 010 | Malformed request: missing one or more mandatory core parameter(s) | 011 | Malformed request: missing one or more mandatory Payment Processor parameters | 012 | Malformed request: missing one or more mandatory SourceConnector parameters | 200 | Invalid data: the supplied data is incorrect (e.g. an invalid e-mail address). | 201 | Sort code or bank account is invalid (Bacs Direct Debit). | 202 | IBAN _<your-IBAN>_ is not valid. | 203 | The provided IBAN is not in SEPA geographical zone. | 204 | BIC is required to collect SEPA Direct Debit from a non-EAA country bank account. | 205 | Street, Housename or Number, Zip code and City are required to collect SEPA Direct Debit from a non-EEA country bank account. | 206 | Clearing number and/or bank account invalid (Sweden). | 998 | An object is missing and no default is specified in the org. | 999 | Error without specific category: consult the `error_message` for details. ## Webhook events and notifications To receive updates on payments created with the `/PaymentIntent` endpoint: - pass an endpoint URL in the `WebhookURL` parameter in the request body. - add your URL to the [Remote Site Setting](https://help.salesforce.com/articleView?id=configuring_remoteproxy.htm&type=5) of the Salesforce org. FinDock sends you notifications for the following events around your API call: | Event | Description | | ----- | ------------ | |`paymentIntent.processed` | Processing of the API call has finished successfully. This does not mean a payment is collected. | |`paymentIntent.in_review` | Processing of the API call has stalled and manual intervention from Salesforce side is needed. This does not stop the payer from completing the payment flow. | |`paymentIntent.failed` | Processing of theAPI call has failed and needs to be handled in the Salesforce environment. This does not stop the payer from completing the payment flow. | |`installment.created` | When an Installment record (expected one-time payment) is created. | |`installment.status_change` | If the `status` of the Installment record changes, either via a notification from a PSP or manually changed. | No specific events are sent for recurring payments other than the `paymentIntent` which contains the Salesforce Id of the recurring record. For more information about processing online payments, please [Processing online payments](/docs/@production/reconciliation/processing-and-reconciling-online-payments.md). For `paymentIntent` you receive notifications with the following body. Each event contains a `type` and a `data` object with further details. Check out the [PaymentIntent object schema](/api/payment-api-v2/payment-intent) for definitions. ```json { "type": "paymentIntent.processed", "data": { "Status": "Matched", "Recurring": { "Url": "/services/data/v65.0/sobjects/cpm__Recurring_Payment__c/a0V3X00000S7b5YUAR", "Type": "cpm__Recurring_Payment__c", "Id": "a0V3X00000S7b5YUAR" }, "Payer": { "Contact": { "Url": "/services/data/v65.0/sobjects/Contact/0033X00003H9uZPQAZ", "Type": "Contact", "Id": "0033X00003H9uZPQAZ", "Name": "Test Payment" }, "Account": { "Url": "/services/data/v65.0/sobjects/Account/0013X00002bZPGIQA4", "Type": "Account", "Id": "0013X00002bZPGIQA4", "Name": "Payment Family" } }, "OneTime": { "Url": "/services/data/v65.0/sobjects/cpm__Installment__c/a083X00001mFTBAQA4", "Type": "cpm__Installment__c", "Id": "a083X00001mFTBAQA4", "Status": "Pending" }, "Id": "pi_6cazikr7625yqt9mf" } } ``` For `installment` you receive a notification with the following body. ```json { "type": "installment", "data": { "Url": "/services/data/v65.0/sobjects/cpm__Installment__c/a083X00001kJynLQAS", "Type": "cpm__Installment__c", "Id": "a083X00001kJynLQAS", "Target": "Adyen1", "Status": "Collected", "RecordTypeName": "Receivable", "PayUrl": "https://link.dev.findock.com/pay/3xxxxmuai2/8897b4da-e48a-7ff3-90dd-ecb65094802c", "Payments": [ { "Url": "/services/data/v65.0/sobjects/cpm__Payment__c/a0R3X00000V1sutUAB", "Type": "cpm__Payment__c", "Id": "a0R3X00000V1sutUAB", "PaymentProcessor": "PaymentHub-Adyen", "PaymentMethod": "CreditCard", "CollectionDate": "2020-11-26", "Amount": 15 } ], "PaymentProcessor": "PaymentHub-Adyen", "PaymentMethod": "CreditCard", "PaymentIntentId": "pi_5jthokq7z8som0w6o", "AmountOpen": 0, "Amount": 15 } } ```