Frequently asked questions

It depends on how complete your business information is, your industry profile and review complexity. Your adviser will provide an estimated timeline during onboarding based on what you supply; the final outcome still depends on review results.

This generally includes registration records, a business description, and identity and address proof for responsible persons. The list may vary by entity type and products being activated — follow the checklist your adviser provides.

Activation can be staged based on assessment. Currency and product combinations must comply with review outcomes and contractual terms, and may affect pricing and operational workflows.

We typically explain required documents or outcomes through your agreed contact channels. Please monitor your registered email and phone, and submit supplementary materials within the stated timeframe to avoid delays to activation.

Foreign trade collections focus on B2B goods payments, documentation and inbound narrative alignment. Global collections cover a broader range of e-commerce, platform and multi-store aggregation scenarios. Actual module names and scope follow your agreement and product documentation.

They can be combined based on your needs. Acquiring focuses on checkout authorisation and risk controls; collections cover inbound funds and accounting views. Whether both are activated and how reconciliation connects are determined through assessment and your agreement.

Common examples include supply chain payments, contractor/payroll disbursements, batch FX conversion and internal approval workflows. Available routes, currencies and limits depend on your plan and agreement.

Depending on product design, aggregation and permission separation can be organised by store, tag or entity. Detailed capabilities and report formats depend on your activated version and internal control settings.

Pricing is typically assessed based on product mix, transaction volume, currencies, operating regions and risk profile. Formal quotes are provided in writing through assessment and your agreement.

This varies by plan version. Refer to your quote and contract terms, or ask your adviser to walk through each item during a business inquiry.

Export and ERP/accounting integration can often be evaluated for most scenarios. Fields and frequency depend on product capabilities and project scope.

Disclosures about service architecture and partner entities are available in the website compliance section and your agreement. Different product lines may involve different partners.

Access and retention are managed under internal security and permission policies. Further details can be requested before signing, or adjusted where required by local law.

To comply with anti-money laundering and related regulations, we must verify customer identity and business legitimacy. Insufficient information may result in requests for additional documents or inability to activate certain features.

Depending on the product line, technical documentation, SDKs or plugins may be available. Integration scope and testing approach are explained during project assessment.

Sandbox validation can often be arranged for acquiring and integration projects. Availability and duration depend on your agreement and technical support scope.

This varies with review, integration complexity and testing schedules. Your adviser and technical contact will suggest milestones for your project.

Use the business inquiry form or contact us. Existing customers should reach their account manager or support through agreed channels.

Depending on product type, platform rules, card scheme time limits or bank processes may apply. We can assist with necessary information exchange; final decisions rest with the relevant authority or partner rules.

Follow termination, settlement and data handling terms in your agreement. We recommend confirming notice periods and treatment of outstanding transactions with your adviser or legal team in advance.

Cross-border e-commerce collections mainly handle platform or buyer funds inbound, currency handling and reconciliation. Cross-border e-commerce payments focus more on checkout authorisation, payment methods, refunds and transaction risk controls. Whether both can be combined depends on product, region and partner assessment.

Third-party payment platforms typically focus on checkout, authorisation and payment method integration. Third-party collection platforms lean toward inbound overseas funds, platform settlement aggregation, currencies and reconciliation. Actual services and responsibility boundaries should follow the provider's product documentation, review outcomes and agreement.

Start by sharing platform account entity, collection region, settlement currency, business model and estimated volume, then assess whether Amazon collections, eBay collections or other platform inbound routes are suitable. Platform names alone do not imply committed support — final availability depends on review and written agreement.

Compare foreign trade collection methods by buyer location, transaction currency, documentation and invoice requirements, settlement timing, reconciliation approach, and bank or partner rules. FX settlement must also be confirmed against local regulations, bank requirements and your actual agreement — rates alone should not drive the decision.