Built for creators

How to Collect Video Editor Payment Details Securely

Collecting payment details from the people you work with sounds straightforward.

Start secure sharing See how it works
256-bit TLS encryption No account required for payees Free to start
The problem

Why this matters

Collecting payment details from the people you work with sounds straightforward. In practice, it's one of the most security-sensitive steps in any business relationship — and most businesses handle it in a way that creates unnecessary risk.

What Most Businesses Get Wrong

The typical approach: someone asks for bank details over email, Slack, or text. The contractor types them out and hits send. The payer copies the numbers into their banking portal. Both parties assume this is fine because it has always worked before.

It isn't fine. Every time sensitive payment information moves through an unencrypted channel, it's exposed to interception. Business email compromise (BEC) attacks specifically target this moment — they wait for a payment detail exchange and swap account numbers before either party notices. By the time the misdirected payment surfaces, the money is gone.

The other problem is storage. Payment details that arrive via email end up in an inbox — searchable, accessible to anyone with account access, and vulnerable to data breaches. That's not a payment record. It's a liability.

What to Collect — and How to Ask for It

01

Request Through a Secure Link

Send a Garded payment request link — your payee fills out their details directly in an encrypted form. Nothing travels over email.

02

Collect Only What You Need

Legal name, tax ID, bank routing, account number, and payment preference. Don't ask for more than necessary, and don't store it outside a secure system.

03

Store It with Access Controls

Payment details should live in a system with row-level security — accessible only to authorized users in your organization, not to everyone with email access.

04

Keep It Current

Payment details change. Set a reminder to re-verify annually, or any time a payee reaches out to update their information.

What you'll need from your Video Editor

FieldWhy it mattersProtection
Legal nameFor 1099 if you pay them over $600/yearAES-256 encrypted
Bank routing numberACH depositAES-256 encrypted
Checking account numberDirect depositAES-256 encrypted
Payment preferenceACH, PayPal, or WiseAES-256 encrypted
Invoice triggerAfter final cut delivery or approvalAES-256 encrypted

Collect Payment Details the Right Way — Starting Today

Send your first secure payment request in minutes. No credit card required.

Get started free No credit card required · Set up in minutes

Common questions

Does the payee need to create a Garded account?
No. They receive a secure link and fill out their payment details directly — no account, no download, no friction.
Where are the collected details stored?
All payment details are encrypted with AES-256 and stored with row-level security. Only authorized users in your account can access them.
What if the payee updates their banking details later?
You can send a new Garded request at any time. The updated details replace the old ones and the change is logged.