Glossary

A scheduled pull of funds from a client's linked bank account over the ACH network, initiated with Add Client Funds. Drafted funds are pending (PUSD) for ~2 business days before becoming tradable. A failed draft appears in the Returns Report.

Anti-money-laundering review Reliant performs on digital asset wallet addresses before they can send or receive funds, part of registering an address via Add Wallet Address (see whitelisting).

See short-term token.

A named disbursement configuration: a permutation of payout rails (ACH bank transfer, prepaid card, check by mail, real-time payment, Venmo, PayPal, international transfer) and the per-rail consumer fee (percentage and flat) on each. Payees added to a campaign choose from exactly these methods. Campaigns are created and updated by Reliant administrators (read-only via the API) and read with Get Campaign; each is identified by its campaignGuid.

GUID identifying a disbursement campaign, returned by Get Campaign and used as the target when provisioning payees with Add Consumers.

A tokenized card identifier (never a raw PAN) representing a stored card, retrieved via Get Card on File. Used by Pull from Card and Push to Card; raw card numbers never reach your application.

An end user (consumer or business) onboarded onto RAMFi under your program: the owner of balances, linked accounts, cards, and transactions. Created with Create Client.

Your unique external identifier for a client, supplied when calling Create Client and passed on nearly every subsequent call. Distinct from RAMFi's internal id.

In Disbursements, a person being paid through a campaign. Added with Add Consumers (name, email, amount, eligible rails); listed with Get Consumers and edited with Update Consumer. Reliant emails them a link to pick their payout method. Lifecycle: Invited → MethodSelected → Paid (or Failed).

The fee a payee bears for a given payout rail, set per method on the campaign. The payee receives amount − consumerFee; fees are disclosed on the selection page.

Exchanging one supported currency for another (e.g. USD → USDC) at the market rate at time of conversion, via Convert Client Funds.

Enum of supported currencies: USD, PUSD, BTC, ETH, XRP, USDC, SOL, DOGE, PYUSD, BTCC, LINK, XLM, AVAX, SHIB, USDT. See Data Models.

The payout surface: you provide a payee's name and amount; Reliant emails them a secure link to choose how to get paid from the campaign's rails. See the Disbursements section of the API Reference.

Numeric identifier of an uploaded client document, returned by Add Document and used with Get Document Status.

The standard response wrapper { isSuccess, result, errorMessage }. Inspect isSuccess before consuming result; on failure, errorMessage explains why. Batch endpoints return per-item results in request order.

Your unique reference attached to a money movement (draft, conversion, withdrawal, card pull). Make it unique per transaction and store it, it is your reconciliation key against Transactions and the Client Ledger.

An accountStatus indicating the client is blocked from transacting, typically set after a returned draft. Resolve the underlying issue, then set the client back to Active with Update Client.

Risk assessment of a digital asset wallet address. Runs automatically as part of whitelisting when an address is registered via Add Wallet Address.

Identity verification Reliant runs when a client is created. A client whose KYC passes carries accountStatus: Active and can transact.

A client's bank account connected through the Bank Connection SDK (open banking). Enables ACH funding and the Linked Account Intelligence endpoints (balance, history, validation). Credentials stay with the provider, your app only sees the link.

Your program's long-lived credential, issued by Reliant. Used only to provision short-term tokens via Provision Token, never on regular calls. Keep it server-side.

Original Credit Transaction: a push-to-card payout rail that lands funds on a payee's debit card, typically in minutes. One of the eight Disbursement rails; also the mechanism behind Push to Card.

The live RAMFi environment where real money moves. Access is granted after contracting and compliance approval, see the onboarding journey.

Pending USD, funds drafted from a bank that have not yet cleared. PUSD appears in balances as non-tradable and converts to USD after ~2 business days.

The payment networks available for moving money: ACH, card (pull/push), check, prepaid card, OCT, PayPal, Venmo, cross-border, and digital asset. Disbursement campaigns are permutations of rails plus consumer fees.

ACH drafts that failed after initiation (e.g. NSF, closed account). Poll the Returns Report; a returned draft places the client on Hold.

The simulated environment where you build and verify your integration with test credentials before production; its base URL (https://FQDN/) and API version are provided during onboarding. Requested through your Reliant integration specialist.

The bearer token your server uses on API calls, obtained from Provision Token using the Main Token. Short-lived; refresh as it expires and pair every call with X-OTP.

The shared secret from which X-OTP values are generated (RFC 6238 time-based one-time passwords). Issued alongside your Main Token; keep it server-side.

Registering and AML-screening a digital asset wallet address with Add Wallet Address before it may send funds to or receive funds from RAMFi. Sends to non-whitelisted addresses fail.

Header carrying the current time-based one-time password, required on every authenticated call alongside the bearer token. Generate it from your TOTP seed, the API Reference includes a working generator.