Accept Blue

Setting up Accept.blue

The Foxy wiki has no ported setup instructions for this gateway ("Details coming soon" is all it says), so the steps below are the standard Foxy admin flow plus what an Accept.blue account requires.

1. 1

   Sign up for an Accept.blue account, or ask your ISO/reseller partner to provision one — Accept.blue sells primarily through partners rather than direct self-signup.

2. 2

   In the Foxy administration at https://admin.foxy.io, go to Settings > Payments.

3. 3

   Select the payment method set you want to use, or create one.

4. 4

   Click Add payment method + and choose Accept.blue.

5. 5

   From your Accept.blue account, copy your credentials into the Foxy panel: the API Source Key field takes your Accept.blue source key, and the API Pin field takes your Accept.blue API pin.

6. 6

   Click Create to save the payment method.

The panel is split into a Live setup block and a Test setup block, both carrying the same two fields, API Source Key and API Pin. There is no third credential for this gateway.

Testing

Foxy provides shared test credentials for Accept.blue, so you can run test transactions without setting up your own sandbox account. Leave the Test setup fields as they are.

Those shared credentials are for testing the integration only. If you need to test against your own account configuration — your own enabled card brands, your own Level 2/3 field mapping — get a sandbox account from Accept.blue and fill in the Test setup fields with its credentials.

Obtaining a test account

The wiki has no ported information here. Contact Accept.blue, or your reseller partner if you signed up through one, for sandbox credentials.

Test card numbers

The wiki has no ported test card numbers for this gateway. Contact Accept.blue for current test cards, or check their developer documentation at accept.blue/api/.

Advanced features

• Level 2/3 interchange data. Accept.blue supports Level 2 and Level 3 data submission on card transactions. This matters specifically to B2B merchants: commercial and purchasing cards qualify for lower interchange rates when a transaction includes the extra line-item and tax detail Level 2/3 data carries (purchase order number, tax amount, line items, and similar fields), instead of settling at the higher default commercial-card rate. Among the gateways Foxy integrates with, Level 2/3 support is uncommon — internally, only Accept.blue and Chase Orbital carry it. If reduced interchange on commercial cards is a requirement for a prospective merchant, that narrows the gateway choice considerably.

• Card verification. Accept.blue has card verification enabled automatically, with a $1 verification amount for Visa, Mastercard, American Express, and Discover.

• Authorize only. Accept.blue supports authorization-only transactions, so you can authorize at checkout and capture later.

• ACH. Accept.blue has a separate ACH gateway integration (accept_blue_ach) for merchants who want to accept bank-account payments alongside cards.

Important notes and caveats

• 3D Secure is not supported on this integration (per the Foxy gateway configuration), so there is no 3DS setup to configure on the Foxy side.

• Multi-currency is not supported. Accept.blue processes USD only through this integration.

Troubleshooting

The wiki has no response-code guidance for this gateway. Contact Accept.blue support — they own the response code definitions and can see transaction detail Foxy cannot.