Payment gateway (merchant) credentials for Trinity

Card payments on your website go through your own payment gateway, under your own merchant account. Trinity needs that gateway's API credentials, which are different from the login you use to view your transactions.

No merchant account yet? You will need a processor that accepts firearms businesses. Email support@2adata.com and we can point you in the right direction.

Authorize.Net

What you need: your API Login ID and a Transaction Key. In the Authorize.Net Merchant Interface they are under Account > Settings > Security Settings > API Credentials & Keys.

You can enter these yourself:

1. In your admin, open System > Settings and choose the Payment tab.
2. Enter your API Login ID and Transaction Key.
3. Leave Use Sandbox Mode (Testing) unticked for a live store, and press Save Payment Settings.
4. Under Test Your Payment Gateway, press Test Connection. It checks your login and tells you whether you are taking real payments or running in test mode. It does not charge a card.

A store left in sandbox mode takes orders all day and settles nothing, so the test is worth running after any change.

Once saved, the Transaction Key is never shown again. To change it, type the new key over the dots.

Blue Dog Payments

What you need: your gateway secret key, and whether the account is live or sandbox. Blue Dog is set up for you by 2AData, so send these the way described in Sending credentials to 2AData safely.

TransNational (NMI)

Trinity also supports TransNational through NMI. This is set up for you by 2AData; email support@2adata.com and we will tell you exactly which keys to send.

Another gateway

If you use a gateway not listed here, email support@2adata.com with its name before you send any credentials, and we will tell you whether Trinity can work with it.

Related

• Connecting your distributors to Trinity
• What happens when NoFraud declines an order
• The full Distributor Credentials Guide on 2AData.com