How agencies pay influencers and talent, by bank and in USDT

The contact keeps how they get paid. A bank rail is picked by scheme, SEPA and IBAN, UK sort code, US ACH or SWIFT, and filled in as fields; an IBAN or a US routing number with two digits swapped is refused as it is typed. A wallet address is saved per network, with one default, and a PayPal email is a rail too.

Beside the rails sit the tax id, tags such as creator or manager, and the documents you keep on this person: the agreement, a W-9 or a W-8BEN.

A CSV or XLSX with a name column and whatever else it has, up to 500 rows, with a preview that says which rows are new and which are already in the book before anything is created.

Only an owner or admin can mark a contact trusted, and editing a trusted contact's rails drops the trust until it is confirmed again, because trust belongs to the exact details that were checked.

Up to 200 rows: a payee, an amount, an optional note and category, typed or imported from a CSV with a preview of what matched. Each row shows where it pays, the contact's default address for the paying account's network, and is flagged when that contact has no address for it.

A row repeating a payment to the same contact for the same amount within three days is flagged before you submit.

A template: the saved row list plus a schedule, monthly on a day or weekly. On the day Orla prepares the draft and tells its author it is ready; sending is always a person's press, because who is on the roster changes from month to month.

On a plain bank account Orla records the transfers and the transfers are made in the bank. On a connected Revolut Business or Airwallex account Orla prepares the whole run as one draft inside the bank, so forty payments are approved once there, and only the lines the bank actually paid are recorded as spent.

From a connected Mercury account each payment is requested into your Mercury approval queue, in US dollars. From Slash a person presses Send via Slash.

With a PayPal Payouts credential connected, the creator's PayPal email is a rail and the batch is paid from the PayPal balance. A per-payout ceiling set when you connect refuses a single payout above it even with a full quorum, and Pay via PayPal is a press.

A payout PayPal returns unclaimed is noticed, and Orla books the refund itself so the books net out.

From your own wallet on TRON, Solana, Ethereum, Base, Arbitrum or Polygon. The run sends every approved payment of one wallet in one sitting with the wallet unlocked once, screens addresses never screened before, and shows what the network will cost next to the balance.

A run that is 60% funded pays 60% of the people, and the rest stay approved for after the top-up with no second round of signatures.

Payments above a threshold need a number of signatures, and a batch is checked on its total, so a payout split into small rows needs the same signatures the whole amount would. Whoever proposes a payment cannot sign it.

A rule can name who may sign, and address-book only forces signatures for any destination that is not a trusted contact.

The notification names the contact, the amount and the rail: the network and a shortened address for a wallet, the last digits of the account for a bank payee. A whole batch can be signed or rejected from Telegram or Slack with one button. Building the batch and sending the run stay at a desk on purpose.

The owner can always reject a payment and a proposer can withdraw one, so nothing waits on somebody who is away. On Scale a rule can also give a named person a monthly allowance they may send without a signature.

Each campaign is invoiced, and a signed agreement can be read into a billing schedule so the invoices go out on their dates. What should arrive this week and who pays slowest answer from the invoices themselves, and a reminder with the pay link goes out on its stage without anyone writing it.

A creator who invoices you forwards the invoice to the space's own address, and it becomes a draft bill for a person to accept; where to pay comes from the contact card, never from the email.

A creator who never sends a document can be covered by a self-billed invoice written on their behalf, where that is switched on for the space, with a plain warning that a tax office may refuse one without a self-billing agreement.

Costs and income carry a project, and profit and loss by project reads the margin per campaign from the same rows. Ad spend runs on virtual cards funded from one prepaid balance, each card with its own ceiling.