Testing Guide

Overview

This guide provides comprehensive testing information for the Ionic Payment Gateway, including test card numbers, amounts, credentials, and scenarios to verify your integration.

Never use real payment information in test mode. Always use the test credentials and card numbers provided below.

Test Mode

Enabling Test Mode

You can enable test mode in two ways: Option 1: Via Merchant Dashboard Enable test mode in your merchant control panel: Options > Settings > Transaction Options > Test Mode. This affects all transactions for your account. Option 2: Per-Transaction Parameter Add the test_mode parameter to individual API requests:

test_mode=1

When test mode is enabled:

Transactions are processed but not settled
No actual funds are transferred
Test card numbers should be used
Results appear in your test transaction reports

Always enable test mode during development and testing. Disable it or set test_mode=0 for live transactions.

Test Credentials

API Security Keys

All API requests require authentication using your security key:

Credential	Value
security_key	Your API security key
API Endpoint	`https://api.ionicfi.com/api/transact.php`

Generate API security keys from the merchant control panel under Settings > Security Keys. You can create separate keys for testing and production environments.

Three Step Redirect Testing

For Three Step Redirect integration testing:

Credential	Value
Username	`demo`
Password	`password`

Test Card Numbers

Basic Test Cards

Use these card numbers for standard testing scenarios:

Card Number	CVV	Expiration	Result
`4111111111111111`	`999`	Any future date	Approved - Standard approval
`4000000000000002`	Any	Any future date	Declined - Generic decline
`4000000000000010`	`999`	Any future date	Approved - With full AVS match
`4000000000000028`	Any	Any future date	Declined - Insufficient funds
`4000000000000036`	Any	Any future date	Declined - Do not honor
`4000000000000044`	Any	Any future date	Declined - Card expired
`4000000000000051`	Any	Any future date	Declined - Invalid card number

Use 4111111111111111 as your primary test card for successful transactions.

Card Number	CVV	Expiration	Result
`5424000000000015`	`999`	Any future date	Approved - Standard approval
`5555555555554444`	`999`	Any future date	Approved - Alternative test card
`5424000000000023`	Any	Any future date	Declined - Insufficient funds
`5424000000000031`	Any	Any future date	Declined - Do not honor

Card Number	CVV	Expiration	Result
`378282246310005`	`9999`	Any future date	Approved - Standard approval
`371449635398431`	`9999`	Any future date	Approved - Alternative test card
`378734493671000`	Any	Any future date	Declined - Generic decline

American Express uses 4-digit CVV codes (printed on the front of the card).

Card Number	CVV	Expiration	Result
`6011000000000012`	`999`	Any future date	Approved - Standard approval
`6011111111111117`	`999`	Any future date	Approved - Alternative test card
`6011000000000020`	Any	Any future date	Declined - Generic decline

Card Number	CVV	Expiration	Result
`3530111333300000`	`999`	Any future date	Approved - Standard approval
`3566002020360505`	`999`	Any future date	Approved - Alternative test card

Card Number	CVV	Expiration	Result
`30569309025904`	`999`	Any future date	Approved - Standard approval
`38520000023237`	`999`	Any future date	Approved - Alternative test card

AVS/CVV Testing Cards

Test Address Verification System and Card Verification Value responses:

Card Number	AVS Response	CVV Response	Description
`4111111111111111`	`X`	`M`	Full match (address + ZIP + CVV)
`4000000000000002`	`N`	`N`	No match (address, ZIP, or CVV)
`4242424242424242`	`Y`	`M`	Address + 5-digit ZIP match, CVV match
`4000000000000101`	`A`	`M`	Address match only, CVV match
`4000000000000200`	`Z`	`M`	ZIP match only, CVV match
`4000000000000085`	`N`	`M`	No address match, CVV match
`4000000000000093`	`Y`	`N`	Address + ZIP match, CVV fail

Use these cards to test your fraud prevention rules and AVS/CVV validation logic.

Partial Approval Testing

Test partial approval scenarios:

Card Number	Requested Amount	Approved Amount	Description
`4000000000000259`	`$100.00`	`$50.00`	Partial approval - 50%
`4000000000000267`	`$100.00`	`$75.00`	Partial approval - 75%

Example:

ccnumber=4000000000000259
amount=100.00
# Response: amount_authorized=50.00, partial_payment_balance=50.00

Test Amounts

Use specific amounts to trigger different response scenarios:

Amount-Based Testing

Amount Pattern	Response	Description
`x.00`	Approved	Any amount ending in .00
`x.01`	Declined	Any amount ending in .01
`x.02`	Error	Any amount ending in .02 (processing error)
`x.05`	Approved	AVS mismatch (AVS=N)
`x.10`	Partial Approval	Approved for $50.00
`x.27`	Declined	Insufficient funds
`x.51`	Declined	Do not honor

Specific Test Amounts

amount=25.00
# Response: response=1, responsetext=SUCCESS

