Payment creation and queries
Create individual payment orders and follow their processing through order queries and lists.
EMBEDDED FINTECH · CONNECT YOUR SYSTEM
Connect fund operations to your business system.
Use the current public APIs for payment creation, receipt records, account applications and balance queries, with product workflows grounded in verifiable business states.
ILLUSTRATION · NOT LIVE DATA
Connect instructions to fund operations
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.
IN PRACTICE
Build from the APIs available today.
Customers and collection accounts
Connect customer registration, collection account applications and queries, allowing for reviews and additional information.
Funds and receipt views
Query fund-pool balances and receipt records while distinguishing fund availability from collection statistics.
THE WORKFLOW
Four practical steps to integration.
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
Create and query
Call the relevant endpoints in business order, retaining merchant references and responses.
- 04
Validate exception paths
Test invalid parameters, timeouts and unresolved states. Confirm notification and retry behaviour during integration.
BEFORE YOU START
Establish the integration boundaries.
Give product, engineering and finance teams a shared starting point.
Discuss your needs- 01
API scope
Use the current developer catalogue. It does not include standalone FX execution or batch payment creation endpoints.
- 02
Authentication
Signed JSON, unsigned queries and file uploads have different requirements. Follow the documentation for each endpoint.
- 03
Results and notifications
Verify business status through queries. Confirm notification fields, verification and retries during integration.
FAQ
Questions, answered
Practical details about availability, activation and daily use.
Where is the developer documentation?
Documentation is available in this website’s developer centre, including the endpoint catalogue, fields and signed request examples.
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.
Make your business needs the next step.
Tell us your regions, currencies and payment flows to find the appropriate services and integration approach.