Configuration

Estimated reading: 5 minutes 184 views

🔑API Keys

All keys are found in your accept.blue merchant dashboard under Sources. Keep your keys private — never share them or commit them to version control.

Live API Key	Your accept.blue live source key. Required for live transactions.
Test API Key	Your accept.blue sandbox source key. Used when Test Mode is on.
Live Tokenization Key	Public key for the Hosted Tokenization iframe and 3DS (live mode).
Test Tokenization Key	Public key for the Hosted Tokenization iframe and 3DS (sandbox).
Test Mode	Toggle between live and sandbox. Disable before accepting real payments.

Permissions matter. Your source key must have Charge permission for basic payments, plus Capture and Adjust if you use the Adjust & Capture feature.

🛠General Settings

Enable / Disable	Toggle the gateway on or off. When disabled it won’t appear at checkout.
Title	Payment method label shown to customers at checkout (e.g. “Credit Card”).
Description	Short text shown below the title on the checkout page.
Default Order Status	Order status set after a successful payment. Use Default for WooCommerce’s automatic logic (virtual = Completed, physical = Processing).
Gateway Icon	Show or hide the accept.blue logo next to the payment method title on the checkout page.
Checkout Block	Enable support for WooCommerce Block-based Checkout. See the Checkout Setup Guide for mode-specific requirements.

💳Card & Payment

Force Capture	Capture the payment immediately at checkout. When disabled, only an authorization is placed — you capture (or adjust and capture) later.
Capture on Status	When Force Capture is off, the gateway auto-captures when the order reaches this status (e.g. Processing, Completed).
Save Card	Allow customers to save their card for future purchases. Requires the customer to be logged in.
Force Save Card	Always tokenize and save the card, without a customer opt-in checkbox.
Card Auth Methods	Restrict accepted card authentication methods if required by your processor.

🏷Surcharge

Apply a processing surcharge to card payments. Your surcharge settings must exactly match the configuration in your accept.blue merchant account.

Enable Surcharge	Apply a surcharge fee line item to card payments at checkout.
Show Surcharge in Checkout	Display the calculated surcharge amount on the checkout page before the customer places the order.
Manual Surcharge	Enter a fixed value instead of pulling the surcharge from the accept.blue API.
Surcharge Type	`percent` or `flat` — must match your accept.blue merchant surcharge setting.
Surcharge Value	The percentage (e.g. `3.5`) or flat amount (e.g. `1.50`).
Surcharge Label	The label shown to customers on the checkout page and order receipt (e.g. “Card Processing Fee”).

The Surcharge Type and Valuemust exactly matchyour accept.blue merchant account settings. Mismatched values will cause transaction errors or incorrect amounts.

📊Level III Data

Level III line item data qualifies B2B and corporate card transactions for lower interchange rates. When enabled, the plugin sends itemized order data with every transaction.

Enable Level III	Send itemized line item data with each transaction for potential interchange savings.
Truncate Fields	Automatically trim item names, SKUs, and descriptions to processor character limits.
Unit of Measure	Default unit of measure for line items (e.g. `EA`, `EACH`).
Commodity Code	Default 8-character commodity code applied to all line items.

Level III data is automatically skipped for $0 free-trial subscription orders where there are no real items to report, preventing API validation errors.

🔒3D Secure (3DS)

3D Secure adds an additional authentication step (e.g. OTP or biometric) via the Paay 3DS provider, shifting fraud liability to the card issuer.

Enable 3DS	Enable Paay 3D Secure authentication for credit card payments.
Frictionless 3DS	Attempt frictionless authentication (no customer challenge) when supported by the issuing bank.

Tokenization Source Key required.3DS uses the Hosted Tokenization SDK, so your Tokenization Key (Live or Test) must be configured in the API Keys tab.

🌐Google Pay

Display a Google Pay button on product pages, the cart, and the checkout page. Customers can pay using cards saved in their Google account.

Enable Google Pay	Show the Google Pay button on product pages, cart, and checkout.
Merchant ID	Your Google Pay Merchant ID — required for live/Production mode. Not required for Test mode.
Environment	`TEST` or `PRODUCTION`. Must be set to PRODUCTION on live stores.
Button Style	Choose the button colour and style (black, white, outline).
Button Locale	Override the button language. Leave blank to auto-detect.
Billing Address Required	Require the customer to provide a billing address when paying via Google Pay.

Google Pay requires your store to run over HTTPS. In Test mode, any Google account can be used without a real Merchant ID.

🎨Appearance

Control the visual style of the card input form on the checkout page.

Color Scheme	Auto follows the system preference. Light forces light mode. Dark forces dark mode. Custom uses your chosen colours.
Custom Background	Background colour for the card input area. Visible only when Color Scheme = Custom.
Custom Text Color	Text and label colour for card input fields. Visible only when Color Scheme = Custom.
Custom Border Color	Border colour for card input fields. Visible only when Color Scheme = Custom.

Accept.Blue Documentation

accept.blue Payment Gateway Docs