Trolley

Trolley, formerly Payment Rails, is a global payouts platform. Agents onboard recipients and their payout accounts, build and submit payment batches, quote currency, manage invoices and invoice payments, and react to payment and recipient events.

Verified 1 trigger 62 actions Custom auth available

Trolley website Platform Documentation Capability data verified 2026-08-25

The monthly payout cut-off arrives for a roster of contractors and creators

Agent reads approved earnings from the ledger and resolves each payee to a Trolley recipient

Get Recipient confirms compliance status and a primary payout account on every payee

Create Batch and Create Payment stage the whole run without sending anything

Generate Quote locks the exchange rates, and Get Batch Summary is compared against Get Balances

The finance owner receives the totals, the currency split, and the fee figure

The finance owner confirms the funded total, and only then does the agent call Process Batch

What This Integration Enables

Trolley, formerly Payment Rails, is built for paying people you do not employ. That inversion runs through the whole API. The invoice object represents money a contractor is claiming from you rather than money you are claiming from a customer, and the compliance and tax reporting surface is the product rather than an add-on. FlowRunner agents onboard recipients, add and correct payout accounts, run identity and watchlist verifications, and record payments made outside Trolley so a payee's earnings history stays whole.

The payout side is deliberately staged. A batch is an envelope that holds payments and moves no money until it is processed, a quote fixes the exchange rates for a moment, and a summary reports what the run will actually cost. FlowRunner agents do all of that assembly work, and then stop. The commit belongs to a person, which is what human-in-the-loop means on a payout run: the machine builds the number, and someone accountable releases it.

Without FlowRunner

Payee readiness discovered late Missing bank details and blocked compliance status surface during the run rather than before it

Totals rebuilt by hand The payout figure is reassembled in a spreadsheet each cycle at whatever rate was current when someone typed it

Split earnings picture Money paid to the same contractor outside the platform sits somewhere else entirely when year-end forms are due

With FlowRunner

Readiness checked while the batch is still editable Compliance status, payout accounts, and corridor requirements are verified before a payment is staged

Totals taken from the batch itself Quoted rates, fees, and the balance check all come from Trolley before anyone approves a number

One earnings record per payee Payments made outside Trolley are recorded against the same recipient, so the reporting totals are complete

Use Case Scenarios

The monthly payout run, staged and quoted before anyone approves it

Earnings for the period are read from the ledger, whether that lives in Google Sheets, Airtable, or NetSuite. The agent resolves each payee with List Recipients, reads compliance status with Get Recipient, and sets aside anyone blocked or missing a primary payout account. Create Batch opens the envelope, Create Payment adds a line per payee with the target amount fixed so the contractor receives exactly what they earned, and Generate Quote locks the rates. Get Batch Summary and Get Balances go to the finance owner in Slack together, because the useful question is not what the run costs but whether the account covers it.
Onboarding that finishes before payday, not on it

A new contractor signs. The agent calls Get Country first, since the corridor decides which bank fields and government identity documents are actually required, then Create Recipient and Create Recipient Account with the right shape rather than a rejected guess. Trigger Verification starts the identity and watchlist checks, and because the result arrives later, the agent watches for it rather than polling blindly. When a verification comes back needing attention, the recruiting or finance owner hears about it days before the payout run instead of during it.
Contractor invoices that become a payment run

Contractors submit invoices through Create Invoice and Create Invoice Lines, or through your own intake form. An approver marks lines as accepted in the system of record. The agent then calls Create Invoice Payment to attach the approved lines to a payment inside a named batch, which is the join between the invoicing half of Trolley and the payout half. Nothing has moved yet. The batch still has to be quoted, checked against the balance, and processed, which is exactly where the human sits.

Human-in-Loop Highlight

Process Batch is the operation that moves the money, and Trolley is blunt about it: after it runs, the batch cannot be deleted and individual payments cannot be edited. What makes the gate interesting is the quote. Generate Quote locks the exchange rates for a limited window, so the total a person approves is only the total that leaves the account while that quote is alive. The agent posts the run to the finance owner: "142 payments, 218,400.00 USD source, 4 currencies, 611.20 USD in fees, against an available balance of 240,110.00 USD. Quote expires in 19 minutes. Process?" If the answer arrives after the window has lapsed, the agent does not treat a stale approval as a live one. It re-quotes, re-reads Get Batch Summary, and asks again with the new number. The approval is on a figure, not on a button.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

62 actions

Recipients

Create Recipient Creates the person or business you intend to pay. Creating one does not make them payable, which is why the account step follows.
List Recipients Filters recipients by status, compliance status, payout method, country, currency, tags, and free text. The compliance filter is the one that predicts whether a payment will actually land.
Get Recipient Reads one recipient in full, including identity, address, tags, compliance status, and their payout accounts.
Update Recipient Updates recipient details. Tags replace the stored set rather than adding to it, and changing an address or identity document can reopen compliance screening.
Delete Recipient Removes a recipient record. Payments already made to them survive the deletion.
Delete Multiple Recipients Removes several recipients in one call, for a bulk cleanup where per record error reporting is not needed.
Get Recipient Logs Reads the audit trail for one recipient: every change to their details, accounts, and compliance status. This is what answers a dispute about when a bank account was altered.
Get Recipient Payments Lists every payment made to one recipient across all batches, which is the statement a contractor is asking for.

Recipient Accounts

Create Recipient Account Adds the payout account that makes a recipient payable. Which fields matter depends on the method and the corridor.
Get Recipient Account Reads one payout account with its type, currency, country, and masked identifiers.
Update Recipient Account Updates a payout account, most usefully to move which account is primary.
Delete Recipient Account Removes a payout account. Deleting the primary leaves the recipient with no default, so payments fail until another is marked.

Batches