ACH/eCheck Testing

Test Bank Accounts

Use these routing and account numbers for ACH testing:

Approved
Declined

Routing Number: 123456789Account Numbers:

Account Number	Result
`9876543210`	Approved
`1111111111`	Approved
`2222222222`	Approved

checkname=John Doe
checkaba=123456789
checkaccount=9876543210
account_type=checking
sec_code=WEB
amount=50.00

Routing Number: 123456789Account Numbers:

Account Number	Return Code	Description
`0000000001`	R01	Insufficient Funds
`0000000002`	R02	Account Closed
`0000000003`	R03	No Account
`0000000004`	R04	Invalid Account Number

checkaba=123456789
checkaccount=0000000001  # Returns R01 - Insufficient Funds

SEC Codes for Testing

SEC Code	Description	Test Scenario
`WEB`	Internet-initiated	Online checkout
`PPD`	Prearranged Payment	Recurring billing
`TEL`	Telephone-initiated	Phone orders
`CCD`	Corporate Credit/Debit	B2B payments

3D Secure Testing

Test Cards for 3DS Authentication

Successful Authentication
Failed Authentication
Challenge Flow

Card Number	3DS Result	Description
`4000000000001000`	Authenticated	Full 3DS authentication successful
`4000000000001091`	Authenticated	Frictionless flow (no challenge)

Expected Response:

{
  "authenticated": true,
  "cardholder_auth": "Y",
  "eci": "05",
  "cavv": "AAABCZIhcQAAAABZlyFxAAAAAAA=",
  "xid": "ABC123XYZ..."
}

Card Number	3DS Result	Description
`4000000000001018`	Unavailable	Authentication unavailable
`4000000000001034`	Failed	Authentication failed
`4000000000001026`	Attempted	Authentication attempted but not completed

Expected Response:

{
  "authenticated": false,
  "cardholder_auth": "N",
  "eci": "07"
}

Card Number	3DS Result	Description
`4000000000001042`	Challenge Required	Cardholder must complete challenge
`4000000000001059`	Challenge Successful	Challenge completed successfully

Challenge Simulation:

Use these cards to test the challenge flow
Gateway will redirect to 3DS challenge page
Complete challenge and return to merchant

Fraud Detection Testing

Kount Testing

Test fraud detection with specific email patterns:

Email Pattern	Fraud Score	Risk Level	Action
`[email protected]`	10	Low	Approve
`[email protected]`	50	Medium	Review
`[email protected]`	90	High	Decline
`[email protected]`	95	Critical	Escalate

Example:

email=[email protected]
# Kount returns score: 90 (High Risk)

Velocity Testing

Test velocity rules with rapid transactions:

# First transaction
amount=10.00
# Approved

# Second transaction (within 1 minute)
amount=10.00
# May trigger velocity check based on your rules

Digital Wallet Testing

Apple Pay Testing

Test Device Requirements:

Safari browser on macOS or iOS device
Test Apple Pay account configured in Wallet

Test Cards in Wallet:

Add test card 4111111111111111 to Apple Wallet
Use in test environment for Apple Pay transactions

Google Pay Testing

Test Device Requirements:

Chrome browser or Android device
Test Google Pay account

Test Cards:

Add test card 5424000000000015 to Google Pay
Use test merchant ID provided by gateway

Customer Vault Testing

Test Customer IDs

Pre-configured test customer vault IDs:

Customer Vault ID	Payment Method	Details
`TEST_CUSTOMER_1`	Visa	•••• 1111, Exp: 12/25
`TEST_CUSTOMER_2`	Mastercard	•••• 0015, Exp: 12/25
`TEST_CUSTOMER_3`	ACH	Account ••••3210

Example:

customer_vault_id=TEST_CUSTOMER_1
type=sale
amount=25.00
# Uses stored Visa ending in 1111

Recurring Billing Testing

Test Subscription Scenarios

Scenario	Configuration	Expected Result
Successful Recurring	`plan_payments=3`, day_frequency=1	Charges on Day 1, 2, 3
Failed Payment	Use card ending in .01 amount	First charge fails
Expired Card	Set ccexp to past date	Card declined after expiration

Example Test Subscription:

recurring=add_subscription
plan_amount=29.99
plan_payments=3
day_frequency=1
start_date=20251031
# Creates subscription charging $29.99 for 3 days

Webhook Testing

Trigger Test Webhooks

Manual Testing:

Go to Merchant Control Panel > Webhooks > Test Events
Select event type to test
Click “Send Test Webhook”

Automated Testing: Process test transactions to trigger real webhooks:

# This will trigger transaction.sale.success webhook
type=sale
amount=25.00
ccnumber=4111111111111111
ccexp=1225

Test Webhook Payloads

Example Test Webhook:

