Skip to main content
Legacy Integration Method - This is an older integration approach. For new implementations, we recommend using Collect.js for tokenization or Collect Checkout for a hosted solution instead.

Overview

The Three Step Redirect API is a redirect-based integration where customers are sent to a secure gateway-hosted payment form. While this approach reduces PCI compliance burden (since card data never touches your servers), modern alternatives like Collect.js offer better user experience and more flexibility.
When to Use This: Only use Three Step Redirect if you’re maintaining an existing integration. New projects should start with Collect.js or Collect Checkout.

How It Works

The integration follows three sequential steps:
1

Step 1: Initiate Request

Your server sends transaction details to the gateway and receives a secure token
2

Step 2: Redirect Customer

Redirect the customer to the gateway’s secure payment form using the token to enter payment information
3

Step 3: Process & Return

The gateway processes the transaction and redirects back to your site with the results

Supported Operations

Transaction Types

Sale

Immediate settlement flagging for quick processing

Authorization

Reserve funds without settlement for later capture

Capture

Settle previously authorized transactions

Void

Cancel unsettled transactions

Refund

Reverse previously settled transactions

Credit

Apply direct account credits

Validate

Verify account without authorization

Recurring Billing Operations

The API supports recurring billing functionality:
  • Plan Creation - Define billing frequency and terms
  • Subscription Management - Track and manage customer subscriptions
  • Automatic Charging - Process payments at specified intervals

Customer Vault Operations

Securely store payment information for future transactions:
Transmit payment information through a Secure Sockets Layer connection for storage in a Level 1 PCI certified data facility.
Benefits of Customer Vault:
  • Store payment data without maintaining local databases
  • Initiate transactions using stored credentials
  • Reduce PCI compliance scope
  • Improve checkout experience for returning customers

Testing

Use these credentials for testing your integration:
CredentialValue
Usernamedemo
Passwordpassword
These test credentials should only be used in sandbox environments. Never use them in production.

Key Features

  • Multiple Payment Methods - Accept credit cards, ACH, and digital wallets
  • Merchant-Defined Fields - Add custom fields to track additional data
  • Webhook Notifications - Receive real-time event updates
  • Secure Tokenization - Payment data is tokenized for security
  • Mobile Responsive - Payment forms work on all devices

Next Steps