Overview

WorldFirst Enhanced Solution is a comprehensive payment and financial infrastructure platform that enables businesses to manage multi-currency accounts, process cross-border payouts, execute foreign exchange trades, and handle financial operations — all through a single, unified and enhanced API.
Integrate once to unlock global collections, payouts, and multi-currency treasury — powered by a modular API stack and intelligent strategies that help you move capital efficiently, improve yield, and scale operations across borders.

How It Works

Request Format

Most API requests use the POST method with a JSON body over HTTPS; the OAuth authorization endpoint uses GET. The base URL follows the pattern:
https://{domain}/api/open/v1/{resource}/{action}

Base URL and environments

Replace
{domain}
with the site-specific API host assigned to your account in Developer Center.
The assigned host can vary by contracted WorldFirst site. Keep sandbox credentials and hosts separate from production credentials and hosts.

Authentication

WorldFirst supports two authentication methods:
  • API Key (Suggested): send your API Key in the
    Authorization: Bearer
    header. No request signing or response verification is required. Use this method for new integrations.
  • RSA signature: existing integrations can continue to sign each request with a SHA256withRSA private key and verify WorldFirst's response signature.
The code examples in this reference use API Key authentication. See Authentication for both methods.

Idempotency

API endpoints with a
requestId
field in the request body use it as an idempotency key to prevent duplicate operations. Reusing a
requestId
returns
resultStatus: F
and
resultCode: REPEAT_REQUEST
; the original response is not replayed. If a previous request has an indeterminate outcome, query the resource before submitting a new request.

Webhooks

Asynchronous operations — such as payout processing, beneficiary approval, and FX settlement — deliver status updates via webhook notifications to your configured callback URL on Developer Center. Each webhook notification is signed. For API Key integrations, verify it with your Webhook Secret as described in Verify webhook signatures.