What happens next
A confirmed response loop
- Submit crypto intent or invoice / wire request.
- Orkid confirms the lane, references the order, and routes the follow-up.
- Delivery expectations or procurement next steps arrive within one business day.
← Back to commercial path
Tier 3 // Payment portal
Move this engagement into a confirmed commercial lane
Crypto stays native on-site. Invoice and wire requests route through a Mercury-backed server-side handoff, with buyer confirmation within one business day.
// SELECTED TIER
Tier 3
$25,000 – $100,000+
High-touch infrastructure engagement for teams that already know the need is strategic.
- Best for teams with a real deployment path, not exploratory category education.
- You get a direct commercial lane into scoped implementation planning.
- Invoice and wire buyers use Mercury; crypto buyers stay in the native chain-selection flow.
Buyer assurance
No unnecessary friction
- No wallet connect, browser extension, or forced account creation.
- Invoice and wire buyers start with billing context, not a blind email handoff.
- Fallback stays explicit if bank-transfer routing needs manual review.
Need more context?
Keep the route without stalling
If the team still needs context before committing, go back to the launch brief, packet, or comparison surfaces. This page is for buyers who already want a commercial next step.
Tier navigation
Switch the commercial lane without leaving the flow
Payment method
Choose the settlement path
Chain + token
Native settlement details
Network
Token
Send to this wallet
0xA73148bBA39c01Be4Eefd2788973f88e9D6940e6 Amount
Custom scope
Use notes to flag flow, jurisdiction, or settlement context.
Submit intent
Tell Orkid how to follow up
Submit before or after sending on-chain. If you already have the transaction hash, include it now. If not, Orkid will still confirm the next step inside one business day.
Invoice / wire path
Mercury-backed commercial handoff
Submit the billing context here. Orkid captures the request locally, then routes the bank-transfer follow-up through Mercury when available.
- Primary contact and organization are required for invoice and wire routing.
- Use billing currency and notes to speed up procurement-ready follow-up.
- Manual fallback remains available if the bank-transfer backend needs review.
Request billing route
Submit invoice / wire details
This is the fastest way to move into formal invoicing or wire instructions without losing the commercial context.
// HANDOFF CONFIRMED
Next steps
Request received
Order reference
Tier
Method
Buyer reference
Response window
Commercial FAQ
Remove the last conversion questions
FAQ
What does the Mercury route mean here?
Mercury-backed invoice and wire handling are the primary bank-transfer route for commercial buyers. You submit billing context here, then Orkid confirms the correct invoicing or wire instructions by email within one business day.
FAQ
Can I submit before I have the full transaction hash or procurement packet ready?
Yes. Crypto buyers can submit intent before or after sending on-chain and add the transaction hash later. Invoice and wire buyers can start with primary contact and organization details first, then continue the formal procurement exchange over email.
FAQ
What happens if the bank-transfer backend is unavailable?
Orkid still captures the request locally and moves the buyer into a manual fallback path. The promise stays the same: confirmation and the right next step within one business day.