Services

Three core services — different ticket sizes and payees

Ticket size, beneficiaries and review differ by service. Onboard in stages by business priority.

System delivery is under Project practice; screening and licensing paths are on separate pages.

Customers pay by card, bank / local transfer, fiat cash or crypto.

Multi-channel collection

Track everything via Payment Link, Invoice, QR, API or Dashboard.

Convert your own crypto to fiat or retain crypto.

Multi-currency settlement (large)

Organise source and purpose, then settle against a formal quote.

Pay external payees: wallets, multi-currency fiat or local rails.

Bill payout (small–mid)

Route by payee region; purpose and status can be checked.

Gaps in accounts, day-end and monitoring systems.

Project practice

Three anonymised delivery summaries — shipable in stages.

Customer data and screening results are scattered.

AML / CRM

Connect a reviewable path from onboarding to monitoring.

Payments, wealth, lending, embedded finance, on-chain and RegTech.

Fintech projects

Define delivery scope before front/back-end integration.

Licence path must match the real business.

Licensing & professional services

Clarify entity and cashflow before engagement.

CompareService lines

Assess settlement and bill payout separately

Core payment services and common frictions
Lens	Multi-channel collection	Multi-currency settlement	Bill payout
Typical friction	Scattered methods, hard reconciliation	Large FX, scattered paperwork	Payees in many places, mixed rails
Fund direction	Customer → merchant	Merchant’s own funds convert / retain	Merchant → external payee
Focus	Inbound tracking & reconciliation	Source, purpose and quoted settlement	Multi-region payout & purpose checks

Channels, limits and documents follow merchant review outcomes.

Who this is forCommon frictions

If you face these operating frictions

Describe the business and regions clearly — it is easier to judge fit and which segment to tackle first.

Channels scattered, manual reconciliation

Cards, local transfers, cash rails and crypto each run separately. Use Payment Link / Invoice / QR / API / Webhook to pull status into one place.

Settlement and payout mixed in one talk

Large conversion of your own funds differs from smaller affiliate / supplier payouts in limits, documents and channels.

Higher-risk sectors miss standard rails

Feasibility and document review come first; then discuss what can be enabled.

Finance wants reports, tech wants APIs

Both sides should share one source of truth; start on Dashboard for low volume, then API and Webhook.

FAQCommon questions

Understand first, then start.

On scope, settlement vs payout, and what to prepare before onboarding.

Can we discuss only one service?

Yes. Use cases, documents and channel conditions differ — assess the highest-priority segment first.

Why ask about business and fund use early?

Payees, locations, scale and purpose affect feasibility; clearer data yields accurate replies.

Does the website mean we can go live immediately?

No. Entities, scope and terms are confirmed only after merchant review and formal documents.

Merchant enquiry

Ready to enquire? Bring the basics in one go

Company, region, use case and expected scale — clearer notes get faster replies.IDs can follow the review checklist later; copies are not needed on first contact.

Start a merchant enquiry