Partner introductions
Crypto payment gateway API — partner questions
We help merchants request introductions for crypto payments via MiCA-authorised partners.
What a partner API typically covers
Partners expose endpoints to create charges, retrieve statuses, and reconcile payouts to your bank or treasury according to your agreement.
OrsunPay orchestration, when used, sits above partner APIs you are authorised to call — it does not replace the partner’s compliance boundary.
Questions for your partner shortlist
Use these topics in waitlist notes so we route you to a technically suitable partner.
- Sandbox base URL, authentication, and idempotency keys
- Webhook signatures, retry policy, and status codes
- Supported chains, confirmation thresholds, and underpayment handling
- Payout currency options and treasury cut-off times in your contract
White-label and platform models
If you onboard sub-merchants, partners may require you to hold your own authorisation or use a specific platform programme. Clarify liability before building a marketplace UI.
OrsunPay does not offer a white-label CASP. Software discussions are separate from partner licensing.
FAQ
- Does OrsunPay publish a public crypto processing API?
- No. Public payment APIs come from the licensed partner you contract with. We may connect orchestration software to those APIs after partner onboarding.
- Can I self-host nodes instead of a partner?
- Operating conversion or custody for third parties typically requires authorisation. Most merchants use a partner API rather than building regulated infrastructure.
- Where do API keys live?
- Partners issue keys to your merchant account. Store them in your secret manager; OrsunPay does not distribute partner production keys from a waitlist signup.