GuidesRecipesAPI ReferenceChangelog
Guides
  1. B2B Payments App

Contacts

Overview

A Contact is a person or business you can send money to. The Contacts feature stores
identity details, payment methods (bank accounts and stablecoin wallets), and verification status.
A Contact must reach Verified status and have at least one payment method before you can send a
payment. Reach the feature from Sidebar → Send.

Available actions

  • Add a Contact — Individual or Business — through a three-step form (Contact Info → Address →
    Payment Methods).
  • Add payment methods to an existing Contact — bank accounts or stablecoin wallets, multiple
    per Contact.
  • View a Contact's details, including all payment methods and current verification status.
  • Search Contacts by name.
  • Remove a payment method from a Contact.
  • Start a payment from a Contact's row using the Send Payment action.

The Contacts list displays Name, Type (Individual or Business), Status, and Actions.

Add a Contact

Prerequisites

  • The Contact's Type: Individual or Business
  • For an Individual: First Name, Middle Name (optional), Last Name
  • For a Business: Business Name, optional Alias ("doing business as" name)
  • A real, deliverable physical address: Street Address, Street Address 2 (optional), City, State or
    Province, Postal Code, Country
  • At least one payment method (bank account or stablecoin wallet — see below)
  • For some corridors, extra fields:
    • Colombia (COP) — Email Address, plus a Passport or Cédula de Ciudadanía (individual) or NIT
      (business)
    • Dominican Republic (DOP) — a Cédula (individual) or RNC (business)

See B2B App Payout Corridors for
the full list of corridor-specific requirements.

Notes

  • Contact name and address cannot be edited after creation. Add a new Contact with corrected
    details to fix a mistake.
  • Names must match official ID. Verification compares against records — a typo or a nickname
    will fail verification.
  • The address must be a real physical address. PO boxes are not accepted in most regions.

Add a payment method

A payment method is the destination money goes to on a Contact: a bank account or a stablecoin
wallet. Add a payment method during Contact creation (Step 3 of the form) or later on an existing
Verified Contact.

Bank account requirements

  • Currency — the currency the account holds (USD, CAD, MXN, COP, DOP)
  • Payment Rail — the bank network. Depends on currency. See
    B2B App Payout Corridors
  • Nickname — a friendly label, for example "Primary Checking"
  • Account Number — typically 8–12 digits. Not used for MXN, where CLABE replaces it
  • Routing identifier — the field and format depend on the country:
    • US: 9-digit Routing Number (ABA)
    • Canada: 8-digit Transit & Institution
    • Mexico: 18-digit CLABE
    • Colombia: 3-digit PSE code
    • Dominican Republic: SWIFT/BIC
  • For PSE (Colombia) and LBTR (Dominican Republic): an Account Type — Checking or
    Savings

Stablecoin wallet requirements

  • Cryptocurrency — the stablecoin the wallet receives (USDC, USDT, etc.)
  • Nickname
  • Wallet Address — the blockchain address. Always copy and paste — never type
  • Tag / Memo — required only by certain networks. Leave blank when not requested

Notes

  • The Contact must reach Verified status before you can add a payment method later. The
    Add Payment Method action is unavailable while the Contact is Processing, Pending
    Verification, or Declined.
  • Wallet addresses are case-sensitive. Always copy and paste.
  • A wrong asset or wrong network results in lost funds. Confirm the Cryptocurrency matches
    the recipient's expectation and verify the blockchain network.
  • A Contact can hold multiple payment methods. Pick one when sending.
  • Payment method removal is permanent. A confirmation dialog warns before deletion.

Contact verification

Every new Contact and every new payment method goes through an automatic identity check. The check
runs in the background — no user action is required.

Verification statuses

StatusMeaning
ProcessingThe Contact is being saved. Brief — a few seconds
Pending VerificationThe Contact's identity is being checked. Under a minute in most cases
VerifiedAll clear. Payments can be sent to this Contact
DeclinedThe Contact did not pass verification

Notes

  • Most Contacts reach Verified within about a minute. Some take a few minutes. Refresh the
    page if the status appears unchanged.
  • Verification runs on a fixed schedule and cannot be accelerated.
  • A Contact in Pending Verification cannot receive payments. The Send Payment action is
    disabled until the Contact is Verified.
  • Declined Contacts cannot be edited. Add a new Contact with corrected details. Contact your
    administrator if a fresh Contact is also Declined.
  • Verification is per-Contact. Once Verified, the status persists — no re-verification on
    subsequent payments.

Related resources