Payment creation and queries
Create individual payments, filter the order list by merchant order number and query payment details using the system order ID.
FINTECH PAYMENT INTEGRATION · BUSINESS SYSTEMS
Cross-border payment APIs, for business system integration.
Integrate customer registration, collection account applications, individual payment creation, receipt queries and currency account balance queries into business systems. Support document submission, asynchronous payment notifications and result reconciliation.
ILLUSTRATION · NOT LIVE DATA
API requests and result queries
Illustrative request and query flow
Your system
OK Wire API
Result query
https://api.example.com
POST
/v1/tf/order/createCreate payment
POST
/v1/tf/orderQuery order
Example address; actual access details are supplied during onboarding.
SERVICE OVERVIEW
Available business APIs
Customers and collection accounts
Integrate customer registration, collection account applications and status queries, supplying business and associated individual information as required.
Collection and account balance queries
Query collection records, net collection summaries and currency account balances separately, reconciling each according to its reporting and funding purpose.
THE WORKFLOW
API integration and validation workflow
Find endpoint paths, request fields and signing examples in the on-site developer centre.
- 01
Agree on scope
Confirm products, currencies, accounts, payment use cases and activation requirements.
- 02
Configure server-side access
Obtain access details, implement the required signatures and keep secrets out of the frontend.
- 03
Submit business requests and query results
Call endpoints in business workflow order and retain merchant references, system order IDs and business responses for subsequent queries and reconciliation.
- 04
Validate notifications and exception handling
Test signature failures, timeouts, duplicate requests and pending states, and confirm how payment notifications and order queries are handled.
ONBOARDING REQUIREMENTS
API scope and integration requirements
Confirm endpoint capabilities, authentication and result handling requirements for product, engineering and finance teams.
Discuss your requirements- 01
API scope
Public endpoints currently provide payments, collections and related queries. Bulk import and account conversion operate through the business console and do not imply corresponding public execution APIs.
- 02
Authentication
Handle signed JSON, public reference queries or file uploads according to endpoint type, keeping integration credentials on the server.
- 03
Results and notifications
Verify business status through queries. Confirm notification fields, verification and retries during integration.
FAQ
Frequently asked questions
Review service availability, activation conditions and operating requirements.
Where is the developer documentation?
The developer centre provides the public API catalogue, request fields and signing examples. Confirm environments, permissions and notification conventions during onboarding.
Can I call the example domain?
No. Documentation uses reserved example domains such as api.example.com. Actual addresses and credentials are provided during onboarding.
Does an HTTP success mean a payment is complete?
No. Inspect the business response and query the order’s final state rather than using HTTP status alone to mark payment completion.
Find the right cross-border payment services
Provide your business regions, currencies and payment requirements to confirm suitable services and integration options.