# Authorize.net

FinDock integrates with [Authorize.net](https://www.authorize.net/), an global provider of payment services and subsidiary of Visa.

| [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 |  |  |  |


## Prerequisites

* FinDock is installed and configured.
* Working connections to ProcessingHub and WebHub.


## Prepare Authorize.net merchant account

To integrate FinDock with an Authorize.net merchant account, you'll need API credentials and a webhook endpoint for notifications. You create the credentials through the Authorize.net portal.

To create API credentials:

1. Log in to your Authorize.net account.
2. If you are setting up an org for testing, [create a sandbox account](https://developer.authorize.net/hello_world/sandbox.html).
3. Follow the [Authorize.net instructions](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-07619) to create new **Transaction Key** and **Signature Key** credentials.
4. Copy your API Login ID and Transaction Key values and save them in a temporary location. They are needed for the FinDock setup. (The Signature Key is for webhook notifications to FinDock.)


After the FinDock configuration, you'll need to go back to the Authorize.net portal to complete the integration, so you can leave it open in a separate browser tab or window.

## Install and activate Authorize.net extension

Follow the standard procedure for [installing](/docs/setup/install-findock) and [activating](/docs/setup/add-payment-extensions) the Authorize.net for FinDock payment extension.

Check and assign the [required permissions](/docs/setup/general-permission-guidance). If you are using custom permission set groups, ensure the [package-specific permission sets](/docs/setup/permission-set-groups#authorize-net-permission-sets) are assigned.

## Activate payment method and add account for Authorize.net

To integrate with Authorize.net, you need to add a merchant account in FinDock that defines named credentials and other details related to your customer account with Authorize.net. Details may vary depending on whether you are configuring a test or production setup.

To add a merchant account for Authorize.net:

1. Launch the FinDock app and go to the **FinDock Setup** tab.
2. Click **Processors & Methods** in the left-hand menu.
3. On the **Installed** tab, click the Authorize.net processor entry.
4. On the **Accounts** tab, click **Add account** and fill in the settings as described below.
5. If not done already, on the **Payment Methods**, click the toggle next to the payment methods you want to activate and use.


**Authorize.net target settings**

* **Merchant Account Name (Target)**: This is the value that you see in Target picklists. The name does not need to match the name of your account in the Authorize.net portal, however, make sure it easily distinguishable from other accounts in the org. If you use multiple currencies, we recommend including the currency identifier in the name.
* **Test Account**: If you are configuring a test integration, mark this checkbox. The If checked the test endpoint will be used.
* **Default Account**: Toggle this setting on if you want this account to be used for new Authorize.net payments that do not include a specific target in the payment intent.
* **Log Requests**: Toggle this setting on if you want to capture all API requests between FinDock and Authorize.net. The requests are stored in Log object records.
* **Notification URL**: This is the webhook URL used by Authorize.net to notify FinDock of payment events. Copy-paste the URL generated by FinDock into the Webhooks configuration of your Authorize.net portal under Notification Settings > Webhooks.
* **Currency**: Select the currency used by your Authorize.net account. Each merchant account at Authorize.net supports a single currency. If you use multiple currencies, you need separate merchant accounts at Authorize.net (and in FinDock) for each currency.
* **API Login ID**: Copy-paste the unique API Login ID associated with the account you are integrating with FinDock. If you do not have the original email from Authorize.net with this information, you can find the ID in your account portal under General Security Settings > API Credentials & Keys.
* **Transaction Key**: Copy-paste the unique Transaction Key for the API Login ID you entered above. If you don't have the original email, you can generate a key under General Security Settings > API Credentials & Keys.


## Add webhook endpoint to Authorize.net

The Notification URL from your target setup above needs to be added to your Authorize.net account so FinDock can receive webhook events from Authorize.net.

To add the Notification URL to Authorize.net:

1. Log in to your Authorize.net account.
2. Follow the [Authorize.net instructions](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-07621) to add a new endpoint for FinDock.
3. For the new FinDock endpoint:
  * Enter a name for the endpoint.
  * Copy-paste the Notification URL from FinDock into the Endpoint URL field.
  * Set status to Active.
  * Select **All events** for the endpoint.
4. Click **Save** when you are done.


## Using Authorize.net

For both credit card and ACH payments, FinDock relies on the Transaction Id from Authorize.net to manage the installments. In the case of recurring ACH payments, FinDock also creates a mandate to capture the payer authorization for future installments of recurring payment.

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

* [Giving Pages](/docs/payments/creating-and-updating-giving-pages): accept payments through Givings Pages configured to use Authorize.net for card payments
* [PayLinks](/docs/payments/configuring-findock-paylinks): create and share PayLinks for one-time or recurring payments
* [Payment API](/api/how-to-use-the-payment-api-v2): custom front-end integration to the Payment API to accept new payments and update existing commitments
* [Virtual Terminal - MOTO](/docs/payments/configuring-findock-moto): FinDock component for agents to setup payments with the payer present


To validate a payer's account for a card, Authorize.net validates the payer's account for the card before setting up the payment. This can be a zero-dollar authentication step or a 1-cent transaction. The validation only applies to production environments and depends on the payer's card type and processor.

New one-time payments are automatically processed, collected and reconciled like normal [online payments](/docs/payments/accepting-payments-with-findock).

After a new recurring payment is set up, you use [payment schedules](/docs/payments/introduction-to-payment-schedules) to collect future installments.

### Refunds and transaction settlement with Authorize.net

The FinDock integration with Authorize.net also supports both full and partial refunds. You can issue a refund with the [Authorize.net Quick Refund feature](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001221). The refund process sends notifications to FinDock for updating the impacted installments and creating negative Payment records. In the case of full refunds, the installment status is changed to Refunded. If the refund is a partial refund, the installment status is updated to Partially paid.

FinDock also handles notifications of transactions that are voided after they have been captured. In the voiding scenario, the transactions are captured but not yet settled, so they are not technically refundable. Instead, a void action is used by Authorize.net. FinDock uses this void notification uses to update the related installment status to Refunded (and create a negative Payment record to cancel out the initial positive payment). In addition, FinDock adds a Last Status Reason value to the installment that refers to the voiding action.

### IP address fraud detection

FinDock supports the [IP-Shipping Address Mismatch Filter](https://account.authorize.net/help/Tools/Fraud_Detection_Suite/Transaction_Filters/IP_Shipping_Address_Mismatch_Filter.htm) fraud detection option which needs to be enabled in your merchant account.

Once enabled, FinDock uses two fields for IP address fraud detection:

* Customer IP Address (`aufd__Customer_Ip__c`) on Mandate to store the payer's IPv4/IPv6 address
* Country (`cpm__Country_PL__c`) on Payment Profile to store the 2-letter ISO code of the payer's country


For a new (recurring) payers, the customer IP address is captured from the incoming Authorization.net notification (in an inbound report). All subsequent collections for that same recurring payment use the IP address. If for some reason FinDock does not have an IP address, e.g. for existing Authorize.net payers, new collections do not include an IP addresses. The payer either needs to create a new recurring payment, or the merchant can manually add the IP address. If no IP address is available, FinDock uses 0.0.0.0 as the Customer IP Address value.

The Country can be set with the `countryCode` parameter in the PaymentMethod block of the [payment intent](/api/payment-api-v2/payment-intent). For Giving Pages or PayLinks, enable the  `countryCode` parameter for the credit card payment method configuration. You can use [merge fields](/docs/payments/payment-form-configuration-options#merge-fields) from address input fields to prefill the country code.

If fraud is detected, Authorize.net sends FinDock fraud-related notifications which are handled as follows:

* `payment.fraud.held`
  * Installment Status = Pending
  * Last Status Reason = 252 - The transaction was accepted, but is being held for merchant review.
* `payment.fraud.declined`
  * Installment Status = Failed
  * Last Status Reason = 251 - The transaction was declined as a result of triggering a Fraud Detection Suite Filter.
* `payment.fraud.approved`
  * Processed as a normal successful payment intent (same as `payment.authcapture.created`)


## Payment API examples

The following are example payment intent messages for one-time and recurring card payments set up via the Payment API (with FinDock as source).

If you are passing several parameters in a payment intent, the redirect URL may get very long. The Description in particular, can be long (max. 255 characters). A very long URL can break the payment flow with Authorize.net, leading to a "page isn't working" redirect error.

### One-time card payment


```json
{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Test",
                "LastName": "Payment",
                "Email": "testpayment@findock.com"
            }
        }
    },
    "OneTime": {
        "Amount": "100"
    },
    "PaymentMethod": {
        "Name": "Creditcard",
        "Processor": "AuthorizeNet-for-FinDock"
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}
```

### Recurring card payment


```json
{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Test",
                "LastName": "Payment",
                "Email": "testpayment@findock.com"

            }
        }
    },
    "OneTime": {
        "Amount": "25",
    },
    "Recurring": {
        "Amount": "25",
        "Frequency": "Monthly",
        "StartDate": "2025-04-01"
    },
    "PaymentMethod": {
        "Name": "CreditCard",
        "Processor": "AuthorizeNet-for-FinDock"
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}
```