Conclusion in a Nutshell
Dotva is not a card issuance website for individual users, but rather an API platform for issuing virtual cards that is designed for developers and businesses. If your team needs to integrate the entire process of ”card issuance, top-up, and management” into your own system, Dotva’s server-to-server API design is worth serious consideration; if you simply want to issue a card for your own subscription use, it is not the right choice for you. API Documentation:https://dotva.io/api/v1/docsThe
Platform Overview
Dotva provides a complete set of APIs for virtual card issuance. The API documentation complies with the OpenAPI 3.1 specification and is hosted at /api/v1/docs. The platform operates on a workspace model, offering subscriptions to developers and serving B2B clients—such as cross-border e-commerce teams, advertising agencies, and fintech companies—that require bulk, automated card issuance.
Unlike typical virtual card platforms, Dotva’s default interaction method isn’t simply clicking a few times on a web page to issue a card; instead, all operations—including card issuance, card inquiry, top-up, freezing, unfreezing, and card deactivation—are performed via API calls, with card details delivered asynchronously via webhooks. The entire process can be fully automated, making it ideal for teams looking to integrate card issuance capabilities into their own systems.
The value of the OpenAPI 3.1 specification lies in the fact that developers can use standard toolchains to automatically generate client-side code, perform API testing, and browse documentation—all at a much lower integration cost than that of legacy APIs that rely solely on a single PDF document. For an API-first platform, the quality of documentation is an integral part of the product’s value, and Dotva’s investment in this area is clearly evident.
Card Products and Fees
Taking the card product described in the platform documentation as an example: BIN 441357, U.S. card, USD currency, virtual card, with the product code 1-441357-usd-virtual. The fee structure is as follows:
- Activation fee: $3.00 (fixed); no hidden monthly fees
- Recharge Fee: Fixed 0 + 3% (percentage)
- Minimum Initial Top-Up: 1TP, 4T, 10
- Minimum Top-Up: $1
This fee structure is considered average among API card-issuing platforms. The card issuance fee is fixed at $3, making costs manageable in bulk card issuance scenarios; however, the 3% top-up fee requires evaluating the overall cost in relation to your business transaction volume. Teams with high transaction volumes may want to assess whether there are more optimal solutions or optimize their top-up frequency to ”low-frequency, high-value” transactions to spread out the costs.
Please note that the card product examples shown here illustrate configurations for a single BIN; the actual range of available card products is subject to the product list provided after the platform is activated. Teams planning bulk purchases are advised to contact the platform directly to confirm pricing and credit limit policies.
A Detailed Overview of API Capabilities
Dotva's API covers the entire lifecycle of virtual card services:
- Card Issuance: Create virtual cards via the API; supports custom cardholder names and billing addresses
- Card: View card details, balance, and transaction history
- Top-up: Top up cards; batch operations are supported
- Freeze/Unfreeze: Quickly freeze the card in case of an anomaly; unfreeze it once the risk has been resolved.
- Level: Close Cards You No Longer Use
- Orders and Wallets: Manage Card Issuance Orders and Platform Wallet Balances
- Transaction History: View all transaction records for easy reconciliation
For development teams, the most critical capability is the ability to ”customize the cardholder’s name and billing address”—many cross-border e-commerce and advertising scenarios require that card information match business records. Direct support at the API level eliminates the need for manual card information updates and means that the entire card issuance process can be dynamically generated according to business needs, rather than relying on manual operations for each card.
Bulk processing capabilities are another key consideration: Clients such as advertising agencies often need dozens or even hundreds of cards at a time. The core value of an API platform is that it allows such bulk operations to be handled with just a few lines of code; combined with order and wallet APIs, this also enables automated financial reconciliation.
Safety Design
Encrypted Card Secret Delivery via Webhook: This is a distinctive feature of Dotva’s design. After a new card is created, sensitive information such as the card number and CVV is not returned directly; instead, it is delivered in an encrypted format via the `card.issued.secrets` webhook. Since sensitive card credentials do not appear in standard API responses or logs, this reduces the risk of data leaks and makes it easier for developers to securely integrate the credentials into their own key management systems. For fintech teams, this design ensures that the flow of card credentials is controllable and auditable.
Idempotent Key Mechanism: The API supports the X-Idempotency-Key header with a 24-hour retry window. Retrying the same request after a network timeout will not result in duplicate charges or duplicate card issuances. This is a critical requirement for automated systems and a key indicator of an API platform’s maturity. APIs without idempotent keys are prone to incidents of duplicate card issuance in high-concurrency retry scenarios.
Rate-Limiting Protection: The API implements a 429 rate-limiting mechanism and returns a `Retry-After` header; clients can back off and retry as indicated. The well-designed rate-limiting mechanism demonstrates that the platform has carefully considered the stability of the production environment, rather than simply and indiscriminately rejecting requests. When integrating the API, it is recommended to implement rate-limiting backoff logic within the SDK or at the client layer to prevent blind retries from exacerbating issues after being throttled.
Integration Process
For developers, the typical process for integrating with Dotva is as follows: First, review the OpenAPI 3.1 documentation to verify the API capabilities and parameters; apply for a workspace and obtain API credentials; test the core workflows—such as card issuance, top-ups, and card balance inquiries—in a sandbox or test environment; configure webhooks to receive card PINs; and finally, roll out the integration to the production environment in a phased manner. The entire process is not complicated for teams with some backend experience; the main challenge lies in integrating the security design components.
It’s important to note that virtual card services involve financial transactions. When integrating them, be sure to handle the basics properly—such as securing transaction records, verifying webhook signatures, and implementing idempotent retries—rather than focusing solely on the number of APIs.
Analysis of Pros and Cons
Advantages:
- API-first design, OpenAPI 3.1 documentation, low integration costs
- Supports custom cardholder names and billing addresses to accommodate various business scenarios
- Key codes are delivered via encrypted webhooks, with a professional focus on security design
- Idempotent keys with rate-limiting mechanisms—a testament to solid API engineering practices
- Covers the entire lifecycle from card issuance to account closure
Disadvantages:
- Intended for B2B developers; individual users cannot use it directly.
- The 3% recharge rate isn't very favorable for high-frequency, large-volume transactions.
- The platform has limited visibility, with few publicly available case studies and community discussions.
- The actual range of available card products will be confirmed after activation.
Fits the crowd
Cross-border e-commerce teams: Need to issue cards in bulk to support the operation of stores across multiple platforms, and use APIs to integrate the card issuance process into their own order systems; Advertising Agencies: Need to provide stable payment cards for a large number of ad accounts; bulk card issuance and automated reconciliation are essential requirements; Fintech Teams: Need to integrate virtual card capabilities into their own products; encrypted delivery via webhooks and idempotent design perfectly meet compliance requirements; Automation Developers: Seek a fully automated, unattended card issuance system.
Not suitable for individual users: The platform does not offer a web-based, user-friendly card issuance process. For individual subscription scenarios, a standard virtual card platform is more suitable; there’s no need to pay for API capabilities.
Frequently Asked Questions
Q: Can individual developers use Dotva? A: Technically, yes. The platform operates on a workspace model, and individual developers can also apply; however, the product’s default interaction is via API, and there is no web-based sign-up process for general users. It is therefore better suited for individuals or teams with backend development capabilities.
Q: What should I do if I don’t receive the card code delivered via webhook? A: This is the most critical point to note during integration. We recommend configuring webhook retries and monitoring alerts, while also confirming whether the platform offers a fallback solution for reissuing or retrieving card codes to prevent the card code from becoming unusable due to a lost callback.
Q: If a top-up fails, will the payment be charged again? A: Dotva supports the X-Idempotency-Key. Within the 24-hour replay window, repeated requests for the same operation will not be processed again. We strongly recommend using this mechanism during integration.
Q: What types of transactions does the card support? A: Taking the USD virtual card with a U.S. BIN as an example, it supports standard online subscriptions, e-commerce, and advertising purchases. The specific scope of use is subject to the actual payment results after the card is issued; transactions at high-risk merchants may still be declined.
Official Website Link
API Documentation:https://dotva.io/api/v1/docs; Official Website:https://dotva.ioThe
We recommend that developers first read the OpenAPI 3.1 documentation to assess the API’s capabilities before applying for a workspace to conduct integration testing. Overall, Dotva is a developer-oriented platform that prioritizes API quality over marketing hype, making it ideal for teams willing to handle the integration process themselves.
English 
Chinese