Slash
prepared by the autopilot, sent on your press
Connect Slash and every virtual account arrives with its statement. Inside the mandate the autopilot approves and lines up the payment; a person presses Send via Slash, because a Slash transfer has no draft. Your own approval rules in Slash stay the second guard.
What lands in the book
Every virtual account
with its statement, every hour
- Slash · Operating
- $56,420.10
- Slash · Payroll
- $22,000.00
- Slash · Ads
- $8,915.40
- Posted movements only
- About a month back when you connect, then every hour. A pending one keeps its place until it posts.
- Between your own accounts
- Moving money from Operating to Payroll is one transfer, not an expense and an income.
- Never booked twice
- When the statement brings a transfer Orla made, the payment you have gains the bank's reference and date.
- Details to be paid into
- Account and routing number of the primary account, as Slash states them. Card accounts are not brought in.
Who presses last
Lined up by itself
sent when a person presses
- Three supplier bills inside the Tools budgetApproved, waiting for Send via Slash
- Dana pressed Send via SlashSent by ACH, booked when settled
- A new payee, Lumen PrintWaits: add the payee to Slash first
- A transfer returned in SlashRefused in Orla, nothing booked
- No draft to leave
- A Slash transfer is real the moment it exists, so Orla creates one only on Send via Slash, pressed by someone allowed to release.
- ACH or a domestic wire
- Whichever the payee's details in Slash accept. An international wire is sent from Slash itself.
- Pressing twice is safe
- A second press looks the transfer up in Slash first, and creates it only if Slash holds none.
- Your Slash rules stay on
- Keep Slash's own approval for outbound transfers switched on. Orla cannot read it, and it is the second guard.
The key
A personal key
made by the right person
- Accounts and transactions
- View
- Contacts
- Manage
- ACH and wires
- Initiate
- Cards
- Nothing
- It acts as its maker
- Slash takes only personal keys, with that person's access. Make it as a user whose role can do exactly this.
- Your legal entity ID
- It starts with le_, and Slash needs it on every call.
- Orla's address on your allowlist
- Until it is there, Send via Slash is refused with that reason; statements keep coming in.
- A ceiling per payment
- Set when you connect. A payment above it is not sent.
On autopilot
What goes by itself
and what still waits for you
Goes by itself
- A bill or a payout inside its budget in the mandate
- From Airwallex, PayPal or the account inside Orla
- An agent's card or API spend inside its cap
Waits for you
- A new payee, and bank details that changed
- Anything past a budget or a limit
- Every payment from Mercury, Slash, a Safe or a wallet you sign
The brakes above both
- $2,000 a payment and $10,000 a day until you change them
- Loosening a limit waits 24 to 72 hours
- One pause stops every payment at once
Questions
Slash and Orla
the short answers
Does Orla pay from Slash by itself?
No. A Slash transfer goes only when someone on your team presses Send via Slash, and your Slash rules still apply.
Why not a draft, as with Airwallex?
Slash has no draft state: a transfer created there is a real transfer. So the press stays with a person in Orla.
What does it cost?
Nothing from Orla: a Slash payment is pressed by a person. Slash's own fees apply as they do today.
What if Slash has not opened its API to us?
Connecting says so and asks you to have Slash turn it on for your legal entity.
In the cabinet
- Pay and get paid
Pay bills on your rule, get invoices paid
- Inbox and the ledger
File every bill and receipt, with its paper
Read next
- Safe
Proposed by the autopilot, signed by your owners
- Your bank stays
And the autopilot knows how far it reaches
- Airwallex
Paid from by itself, inside the mandate
Connect Slash
and keep the send in your hands
On a thirty minute call we draft your first mandate and show which Slash payments it would line up.