Transactions (Gateway Proxy)

The Transaction API enables you to securely process both card-not-present and card-present transactions. This comprehensive API supports tokenization for secure card storage, various transaction types, and robust search capabilities.

All transactions are stored in batches. You can:

• Configure batches for automatic closure using the Gateway Settings API

• Manage batch closure manually using the Batches API

• Search for batches the Batches Warehouse API

For token operations, use the Vault API endpoint.

Other useful links:

• Card numbers for testing

• Code samples in various languages

Available Endpoints:

• Search transactions: GET /rest/v2/transactions

• Authorize: POST /rest/v2/transactions/auth

• Sale: POST /rest/v2/transactions/sale

• Capture: POST /rest/v2/transactions/capture

• Forced sale: POST /rest/v2/transactions/forced-sale

• Refund: POST /rest/v2/transactions/refund

• Void: POST /rest/v2/transactions/void

• Adjust tip: PUT /rest/v2/transactions/{id}

Path Parameters

Name	Data Type	Required?	Description
Id	String	Required	ID of the transaction to adjust tip for

Rate Limiting Notice for Integrators

The API enforces rate limits to ensure fair usage and system stability. If a single integrator exceeds the allowed request threshold, they may receive an HTTP 429 (Too Many Requests) response.

If you encounter a 429 error:

• Wait for the period specified in the Retry-After header, if provided.

• Implement exponential backoff before retrying the request.

For sustained high-volume needs or to obtain detailed limit information, contact your integration specialist.