How Ostro works: receive, track, and choose your payout
Understand the Ostro payment journey, from sharing available receiving details to tracking an incoming payment and choosing an eligible bank or wallet payout.
THE IDEA TO TAKE WITH YOU
Start with the instructions your payer can use. Track what happens after they send. Choose a payout from the options available to you.
A client is ready to pay you. They ask for your payment details.
What should be a short exchange can become a longer conversation: which currency, which account name, which transfer method, and what happens once the payment arrives?
Ostro is being built around that moment. The intended journey has three parts: share available receiving details, follow the incoming payment, and choose an eligible payout.
This guide explains how those parts fit together, which details matter, and where invoices and payment links can help. Product access remains subject to activation, verification, and approval. The options in your workspace determine what you can actually use.
1. Start with available receiving details
Receiving details are the instructions an eligible payer uses to send you a supported payment. Depending on the route, they can include an account-holder name, account identifiers, the currency, the payment rail, and a required reference.
You share those instructions with a legitimate client, employer, customer, marketplace, or business partner, much as you would share ordinary bank-transfer instructions.
The complete set matters. An account number without the permitted currency or transfer method can leave the payer guessing.
For example, a client who has a USD invoice still needs to know which supported USD payment method to use. The currency alone does not tell their finance team whether a particular account can receive the transfer they intend to send.
Ostro’s receiving-details guide explains what to check before sharing instructions.
What “details in your name” means
The wording is specific: Account details in your name, where available and approved.
That is a conditional product option. It does not mean every applicant receives named details, every currency has the same account type, or Ostro provides a traditional bank account.
Always use the beneficiary name displayed for the actual route. Do not replace a displayed name with your trading name because it looks more familiar to the client.
2. Keep the payer’s task simple
Your client needs a clear instruction for the payment they are sending. They do not need to understand every possible payout you might choose later.
A useful handover answers four questions:
- Which currency should the payer send?
- Which receiving details and payment method should they use?
- Is there a required memo or reference?
- Who should they contact before sending if their bank cannot follow the instructions?
Consider an illustrative example: a freelance researcher invoices an overseas company in a supported currency. The company’s finance team receives the current instructions and sends through the specified route. The researcher later considers the eligible payout options in their own workspace.
Those are connected steps, but the client and the researcher have different decisions to make. Keeping those decisions separate makes the handover easier to explain.
If you need a message you can adapt, use our international payment handover template.
3. Follow the payment beyond “sent”
A sending confirmation is useful evidence of what the payer submitted. It is not, by itself, confirmation that a payment is available for payout.
A clearer payment conversation distinguishes these events:
| Event | What to check next |
|---|---|
| A payment request was shared | Has the payer approved and submitted the transfer? |
| The payer says the transfer was sent | Keep the confirmation and check the actual payment status. |
| The payment is being reviewed | Look for any information requested through the appropriate channel. |
| A payout option becomes available | Check the destination, charges, requirements, and timing before proceeding. |
This table describes stages in the journey, rather than a list of exact interface labels. The payment-status guide provides product-specific explanations.
If a payment needs investigation, a precise question is more useful than “Where is it?” Include the date, amount, currency, route, and available payment reference when contacting support. Keep identity documents and full financial records out of an initial public contact-form message.
4. Choose where the payment goes next
The available payout paths are local currency to a verified bank account, or an eligible stablecoin to a verified wallet where supported and permitted.
Start with the destination you actually need.
Local currency to a verified bank account
Check the account, beneficiary, destination currency, and supported payout route. If you need funds in a bank account for an upcoming expense, confirm that the account can accept the particular payout.
Ostro’s broader local-payout coverage through licensed financial partners is separate from its six fiat funding and receiving categories. A currency being available for a local payout does not automatically mean receiving details are offered in that currency.
Stablecoins to a verified wallet
Check the asset and network together with the wallet address and any required memo or tag. A wallet displaying an asset is not sufficient evidence that a particular payout route can deliver it there.
An approved route, destination verification, and applicable restrictions still matter. Do not assume all stablecoins or all networks are supported.
For a more detailed comparison, read local currency vs stablecoin payouts.
5. Understand what the currency list tells you
Ostro’s fiat funding and receiving categories include USD, EUR, GBP, BRL, MXN, and COP, subject to the routes available for your account. They also support eligible payout flows where available.
Those categories are useful for exploring the product. They are not an instruction to send any currency over any rail, or a guarantee that each option is enabled for every customer.
Check both sides of the journey:
- Incoming: the currency, payer type, receiving details, and rail.
- Outgoing: the destination country, currency or asset, bank account or wallet, and any network requirements.
Use the currency guides and country directory for context. Your workspace remains the place to confirm the options approved for you.
For an independent explanation of the systems behind those options, the blog’s currency library covers USD, EUR, GBP, BRL, MXN, and COP receiving and payout workflows.
6. Use invoices when the relationship needs them
Some payers only need receiving instructions. Others need a formal invoice before their finance team can approve payment.
Invoices and payment links are additional ways to communicate a request where those features are enabled. They do not replace the requirements of the underlying payment route or establish that money has arrived.
Choose the format that helps the payer do their job. Keep the amount, currency, beneficiary information, and any mandatory payment reference consistent across that format.
Our comparison of receiving details, invoices, and payment links explains when each is useful.
7. Know who handles each part
Ostro supports customer onboarding, identity verification, KYC and sanctions screening, country eligibility checks, transaction monitoring, recordkeeping, and compliance escalation.
Payment processing, foreign-exchange and stablecoin conversion, custody where applicable, and settlement are provided by licensed financial partners. Conversion takes place only where needed and supported.
Ostro is not a bank and does not hold customer funds. Neither conversion nor payout should be assumed to be instant.
Clear responsibilities help you know where to raise a question. Start with Ostro support for an Ostro payment issue, using the support contact guidance.
Before your first payment
Check your country eligibility and complete the required verification. Wait until the receiving instructions you intend to use are active and approved. Then confirm that the payer can follow the complete instructions.
When the payment arrives, review the available next step rather than assuming a particular payout will be offered.
That is the experience Ostro is working toward: a payment journey you can understand from the first instruction to the destination you choose. Explore how it works or find the solution for your work.
Availability depends on eligibility, jurisdiction, compliance review, supported routes, and partner availability. Use the options shown in your Ostro workspace.
Find practical answers in the Help Center ↗