Virtual Card API
in Japan

Developers in Japan use the Eisy virtual card API to put card issuing inside their own product. Create a card holder, run their ID check, issue a Visa or Mastercard virtual card, fund it and read its transactions, all over a REST API with scoped keys and signed requests.

Apply for API accessSee how merchant accounts work
InterfaceREST + webhooks
AuthSigned requests
Card networksVisa · Mastercard

One REST API for the whole card lifecycle in Japan.

Apply for API access

A virtual card’s lifecycle over the API in Japan

Each step is one API call, and the result comes back as a signed webhook.

  1. Create a card holder

    Send the user’s details and start their ID and selfie check.

  2. Issue the card

    Choose Visa or Mastercard; card details are returned securely when you request them.

    card.issued

  3. Fund it

    Move USD from your business wallet onto the card.

    card.topup.completed

  4. Spend

    Authorisations and settlements are pushed to your endpoint as they happen.

    card.transaction.settled

  5. Freeze, unfreeze or withdraw

    Pause a card or pull unused funds back to the wallet.

    card.withdrawal.completed

  6. Terminate

    The card stops working and any balance returns to your wallet.

    card.terminated

Everything in the card API

Issue cards

Create Visa or Mastercard virtual USD cards for verified card holders and get the card details back securely.

card.issued

Fund and withdraw

Top up a card from your business USD wallet, pull funds back when a card is no longer needed.

card.topup.completed

Transaction webhooks

Authorisations, settlements, declines, reversals and refunds arrive as signed events with automatic retries.

card.transaction.settled

Controls

Freeze, unfreeze and terminate cards; balances return to your wallet on termination.

card.terminated

Card holders with KYC

Every card holder passes an ID and selfie check before a card can be issued to them.

card.verified

Keys, signing and IP whitelists

Scoped API keys with a secret you can rotate or revoke, request signing, and an IP whitelist of your servers on every key.

Built on events

Every card event is delivered to your endpoint as a signed webhook and retried until you acknowledge it. A simplified example:

{
  "event": "card.transaction.settled",
  "data": {
    "cardId": "crd_…",
    "amount": "12.99",
    "currency": "USD",
    "merchant": "Netflix.com",
    "status": "settled"
  }
}
card.issuedcard.topup.completedcard.withdrawal.completedcard.transaction.authorizedcard.transaction.settledcard.transaction.declinedcard.transaction.reversedcard.transaction.refund_settledcard.blockedcard.expiringcard.terminated

Why developers in Japan build on Eisy

  • •One REST API covers the whole card lifecycle for users in Japan: card holder, KYC, issue, fund, freeze, unfreeze, withdraw and terminate.
  • •Card details are returned securely on request, so you decide when and where a user sees their card number.
  • •Every key has a signing secret and an IP whitelist, and each request is signed, so a leaked key alone is not enough to move money.
  • •Webhooks for authorisations, settlements, declines, reversals and refunds keep your ledger in step without polling.

Where cards are used in Japan

International services Eisy card users in Japan pay for. Cards you issue through the API work on the same Visa and Mastercard networks.

JPY

Prices in Japan are in Japanese yen (JPY); cards issued through Eisy hold US dollars. Merchants that charge in USD are paid directly, and charges in JPY or another currency are converted to USD by the card network.

SpotifyParamount+AliExpressChatGPT Plus

What you can build in Japan

Products teams launch on the Eisy card API.

In-app cards for wallets and neobanks
Cards issued at checkout or sign-up
Per-user cards for subscriptions and online spend
Cards for marketplace sellers and gig workers
Single-use cards you terminate after a purchase
Internal tools that issue cards to staff

Pricing

Set per business and shown in your merchant dashboard before every action you confirm. Want the consumer product instead? See virtual dollar cards in Japan.

Card creationPer card
Card fundingFlat fee or percentage
Termination and declinesPer event
Platform or monthly feeNone

More ways to issue cards in Japan

Virtual USD Card API in JapanCard Issuing API for Startups in JapanCard Issuing Platform in JapanCorporate Expense Card API in JapanPrepaid Virtual Card API in JapanVirtual Cards for Ad Spend in JapanVirtual Debit Card API in JapanCredit Card API in Japan

One REST API for the whole card lifecycle in Japan.

Apply for API access

How to go live with the virtual card API in Japan

From application to your first issued card: verify your business, fund your wallet, connect your webhook and start issuing.

Apply for API access
1

Apply and verify your business

Create an Eisy account, apply for a merchant account and complete business verification (KYB). We review and email you when you are approved.

Apply and verify your business
2

Get your keys and fund your wallet

Generate API keys, set your webhook URL and fund your business USD wallet. Invite admins and members to help manage cards.

Get your keys and fund your wallet
3

Verify card holders and issue cards

Card holders pass an ID and selfie check, then you issue, fund, freeze or terminate cards and receive every event by webhook.

Verify card holders and issue cards

Virtual card API in other countries in Asia

BangladeshCambodiaChinaHong Kong S.a.r.IndiaIndonesiaIsraelKazakhstanKuwaitMalaysiaMongoliaNepalOmanPakistanPhilippinesSaudi ArabiaSingaporeSouth KoreaSri LankaTaiwanThailandTurkeyTurkmenistanUnited Arab EmiratesVietnam

FAQs about the virtual card API

1

Who can use the Eisy card API in Japan?

Registered businesses in Japan and elsewhere. You apply for a merchant (business) account, complete business verification (KYB), and your account is reviewed before API keys are issued.

2

Which card networks and currency are supported?

Visa and Mastercard virtual cards denominated in US dollars. Every card is funded from your business USD wallet.

3

Do card holders need to verify their identity?

Yes. Each card holder completes a quick ID and selfie check before cards can be issued to them. You can run this from your dashboard or through the API.

4

How do I know when a card is used?

Webhooks. You receive signed events when a card is issued, funded, authorised, settled, declined, reversed, refunded, blocked or terminated, with automatic retries if your endpoint is down.

5

What does it cost?

Pricing is set per business: a card creation fee, a funding fee (flat or percentage), and termination and decline fees. The fees for your account are shown in your merchant dashboard and before every action you confirm.

6

How do I authenticate with the virtual card API?

Exchange your client ID and secret for a one-hour access token, then sign each request with your secret. Every key is tied to an IP whitelist of your servers, and keys can be rotated or revoked from your dashboard.

7

Can I see a card’s balance and transactions?

Yes. The API returns each card’s balance and transaction history, and webhooks push new authorisations, settlements, declines and refunds as they happen.

8

Can the cards pay merchants that charge in JPY?

Yes. The cards hold US dollars, and when a merchant charges in Japanese yen (JPY) or any other currency, Visa or Mastercard converts the amount to USD at the time of the transaction.

Get your API keys

Apply, verify your business and make your first card API call for users in Japan.

Apply nowDownload app
Get Started