# Paya

FinDock integrates with Paya, an payment service provider that is today part of [Nuvei](https://www.nuvei.com/paya).

The Paya payment extension is in a closed pilot. Please contact FinDock Support if you would like to participate. Please note that this article includes pre-release features that may not yet be deployed to all pilot customer orgs.

| [Multi-merchant](/docs/payment-processors/multi-merchant-accounts-for-psps) | [Multi-currency](/docs/payment-processors/multiple-currency-support-in-findock) |
|  --- | --- |
|  |  |


| Payment Method | [Online Payment Flow](/docs/payments/accepting-payments-with-findock#online-payment-collection) | [Integration Patterns](/docs/payments/accepting-payments-with-findock#online-integration-patterns) | [Data Entry](/docs/payments/accepting-payments-with-findock#data-entry) | One-time | Recurring | [Refunds](/docs/payment-processors/payment-methods/payment-methods-overview#refunds) |
|  --- | --- | --- | --- | --- | --- | --- |
| [ACH Direct Debit](/docs/payment-processors/payment-methods/ach-direct-debit) | Online Redirect | API, [Virtual Terminal](/docs/payments/accepting-payments-with-findock#findock-virtual-terminal) | No |  |  |  |
| [Card](/docs/payment-processors/payment-methods/cards) | Online Redirect | API, Virtual Terminal | No |  |  |  |


## Pilot scope and limitations

The FinDock integration with Paya is a work in progress. We are adding features to the payment extension during the pilot phase. Currently, please note the follow limitation(s):

* Recurring payments via API (PayLinks, Giving Pages and Payment API) do not support AVS. New payment intents for recurring payments must exclude billing information
* Refunds from Salesforce support Paya as the payment processor, but only work with FinDock Standalone or Fundraising (NPC, EDU) as source at this time


**Prerequisites**

* FinDock is installed and configured.
* Working connections to ProcessingHub and WebHub.
* You have at least one Paya account and the associated credentials.


## Install Paya for FinDock

To install the Paya payment extension, the Paya feature pilot needs to be enabled for your org.

To install Paya and activate payment methods:

1. Contact FinDock Support and provide [your Org Id](/faq/what-is-my-salesforce-org-id).
2. Wait for confirmation that the Paya feature pilot is enabled.
3. Once enabled, go to FinDock Setup and install Paya for FinDock following the [standard procedure](/docs/setup/add-payment-extensions#install-a-payment-extension).
4. Activate one or more payment methods following the [standard procedure](/docs/setup/add-payment-extensions#add-payment-methods).
5. Check and assign the [required permissions](/docs/setup/general-permission-guidance) and [FinDock permission set groups](/docs/setup/permission-set-groups).
6. If you installed the Paya package prior to the March '26 release, add the **FinDock Paya Base** permission set to all FinDock permission set groups.


## Configure Paya for FinDock

To integrate FinDock with Paya, you need to add a merchant account. The merchant account setup requires your Paya account Merchant Id and Merchant Key. These credentials are only available in the email response from Paya when you set up the account.

For ACH sandbox testing, you need to use Merchant Id 173859436515 and Merchant Key P1J2V8P2Q3D8. You can not perform ACH sandbox tests on your own merchant.

To add a merchant account:

1. Go to FinDock Setup and select **Processors & Methods**.
2. On the **Installed** tab, click the Paya processor entry.
3. On the **Accounts** tab, click **Add account**.
4. Enter your Merchant Id and Merchant Key.
5. Set the default **Address Verification Services (AVS)** requirement for new payment intents for all [payment acceptance channels](/docs/payments/accepting-payments-with-findock). AVS must be enabled for your account at Paya to use it with FinDock. The options are:
  * None: billing information for AVS *cannot be* included
  * Optional: billing information for AVS *may be* included
  * Required: billing information for AVS *must be* included
6. Adjust other settings as needed and click **Save**.


## Configure notifications from Paya

FinDock reconciles Paya payments using asynchronous notifications in the form of a CSV file. This requires you to set up file delivery from Paya.

To configuration notifications:

1. If you haven't already, go to Salesforce Setup > Email Settings and enable **Allow Posts via Email** and **Allow Attachments via Email**.
2. If you haven’t already, go to FinDock Setup and [configure file exchanges](/docs/setup/configure-processinghub#configure-file-exchanges).
3. Ensure your FinDock integration user is a member of the Chatter group for file exchanges.
4. Note down the **Group Email** on the Chatter group page for file exchanges.
5. Log into the Paya Virtual Terminal with user credentials associated with the merchant account you added above.
6. Go to Configuration > Email Notifications > General email settings.
7. Adjust the Batch Close Notification Settings:
  * **Batch Close Email Address**: your FinDock integration user email address
  * **Batch Close Notifications**: select the option “Email Me, Generic Export Format”
8. Save your changes and go back to your Salesforce org.
9. Configure the integration user email to forward emails from `noreply@paya.com` to your file exchange Chatter Group Email.


## Using Paya for FinDock

For both credit card and ACH payments, FinDock relies on the Payment Intent Id from FinDock to create the Paya Transaction Order Number value to manage the installments. In the case of recurring ACH payments, FinDock also creates a mandate to capture the payer authorization to collect future installments. However, the mandate itself is controlled by Paya.

You can set up and accept one-time and recurring payments through the following channels:

* [FinDock Virtual Terminal](/docs/payments/configuring-findock-moto) (MOTO)
* [PayLinks](/docs/payments/configuring-findock-paylinks)
* [Giving Pages](/docs/payments/configuring-giving-pages)
* [Payment API](/api/getting-started-with-the-payment-api-v2)


New one-time payments are automatically processed and collected. For recurring payments, you use [payment schedules](/docs/payments/introduction-to-payment-schedules) to collect future installments. When running large payment schedules, please be aware that you may receive multiple email notifications from Paya about transaction updates. (Please contact Nuvei, if needed, regarding the notification settings in your production merchant account batch/settlement configuration.)

### Address Verification Service

Please note that FinDock AVS settings are independent of your account settings at Paya. If you have enabled AVS at Paya, but do not require it in your FinDock setup, Paya payments fail.

Paya supports fraud detection through Address Verification Service (AVS). The option is enabled through your merchant account [Paya Exchange settings](https://support.paya.com/44663-how-to/310559-how-to-change-the-address-verification-avs-settings-in-paya-exchange).

If you are migrating existing payers to FinDock that have AVS in use, please note that in addition to the [standard data migration](/docs/setup/migrating-payment-data), you there are several [AVS-specific fields for Payment Profile to migrate](/docs/setup/migrating-payment-data-special-considerations#paya-migrations).

If the payer's street address has more than one line (manually entered or pre-filled), FinDock automatically combines the multi-line address into one line with line breaks replaced by commas. This is required as Paya AVS uses only one address line.

You have two controls for AVS in FinDock. The target-level (merchant account) setting tells FinDock what to do by default for any Paya payment using that target. In addition, specifically for MOTO (virtual terminal) payments, you have an **Override AVS** setting in the FinDock Payment component.

### AVS with virtual terminal payments

If AVS is required for the target used in the Payment component configuration, the AVS override cannot change that requirement. The component level override can only be stricter, e.g. the target-level setting makes AVS optional, but for the component, you use the override to make AVS required. In addition to the override, you define which Salesforce fields are used to pre-fill address values in the component.

Payment Component AVS settings
The Payment component can also be used in Flows with AVS enabled. With Flows, merge fields should be used for pre-filling address values.

Payment Component AVS settings for Flow
### Refunds with Paya

With the Paya integration, FinDock supports refunds from Salesforce. You can initiate refunds for individual Payment records for a given (receivable) installment. For further information, see [Refunding from Salesforce](/docs/payments/refunds-from-salesforce).

## Reconciling Paya payments

Payment reconciliation is [file-based](/docs/reconciliation/processing-bank-statements) using the file Paya sends on a daily basis. Transaction entries are parsed into Inbound Report records that are processed through [Guided Matching](/docs/reconciliation/what-is-guided-matching). For Paya, the Inbound Report type is Paya-for-FinDock with the following subtypes.

| Inbound Report Subtype | Installment Status |
|  --- | --- |
| installment.collect | Collected |
| installment.expired | Failed |
| installment.settled | N/A (status unchanged) |
| installment.voided | Failed |