Payments
Learn how to send, receive, and manage payments securely with BinaxPay. Understand timelines, limits, common statuses, and safe payment habits.
Individual (mock)
Individual · send payment (mock)
Send payment
Recipient
Amount
Route
Standard transfer
Timeline (sample)
Initiated
Request accepted • mock time
In review
Automated screening (illustrative)
Processing
Release toward destination
Completed
Status shown generically — not yours
Illustrative mock • not signed-in data • not a real screenshot
- Recipient picker, masked amount rails, and status timeline mimic in-app ergonomics.
- No payouts can be initiated from this Community illustration.
Overview
BinaxPay routes money through regulated partners. In the Individual app you choose a recipient, amount, and rail; behind the scenes risk and settlement checks may pause or release movement. This guide explains what you can reason about in public Community threads versus what only Support can confirm for your account.
Payment methods
Most journeys look like a bank-style transfer, card-funded send, or wallet-to-wallet move. The exact labels you see depend on region, verification tier, and counterparty type—always pick the flow inside the authenticated app rather than following steps from chat screenshots.
What each path is good for
Bank / ACH-style routes
Batch windows and cut-offs matter. Best for planned bills and larger amounts when you can wait for settlement.
Faster / instant-style rails
Higher velocity and stricter limits. Ideal for smaller urgent sends when the recipient bank supports the route.
Internal wallet moves
Reallocate between your own balances without exposing external account numbers in Community.
Payment timelines
Initiated
You confirm in-app; the payment is accepted for processing.
In review
Automated or manual checks may appear for risk, limits, or sanctions screening.
Released
Funds leave BinaxPay’s holding pattern toward the destination route.
Completed
The receiving institution acknowledges credit—timelines vary by rail and weekend/holiday windows.
Common payment statuses
| Status | What it usually means |
|---|---|
| Pending | Queued or waiting on a cut-off, counterparty bank, or internal review. |
| Processing | Actively moving through partners—may still be reversed if a risk flag trips. |
| Completed | Successful credit path for that payment leg; verify in your in-app history, not public posts. |
| Failed / returned | Destination rejected or data mismatch—Support helps with account-specific return codes. |
Limits and checks
Limits protect you from fraud and keep routes compliant. Rolling daily windows, per-recipient caps, and corridor rules can all apply at once—Community explains the vocabulary; exact numbers appear only after you sign in.
- Step-up verification can raise send ceilings without you posting documents publicly.
- New recipients may require a cooling-off period or smaller first send.
- Currency conversions add spread components—discuss concepts, not live quotes from statements.
Safe payment habits
- Confirm recipient nicknames in-app before scheduling large sends.
- Avoid sharing OTPs, CVVs, or full card numbers—even “partially hidden” screenshots leak metadata.
- Use official BinaxPay notifications to spot impersonation; never wire money because someone DMed you from “Support.”
- If a thread asks for “proof,” describe the situation narratively—don’t upload receipts with personal account data.
When to use Support
Open a Support conversation when you need confirmation tied to your ledger, a specific return code, a deadline that has passed beyond documented windows, or any request that would require sharing private documents.
Good reasons to escalate
- The app shows repeated failures after you’ve verified recipient details privately.
- You suspect unauthorized outgoing transfers or social engineering.
- A time-sensitive bill is at risk and public guidance can’t confirm your payment’s state.