Product · money in
Ask on the rail the payer already uses.
A payment request is worth only as much as how easily the payer can act on it. One link covers a bank transfer or a stablecoin, and the money books itself when it lands.
Pay links
A link that asks for an amount, in crypto or by bank details with a reference. A crypto payment is matched on-chain and booked as income without you touching it. Links expire, can be cancelled, and can be marked paid by hand.
Invoices with a public page
Client details, line items, a due date, a PDF and a public link. Statuses run draft, sent, partially paid, paid, void, and a paid invoice books the income. Your logo and seller details come from Settings.
Paid in halves, tracked in halves
Record any amount up to the balance and the invoice turns partially paid: the list says paid 6,000 of 12,000, and the public page and the reminders switch to speaking in what is still due. Overpayment is refused. Closing one early writes off the remainder and puts the write-off in the log.
It chases the client itself
A sent invoice with an email on it is reminded three days before the due date, on the day, then three and seven days after. Each goes once and carries the pay link. Clients get an unsubscribe link, and any one invoice can be taken off the schedule from its row.
The work that repeats
Turn a sent or paid invoice into a weekly or monthly schedule and each cycle is raised and sent from that snapshot. Run out of your monthly allowance and it pauses itself, tells the owners, then sends a single catch-up when you resume.
The payer gets something too
The public page offers to save the payment to their own ledger. They get a free account and the expense on their side, with you in their contacts. Clicking twice never duplicates it.
An inbox for bills
Invoices from other Orla users land in Incoming. Accept one into a space to track it, decline it, or mark it paid. A bill from someone you have no history with is flagged unverified, because the name and the address on it were typed by whoever sent it. Tick several and pay them as one run.
Virtual Visa cards
Issue a card to someone's email against a shared prepaid balance. They open the link, pass the issuer's identity check, and the card goes live. Their ID goes to the issuer, not into Orla. Freeze, block, rename or top up at any time. Top up in stablecoins.
- Pay-link rails
- Crypto (auto-matched) or bank details with a reference
- Invoice output
- Public link + PDF, branded from Settings
- Invoice statuses
- Draft · sent · partially paid · paid · void
- Auto-reminders
- 3 days before, on the day, 3 and 7 days after, once each
- Repeats
- Weekly or monthly, one catch-up after a pause, never a burst
- Card network
- Virtual Visa, funded from a shared prepaid balance
- Card top-up
- USDT / USDC on a supported network, exact amount, fee shown
- 3-D Secure
- Telegram bot, SMS fallback
Does the payer need an Orla account?
No. Pay-link and invoice pages are public. An account only matters if the payer wants the payment in their own ledger.
How does a crypto payment get matched to my invoice?
By the exact amount sent to the address on the page. A rounded transfer cannot be attributed with confidence, so the page insists on the exact figure.
What happens to card holders' data if I delete the space?
You cannot delete a space that still has live cards, so block or close them first. After that the holders' personal data is erased and old card links stop working.
Can I put my own branding on invoices?
Yes. Your logo and seller details come from Settings and show up on both the public page and the PDF.
Someone pays late, after I have emailed the invoice. Now what?
The link in the email still works and the payment books against the same invoice. Clicking it twice never duplicates the record.
Send one invoice.
Public link, PDF, and the income booked when it is paid.