A Trolley recipient account exists so that a business can collect and maintain the information it needs to pay you.
For recipients, the process may look like a separate Trolley-hosted portal, a branded page connected to the payer, or a payment section embedded directly inside another company’s website or app.
That flexibility is intentional. Trolley currently offers a hosted customizable portal, a modular recipient widget, SDK tooling and APIs for companies that want to build more of the experience themselves.
As a result, there is no reason to expect every legitimate Trolley onboarding flow to look identical.
Start With the Organization Paying You
The payer is the anchor for the relationship.
If a company tells you that it uses Trolley, follow the recipient instructions provided through a company channel you recognize.
That is safer and usually more accurate than searching the web for a generic “Trolley sign in” page and assuming that every merchant uses the same portal.
A payer might direct you to:
- a Trolley-hosted recipient portal;
- an embedded Trolley section inside its own account area;
- a customized workflow using Trolley’s APIs.
Why the Portal Can Look Like the Payer’s Website
The hosted recipient portal can be customized.
Trolley’s portal documentation describes options for merchant branding, including appearance and white-label communications. Its embedded widget similarly allows businesses to keep recipients inside their own product experience.
This is especially relevant when deciding whether a page is “really Trolley.”
Branding alone does not answer that question.
The important evidence is whether the workflow comes from a company that genuinely owes you money and whether the destination is the one that company officially provided.
Email OTP Instead of an Ordinary Password
Trolley’s current recipient-management materials describe hosted recipient access that can use an email one-time password.
The code is delivered to the recipient’s email and used to authenticate the session.
A one-time code should be treated like any other authentication factor.
Do not send it to someone claiming to be support.
The point of an OTP is to prove that you control the recipient account or email session—not to give another person the ability to authenticate as you.
Building the Recipient Profile
The information required depends on the payout and compliance configuration.
A basic bank-transfer workflow can require personal or business information plus the destination account.
Trolley’s API model treats the recipient itself separately from the recipient’s payout account. A recipient can have multiple payout accounts associated with the profile, although one is designated as the primary destination at a particular time.
This structure is useful because it separates:
Who is being paid?
from
Where should the current payment be delivered?
Selecting a Payout Method
The payer decides which methods to make available.
A recipient may encounter bank transfer, PayPal, Venmo, a supported debit card, a mobile wallet, a check or another eligible destination depending on the program.
Do not be surprised if another Trolley user sees a choice that you do not.
Differences can result from:
- recipient country;
- currency;
- payer configuration;
- product eligibility;
- the financial account being used.
Our Trolley Payout Methods and Timing guide covers the practical differences between these options.
Why Trolley May Need Your Address
Financial payment routes often require more than an account number.
For example, Trolley’s bank-transfer API documentation includes recipient address information as part of the bank-transfer data model and specifies additional location-dependent requirements.
Address collection should therefore not automatically be interpreted as unrelated to payout processing.
But it should still occur only through the legitimate workflow associated with the payer.
Tax May Be a Separate Module in the Same Experience
Trolley’s recipient widget is modular.
Its documented modules include Pay, Tax and Trust, allowing a merchant to collect payout information, tax information and verification information through connected onboarding components.
A recipient might therefore complete several tasks without leaving what appears to be one onboarding flow.
They serve different purposes:
Pay helps establish how the recipient receives money.
Tax handles applicable tax information.
Trust can support identity or business-verification requirements.
Keeping those concepts separate helps explain why some recipients finish onboarding after adding a bank account while others see additional steps.
Can You See Payment History?
Trolley’s recipient-management product can expose live payment-status information, historical records and tax forms in the recipient dashboard when the merchant enables the relevant functionality.
That makes the recipient experience useful after initial setup as well.
A portal can become a place to maintain the payout destination and review payment information rather than something used only once.
What If Your Bank Information Changes?
A payout-destination change is security-sensitive.
Use the authenticated recipient workflow associated with your payer to update the information.
Do not send complete bank credentials in ordinary email because someone claims to need them to “unlock” or “verify” a payout.
Where a payment problem follows a bank-detail change, contact the payer using a trusted channel and review the recipient profile before attempting repeated edits.
What If the Invitation Expires or the OTP Does Not Work?
Authentication trouble and payout trouble are separate problems.
If you cannot authenticate, you may not yet be dealing with the payment itself at all.
Check:
- that you are using the same email address associated with your recipient account;
- whether a newer OTP has replaced an older one;
- whether you are following the current invitation from your payer;
- whether the payer has changed the recipient email or onboarding workflow.
If access still fails, the paying organization should usually be your first escalation point because it controls your commercial relationship and can identify the recipient record associated with you.
Avoid Fake “Account Recovery”
[PUBLICATION NAME] does not provide Trolley account recovery.
We will never ask you for an OTP, password, bank number, card number or tax identifier.
A website explaining Trolley is not automatically connected to Trolley merely because it ranks for a search containing the company’s name.
Use the actual recipient workflow provided by the organization paying you.