Create Batch Opens the envelope every payment lives in. A batch left unprocessed pays nobody, which is what makes staging safe.
List Batches Lists batches filtered by status, currency, tags, reference, and an updated date range.
Get Batch Reads one batch with its status, total, payment count, and timestamps. Only a completed batch has actually paid anyone.
Delete Batch Deletes an unprocessed batch and the payments in it. Refused once the batch has been processed.
Delete Multiple Batches Removes several unprocessed batches in one call.
Generate Quote Locks the exchange rates for a cross-currency batch. The quote expires, which is the fact this page's human gate is built on.
Get Batch Summary Reads the batch totals: payment count, amounts per currency, and fees. The last chance to compare what you are about to send against what you expected.
Process Batch Sends the batch for processing. This is the operation that moves the money, and the one the agent is not allowed to call unattended.

Payments

Create Payment Adds a payment to a batch. Target amount fixes what the recipient receives, source amount fixes what leaves your balance, and the two are not interchangeable.
List Payments In Batch Lists the payments inside one batch, optionally filtered by status.
Get Payment In Batch Reads one payment addressed through the batch that holds it.
Get Payment Reads one payment by its id alone, which is what an event handler usually has.
Update Payment Edits a payment while its batch is still open. Refused once the batch has been processed.
Delete Payment Removes a payment from an open batch.

Offline Payments

Create Offline Payment Records money you paid a recipient outside Trolley. No money moves, and the point is that tax reporting sees the full picture rather than the platform's share of it.
List Offline Payments Lists every offline payment recorded on the account.
Get Recipient Offline Payments Lists the offline payments recorded against one recipient, which completes their earnings picture.
Update Offline Payment Corrects an offline record. Both amount and withholding are required, so read the record before writing it.
Delete Offline Payment Removes an offline record. It changes reporting totals, so it belongs to correcting mistakes rather than tidying history.

Invoices

Create Invoice Creates an invoice a recipient is claiming from you, which is the inverse of the invoice most billing APIs model.
Get Invoice Reads one invoice with its lines and their individual statuses.
Search Invoices Searches invoices by recipient, number, external id, date, memo, or tags, with several filters accepting lists.
Update Invoice Updates an invoice's description, dates, external id, or tags. It does not touch the lines.
Delete Invoice Deletes one or more invoices. A paid invoice is refused.
Create Invoice Lines Adds lines to an invoice. Lines are what a payment actually settles, so an invoice can be paid a line at a time.
Update Invoice Lines Updates lines on an invoice. A line already paid cannot be edited.
Delete Invoice Lines Removes lines from an invoice, once nothing is paying them.
Create Invoice Payment Attaches approved invoice lines to a payment inside a named batch. Approving here still does not move money, because the batch has to be processed.
Search Invoice Payments Answers both directions of the reconciliation question: which payment settled this invoice, and which invoices did this payment cover.
Update Invoice Payment Changes how much of a payment is applied to one invoice line.
Delete Invoice Payment Unlinks invoice lines from the payment settling them, returning those lines to unpaid.

Verifications

List Verifications Lists identity, business, phone, and watchlist checks run against recipients, with the status of each.
Trigger Verification Starts verification for one or more recipients. The outcome arrives later, so a flow watches for it rather than expecting an answer inline.
Expire Verification Marks verifications expired, which forces a recipient to verify again when a document has aged out or policy requires it.

Balances

Get Balances Reads every account balance across funding sources and currencies. The check that belongs immediately before a payout run.
Get Trolley Balance Reads the balance held in the Trolley wallet itself.
Get PayPal Balance Reads the linked PayPal balance, which funds PayPal payouts separately from the wallet.
Get Funding Information Reads the bank details for topping the account up, which is what finance needs when the balance falls short of a batch.

Reference

Get Country Reads what a payout into one country actually requires: bank fields, accepted identity documents, and regions. The lookup that prevents a rejected account.

Administration

Set Widget Configuration Sets the colors of the hosted onboarding widget where recipients enter their own bank details.
Update Onboarding Information Updates the volume figures Trolley holds about your business, which feed its compliance review of your account.
Create Sub-Merchant Creates a sub-merchant under a platform account, which is how a marketplace gives each seller its own payouts identity.
Create Sandbox Merchant Provisions a sandbox merchant for testing a sub-merchant flow without touching production.
Delete Sandbox Merchant Removes a sandbox merchant and its test data.

Webhooks

List Webhooks Lists the event subscriptions on the account, each naming one model and one action.
Create Webhook Creates a subscription for a single model and action, which is what you use when the target sits outside FlowRunner.
Get Webhook Reads one subscription with its model, action, target URL, and validation state.
Update Webhook Updates a subscription. Changing the target re-runs endpoint validation, so delivery pauses until the new URL answers.
Delete Webhook Deletes a subscription.
Retrigger Webhook Validation Asks Trolley to re-run endpoint validation after an unreachable endpoint has been fixed.

Triggers

1 triggers

Event Triggers

On Trolley Event Fires when Trolley reports a change: a recipient or payout account created, updated, or deleted, a payment created, processed, failed, or returned, a batch moving through its lifecycle, a tax form status change, a verification result, or funds arriving in your account. The record is lifted out of the vendor's envelope so the flow reads it directly, which is what lets a payout run react to a returned payment rather than discovering it in a month-end reconciliation.

Frequently Asked Questions

What can FlowRunner do with Trolley?

FlowRunner agents can run Create Recipient, List Recipients, and Get Recipient in Trolley, plus 59 more actions.

Does connecting Trolley to FlowRunner require OAuth?

Trolley uses a custom authentication method to connect to FlowRunner.

Can Trolley trigger a FlowRunner workflow automatically?

Yes. Trolley supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Trolley

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us