Authorize.Net

Supported features

Payment provider configuration options

You will need to sign up with Authorize.Net if you don’t already have an account.

To generate the Client Key, log in to the Merchant Interface as an Administrator and navigate to Account > Settings > Security Settings > General Security Settings > Manage Public Client Key.

If the Public Client Key does not yet exist, answer your security question to generate the key.

To specify the Public Key, add the following to the API Options field of the Payment Provider record:

```yaml

public_key: “YOUR_PUBLIC_KEY” ```

Using card and ACH on one merchant account

You can run this provider and Authorize.Net ACH on the same Authorize.Net merchant account. When you do, the two share one customer profile per customer at Authorize.Net, keyed on the customer’s contact record, so a customer’s card and bank account sit side by side under one profile.

StoreConnect keeps the two apart:

• The card provider only ever updates a customer’s stored card, and the ACH provider only ever updates their stored bank account. Updating one leaves the other alone.
• A card subscription renews on the stored card and an ACH subscription renews on the stored bank account, whichever the customer saved most recently.
• Where a customer has more than one card saved, an update is applied to the card their subscription is billed on, rather than adding another.
• If a subscription’s own kind of payment method is not on file at all, the renewal charges whatever the customer does have saved rather than failing.

:::warning This behavior needs StoreConnect v21.0.15 or later, and an earlier version gets it wrong in both directions. A bank account added after a card was discarded without an error, so the customer’s ACH subscription carried on renewing on their card. Updating a payment method wrote over whichever stored method Authorize.Net had marked as default, so saving a card could destroy a customer’s stored bank details and re-point their ACH subscription at that card. If you run both providers on one merchant account, upgrade before you let customers update their payment details. :::

Authorize.Net allows ten stored payment methods per customer. Once a customer reaches that limit, no further payment method can be saved for them until one is removed in the Authorize.Net Merchant Interface.