Business and transaction evidence
Customer registration and account applications collect business and relevant individual details. Transaction reviews may require additional evidence.
SECURITY & COMPLIANCE · AT EACH STAGE
Make security part of the everyday workflow.
From business details and transaction evidence to request verification and reconciliation, understand the platform’s controls and the practices your team needs to maintain.
ILLUSTRATION · NOT LIVE DATA
Four stages of checks
Operational illustration · not certification
- 01Prepare evidence
- 02Verify requests
- 03Operate within permissions
- 04Reconcile and follow up
IN PRACTICE
Put safeguards in their business context.
Request and secret protection
Use signatures or the applicable encrypted mode as required by each endpoint. Keep secrets on controlled servers.
Access and record checks
Assign access according to the actual configuration and follow results through orders, receipts and balance records.
THE WORKFLOW
Put controls to work at every stage.
This illustrates operational stages, not licences, certifications or approval of a particular transaction.
- 01
Prepare evidence
Submit accurate business and relevant individual details, with transaction evidence as requested.
- 02
Verify requests
Apply the required signatures, handle credentials securely and use the correct access configuration.
- 03
Operate within permissions
Follow the console’s actual roles and approval settings, avoiding shared privileged accounts.
- 04
Reconcile and follow up
Compare order and fund records and investigate unclear states or discrepancies promptly.
BEFORE YOU START
Controls work with good team practices.
Build these practices into daily operations and integration maintenance.
Discuss your needs- 01
Protect credentials
Keep secrets out of browsers, public repositories and logs. Contact your integration team promptly if exposure is suspected.
- 02
Maintain access settings
Assign access by responsibility and review personnel changes. Approval coverage depends on the enabled configuration.
- 03
Investigate exceptions
Keep order references and relevant operational details. Avoid sending secrets or unnecessary sensitive data when reporting issues.
FAQ
Questions, answered
Practical details about availability, activation and daily use.
Does every API enforce an IP allowlist?
Do not assume this. Signed JSON, encrypted requests and uploads follow different paths. Allowlist checks depend on the applicable access mode and configuration.
Are regulatory licences or third-party certifications listed?
Specific licensing and regulatory information requires legal confirmation. The workflow illustrations on this page are not evidence of regulatory status or certification.
How do I verify a transaction’s final outcome?
Check order and relevant fund query results. Submission success or a notification alone does not establish final completion. Confirm notification rules during integration.
Make your business needs the next step.
Tell us your regions, currencies and payment flows to find the appropriate services and integration approach.