Implementation-focused articles on building software that scales cleanly.
More In Documentation
Related Posts
- Transaction Lifecycle in WooCommerce + Authorize.Net (Auth, Capture, Settlement, Void, Refund)
- Why SSL Is Required for Authorize.Net Payments in WooCommerce
- Unlocking e00027 Authorize.net: Troubleshooting Tips & Solutions
- Production-Ready WooCommerce Store Launch Audit
- How to Install and Set Up WooCommerce on WordPress
- Authorize.net API credentials explained: API Login ID vs Transaction Key vs Signature Key vs Public Client Key
Sandbox Setup and Testing Guide for Authorize.Net WooCommerce Plugin
This guide explains how to test credit card payments using an Authorize.Net sandbox account in a WooCommerce store using the Indatos Datamatix Authorize.Net gateway plugin. Sandbox testing helps you validate checkout, payment approval/decline behavior, and order updates without processing real money.
Product reference: Authorize.Net WooCommerce Plugin
What you will accomplish
- Create an Authorize.Net sandbox account
- Generate sandbox API credentials (API Login ID and Transaction Key)
- Configure the plugin for sandbox mode in WooCommerce
- Run end-to-end checkout tests with sandbox test cards
- Verify transactions in WooCommerce and in the Authorize.Net sandbox dashboard
Prerequisites
- WordPress admin access to your store
- WooCommerce installed and active
- Indatos Authorize.Net plugin installed and active
- Your plugin license key (if your build requires license activation)
- A staging site is recommended for testing. Testing on live sites is possible, but you must keep sandbox mode enabled and use sandbox credentials.
Key concepts you should understand
- Sandbox and production are separate environments. Sandbox credentials do not work in production, and production credentials do not work in sandbox.
- The plugin has a mode toggle (sandbox/test vs production/live). The mode must match the type of keys you paste into the settings.
- If the mode and keys do not match, you will typically see authentication errors such as “incorrect authentication values” or “authentication failed.”
Step 1: Create an Authorize.Net sandbox account
Authorize.Net sandbox accounts are created through the Authorize.Net Developer portal. Use the sandbox signup link below and follow the registration flow.
- Open the sandbox signup page: Authorize.Net Sandbox signup
- Create your developer account (email, password, and basic profile details)
- After signup, you will have access to the sandbox environment at: sandbox.authorize.net
Tip: Keep the sandbox login credentials saved securely. You will need them whenever you generate or rotate keys, review test transactions, or change sandbox configuration.
Step 2: Generate sandbox API credentials (API Login ID and Transaction Key)
The plugin typically requires two credentials from your Authorize.Net sandbox merchant interface:
- API Login ID
- Transaction Key
To generate these credentials in the sandbox merchant interface:
- Sign in to the sandbox merchant interface: sandbox.authorize.net
- Go to Account
- Under Security Settings, open API Credentials and Keys
- Copy the API Login ID
- Generate a new Transaction Key and copy it immediately
Important handling notes:
- The Transaction Key is sensitive. Store it in a secure password vault or secrets manager.
- If you rotate keys later, you must update the plugin settings with the new Transaction Key.
- Do not paste keys into public tickets, screenshots, or shared documents.
Step 3: Configure the Indatos plugin for sandbox testing
After you have sandbox credentials, configure the gateway in WooCommerce.
Open the plugin settings using either path below:
- WooCommerce → Settings → Payments → Authorize.Net → Manage
- Plugins → Installed Plugins → locate the Authorize.Net plugin → Settings
In the gateway settings:
- Paste your plugin license key (if the plugin shows a license field)
- Set the mode to Sandbox or Test mode (wording varies by build)
- Enter the sandbox API Login ID
- Enter the sandbox Transaction Key
- Save changes
Quick validation checklist after saving:
- The gateway shows as enabled in WooCommerce payments
- The checkout page displays the Authorize.Net payment option
- No authentication error appears in the plugin status/log area (if available)
Step 4: Run checkout testing (end-to-end)
Prepare your store for a clean test
- Create a simple product with a small price (for example 1.00)
- Ensure shipping and taxes are not blocking checkout (you can test with a virtual product to avoid shipping)
- If your checkout uses blocks, keep it enabled. The Indatos plugin supports block checkout and classic checkout.
Use sandbox test card numbers
Authorize.Net publishes test cards that work only in the sandbox. Use any future expiration date. Use any 3-digit CVV for most cards.
- Visa: 4111111111111111
- Visa: 4012888818888
- Mastercard: 5424000000000015
- American Express: 370000000000002 (use a 4-digit CVV)
Source: Authorize.Net Testing Guide
Place a test order
- Add the test product to cart
- Proceed to checkout
- Select the Authorize.Net payment method
- Enter a sandbox test card number, expiration date, and CVV
- Place the order
Verify results in WooCommerce
- Go to WooCommerce → Orders
- Open the test order
- Confirm the order status is updated appropriately (processing/completed/on-hold depends on your store settings)
- Look for transaction information (authorization code, transaction ID, notes) if the plugin displays it on the order screen
Verify results in the Authorize.Net sandbox dashboard
- Sign in to the sandbox merchant interface: sandbox.authorize.net
- Locate your transactions list or reporting area
- Confirm the test transaction appears with the expected amount and status
Optional tests: refund and void
Your plugin build supports refunds and voids from WooCommerce:
- Open the order in WooCommerce
- Initiate a refund or void (depending on settlement state)
- Confirm the action reflects in WooCommerce order notes and in the sandbox transaction history
Step 5: Troubleshooting common sandbox issues
Authentication failed or incorrect authentication values
- Confirm the plugin is in Sandbox/Test mode
- Confirm you used sandbox API Login ID and sandbox Transaction Key, not production keys
- Re-copy and paste credentials to remove hidden spaces
- If you recently generated a new Transaction Key, update the plugin with the newest key
Authorize.Net method does not show at checkout
- Ensure the gateway is enabled in WooCommerce → Settings → Payments
- Confirm you saved settings after entering keys
- Check that your currency and store country settings are supported by your payment configuration
- If using a caching plugin, clear cache and test again
Checkout errors only on blocks or only on classic checkout
- Confirm your WooCommerce checkout mode (block checkout vs classic)
- Update WooCommerce and the gateway plugin to the latest compatible versions
- Temporarily switch to a default theme to rule out theme conflicts
Step 6: Sandbox testing checklist
Before testing
- Sandbox account created
- Sandbox API Login ID and Transaction Key generated
- Plugin set to Sandbox/Test mode
- Sandbox keys pasted and saved in plugin settings
- Gateway enabled and visible at checkout
During testing
- At least one successful payment attempt with sandbox test card
- Order created correctly in WooCommerce
- Transaction appears in Authorize.Net sandbox dashboard
After testing
- Optional refund or void tested (if your workflow requires it)
- Store logs reviewed for warnings/errors
- Notes recorded for go-live configuration
Step 7: Next steps (moving from sandbox to live)
When you are ready to accept real payments:
- Switch the plugin mode to Production/Live
- Replace sandbox keys with production API Login ID and production Transaction Key
- Run a small real transaction to confirm live processing
- Continue monitoring payments and keep the plugin updated
FAQ
Do sandbox transactions charge real money?
No. Sandbox transactions never reach financial institutions. They are test-only and do not move real funds.
Can I use my production API Login ID and Transaction Key in sandbox?
No. Sandbox and production are separate environments and require separate credentials. Mixing them causes authentication failures.
Where do I find the API Login ID and Transaction Key in sandbox?
Sign in to the sandbox merchant interface at sandbox.authorize.net, then go to Account, open Security Settings, and choose API Credentials and Keys.
What does “incorrect authentication values” mean?
It usually means the plugin mode does not match the credentials you entered, or the API Login ID and Transaction Key were copied incorrectly. Confirm sandbox mode is enabled and re-paste your sandbox keys.
What test card should I use?
Use Authorize.Net’s published sandbox test cards, such as 4111111111111111 for Visa. Full lists and rules are available in the Authorize.Net testing guide: developer.authorize.net testing guide.
Can I test on my live website?
Yes, but it is safer to test on a staging site. If you must test on a live site, ensure the plugin remains in Sandbox/Test mode and that sandbox keys are in place, so real payments are not processed.
Does the Indatos plugin support checkout blocks?
Yes. The Indatos Authorize.Net WooCommerce plugin supports both block checkout and classic checkout. Refer to the product page for current compatibility details: Authorize.Net WooCommerce plugin.