A clearer next step.
One question at a time.

What do you need help with?

Choose the closest match. We’ll help you check the right things.

What is happening with the incoming payment?

Use the status you can see. A sender’s confirmation is not always proof of arrival.

Which payment rail was actually used?

Ask the sender if you are unsure. The currency alone does not identify every rail.

Where is the payout going?

Choose the destination for the payment you already requested.

What does the bank payout show?

Check the current status before submitting another payout.

What is happening with the stablecoin transfer?

Check the exact asset and network, not only the wallet address.

What is blocking access?

Choose the message or step that best matches your situation.

Do you still have the authenticator entry?

Do not delete an existing entry or share its setup secret.

Check before the payer sends.

Use only the active instructions issued for the intended flow.

1. Confirm verification, approval and route activation are complete.
2. Match the currency, rail, beneficiary and required reference.
3. Confirm whether the sender is an eligible business or individual, or whether this is your own funding.

Trace the ACH payment.

First establish whether the sending bank submitted the payment.

1. Check the ACH processing window, banking days and applicable cutoff.
2. Ask the sending bank for the ACH trace number and current bank status.
3. Compare the routing information, beneficiary and reference with your active instructions.

Check the wire reference and cutoff.

A submitted wire can still require receiving-bank processing.

1. Confirm this was a U.S. domestic wire rather than SWIFT.
2. Ask the sender for the IMAD or wire reference and time sent.
3. Check the wire cutoff and compare the destination with the issued instructions.

Match the payment to its actual rail.

Timing and tracking information differ across fiat routes.

1. Ask the bank which rail was used and whether it completed or returned.
2. Check the currency guide and processing window for that method.
3. Keep the receipt, payment reference, amount and time sent.

Ask the payer to identify the transfer.

You do not need to guess the rail from the payment currency.

1. Ask for the bank confirmation, actual method and submission time.
2. Check whether the bank shows pending, completed or returned.
3. Compare the instructions used with those issued in your workspace.

Check for an outstanding information request.

Review can apply even after your account was approved.

1. Read the request associated with the payment or account.
2. Provide accurate supporting information through the instructed secure route.
3. Keep the payment reference and avoid repeated submissions.

Keep the receipt and explain the mismatch.

Changing a message or invoice does not correct an already-submitted bank transfer.

1. Record the actual reference or details used by the sender.
2. Keep the bank confirmation, amount, currency and transfer date.
3. Compare the sent instructions with the correct active instructions.

Compare the payment records.

Check the currency, quote and actual deductions before concluding money is missing.

1. Compare the amount the sender submitted with the amount received.
2. Check whether currency conversion took place.
3. Review itemized charges and keep the original confirmation.

Establish whether there are two payments.

Repeated notifications can refer to the same transfer.

1. Compare bank and Ostro references, amounts and timestamps.
2. Ask the sending bank whether it submitted one or two transfers.
3. Keep both records if two payments exist.

Check timing before trying again.

A pending payout may still be in partner or bank processing.

1. Check the actual rail, submission time and stated estimate.
2. Account for applicable banking days, cutoffs and review requests.
3. Keep the destination and payout reference available.

Understand the failure before resubmitting.

A failed or returned status does not by itself confirm a new payout is safe.

1. Read the stated reason and any corrective action.
2. Check whether the original funds were released, are returning or are available again.
3. Confirm verified destination details before any permitted retry.

Check recipient-bank crediting.

A completed processing step may still need destination-bank reconciliation.

1. Confirm the bank account, beneficiary and payout currency used.
2. Ask the recipient bank to check against the payment reference.
3. Keep the Ostro reference and the bank’s response.

Report incorrect destination details promptly.

A payout already submitted may not be cancellable.

1. Keep the payout reference and the destination actually used.
2. Explain which information is incorrect without sending account secrets.
3. Avoid another payout until the original outcome is clear.

Check the stage before checking the blockchain.

Without a transaction hash, a transfer may still be queued, under review or awaiting release.

1. Check the current payment or withdrawal status.
2. Confirm the selected asset, network and verified destination.
3. Use the reference window for the enabled route.

Compare the asset, network and destination.

A blockchain confirmation and a wallet or exchange credit are separate things.

1. Keep the transaction hash and actual network used.
2. Compare the destination and asset with the original instructions.
3. Check whether the destination provider shows pending credit or requires additional processing.

Stop further transfers and preserve the hash.

An unsupported network, asset or address may cause permanent loss.

1. Record the transaction hash, asset, network and destination.
2. Keep the sending provider’s withdrawal reference if available.
3. Never send more funds or disclose wallet secrets to someone promising recovery.

Separate approval from issuance.

Approved account details can still be waiting for partner setup or currency issuance.

1. Check for any outstanding account or partner request.
2. Note whether USD or another requested currency is missing.
3. Record the exact status and approximate approval time.

Check what the review still needs.

Submission is the start of review, not approval to use payment services.

1. Check for a request to correct or resubmit information.
2. Use the secure verification route instructed for your account.
3. Keep identity documents out of an initial support email.

Check the inbox and use the latest link.

An email delivery issue and an expired link need different checks.

1. Check the signup email address, spam and workplace quarantine.
2. Use the newest confirmation or password-reset message.
3. Pause repeated resend attempts if a request limit appears.

Check the entry and device time.

A valid authenticator entry can still show a code that fails if device time is incorrect.

1. Select the entry for the correct Ostro account.
2. Enable automatic date and time on the device.
3. Use a fresh code once and follow any retry limit.

Use verified account recovery.

Losing an authenticator requires a separate identity-checked recovery process.

1. Contact Ostro from your registered email where possible.
2. Explain that you lost the authenticator, without sending a password.
3. Follow the verification instructions for any administrator-assisted reset.

Pause repeated attempts.

A 429 limit may apply to more than your IP address.

1. Close duplicate tabs repeating the action.
2. Follow any retry time shown by the app.
3. Make one attempt after that period rather than cycling VPNs or automating retries.

Check the official sign-in route.

Use your registered email and the current password for that account.

1. Open app.tryostro.com/login directly.
2. Use password recovery if needed, rather than guessing repeatedly.
3. Complete the authenticator challenge if your account requires it.