Section 01 · Corridors
/remit is a corridor on rails, not a wire on a screen.
Remittance is settle, not forwarding. A dollar routed through an outdated SWIFT chain can pass through four intermediaries, sit in correspondent nostros, and arrive three business days later at a downstream rate that bears no resemblance to the rate quoted at the payer's window. POINTS /remit treats the corridor as a first-class product surface: a verified payer, a vetted partner rail, an operator-trust grade on every receiving agent, and a settled balance that lands seconds after the haptic confirms the tap.
Corridors are opened the way POINTS opens every regulated surface — by sponsorship, not by signing up. A sponsor-operator passes KYB and CIP at the partner bank; a per-corridor partner rail is onboarded against BSA / AML and OFAC sanctioning; an operator-trust grade is computed from the same five-factor composite used for issuance. Only after that does a participating /remit corridor come online, and only then does the rate card lock in at issuance, not at the moment of the wire.
Section 02 · Markets
The participating markets and corridor categories.
/remit corridors open by category, not by ad-hoc route. Each category sits behind its own underwriting gate, its own vetting list, and its own rate card at issuance — so a fee schedule that's quoted today is a fee schedule that's delivered in the settlement window, with no surprise FX markup, no compounding correspondent margin, and no behind-the-screen wire reroute.
Operator-grade payout corridors.
A category reserved for sponsor-operators underwriting an AI-agent fleet. Settlement legs are routed through Unit-issued deposit accounts at the partner bank and posted as a same-rail ACH ledger entry on the same wrap the rest of POINTS settles on. The receiving side mirrors the issuance shape: a vetted payout partner, a per-transaction cap, an activity ceiling, and a hash-pinned audit row per /remit movement.
SME contractor payouts on regulated rails.
A corridor category for SMBs paying AI contractors across borders, with a disclosed POINTS-priced fee, a window-and-bucket settlement window keyed to ACH cutoff, and real- time RTP where the receiving bank supports it. The /remit path here closes the audit loop the same way /business does on the domestic side: per-tx caps, agent-branded cards, and a hair-cut-stable ledger unit for every payout.
Consumer remittance for verified human senders.
A corridor category for verified human senders sending into the same receiving markets, with the same KYB / KYC posture that gates every POINTS surface. Consumer /remit carries the POINTS-priced fee schedule, never a chained-intermediary margin, and routes through the same partner rails that grade the SME /remit side — no offshore reroute, no correspondent nest.
Section 03 · Fee schedule
Priced in POINTS. 1 POINT = 1 cent. Quoted once at issuance.
Every /remit fee schedule ships in POINTS — the same in-app unit used across /pricing, /billpay, and the agent-platform rail. One POINT equals one cent of USD; the rate card at onboarding is the rate card that lands in the haptic-tap box, with no late-binding FX, no surprise correspondent markup, and no “from” rate that quietly compounds upstream. The /remit corridor is a published POINTS-priced fee applied line-by-line, the same way /billpay writes fee schedules onto the rate card.
Per-corridor POINTS base fee.
Each /remit corridor carries a flat per-transaction fee expressed in POINTS, set at issuance and disclosed per corridor. The base fee covers the regulated-wrap cost of CIP, partner-rail onboarding, and settlement-window management at the partner bank; it is the same rate a regulated partner would surface the operator.
Per corridor POINTS FX spread.
The FX leg is priced as a per-corridor POINTS spread, not a chained “from” rate that re-marks upstream. The spread is locked at the moment the corridor opens, printed on the rate card at issuance, and held flat through the same settlement window as the base fee. No “rate moves by 0.3%” at the wire.
Per-settlement POINTS flat.
Settlement closes on the published ACH / RTP / card rail of the partner, against the receiving bank. The settlement leg carries a small POINTS flat — the same per- settlement flat used across /billpay and /pricing — to cover the receiving- bank cutoff and the partner-bank core processor against which the corridor clears.
No compounding. No correspondent margin. No surprise FX.
The total fee is printed at the moment of issuance and locked through the settlement window. No combined fee, no "rate plus processor plus card" markup, no chained-intermediary margin. POINTS does not move money on this surface and does not route through offshore workarounds; the fee card is the same at the payer's tablet as at the receiving bank's Nostro.
Section 04 · Settlement
Near-instant in corridor, settled within a window.
The /remit settlement leg runs on the partner rail of the receiving corridor — ACH for standard settlement, RTP / FedNow where the receiving bank supports it, and per-corridor card-network rails for time-sensitive operator payouts. Settlement timing is a corridor-by-corridor published window; the same rate card that prints the fee prints the window, and the same audit row that hash-pins the fee hash-pins the time-to-land.
Same-rail ACH settlement.
Standard /remit corridors settle on the partner rail's ACH cutoff, with the receiving bank providing the cutoff window. The published "settles within” line on the corridor card covers the time-to-land for the receiving bank's country, not the time-to-send for the payer's country; POINTS never quietly routes an /remit movement over an offshore rail to extend the visible window.
RTP / instant settlement where supported.
Receivers in RTP / FedNow-participating corridors settle on a per-second rail, with the receiving bank posting the balance inside minutes and POINTS posting the audit row at the same instant. POINTS does not silently upgrade a "settles within" window to a non-published cutoff and does not selectively route a /remit movement to a third-party correspondent to disguise the timeline.
Card-network rails for operator payouts.
The operator-side /remit corridor — the one POINTS /business and /send reference — uses the same per-corridor card rail the agent-branded card surfaces on, with a per-tx cap, an operator-trust underwriting look-up, and a hash-pinned audit row for every movement. The /remit closure here carries the same three-leg audit posture as the rest of POINTS: a regulated-wrap rails row, a settlement leg, and a time-to-land row, all hash-pinned.
Audit trail and dispute window.
Every /remit movement prints a hash-pinned audit row within seconds of settlement — sender, recipient, corridor, fee schedule, time-to-land. Operators can open a dispute case from the console up to the same published window after settlement, and the dispute is replayable against the original /remit audit row, never against a re- generated manifest built under cover.
Section 05 · Operator-trust gate
The corridor gate, and the access window for it.
/remit is not a self-serve free-for-all. The corridor gate is a sponsor-gated issuance: the operator that wants to route a $remit leg must pass KYB and CIP at the partner bank, must underwrite the receiving corridor category, and must hold a five-factor composite at or above the corridor's published trust floor before any /remit movement locks in. /remit is rate-limited per operator — the surfaced cap is the rate-limit and the corridor trust floor is the underwriting signal, both written into the corridor card at issuance, not extra-late-delivered when the wire is in flight.
KYB / CIP at the partner bank.
Each sponsor-operator completes KYB and CIP before any /remit corridor opens. The partner bank performs the verification: beneficial owners, EIN, address, and the OFAC SDN screening that runs continuously thereafter. POINTS does the application layer. The bank does the regulated posture.
Five-factor trust composite, corridor-trust floored.
The five-factor composite — self-sustainability, income production, assets, repayment ability, and income expansion with credit — runs continuously against the operator that seeks to use /remit. Each corridor publishes a trust floor; the operator's composite must meet it for the rate card to lock, and must stay above it for the rate card to stay locked. A floor breach re-tightens the corridor and prompts a re-issue on the next /remit movement, never a fee re-mark.
Request corridor access.
/remit corridor issuance sits behind a sponsor-review window. The fastest path to a corridor is the /business intake queue: drop an email, scope which corridor category fits the operator, and walk through the issuance window. For operators that want to mint against the receiving side first, the /agents/signup form opens the operator mint flow on the same regulated wrap. The /remit corridor card is published at issuance, the fee schedule is printed at the onboarding call, and the rate card is the one POINTS applies — not the illustrative figures on this page.