{
  "event": "transaction.sale.success",
  "webhook_id": "TEST_WH_123",
  "timestamp": "2025-10-30T10:30:00Z",
  "data": {
    "transaction_id": "TEST_123456789",
    "amount": "25.00",
    "status": "approved"
  },
  "signature": "test_signature_hash"
}

Testing Checklist

Before going live, verify these scenarios:

Basic Transactions

Payment Methods

Fraud Prevention

Advanced Features

Integration Points

User Experience

Testing Best Practices

Test All Scenarios

Test both success and failure paths to ensure proper error handling

Use Test Mode

Always use test credentials and never real payment information

Verify Webhooks

Ensure webhooks are received and processed correctly

Check Logs

Review transaction logs for any errors or warnings

Test Edge Cases

Try invalid data, timeouts, and network errors

Security Testing

Verify SSL/TLS, signature validation, and data encryption

Common Testing Errors

Invalid Security Key

Error: INVALID SECURITY KEYCause: Using production key in test mode or vice versaSolution: Use the correct security key for your environment

Invalid Card Number

Error: INVALID CARD NUMBERCause: Card number fails Luhn validationSolution: Use only the test card numbers provided above

Duplicate Transaction

Error: DUPLICATE TRANSACTIONCause: Same card, amount, and details submitted within duplicate windowSolution: Change amount slightly or wait for duplicate window to expire

Webhook Not Received

Problem: Webhooks not arriving at your endpointCauses:

Firewall blocking gateway IPs
Invalid SSL certificate
Endpoint returning non-200 response

Solution: Check webhook logs in merchant portal

Testing Tools

cURL Examples

curl -X POST https://api.ionicfi.com/api/transact.php \
  -d "security_key=YOUR_API_KEY" \
  -d "test_mode=1" \
  -d "type=sale" \
  -d "ccnumber=4111111111111111" \
  -d "ccexp=1225" \
  -d "cvv=999" \
  -d "amount=25.00" \
  -d "first_name=John" \
  -d "last_name=Doe"

Postman Collection

Import this collection for comprehensive testing:

{
  "info": {
    "name": "Ionic Payment Gateway Tests",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    {
      "name": "Sale Transaction",
      "request": {
        "method": "POST",
        "url": "https://api.ionicfi.com/api/transact.php",
        "body": {
          "mode": "urlencoded",
          "urlencoded": [
            {"key": "security_key", "value": "{{api_key}}"},
            {"key": "type", "value": "sale"},
            {"key": "ccnumber", "value": "4111111111111111"},
            {"key": "ccexp", "value": "1225"},
            {"key": "cvv", "value": "999"},
            {"key": "amount", "value": "25.00"}
          ]
        }
      }
    }
  ]
}

Next Steps

Payment API

Start integrating the Payment API

Response Codes

Understand response codes

Webhooks

Set up webhook testing

Go Live Checklist

Prepare for production

Getting Started

Integration Methods

Partners

API Reference

​Overview

​Test Mode

​Enabling Test Mode

​Test Credentials

​API Security Keys

​Three Step Redirect Testing

​Test Card Numbers

​Basic Test Cards

​AVS/CVV Testing Cards

​Partial Approval Testing

​Test Amounts

​Amount-Based Testing

​Specific Test Amounts

​ACH/eCheck Testing

​Test Bank Accounts

​SEC Codes for Testing

​3D Secure Testing

​Test Cards for 3DS Authentication

​Fraud Detection Testing

​Kount Testing

​Velocity Testing

​Digital Wallet Testing

​Apple Pay Testing

​Google Pay Testing

​Customer Vault Testing

​Test Customer IDs

​Recurring Billing Testing

​Test Subscription Scenarios

​Webhook Testing

​Trigger Test Webhooks

​Test Webhook Payloads

​Testing Checklist

​Testing Best Practices

Test All Scenarios

Use Test Mode

Verify Webhooks

Check Logs

Test Edge Cases

Security Testing

​Common Testing Errors

​Testing Tools

​cURL Examples

​Postman Collection

​Next Steps

Payment API

Response Codes

Webhooks

Go Live Checklist

Overview

Test Mode

Enabling Test Mode

Test Credentials

API Security Keys

Three Step Redirect Testing

Test Card Numbers

Basic Test Cards

AVS/CVV Testing Cards

Partial Approval Testing

Test Amounts

Amount-Based Testing

Specific Test Amounts

ACH/eCheck Testing

Test Bank Accounts

SEC Codes for Testing

3D Secure Testing

Test Cards for 3DS Authentication

Fraud Detection Testing

Kount Testing

Velocity Testing

Digital Wallet Testing

Apple Pay Testing

Google Pay Testing

Customer Vault Testing

Test Customer IDs

Recurring Billing Testing

Test Subscription Scenarios

Webhook Testing

Trigger Test Webhooks

Test Webhook Payloads

Testing Checklist

Testing Best Practices

Common Testing Errors

Testing Tools

cURL Examples

Postman Collection

Next Steps