Skip to main content
The cross-chain payments API is separate from the OMS Payments API. It has its own authentication, its own base URL, and its own SDK package. Do not use OMS Payments API credentials or base URLs with these endpoints.

Authentication

All requests require an X-Access-Key header with your API key.
Retrieve your API key from the Trails Dashboard.

Base URL

All endpoints are appended to this base URL. For example, the QuoteIntent endpoint is:

All endpoints are POST requests

This API uses POST for all endpoints, including read operations. Request bodies are JSON.

SDK installation

Initialize the client once and reuse it across your application:

Intent lifecycle

A payment is called an intent. Every intent moves through a defined set of states from quote to settlement.

Expiry and failure

  • A QUOTED intent expires after 5 minutes. After expiry, request a new quote.
  • A COMMITTED intent expires after 10 minutes if ExecuteIntent is not called. After expiry, the intent moves to FAILED.
  • FAILED is a terminal state. Create a new intent to retry.

Next steps

Quotes and execution

QuoteIntent, CommitIntent, ExecuteIntent, and AbortIntent.

Status and monitoring

Track an intent through to settlement.

Routes and discovery

Supported networks, tokens, routes, and prices.

Accept funds

Integration guide for the widget, SDK, and direct API.