Receive via Wire

Share your account's wire coordinates so a payer can send a wire transfer into your Passport Account.

Receive via Wire is how you get paid by wire: you share your Passport Account's wire routable details with a payer, and they send a wire from their bank. The funds arrive as an External Credit and post to your account once matched or reviewed. Use wire for high-value or same-day inbound transfers where finality matters.

Common uses: capital contributions, real-estate or settlement funding, and large B2B payments coming into your account.

Before you share details

  • The receiving Passport Account exists and is ACTIVE. Routable details may be generated earlier, but funds only apply once the account is ACTIVE — see Account Lifecycle.
  • Your webhook endpoint is subscribed to external-transaction events.

The details you share

Read your account's routable details from the GET /v1/customer/id/{id}/account/id/{id} response, under the routableAccount object, and share the wire fields with the payer:

FieldShare for wireDescription
wireAccountNumberAccount number for wire transfers
wireRoutingNumberRouting number for wire transfers
wireMemoOptionalReference the sender includes on the wire for reconciliation

Wire and ACH details are different

Wire uses wireAccountNumber + wireRoutingNumber. The ACH fields (accountNumber, routingNumber) are for Receive via ACH — sending a wire to the ACH details will not route correctly.


How it works

You share details, the payer wires the funds, and PCE records the inbound wire credit for matching and review.

sequenceDiagram
    participant You as Your application
    participant PCE as PCE
    participant Payer as Payer's bank

    You->>PCE: GET account → read routableAccount (wire fields)
    You->>Payer: Share wireAccountNumber + wireRoutingNumber (+ wireMemo)
    Payer->>PCE: Wire arrives on your routable details
    PCE->>PCE: Record External Credit (wire), attempt matching
    alt Matched
        PCE->>PCE: Post funds to your account
        PCE-->>You: Webhook — credit posted
    else Needs correction
        PCE-->>You: Webhook — credit in review
        Note over PCE: Update wire details, then accept (wires can't be rejected)
    end

Wire credits can't be rejected

An inbound wire that can't be matched is corrected and accepted, not rejected through the standard workflow. For a wire received in error or needing compliance handling, follow your program's operational escalation process. See External Credits — Wire Credit.


Scenarios

Scenario 1: Receive a capital contribution (matched)

An investor wires a capital contribution to your operating account. You shared the correct wireAccountNumber, wireRoutingNumber, and wireMemo, so PCE matches the inbound wire and posts it to the account.

You'll also need: the receiving account ACTIVE, and the sender using the exact wire routable details you provided.

Scenario 2: Receive a wire that needs an account correction

A client wires funds but the details don't resolve to a single account, so the credit waits in review. You update the wire with the correct destination account and accept it. See External Credits for the update-then-accept calls.


After the wire arrives

Inbound wire credits are handled as External Credits — that page owns matching, update/accept, and the lifecycle. Track them by webhook (production) or by listing/retrieving External Credits (reconciliation fallback), and don't show funds as available until the credit posts.

Inbound wires emit the external-transaction wire events externaltransaction.wire.create on arrival and externaltransaction.wire.update on each change. For the full catalog, see Webhook Event Types; for the shared status model, see Transaction lifecycle.


Best practices

PracticeDescription
Share only the wire fieldsGive the payer wireAccountNumber + wireRoutingNumber, not the ACH fields
Provide wireMemo exactlyA consistent reference speeds matching and reconciliation
Confirm the account is ACTIVE firstFunds only apply to an ACTIVE account
Plan for update-then-acceptWire credits can't be rejected; corrections are made by update + accept
Don't release funds earlyTreat funds as available only after the credit posts

Related

See also


Did this page help you?
.readme-logo { display: none !important; }