SECURITY AND COMPLIANCE · BUSINESS RISK CONTROLS

Customer and transaction review, payment and access controls.

Manage payment operations through customer registration and review, transaction documentation, separate payment preparation and approval, and API request verification. Assign permissions by role and reconcile transaction and ledger records.

ILLUSTRATION · NOT LIVE DATA

Business operations and security controls

Illustrative customer review and transaction workflow

  1. 01Prepare evidence
  2. 02Verify requests
  3. 03Prepare and review by role
  4. 04Reconcile and follow up

SERVICE OVERVIEW

Business and transaction security controls

Customer information and transaction review

Provide business and associated individual information for the customer and account product, and submit transaction documents required for the payment purpose.

API authentication and replay checks

Signed endpoints validate merchant credentials, timestamps and request replay. Data encryption and IP restrictions follow the integration mode and configuration.

Payment review and ledger traceability

Prepare and review payments under separate roles, retaining order and ledger references for transaction queries and balance reconciliation.

THE WORKFLOW

Onboarding review, authentication and reconciliation

Controls apply according to customer type, payment product and integration configuration. Documentation requirements follow onboarding and transaction review requests.

  1. 01

    Prepare evidence

    Submit accurate business and relevant individual details, with transaction evidence as requested.

  2. 02

    Verify requests

    Apply the required signatures, handle credentials securely and use the correct access configuration.

  3. 03

    Prepare and review by role

    Prepare and review payments according to the business console configuration, with account verification governed by security settings.

  4. 04

    Reconcile and follow up

    Compare order and fund records and investigate unclear states or discrepancies promptly.

ONBOARDING REQUIREMENTS

Business security requirements

Include credential protection, access management and exception reconciliation in daily operations and integration maintenance.

Discuss your requirements
  1. 01

    Protect credentials

    Keep secrets out of browsers, public repositories and logs. Contact your integration team promptly if exposure is suspected.

  2. 02

    Maintain access settings

    Assign access by responsibility and review personnel changes. Approval coverage depends on the enabled configuration.

  3. 03

    Investigate exceptions

    Keep order references and relevant operational details. Avoid sending secrets or unnecessary sensitive data when reporting issues.

FAQ

Frequently asked questions

Review service availability, activation conditions and operating requirements.

Do all APIs apply the same IP access restrictions?

IP access restrictions depend on the endpoint type, integration mode and actual configuration. Requirements may differ for signed JSON, encrypted requests and file uploads.

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?

Reconcile payment orders, collection processing status and related currency account records. API request success, notification delivery and beneficiary receipt are separate events; confirm completion from the final query result for the applicable service.

Find the right cross-border payment services

Provide your business regions, currencies and payment requirements to confirm suitable services and integration options.

Discuss your requirements