OTC desks and exchange-side invoices
Exchange and OTC Desk Order Payments
Collect OTC fees, exchange-side invoices, order deposits, and service balances with payment records tied to each desk workflow.
Back to use casesView all
Practical guide
Collect exchange and OTC service payments with order references before desks allocate liquidity or support.
Exchange and OTC payments are reference-heavy. A fee, deposit, service invoice, or desk order must connect to the correct counterparty and workflow.
Crypto can fit this audience naturally, but raw transfers still create support and reconciliation risk.
MakePay can create branded requests for desk fees, onboarding charges, settlement-related invoices, or account payments while the desk keeps its own trading and compliance controls.
Payment examples
OTC service fee invoice
Desk retainer payment
Order deposit request
Exchange service balance
Why it works
Payment references can match desk tickets or client IDs
Crypto-native customers use a familiar rail with cleaner records
High-value invoices avoid unnecessary percentage fee drag
Settlement stays in the merchant-controlled wallet path
Problems solved
Desk operations need records beyond transaction hashes
Large invoices create fee sensitivity
Client IDs and order references must match exactly
Custodial processor balances can slow treasury movement
Guide
Why desk payments need exact counterparty context
A payment may relate to a client account, quote, service, or settlement workflow. If the reference is unclear, operations has to investigate.
The desk should not rely on screenshots when payment status can be represented as a structured record.
Counterparty mapping matters
Payments should include account or order metadata.
Compliance stays separate
Trading eligibility and checks remain with the exchange or desk.
High values expose fees
Fee clarity matters when amounts are large.
Guide
How MakePay fits exchange-adjacent payments
Use payment links for controlled invoices or API-created requests for product-native flows. Keep each request tied to the counterparty record.
MakePay provides payment status and checkout, while the desk keeps custody, trading, and settlement policy in its own systems.
Private links
Useful for manual desk invoices.
API payments
Useful when the platform creates requests from account workflows.
Desk-controlled settlement
Funds route according to the merchant wallet configuration.
Setup path
Start with one clear payment moment.
Step 1
Create the desk reference
Define counterparty, invoice, service, or order metadata.
Step 2
Send or create payment
Use private links or API-created checkout.
Step 3
Act after status
Move onboarding, service, or support workflow forward after payment.
Step 4
Reconcile with desk operations
Keep payment references available to finance and desk staff.
Questions
Plain answers before you launch.
Does MakePay execute trades?
No. It provides payment requests and status for merchant workflows.
Can this be used for OTC invoices?
Yes, when the desk needs a branded payment request tied to a counterparty record.
More use cases
Explore nearby merchant types
Excellent crypto-native fit
Mining hardware and hosting
Payment links, hosted checkout, and wallet-settled invoices for ASIC resellers, miner hosting operators, repair desks, and electricity-billed mining contracts.
Open
Excellent fit
High-value commerce
Real estate, luxury cars, wholesale B2B, and premium goods where low fees, fast settlement, and no card chargebacks matter.
Open
Strong fit
Travel, events, and bookings
Travel agencies, private charters, conferences, and event operators that need global payment links, deposits, and quick confirmation.
Open