StoreConnect Pay

StoreConnect Pay is StoreConnect’s own branded gateway, built on NMI and routing production traffic through StoreConnect’s reseller gateway. Use this process to set it up for card payments, bank (ACH) payments, or both at web checkout.

Card and ACH are two separate Payment Provider records, not two settings on one record. Set up whichever you need:

What customers pay with	Provider picklist value
Card	StoreConnectPay
US bank account (ACH)	StoreConnectPayAch

Both are offered on web checkout only. Neither is available at the point of sale.

If you already run NMI, the setup fields and the checkout templates are the same. The only difference is the gateway the traffic goes to.

Before you start

• StoreConnect Pay credentials provisioned for your account. Ask your StoreConnect account manager.
• Your Tokenization (public) key and your Private (security) key. These are two different keys and they go in two different fields.
• For ACH, eCheck enabled on the account, and US bank account details from the customer. See ACH direct debit.

Configure StoreConnect Pay in StoreConnect

1. Open the Payment Providers list and select New.
2. Complete the fields as follows, then select Save.

StoreConnect field	Select or enter
Name	StoreConnect Pay, or StoreConnect Pay - test for sandbox
Display Name	The label customers see at checkout, for example Credit card
Provider	The StoreConnect Pay option, picklist value API name StoreConnectPay (or StoreConnectPayAch for bank payments)
API Mode	sandbox or production
API Key	Your Tokenization (public) key
API Secret	Your Private (security) key
Channels	Leave blank, or include web
API Options	Leave blank. See Route to a different gateway host if you have been given one
Active	Select this to offer the provider at checkout

The API Key field must contain your Tokenization key. StoreConnect passes it to Collect.js, which renders the card or bank fields at checkout. If it is empty, those fields do not appear and customers cannot pay.

The API Secret field takes the Private key, which StoreConnect uses server side and never exposes to the browser. The two keys are not interchangeable.

The provider now appears as a payment option at checkout, and a test transaction records a payment against the order with the gateway’s transaction ID.

Sandbox testing

Set API Mode to sandbox and use the sandbox credentials your account manager provides.

In sandbox mode, if API Options has no gateway_host, traffic goes to NMI’s shared sandbox gateway, which needs sandbox credentials. A production key sent to that gateway is rejected when the token is created, and the symptom is the card fields never appearing at checkout rather than an error message. If the fields do not render in sandbox, check that the key belongs to the sandbox environment before looking anywhere else.

Route to a different gateway host

Production traffic goes to StoreConnect’s reseller gateway by default, and almost every store leaves this alone. If your account manager gives you a different host, add it to API Options as a bare hostname, with no https://, no path, and no trailing slash:

```yaml

gateway_host: storeconnect.transactiongateway.com ```

The host applies in sandbox mode as well as production, from StoreConnect v21.0.13 onwards. On an earlier version, sandbox always used NMI’s shared sandbox gateway and ignored this setting.

Take payment from a Salesforce order

The card provider also appears on the payment page for an order in Salesforce, and on the embedded payment page for a cart created through the API. The behavior matches NMI. See NMI.

Bank payments join both pages in StoreConnect v22. On an earlier version, StoreConnect Pay ACH is offered at web checkout only.

For a bank payment, the charge is recorded as pending until settlement resolves, which takes a few business days. A subscription order stores a customer vault ID against the subscription so renewals bill the saved bank account, and no local payment method record is created for the customer.