The direction, destination and account boundary of each funding or withdrawal route.
Topic definitions
Definitions in this topic
32
Access path / scope
Also seen as direct card balance · via provider account · via connected wallet
The account or wallet through which a money-movement route is available, such as a direct card balance, provider account, or connected wallet. The route’s existence in one scope does not make it available everywhere.
Practical explanation
Why it matters
A provider-level deposit or withdrawal may not feed the card balance directly, and a wallet route may require a separate permission or conversion step.
How we treat it
cryptocard.guide names the reviewed account boundary for every route where possible. Provider-account, card-balance, and connected-wallet capabilities are never silently merged.
Automated Clearing House is a United States electronic bank-payment network. Product support can differ for incoming and outgoing transfers, while timing, limits, reversibility and account-ownership rules remain route-specific.
Practical explanation
Why it matters
An ACH label does not establish both deposit and payout support or guarantee the same processing conditions for every account and recipient.
How we treat it
cryptocard.guide displays ACH only for the reviewed direction, currency, account scope, and availability. It does not infer wire, card, or international transfer support.
Also seen as supported asset and network combinations
A structured pairing of each supported crypto asset with the blockchain networks and directions available for it. The map prevents a ticker from being treated as universally depositable, withdrawable, or spendable across every network.
Practical explanation
Why it matters
The same ticker can travel on several networks, but the provider may allow only selected combinations for receiving, sending, conversion, or card use.
How we treat it
cryptocard.guide keeps reviewed asset-network combinations direction-specific. A network listed elsewhere in a profile is not automatically attached to every asset or route.
Also seen as credits as USDC/soUSD/EURe · conversion on deposit
An inbound process where the value sent is exchanged or credited as a different asset or currency before reaching the usable balance. The original asset may therefore disappear from the account immediately after receipt.
Practical explanation
Why it matters
Automatic conversion can change price exposure, available networks, fees, and the balance used for card spending before the user makes a purchase.
How we treat it
cryptocard.guide identifies the reviewed source asset, credited asset or currency, conversion stage, and applicable provider cost. Unknown conversion pricing is not treated as free.
Also seen as balance bridge · conversion bridge · path to the spendable balance
The step between receiving or holding value and making it usable for card spending. It identifies the spendable balance, who controls it, and whether an asset swap or currency conversion happens before or during payment.
Practical explanation
Why it matters
Two cards can accept the same asset but use it differently. One may credit a card balance, another may convert it, and another may keep it in a connected wallet until authorization.
How we treat it
cryptocard.guide explains the approved path from incoming or held value to the balance used for payment. Provider conversion fees and spreads remain separate from external blockchain costs, and an unknown conversion step is not treated as free or frictionless.
Also seen as bank off-ramp · bank-account payout · fiat bank withdrawal
A bank payout or off-ramp is a specific outbound route that delivers fiat value to an external bank account, sometimes after conversion from a crypto or provider balance.
Practical explanation
Why it matters
A bank exit can make a card account more flexible, but it is not established by card spending or crypto withdrawal support and may have separate access rules.
How we treat it
cryptocard.guide treats this as a bank-destination subtype of payout. Currency, recipient, conversion, region, fee, limit and timing details stay attached to the approved route.
Also seen as direct card top-up · card-funded top-up
An inbound funding action initiated with another payment card or an in-app payment method. It usually credits a provider or card balance and can carry different fees, limits, reversibility, and eligibility from bank or crypto deposits.
Practical explanation
Why it matters
Top-up convenience can come with route-specific cost and chargeback rules, and the destination may be a provider account rather than a universally spendable card balance.
How we treat it
cryptocard.guide labels the approved top-up source and destination separately from bank and blockchain deposits. Missing top-up fees or limits are not assumed to be zero.
Also seen as stablecoin deposit · on-chain receive
An inbound transfer of a crypto asset to a supported wallet, provider account, or card-linked balance on a specified blockchain network. Receiving one asset-network pair does not establish support for others or for withdrawal.
Practical explanation
Why it matters
The destination balance and network determine whether the received asset becomes card-spendable, stays separate, or requires conversion before use.
How we treat it
cryptocard.guide publishes crypto deposits only from reviewed inbound route facts. Wallet spending permission is not relabelled as a deposit, and receive support never proves withdrawal.
Also seen as deposit · receive · inbound transfer · crypto deposit · bank deposit
An inbound movement that places value into a named account, wallet, or provider balance. A supported deposit proves only that receiving is possible on the stated asset, currency, and network—not that sending is supported.
Practical explanation
Why it matters
Direction and destination determine whether funds become card-spendable, remain in another account, or require conversion. Receiving on one network also does not establish support for another network.
How we treat it
cryptocard.guide records receive support by asset or currency, network, destination account, and direction. A connected-wallet spending permission is not called a crypto deposit, and receive-only support does not create an outbound capability.
Fedwire is a United States wire-transfer service, while wire transfer is a broader bank-payment label. A product may support one named wire route or use general wording, so currency, direction, timing, and fees need confirmation.
Practical explanation
Why it matters
Wire support can differ from ACH in cost, timing, recipient reach, and reversal behaviour, while vague provider wording may not identify the exact infrastructure.
How we treat it
cryptocard.guide preserves the provider’s reviewed route specificity and avoids converting generic wire wording into Fedwire support without evidence.
Also seen as bank transfer in · cash funding · fiat receive
An inbound transfer of fiat currency through bank or payment infrastructure into a specified account or provider balance. The received currency may remain fiat, be converted, or become usable only after additional account steps.
Practical explanation
Why it matters
Bank details can feed a provider balance rather than the card directly, and the route can differ by currency, country, ownership, and conversion behaviour.
How we treat it
cryptocard.guide ties each reviewed bank deposit to its currency, route, account scope, timing, fees, and eligibility. Bank support in one direction is not generalized.
Also seen as funding method · funding route · adding funds · fund the card
The broader process of making value available to a card. Funding may use a bank transfer, crypto deposit, provider-account move, payment-card top-up, or wallet permission; the destination and route must be stated.
Practical explanation
Why it matters
A provider can advertise broad asset support while allowing only a narrow subset to reach card spending. The funding method determines the account boundary, applicable costs, and preparation required before a purchase.
How we treat it
cryptocard.guide treats funding as a route-specific capability within money movement. Funding contributes to comparisons only when approved facts identify how value reaches the card-linked setup; wallet permissions are not relabelled as deposits.
Also seen as EUR IBAN · virtual IBAN · personal IBAN
An International Bank Account Number identifies a bank-account destination in participating regions. Having an IBAN does not by itself establish account ownership, supported directions, deposit protection, available currencies, or every bank-transfer service.
Practical explanation
Why it matters
Users can mistake an identifier for a complete bank account and assume payouts, third-party deposits, insurance, or personal ownership that has not been established.
How we treat it
cryptocard.guide shows the reviewed IBAN scope, provider, ownership, currencies, and direction where known. An IBAN label alone adds no inferred banking capability.
Direction describes whether a route brings value into a setup, sends value out, or supports both. Bidirectional support must be confirmed for each asset, currency, network, and account boundary rather than inferred from one side.
Practical explanation
Why it matters
A product may receive an asset without allowing it to leave through the same route. Direction prevents partial support from being mistaken for complete transfer capability.
How we treat it
cryptocard.guide records route direction explicitly and never turns inbound evidence into outbound support. Bidirectional status requires reviewed evidence for both sides of the route.
Also seen as provider transfer · username transfer · Tag transfer
A movement between balances or users inside the same provider system. It may be fast and avoid an external bank or blockchain route, but it remains subject to the provider’s account, currency, and access rules.
Practical explanation
Why it matters
An internal transfer can be useful inside one ecosystem while offering no route to an external wallet or bank, so its destination boundary must remain clear.
How we treat it
cryptocard.guide marks internal routes as provider-contained and does not present them as blockchain sends or bank payouts. Fees, limits, speed, and recipient scope remain route-specific.
Also seen as inbound · incoming funds · ways to fund or receive
The set of approved ways value can enter the account, wallet, or balance that supports card use. It can include bank transfers, crypto deposits, internal moves, or card top-ups, depending on the product.
Practical explanation
Why it matters
A card may accept value through several places without making every balance directly spendable. Knowing the exact destination prevents a broad funding claim from hiding conversion steps, route limits, or account requirements.
How we treat it
cryptocard.guide shows only approved inbound routes that reach the relevant card-linked setup. Each route keeps its own assets or currencies, destination, fees, timing, limits, availability, and evidence state; an asset name alone does not prove a working route.
Also seen as outbound · outgoing funds · ways to send, withdraw, or settle
The supported ways value leaves a card-linked setup, such as an on-chain send, bank payout, internal transfer, or balance withdrawal. Each route has its own destination, fees, limits, timing, and eligibility.
Practical explanation
Why it matters
Being able to spend by card does not prove that a user can move the remaining balance to a wallet or bank. Exit routes can materially change how practical an account is.
How we treat it
cryptocard.guide separates card spending, crypto sends, internal transfers, and fiat-facing payouts. An outbound capability appears only for its approved direction and destination, and unknown outbound support receives no positive treatment.
Also seen as external crypto send · blockchain withdrawal
A crypto movement recorded through a blockchain network between compatible addresses or contracts. The selected asset-network combination, confirmation process, wallet support, provider charges, and external network costs determine the practical route.
Practical explanation
Why it matters
Using the wrong network or assuming an inbound network is also available outbound can prevent value from reaching the intended address and introduce unexpected external costs.
How we treat it
cryptocard.guide records the reviewed asset, network, and direction separately. External gas or bridge costs remain outside card fees and scoring even when they affect the user’s transfer.
Also seen as own-name deposit · third-party deposit · recipient in user's name
A transfer rule describing whose legal name must appear on the sending or receiving account. Some routes accept only accounts owned by the user, while others allow approved third parties under separate checks.
Practical explanation
Why it matters
A route can exist yet reject transfers from an employer, exchange, family member, or business because the name or account ownership does not meet its rules.
How we treat it
cryptocard.guide attaches reviewed ownership rules to the exact inbound or outbound route. Unknown third-party support is not presented as allowed.
Also seen as bank payout · fiat payout · local payout · global payout · bank off-ramp
An outbound delivery of value through a bank, local-payment, or other fiat-facing route. A payout may require conversion and account eligibility, and it should not be assumed to be an on-chain crypto withdrawal.
Practical explanation
Why it matters
A payout can make a card account useful beyond purchases, but route coverage, recipient rules, conversion, fees, limits, and timing may vary by currency and region.
How we treat it
cryptocard.guide shows a payout only when approved facts identify a fiat-facing outbound route. Payout currencies, destination rules, route-specific fees, limits, timing, and availability stay attached to that route rather than being generalized across the product.
A shared receiving account used for multiple customers, where a reference, memo, or other identifier assigns incoming money to the correct user balance. Missing or incorrect routing information can delay or prevent credit.
Practical explanation
Why it matters
The user may not control a unique account number, and a transfer can fail operationally even when the currency and banking route are otherwise supported.
How we treat it
cryptocard.guide surfaces a reviewed memo or reference requirement with the receiving route. Shared infrastructure is not described as a personal bank account.
Also seen as money-movement rail · transfer rail · route · method · path
A specific mechanism used to move value, such as SEPA, ACH, an on-chain network, or an internal provider transfer. cryptocard.guide uses route in compact copy and rail when discussing the underlying infrastructure.
Practical explanation
Why it matters
Different routes under one product can have different destinations, coverage, fees, speed, limits, and account rules. Naming the route prevents one supported method from being generalized to all money movement.
How we treat it
cryptocard.guide introduces the concept in plain language as a money-movement route. Approved route facts remain direction-specific and carry their own scope; internal product shorthand such as rail signals is not suitable public copy.
Receive-only means approved evidence explicitly limits a route or asset-network pair to inbound transfers. If outbound evidence is merely absent, sending remains unknown rather than confirmed unsupported.
Practical explanation
Why it matters
Value may enter successfully but require conversion, card spending, or another provider route to leave, reducing flexibility and making exit assumptions unsafe.
How we treat it
cryptocard.guide uses Receive-only only for an explicit one-direction restriction. When evidence confirms inbound support but says nothing about outbound use, the outbound state remains unknown.
Also seen as fee components · limit scope · external cost scope
The exact route, asset, currency, region, amount, direction, or account to which a stated fee or limit applies. Scope prevents one route’s price or allowance from being generalized across the whole product.
Practical explanation
Why it matters
A low fee or generous limit can be real for one path while another route is more expensive, restricted, or still unknown.
How we treat it
cryptocard.guide attaches every reviewed fee and limit to its applicable route. External blockchain costs stay separate from provider charges and outside card scoring.
Also seen as send · withdraw · crypto withdrawal · outbound transfer · external send
An outbound movement from a wallet or account to an external destination. A crypto send normally targets a blockchain address; a withdrawal may instead reach a bank, card, or another provider balance.
Practical explanation
Why it matters
Providers may support card purchases without supporting a reusable exit route. The exact destination and network determine whether the user can regain wallet or bank access to the remaining value.
How we treat it
cryptocard.guide distinguishes on-chain sends from fiat withdrawals and internal moves. The public label names the destination where possible, and approved receive support is never used as evidence of withdrawal support.
The Single Euro Payments Area provides bank-transfer schemes for eligible euro payments. Standard and instant services are distinct route variants, and product support can differ by direction, account type, region, timing, and limits.
Practical explanation
Why it matters
A SEPA claim may cover only receiving, only payouts, or one service variant, so it should not imply universal two-way euro banking.
How we treat it
cryptocard.guide states the reviewed SEPA variant, direction, currency, and account scope. Standard SEPA is not labelled instant without supporting evidence.
Also seen as payment setup · card spending path · how spending works
The account, wallet, balance, and payment rules used when a card transaction occurs. It explains what the card draws from, whether conversion or borrowing happens, and what control the user keeps before payment.
Practical explanation
Why it matters
A familiar card format can sit on top of very different money flows. The setup reveals whether the user must preload, enable a wallet asset, maintain a provider balance, or borrow against collateral.
How we treat it
cryptocard.guide presents spending setup as a practical description, not a marketing category. Approved facts about the source balance, conversion, borrowing, and control boundary inform the relevant comparison and Funds control explanations.
Also seen as coverage · payout currencies · stablecoin set
Three separate coverage dimensions: the asset or fiat currency involved, the infrastructure carrying it, and the direction or route supported. A broad list in one dimension does not establish support in the others.
Practical explanation
Why it matters
A product can support many assets for holding, few networks for transfer, and a different set of currencies for bank payouts, producing very different practical coverage.
How we treat it
cryptocard.guide normalizes assets, fiat currencies, blockchain networks, and payout currencies separately. Coverage claims require reviewed route and direction context.
SWIFT is a global financial messaging network commonly used to coordinate cross-border bank payments. A SWIFT-labelled route can involve several institutions, currencies, conversion steps, timing windows, and intermediary or recipient charges.
Practical explanation
Why it matters
The provider’s stated fee may not cover every intermediary deduction or conversion, and supported destinations can be narrower than the global label suggests.
How we treat it
cryptocard.guide treats SWIFT as a route label, not a promise of worldwide availability or total-cost certainty. Reviewed direction, currency, fees, timing, and coverage remain visible.
Also seen as money transfer · money movement · internal transfer · external transfer
A general movement of value between balances, accounts, wallets, or recipients. The word alone does not reveal direction, destination, currency, network, custody boundary, or whether the movement is internal or external.
Practical explanation
Why it matters
A broad transfer claim can hide a closed provider-only move or a route available in only one direction. Users need the mechanism and destination before comparing usefulness.
How we treat it
cryptocard.guide qualifies transfers as internal, on-chain, bank, local-payment, or another approved route. Scenario comparisons use confirmed direction and practical route details rather than treating the word transfer as a complete capability.
Also seen as instant · same day · business days · network-dependent · variable
The expected time for a money-movement route or one of its stages to complete. Speed can depend on provider processing, banking days, blockchain confirmation, recipient systems, compliance checks, and when measurement begins.
Practical explanation
Why it matters
A route described as instant may cover only internal credit while settlement, withdrawal, or recipient availability takes longer, so the measured stage must be known.
How we treat it
cryptocard.guide keeps reviewed timing attached to the exact route and stage. Marketing speed for one transfer type is not generalized to deposits, payouts, or settlement.
Also seen as USD virtual account · local account details · virtual IBAN
Receiving details made available through a provider, often issued or operated by a banking or payments partner. They do not by themselves prove a personal bank account, deposit insurance or full banking access.
Practical explanation
Why it matters
Users may mistake receiving details for a conventional bank account and assume ownership, protection, withdrawal, or payment capabilities that the product does not provide.
How we treat it
cryptocard.guide describes the reviewed receiving scope and responsible provider, and adds a bank-account or protection caveat where needed. No extra banking capability is inferred.