Payment collection cases

The following typical use cases provide a simple outline of the main steps of different kinds of payment collection flows.

One-time credit card payment with PSP

1. Payer authorizes payment online through a custom payment form, FinDock Giving Pages or a hosted PSP page.
2. Required data is automatically created at PSP and in FinDock.
3. PSP notifications to FinDock are automatically processed for reconciliation.

Examples of other payment methods that follow this flow: iDEAL, SOFORT, Bancontact, GoCardless Instant Bank Pay

Recurring SEPA direct debit with FinDock

1. Payer authorizes recurring payment online through custom payment form or Giving Page, or offline through phone or paper.
2. FinDock creates a mandate and recurring payment record; if authorization is offline, the records are created manually by a Salesforce user.
3. Creditor runs a payment schedule, triggering FinDock to generate an installment and create a payment collection file.
4. Creditor submits collection file to bank.
5. Creditor uploads bank statement(s) from the bank, and FinDock automatically reconciles payment(s) for the submitted installment.

Examples of other payment methods that follow this flow: LSV+ and CH-DD. Using FinDock to process Bacs Direct Debit is similar, but requires a separate flow to first register mandates (Direct Debit Instructions) before collecting.

Recurring credit card or direct debit with PSP

1. Payer authorizes recurring payment online through custom payment form or Giving Pages.
2. FinDock creates a mandate and recurring payment record.
3. Creditor runs a payment schedule (manually or through auto-collection), triggering FinDock to generate the next installment.
4. The required data to collect the installment is automatically created in FinDock and at the PSP.
5. PSP notifications about payment status are sent to FinDock and automatically processed for reconciliation.