Start with the work the card needs to do
A useful virtual card fits a real payment workflow. Before comparing providers, write down the platforms you pay, their billing countries and currencies, the expected charge sizes and the people responsible for keeping them funded. That gives you something concrete to evaluate beyond an attractive dashboard or a long feature list.
Check the actual card classification and permitted use. For example, Google’s payment-method guidance excludes prepaid cards from postpay. “Virtual” describes the format, so ask the provider which requirements its specific program supports. A network logo or a broad compatibility claim should lead to a more specific question, not end the evaluation.
If an approval-rate statistic matters to your decision, ask which platforms, time period and transactions it covers. A number without context does not tell you what to expect from your own payment setting. Use measured results as evidence to examine rather than a guarantee of future charges.
Compare usable balance, not headline fees
Choose a representative funding amount and calculate what would reach a newly issued card, then repeat for an existing card. Include the applicable deposit, conversion, creation and loading costs. Record which charges are fixed, which are percentages and where each percentage is applied. This keeps one-off setup costs distinct from the cost of ongoing use.
Separately check charges that depend on events: declined attempts, currency conversion, refunds, inactivity or returning a balance. Ask which apply to the specific program you are considering. The objective is a comparable calculation, not an assumption that every provider charges for every event. Note any unanswered item before committing funds.
Understand the authentication workflow
Find out how the authorized cardholder completes payment authentication and where a request appears. As EMVCo explains, 3-D Secure can authenticate a transaction without an additional customer step (the frictionless flow) or require a challenge, such as a one-time code or an app approval. Card programmes handle this differently: some deliver codes by SMS or app, and some, Azura among them, confirm 3-D Secure automatically on the issuer side so that no code is ever sent. Know which one you have before a campaign depends on it; a code that goes to a phone nobody on the team holds is a declined payment waiting to happen.
Also ask how you access transaction descriptions. Some platform checks use a small temporary charge with a verification code in its record; Google describes this in its payment verification guidance. That is a different task from completing 3DS. Make sure the person responsible can identify which request they are handling.
Ask what each control actually does
A label such as “budget” can describe an allocated balance, a spending limit or an alert. Ask what happens when the value is reached. For a freeze action, ask what changes immediately, whether it can be reversed and how it differs from a restriction imposed by the provider. Precise behavior matters more than the number of controls on a screen.
If you need merchant restrictions, separate user access, exports, bulk issuance or an API, verify that they exist in the product available to you. Request a demonstration of the workflow you actually need. A feature on a roadmap should not become a dependency in this week’s campaign plan.
Read the rules for when things change
Ask how to investigate a declined payment, where a restriction reason appears and which support channel handles it. Then follow the balance: what happens if you close a card, receive a merchant refund or need to move funds elsewhere? Establish the conditions and costs before buying, rather than assuming every balance can be moved or withdrawn in the same way.
A shortlist you can use
- The specific card type fits the intended merchant and payment setting.
- The funding calculation shows the usable balance after applicable costs.
- Authentication and transaction records are accessible to the right person.
- The required controls and workflows are available today.
- Decline, restriction, closure and remaining-balance rules are clear.
Sources & further reading
Azura product details and getting started.
Read the FAQ