Paying someone out usually starts with a small, awkward negotiation. You need their bank details, so you email a form, or a spreadsheet, or just ask them to type an account number into a reply. They get it slightly wrong. You chase. And when it finally arrives, you are holding a piece of sensitive information you never wanted to store in the first place.
Payment links turn that around. Instead of asking how to pay someone, you send them a link and let them tell you — securely, in their own words, on a page you never have to build.
Send a link, not a form
Creating one takes seconds and no code. You choose who is being paid, how much, and add a short note for your own records — something like "Refund for order #99821." That is the whole setup. Magellan hands back a link, ready to share: email it straight from the dashboard, or copy the URL into a text, a chat, or wherever you already talk to the person.
They choose how to get paid
When they open the link, they land on a hosted page that carries your logo and your terms — not a generic form, and not something you had to design. There, they pick how they want the money: pushed to a bank account in real time, sent over ACH, dropped straight onto a debit card, or even paid out in Bitcoin over the Lightning network. They enter their own details, once, on a page built to hold them safely. You never see a raw account number, and you never store one.
You approve before a cent moves
Nothing leaves your balance on its own. Once the recipient has captured a method, the payout waits for your sign-off. You review it, approve it, and it executes on the rail they chose — landing in seconds over real-time rails, in a day or two over ACH, in minutes on a card. If something looks off, you reject it with a reason and nothing moves. That pause is the point: for refunds, claims, and vendor payouts, the last word should always be yours.
Links that don't linger
Every link has a shelf life — an hour, a day, a week, a month, or a window you set yourself — so nothing stays live longer than it should. Need more time? Extend it. Changed your mind? Cancel it. Recipient lost the email? Resend it. And when a payout is done, you can copy it as a new link in one click for the next one. Behind all of it runs a full timeline — created, captured, approved, paid — so every payout has a clean, auditable story.
From one payout to a platform of them
A single business can send one link from the dashboard and never touch an API. A platform can issue thousands on behalf of the merchants it serves, each branded, each tracked, each scoped to the right account. It is the same hosted flow either way — which is the same promise behind everything we build: one integration that does not change shape as you grow. We wrote more about that in one API, from a single merchant to a global platform.
Anywhere you'd have asked for bank details
Refunds. Contractor pay. Affiliate and partner payouts. Insurance reimbursements. Marketplace disbursements. Wherever the old answer was "send me your account number," the new one is "here's a link." The person on the other end gets paid the way they prefer, you keep the final approval, and nobody ends up holding details they would rather not.
See it in the API documentation, or talk to us about putting payment links to work.