ABcard Review 2026
Virtual cards for media buyers · BINs from 3 issuing GEOs · crypto and wire top-ups
The most useful thing we found is not on abcard.io at all. The marketing site publishes no prices: the only dollar figure anywhere on the four public pages is "$150 first deposit", and it sits in the HTML meta description rather than in visible copy, next to a second price claim, "free card issuance", which the dashboard's own "Card issuance fee" line quietly contradicts. The complete fee schedule does exist and is publicly readable, but it lives in a Notion document linked only from inside the logged-in app, absent from the sitemap and from every marketing page. Read it and the homepage promise, "No hidden fees. Flat commission. You pay only for a top up, everything else is free", stops holding: the same vendor's own schedule adds a per-decline fee that scales with your decline rate, a 2% FX fee on any currency mismatch, and five further per-BIN card fees whose values are served only to logged-in accounts. Two more lines matter before you deposit. The Terms state verbatim that ABcard "does not execute payment transactions and does not provide regulated payment or financial services", and no company registration number appears anywhere, only a Gibraltar street address inside those Terms.
By the numbers
Counted from the public site, its sitemap (12 URLs across ru, en and uk), the published Terms of Services and the vendor knowledge base at time of writing. Figures move; treat every number here as a snapshot.
What ABcard is, and what its own Terms say it is not
Everything in this table is the vendor's own published text, mostly recovered from the Terms of Services. The gaps are as informative as the entries.
| Item | Published position |
|---|---|
| Published address | Suite 16, Watergardens 5, Waterport Wharf, Gibraltar, GX11 1AA (inside the Terms only) |
| Company registration number | Not published anywhere on the site |
| Named directors or team | Not published |
| Governing law | England and Wales, exclusive jurisdiction |
| Terms effective date | March 20, 2026 |
| Regulatory status | Terms: ABcard does not execute payment transactions and does not provide regulated payment or financial services |
| Who issues the cards | Third-party PSPs, BIN sponsors and Bank Providers, never named |
| Issuing GEOs | United States, Hong Kong, Estonia |
| Email for official notices | support@anybill.io (a different domain from the brand) |
| KYC | Required at registration under clause 1.7; registration refusable at ABcard discretion |
| Restricted countries | Clause 8.2 restricts residents of certain countries; no list is published |
| Liability cap | The greater of the prior month fees paid or $5,000 |
| Unclaimed balances | Forfeited 2 years after account closure |
| Uptime warranty | Clause 10.1: access is as is, with no warranty that it will be continuous and uninterrupted |
Read the regulatory line carefully, because it defines what you are actually buying. ABcard is a front end over other people's issuing rails: it says so itself. Your balance is not held by a regulated institution that ABcard names, no safeguarding or e-money arrangement is disclosed, and liability is capped at the greater of last month's fees or $5,000. For a product that exists to hold working capital for ad spend, that cap is the number to weigh against your typical balance.
The price list that is not on the price page
There is no pricing page. The schedule below comes from the vendor knowledge base, which is public if you have the link but is reachable only from inside the app. Top-up commission is the headline number and it does fall meaningfully with turnover.
| Previous-month top-ups, all BIN accounts | USD BINs | EUR BINs |
|---|---|---|
| First month (default rate) | 4.5% | 4.5% |
| Previous month up to 25k | 4.5% | 4.5% |
| Previous month 25k to 100k | 3.5% | 4% |
| Previous month 100k and above | 2.5% | 3.5% |
Where each fee is actually published
This is the table we would want if we were the buyer. Five of the six per-BIN fee lines have no public value at all.
| Fee line | Where it is published | Value |
|---|---|---|
| Top-up commission | Notion knowledge base only | 2.5% to 4.5%, set by previous-month turnover |
| Decline fee | Notion knowledge base only | EUR 0 to EUR 0.80 per declined authorisation |
| FX fee | Notion knowledge base and dashboard | 2% when payment currency differs from card currency |
| Cashback (a credit, not a fee) | In-app tooltip on the BIN account screen | Where ABcard has enabled it on that BIN account: 1% on US, USD ad spend at Facebook, Google, TikTok |
| Card issuance fee | Dashboard label, value from the API | Not public |
| Monthly maintenance | Dashboard label, value from the API | Not public |
| Transaction fee | Dashboard label, value from the API | Not public |
| Transborder fee | Dashboard label, value from the API | Not public |
| Low-value transaction (under $50) | Dashboard label, value from the API | Not public |
| Prohibited transaction admin fee | Terms clause 8.3 | Up to GBP 300 |
| Wrong-account recovery fee | Terms clause 9 | GBP 100 |
The marketing copy and the fee schedule are written by the same company and do not agree. The homepage says "No hidden fees. Flat commission. You pay only for a top up, everything else is free". Their own schedule prices a per-decline fee, a 2% FX fee and five separate per-BIN card fees. The commission is also not flat: it moves between 2.5% and 4.5% depending on last month's volume.
This is not a small wording slip. A media buyer choosing between card providers on a "flat commission, nothing else" basis is choosing on a figure that does not describe the product. The fee schedule itself is reasonable and legible; the problem is that the honest version is the one you cannot see until after you have signed up.
The decline-rate ladder
This is the fee most likely to surprise you, because it is charged on failed authorisations rather than on spend, and it scales. Two schedules run in parallel depending on when the account was registered.
| Decline rate | Registered on or after 17.12.2024 | Registered before 17.12.2024 |
|---|---|---|
| Under 3% | EUR 0 | EUR 0 |
| 3% to 5% | EUR 0 | EUR 0.20 |
| 5% to 7% | EUR 0 | EUR 0.30 |
| 7% to 10% | EUR 0 | EUR 0.40 |
| 10% to 15% | EUR 0.50 | EUR 0.50 |
| 15% to 20% | EUR 0.60 | EUR 0.60 |
| 20% to 25% | EUR 0.70 | EUR 0.60 |
| Above 25% | EUR 0.80 | EUR 0.60 |
The two cohorts are shaped differently and it is worth knowing which you are in. Newer accounts ride free up to a 10% decline rate but are punished harder above it, topping out at EUR 0.80 per decline. Legacy accounts start paying at 3% but their ladder caps at EUR 0.60. If you run high-volume card testing against ad platforms, the newer schedule is more forgiving at the bottom and more expensive at the top.
Their own documentation cannot agree on how the rate is measured. The Russian section of the knowledge base says the decline rate is calculated over the previous 30 days. The English section of the same document says the previous 7 days. Those produce very different bills for the same activity, and we have no way to establish which window production actually applies. The same document also states the USDT to USD conversion as 0.99 in Russian and 0.9 in English, which on a $10,000 top-up is a $900 difference.
Ask support which window and which rate apply, in writing, before your first deposit. That is not a hypothetical caution: the whole ladder above hangs on the answer.
How the platform works
Two account types, fees per BIN account
Transit accounts hold and convert funds but cannot issue cards or spend. BIN accounts are the ones cards draw down from. Fees apply to each BIN account individually, so running several BINs multiplies the per-BIN fee lines rather than sharing them.
Bulk issuance and four limit types
The add-cards form issues to many team members in one submission, with a per-user card count and a per-user limit amount, so cards can be created in batches rather than one at a time. Limits can be set as total, monthly, weekly or daily. Card schemes mapped in the interface include Visa, Mastercard, American Express, China UnionPay, Discover and Diners Club International.
Crypto rails, plus wire in the app
The knowledge base lists USDT on TRC20, USDT on ERC20 and USDC on ERC20. Top-up requires pasting the transaction hash and amount, and the vendor states funds are credited in 3 to 4 minutes. The in-app top-up modal additionally exposes SWIFT and SEPA wire with EUR and USD, although the knowledge base top-up section covers crypto only.
Team roles and per-card 3DS routing
The dashboard covers Bank (BIN and transit accounts), Team, Wallet, News, profile settings and notifications. 3DS handling includes per-card email routing with a code-type enum covering 3DS, Meta Pay and Google, which is the practical detail that decides whether a buyer can confirm a payment without the account owner.
KYC at registration, 2FA at login
Terms clause 1.7 requires identity documents for individuals and legal-status documents for entities, and reserves the right to refuse registration at ABcard discretion. Login uses a numeric second factor with lockout after five wrong codes. Registration accepts an optional 16-character referral code.
Decline analytics exist, on their side
The operator panel carries a decline-rate risk suite: overview of pair risks, pair details, trend and risk clients, alongside tariff scales, service fee, crypto providers and allowed card links settings. It confirms decline rate is a first-class business metric here, which is consistent with charging you for it.
Supported platforms, and the ones that need permission first
Exhibit A of the Terms lists ten advertising platforms.
Google Ads, YouTube, Google Play, Twitter Ads and Twitter require prior manager approval. The knowledge base states that paying or linking cards to them without that approval causes instant and permanent account blocking. Google is the first name in their own supported-platforms exhibit, so this is a trap worth reading twice: the platform is supported, but using it unannounced is a terminal offence.
The published permanent-ban list
- Not paying advertising bills
- Thresholding without actual spend
- Reselling cards, or using cards to sell third-party products
- Using cards only for non-advertising payments such as Twitter Premium or YouTube Premium
- Multi-accounting after a prior ban
- Accumulating debt through declines at zero balance
Credit where due: publishing this list is better practice than most of the segment, which bans first and explains never. The catch is what a ban means when the same company holds your balance and disclaims being a regulated institution.
Vendor claims, reproduced as claims
None of the following is verifiable from outside. No methodology, date or source is attached to any of it, and we did not open an account.
- ·Trusted by 150k+ users
- ·Issued 1M+ cards
- ·9 out of 10 cards are successfully linked
- ·Constantly updated Tier 1 BINs (Tier 1 is never defined and the issuing banks are never named)
- ·No hidden fees. Flat commission. You pay only for a top up, everything else is free
- ·Fast crediting of funds 24/7, and you can also withdraw your funds
- ·Immediate card issuance and unlimited spendings and card issues
- ·Are accounts blocked? We will help you unlock more and reduce the likelihood of being blocked
- ·Funds credited 3 to 4 minutes after the transaction hash is submitted
- ·USDT to USD conversion averages 0.99 in the Russian knowledge base and 0.9 in the English one
The last item is not a marketing claim so much as a documentation defect, and it is the one that costs money. A stated conversion rate of 0.99 versus 0.9 for the same USDT deposit is a 9% spread, sitting on top of a top-up commission of 2.5% to 4.5%. Whichever number is right, one of the two language versions of the vendor's own knowledge base is materially misleading a paying customer.
Who it suits
Teams already past $100k a month
The tiering only pays off at scale: 2.5% on USD BINs above 100k monthly top-ups versus 4.5% at the bottom. Below roughly 25k a month you are paying the highest rate on the card, and the first month is always 4.5% regardless.
Buyers who need card geo to match ad geo
Three issuing GEOs (United States, Hong Kong, Estonia) with per-card limits and bulk issuance is a genuinely workable setup for running many ad accounts across regions from one balance.
Not for anyone needing a regulated counterparty
The Terms disclaim regulated status, no issuing bank is named, no company number is published and there is no safeguarding disclosure. If your finance function requires a named, regulated institution holding the float, this fails at the first question.
Not for Google-first buyers who move fast
Google Ads, YouTube, Google Play and Twitter need prior manager approval, and doing it without approval is stated to be an instant permanent block. If your workflow is spin up and spend today, that friction is real.
Honest limitations
- The homepage contradicts the fee schedule. "No hidden fees. Flat commission. You pay only for a top up, everything else is free" is not compatible with a per-decline ladder, a 2% FX fee and five per-BIN card fees, all published by the same vendor. This is the single largest problem with the product as presented.
- Zero pricing on the marketing site. The only public price claims are "$150 first deposit" and "free card issuance", and both appear solely in the HTML meta description of the four public pages, not in visible page copy. The second one sits directly against the dashboard's own "Card issuance fee" line, whose value is gated behind login. There is no pricing page.
- The real schedule is effectively unlisted. It lives in a Notion document linked only from inside the logged-in app, absent from the sitemap and from every marketing page. Publicly readable, but only if someone hands you the URL.
- Five of six per-BIN fee lines have no public value. Card issuance, monthly maintenance, transaction, transborder and low-value (under $50) fees show their labels in the dashboard, but the values come from the API and require an account. In the dashboard widget three of the six lines are fixed amounts (issuance, maintenance, low-value) and three are percentages (transaction, transborder, FX), with the two gated percentage lines carrying a tooltip that refers to a minimum commission value we cannot see either.
- The vendor's own documentation contradicts itself twice. Decline-rate window: 30 days in Russian, 7 days in English. USDT to USD: 0.99 in Russian, 0.9 in English. Both differences change what you pay.
- No regulated status and no safeguarding disclosure. The Terms state ABcard does not execute payment transactions and does not provide regulated payment or financial services. Cards come from unnamed third-party PSPs, BIN sponsors and Bank Providers, and ABcard disclaims liability for their acts and for those of the advertising platforms.
- No company registration number, jurisdiction detail or named directors. Only a Gibraltar street address inside the Terms. Whether a registered entity exists at that address cannot be established from the site, because there is no number to look up.
- Meaningful funds risk sits with you. The Russian knowledge base states balances can be held up to 60 days where monthly transactions exceed 6,000 with a decline rate above 50%. Unclaimed balances are forfeited two years after account closure. Liability is capped at the greater of last month's fees or $5,000.
- Eligibility cannot be checked in advance. Terms clause 8.2 restricts residents of "certain countries" but publishes no list, so you find out whether you qualify after registering and submitting KYC documents.
- No SLA, no status page, no uptime warranty. Clause 10.1 affirmatively states there is no warranty that access will be continuous and uninterrupted. There is also no public API documentation and no developer docs.
- Four marketing pages, and no substance behind them. No pricing page, no about page, no team page, no blog, no case studies, no changelog. The privacy policy is unmodified generic template boilerplate that still references a placeholder list of advertising partners, names no data controller, no DPO and no address, while asserting GDPR and CCPA rights.
- A second brand nobody explains. anybill.io resolves to the same server, redirects to abcard.io with byte-identical content, and is still the domain used for official notices in the Terms (support@anybill.io). The relationship between the two names is never stated publicly.
- Support is Telegram-first. One customer bot, plus one email address on that unrelated domain (support@anybill.io) buried in clause 13.3 of the Terms. The only named human anywhere on the site, listing 09:00 to 18:00 GMT+3 hours, sells agency accounts for the sister ABagency unit rather than ABcard support. The contact page publishes a Telegram button and nothing else: no email, no phone line, no form, no ticketing system, no published response time.
- Technical hygiene is sloppy in a way that matters. The declared canonical https://abcard.io/en redirects to http://abcard.io/en/, a protocol downgrade off TLS that also affects every sitemap entry. Unknown paths return HTTP 200 through the single-page-app fallback instead of 404.
- Platform-terms exposure is substantial and carried by you. The product exists to fund advertising accounts, and their own knowledge base warns that paying or linking cards to Google Ads, YouTube, Google Play or Twitter without prior manager approval causes instant permanent blocking, balance included. We are describing the mechanics, not recommending the practice.
ABcard + PROXIES.SX: funding layer and network layer
There is no competitive overlap here at all, and we checked properly before saying so. We read the marketing pages, the sitemap, the full single-page-app route table, every service module in the JavaScript bundle and the public knowledge base. ABcard sells no proxy, VPN, IP or hosting product of any kind. The only occurrences of the word proxy in their code are the JavaScript Proxy built-in and the proxy-authenticate and proxy-authorization header names inside bundled libraries. That makes this a straightforwardly complementary review rather than a competitor comparison.
The concrete reason the pairing matters is money, not tidiness. A card issued on a United States BIN presented from a mismatched residential or datacentre IP is a textbook decline and manual-review trigger, and ABcard charges you per decline once your rate crosses its threshold. On the newer schedule that is EUR 0.50 to EUR 0.80 per failed authorisation. Network geo is therefore a direct line item on your card bill, not a hygiene preference. Matching the exit IP country to the BIN country is the cheapest decline reduction available.
PROXIES.SX runs its own 4G/5G mobile and residential network, billed per GB from $4 down to $2.40 at volume, with GB that never expire and endpoints included free. Free endpoints is the part that pairs with a card platform: one dedicated matching-geo endpoint per ad account costs nothing extra, so there is no incentive to run ten funded ad accounts out of one address, which is the pattern that gets both the accounts and the cards flagged together.
ABcard
Funding layer - BIN accounts, cards, limits and spend analytics.
PROXIES.SX
Network layer - one matching-geo 4G/5G mobile IP per ad account, per GB, endpoints free.
Verdict
The product underneath is real and reasonably built. Transit and BIN account separation, bulk issuance, four limit types, per-card 3DS routing, team roles, KYC and 2FA add up to something a media-buying team can actually operate, and the turnover-tiered top-up commission from 4.5% down to 2.5% is a normal, defensible price. Publishing a permanent-ban list and a decline-fee ladder at all is better disclosure than most of this segment manages. What holds it to three is not the pricing but where the pricing lives and what the marketing says instead. A homepage that promises "no hidden fees, you pay only for a top up, everything else is free" while the vendor's own schedule charges per decline, 2% on FX and five more per-BIN lines is a claim that cannot survive contact with its own documentation. Add a fee schedule reachable only from inside the app, five of six card fees with no public value, a knowledge base that contradicts itself on both the decline window and the USDT rate, no company number, an explicit disclaimer of regulated status with no safeguarding disclosure, freeze and forfeiture terms, no SLA, and a canonical URL that downgrades to plain http, and you have a vendor asking for a $150 minimum deposit on trust it has not built in public. 3.0 out of 5: usable infrastructure, genuinely poor disclosure. Read the Notion schedule before you deposit, get the decline window and the USDT rate confirmed in writing, and keep your resting balance well under the $5,000 liability cap.
Related reviews
What we read: the four public pages of abcard.io in English and Russian, its robots.txt and 12-URL sitemap, the Terms of Services (effective March 20, 2026) and privacy policy as served by the application, the fee and rules content of the public ABCard-Info knowledge base, and the application's own JavaScript bundle, from which the fee labels, account-type model, limit types, card schemes, currency enums and business-unit enums were recovered. Corporate facts, fee tiers, decline ladders, ban rules and the 3 to 4 minute crediting time are the vendor's own published statements, reproduced here as claims. The user, card-volume and card-linking-success figures, the meaning of "Tier 1 BINs", the identities of the three issuing banks, the restricted-country list and the five gated per-BIN fee values are all unverifiable from outside. We did not register, complete KYC, deposit funds or issue a card, so crediting speed, decline performance, support responsiveness and withdrawal behaviour are unverified by us. PROXIES.SX has no competitive overlap with ABcard: they sell no proxy, VPN, IP or hosting product, which we confirmed against the route table, the JavaScript bundle and the knowledge base. Nothing here endorses funding advertising accounts in ways that breach platform rules: the vendor's own documentation states that linking cards to Google Ads, YouTube, Google Play or Twitter without prior manager approval causes instant permanent blocking, and that exposure, along with the terms of Meta, Google, TikTok and the other platforms in their Exhibit A, sits with the buyer. Outbound links use rel="nofollow sponsored noopener noreferrer", carry our partner reference, and deliberately point at the trailing-slash form because the non-slash form redirects to plain http.