# Advertisers invoiced on either rail. Publishers paid in one screened batch URL: https://www.orla.finance/en/for/affiliate Markdown twin of that page. Append `.md` to any Orla page URL to get one. Rivet Network runs fintech and gaming offers for three advertisers and a roster of publishers, four people in the office. #### Advertisers invoiced in dollars or stablecoins Brightpay pays by transfer on net 15, Kalypso pays in USDT, Nordic Bet has paid. What is owed, in which currency, and who is next to pay? - Four figures as filters: owed, overdue, received this month, paid without an invoice; each one opens its own list. - Invoices in any currency, paid by transfer or in stablecoins, each priced at the day's rate; an invoice marks itself paid when the money lands. - Recurring invoices and reminders; a quote becomes the invoice. #### Publishers paid weekly in one batch, on chain, PayPal or by bank Forty publishers want USDT on Friday, a few want PayPal, one wants a bank transfer. Can it all go out together, with a quorum and a screening first? - One batch a week: each publisher's amount on it, signed once, paid on the rail each contact carries, a wallet or a bank account, whichever the contact has given you. - A threshold and a quorum: what crosses the line waits for a second signature. - TRON, EVM and Solana payouts from the same list as the PayPal and bank ones; a publisher is a contact with a rail, not a seat, however many there are. - The bank share leaves from your own account. In Airwallex the approved payments are lines of a draft batch, one per currency, that a person submits there. Slash has no drafts, so there a person with the right to release payments presses Send via Slash in Orla after the quorum, the way a PayPal payout is sent. Both are still rolling out. #### Every address screened before it is paid A new publisher sends a TRON address and wants the first payout today. Is the address clean, and who is told when it is not? - An address is screened before the payout leaves: risk score, signals, blacklist; a high score stops the batch and tells a person which row tripped. - Watches on the addresses you pay often; a change in their risk is a notification. - Inbound too: a payment from an address that trips the score is flagged, not booked. - The name behind the wallet is checked too: a counterparty check on the contact's card screens the publisher or the advertiser by name against sanctions, politically exposed persons, criminal lists and adverse media, and confirms a company number in its registry. It spends one check from the same balance as the address screenings, and a verdict under thirty days old answers again for free. #### The patterns fraud leaves One publisher's traffic converts too well and the payouts grew fivefold in a month. Which patterns fired, and why did they? - Patterns that watch the book: a payee first seen this month, a payout grown out of proportion, and a wallet under two different publishers. - Each alert says why it fired and what to do; a case gathers the rows behind it. - On the Payments page a line under a payment says This does not look like you: a payee paid far above their usual, with the usual named, a first-time payee paid a lot by this book's scale, or the same amount to the same payee twice in a week, the second still in the queue. It explains and never blocks: signing works exactly as it did. - A counterparty's history in one place: what was paid, when, on which rail. #### A treasury on both rails, swaps included Advertisers pay in dollars and USDT, publishers want USDT. Where does the USDC go, and does the swap stay in the book? - Wallets on TRON and EVM chains beside the bank; balances and their history per account, each one priced at the day's rate, for a quarter or a year at a time, on one screen. - A swap is priced at the minute it happened, and a transfer between your own wallets is neither income nor an expense, only a move between them. - Cost basis survives the swap, and the realised gain sits in the same month as rent. #### Tools and events on cards topped up in USDT Everflow, Cloudflare and Ahrefs bill the tools card, the Barcelona ticket goes on another. Can the USDT in the treasury fund them, each with its own ceiling? - Virtual cards funded in USDT or USDC through a prepaid balance. - A card per person with a ceiling, freeze and block; the issuer's history is checked against what you allocated, so a stray charge shows up the same day. - Refunds are answered in the books on their own. #### Who can move money, and what holds them Four people, a publisher batch every week above the threshold. Who prepares, who signs, and what does the auditor read? - Roles: owner, admin, member, viewer, accountant. - Signing rules: a threshold, the number of signatures, address book only, a monthly allowance per person counted across every door. - Every action in an audit trail the accountant can read, never edit. #### The month to the accountant Three advertisers on two rails, forty publishers on three, a treasury with swaps, and an accountant who wants one folder. - A closing checklist with a door into each list: rows without a category, without an account code, without paper, unpaid invoices, payments still waiting for a signature. - A zip archive, a journal CSV, and each account's feed for QuickBooks Online and Xero. - Review, Close, Reopen with a reason; what changed after the export is visible, and an accountant seat reads what was closed. #### Four people paying forty publishers - Founder: Signs the weekly batch, reads the alerts, and reads the margin per advertiser. - Treasury: Prepares the publisher batch on TRON, screens the new addresses, and keeps both rails funded. - Account manager: Sends the advertiser's invoice in dollars or USDT and hears when they ask for time. - Accountant: Sees every payout under its advertiser, in the month's files and in a seat that only reads. #### Ask it which payout does not look right Hundreds of payees a month: the composer flags the one payout that does not match its own history. - A payee out of pattern: A payment that does not match the history of that payee and amount, on any rail, not only crypto. It explains and never blocks. - Duplicates before they are paid: A bill checked by number, amount and payee against everything accepted and paid on any rail. The verdict is yours, and both papers stay. - What is burning, one list: Overdue invoices, loans and milestones, connections down, payments waiting for a signature for more than a day. #### Wallets, exchange, each publisher's rail Wallets on TRON and Base by address, the exchange by read-only key, and publishers paid on the rail they chose. #### Publishers screened before they are paid - Screened first: An address is screened before the payout leaves; a high score stops the batch and tells someone. - A quorum: The weekly batch clears the threshold, and a second person signs it before it leaves. - Address book only: A payout goes only to a publisher already in the book, on the rail they gave you themselves, and no other. - Patterns: A payee first seen this month or a payout grown out of proportion is an alert, with the rows behind it. #### Questions ##### Can publishers be paid in USDT on TRON? Yes. A publisher is a contact with a rail: a TRON, EVM or Solana address, or a bank account. The batch pays each on the rail they carry, after the address is screened, and the payout is priced at the day's rate in the book the accountant reads. ##### Does the screening block a payout on its own? A high score stops the batch and tells a person; the rest of the list goes on. The alert says why it fired, and a person decides what happens to that publisher. ##### Are publishers seats? No. Seats are people in the space; publishers are contacts and do not count, however many there are. Paid plans start at $25 a month, and any single limit can be raised with a pack instead of a plan change, so the network pays for the people, not the roster.