Verify and integrate JPYC

What a JPY stablecoin user should check before choosing JPYC, from public sources as of 14 Nov 2026. JPY stablecoins · Compare side by side

Issuer-statedVerified onchainThird-partyNot disclosed: nothing public says it.

Summary

Yen stablecoin by JPYC Inc., redeemable to yenIssuer-statedDetails

JPYC is a Japanese yen stablecoin issued by JPYC Inc. (JPYC株式会社), a Tokyo company registered as a funds transfer service provider; unlike the earlier JPYC Prepaid, it is an electronic payment instrument redeemable for yen. Users buy and redeem it on JPYC EX against bank transfers after ID checks, and one contract address runs on Ethereum, Polygon, Avalanche and Kaia. It serves individuals and businesses using yen for payments, remittances and onchain finance.

English summary of Japanese-language pages.

Issuer-statedjpyc.co.jp ↗2 ↗3 ↗

Issuer and licences

Legal entity
JPYC Inc. (JPYC株式会社)Issuer-statedDetails

JPYC株式会社 (JPYC Inc.); representative director Noritaka Okabe (代表取締役 岡部典孝); founded November 2019; capital JPY 100,000,000.

Issuer-statedjpyc.co.jp ↗

Jurisdiction
Japan (Tokyo)Issuer-statedDetails

Japan; Otemachi Building 4F (FINOLAB), 1-6-1 Otemachi, Chiyoda-ku, Tokyo.

Issuer-statedjpyc.co.jp ↗

Regulator
Kanto Local Finance Bureau (FSA)Issuer-statedDetails

Kanto Local Finance Bureau (Financial Services Agency of Japan), with which JPYC is registered as a funds transfer service provider.

The FSA register (fsa.go.jp) was not reachable from this session, so the registration is as stated by JPYC.

Issuer-statedjpyc.co.jp ↗2 ↗

Licences
Funds transfer provider, Kanto No. 00099Issuer-statedDetails

Funds transfer service provider (資金移動業者), Kanto Local Finance Bureau No. 00099; Prepaid payment instrument issuer, third-party type (前払式支払手段発行者), Kanto Local Finance Bureau No. 00773; Secondhand dealer and secondhand market operator, Tokyo Public Safety Commission

Issuer-statedjpyc.co.jp ↗

Website
jpyc.co.jpIssuer-statedDetails
FXscan licence check

Licensed · FSA (Japan) · 関東財務局長 第00099号 · JPYC株式会社 (JPYC Inc.)

Funds transfer service provider since 18 Aug 2025, Japan's route to issue a yen stablecoin.

Source: fsa.go.jp ↗ · Checked 31 Oct 2026

Funding and ownership

Parent
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗

Owners
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗

Funding
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗

Partners
HashPort, Asteria, double jump.tokyo, NudgeIssuer-statedDetails

Named integrations: HashPort Wallet (recommended wallet; JPYC EX account link for issue and redeem), Asteria (ASTERIA Warp), double jump.tokyo (N Suite corporate wallet), Nudge (credit card repayment in JPYC) and the manga platform comilio.

Issuer-statedjpyc.co.jp ↗2 ↗

Reserves

Backing
Japanese yenIssuer-statedDetails

Japanese yen: JPYC describes itself as a stablecoin collateralised by Japanese yen (日本円を担保とする).

The pages read do not give the reserve composition; The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Issuer-statedjpyc.co.jp ↗

Allocation
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗2 ↗3 ↗

Custodian
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗2 ↗3 ↗

Segregation
Not disclosedChecked

The terms, pre-contract disclosure and FAQ (jpyc.co.jp/legal/*.pdf, faq.jpyc.co.jp, corporate.jpyc.co.jp) returned 403/404 or were blocked for this session, so only the pages listed were read.

Checkedjpyc.co.jp ↗2 ↗3 ↗

Attestation
Not disclosedChecked

JPYC says it plans to publish the status of its reserves regularly (準備金の状況を定期的に公開する予定); no report was found on the pages read.

Checkedjpyc.co.jp ↗2 ↗3 ↗

Proof of reserve
Not disclosedChecked

Mint and redeem

Who can
Verified JPYC EX accounts (My Number)Issuer-statedDetails

JPYC EX account holders after ID verification: individuals with a My Number card (public key authentication); companies through a registered representative, with extra checks otherwise.

Issuer-statedjpyc.co.jp ↗

Process
Bank transfer in; redeem to bankIssuer-statedDetails

Deposit yen to JPYC EX by bank transfer and buy JPYC; to redeem, send JPYC back and receive yen in a registered bank account. Linked apps such as HashPort Wallet hand off to JPYC EX for the same steps.

Issuer-statedjpyc.co.jp ↗2 ↗

Speed
24/7; paid after confirmationIssuer-statedDetails

JPYC EX runs 24/7; account opening from 10 minutes. Redemptions are paid to the bank account after the transaction is confirmed, and can take longer with bank, chain or maintenance delays.

Issuer-statedjpyc.co.jp ↗

Fees
Free; user pays bank fees and gasIssuer-statedDetails

Issuance and redemption are free; the user pays bank transfer fees for deposits and gas.

Issuer-statedjpyc.co.jp ↗2 ↗

Minimums
From ¥3,000; ¥1m issue/redeem capsIssuer-statedDetails

Issuance: from JPY 3,000 and up to JPY 1,000,000 per transaction. Redemption: from JPY 3,000 per transaction, up to JPY 1,000,000 per day. No limit on holding or on transfers between users.

Issuer-statedjpyc.co.jp ↗2 ↗

Any holder at par
Yes, via a JPYC EX accountIssuer-statedDetails

Yes for JPYC EX account holders: JPYC is redeemable for yen (unlike JPYC Prepaid, which was not and stopped new issuance on 2025-06-01).

The redemption terms themselves (terms.pdf) were not reachable.

Issuer-statedjpyc.co.jp ↗2 ↗

FXscan's how-to-get summary

How to get JPYC

Who can mint
Businesses & individuals
Mint
Individuals (Japanese eKYC) and companies with a JPYC EX account send JPY by bank transfer and receive JPYC.
Redeem
Holders send JPYC to JPYC EX and receive JPY by Zengin bank transfer.
Payment rails
Zengin System (bank transfer)

Also available on

Compiled 23 Sep 2026 from public issuer information (espl.jp, corporate.jpyc.co.jp, web3.bitget.com). Not advice. Confirm with the issuer before sending funds. Report a correction.

Token controls

ChainAdminUpgradeablePauseFreezeMint
AvalancheMultisig 3-of-5Verified onchainYesVerified onchainYesVerified onchainYesVerified onchainMultisig 2-of-3AllowanceVerified onchain
EthereumMultisig 3-of-5Verified onchainYesVerified onchainYesVerified onchainYesVerified onchainMultisig 2-of-3AllowanceVerified onchain
KaiaUnknownYesVerified onchainYesVerified onchainYesVerified onchainUnknownAllowanceVerified onchain
PolygonMultisig 3-of-5Verified onchainYesVerified onchainYesVerified onchainYesVerified onchainMultisig 2-of-3AllowanceVerified onchain
Contracts and full control facts

Avalanche

0xe7c3d8c9a439fede00d2600032d5db0be71c3c29
Upgradeable
Yes; Safe 3-of-5Verified onchainDetails

Yes. UUPS (ERC1967Proxy) to FiatTokenV1 0xafac17fc3936a29ca2d2787ced3c5d1c52007d2e; _authorizeUpgrade is onlyOwner, and owner() is Safe 0x8e4cddc4712646ea5222b4f2e959acecefe763c9 (3-of-5). One Upgraded event (deployment, 2025-06-03); ownership moved from deployer 0x11f14c2bfe398379b361019aa440f792c27f9384 to the Safe on 2025-08-04. No Blocklisted event.

Verified onchaineth.blockscout.com ↗api.avax.network ↗api.routescan.io ↗

Pause
Yes; Safe 2-of-3Verified onchainDetails

Yes. pause()/unpause() are restricted to pauser() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a pause stops transfers, mints and burns. paused() is false.

Verified onchaineth.blockscout.com ↗api.avax.network ↗api.routescan.io ↗

Freeze / blacklist
Yes; Safe 2-of-3Verified onchainDetails

Yes. blocklist()/unBlocklist() are restricted to blocklister() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a blocklisted address cannot send, receive, approve or mint. There is no wipe or seize function.

Verified onchaineth.blockscout.com ↗api.avax.network ↗api.routescan.io ↗

Mint authority
Allowance; minter Safe 2-of-3Verified onchainDetails

Allowance-based (USDC-style). minterAdmin() is MinterAdmin contract 0x029ba134614b61ee129e2dc5ae3ead5f0a215694 (owner Safe 0x5ba1b9aaf56af1b761519f924079681d8d061f94; 2-of-3 on Ethereum), which sets minters and allowances. Minters (isMinter true): Safe 0xcb64c718358e0baf7f00090e8bf687583a651ec3 (2-of-3), remaining minterAllowance 1,700,000,000 JPYC; 0xb808af91bdc577bfb3f9c91470f3286dd076e5c1 (JPYC redemption wallet) with allowance 0. The deployer 0x11f14c2bfe398379b361019aa440f792c27f9384 is no longer a minter.

Verified onchaineth.blockscout.com ↗api.avax.network ↗api.routescan.io ↗2 ↗

Burn
Minters, own balanceVerified onchainDetails

Only minters can burn, and only from their own balance (burn is onlyMinters).

Verified onchaineth.blockscout.com ↗

Admin
Multisig 3-of-5Verified onchainDetails

Safe multisig 0x8e4cddc4712646ea5222b4f2e959acecefe763c9, threshold 3 of 5 owners: owner() of the token (upgrades; sets pauser, blocklister, rescuer and minterAdmin).

Verified onchaineth.blockscout.com ↗api.avax.network ↗api.routescan.io ↗

Verified source
YesVerified onchainDetails

Yes: proxy ERC1967Proxy (Sourcify exact match) and implementation FiatTokenV1 (Routescan, Solidity 0.8.11) verified.

Verified onchainsourcify.dev ↗api.routescan.io ↗

Ethereum

0xe7c3d8c9a439fede00d2600032d5db0be71c3c29
Upgradeable
Yes; Safe 3-of-5Verified onchainDetails

Yes. UUPS (ERC1967Proxy) to FiatTokenV1 0xafac17fc3936a29ca2d2787ced3c5d1c52007d2e; _authorizeUpgrade is onlyOwner, and owner() is Safe 0x8e4cddc4712646ea5222b4f2e959acecefe763c9 (3-of-5). One Upgraded event (deployment, 2025-06-03); ownership moved from deployer 0x11f14c2bfe398379b361019aa440f792c27f9384 to the Safe on 2025-08-04.

Verified onchaineth.blockscout.com ↗ethereum-rpc.publicnode.com ↗2 ↗

Pause
Yes; Safe 2-of-3Verified onchainDetails

Yes. pause()/unpause() are restricted to pauser() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a pause stops transfers, mints and burns. paused() is false.

Verified onchaineth.blockscout.com ↗ethereum-rpc.publicnode.com ↗2 ↗

Freeze / blacklist
Yes; Safe 2-of-3Verified onchainDetails

Yes. blocklist()/unBlocklist() are restricted to blocklister() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a blocklisted address cannot send, receive, approve or mint. There is no wipe or seize function. One Blocklisted event on Ethereum (0x7853c438c36f1da398ef60ff44955c8f657405ed, 2026-06-09).

Verified onchaineth.blockscout.com ↗ethereum-rpc.publicnode.com ↗2 ↗

Mint authority
Allowance; minter Safe 2-of-3Verified onchainDetails

Allowance-based (USDC-style). minterAdmin() is MinterAdmin contract 0x029ba134614b61ee129e2dc5ae3ead5f0a215694 (owner Safe 0x5ba1b9aaf56af1b761519f924079681d8d061f94; 2-of-3 on Ethereum), which sets minters and allowances. Minters (isMinter true): Safe 0xcb64c718358e0baf7f00090e8bf687583a651ec3 (2-of-3), remaining minterAllowance 2,000,000,000 JPYC; 0xb808af91bdc577bfb3f9c91470f3286dd076e5c1 (JPYC redemption wallet) with allowance 0. The deployer 0x11f14c2bfe398379b361019aa440f792c27f9384 is no longer a minter.

Verified onchaineth.blockscout.com ↗ethereum-rpc.publicnode.com ↗2 ↗3 ↗

Burn
Minters, own balanceVerified onchainDetails

Only minters can burn, and only from their own balance (burn is onlyMinters).

Verified onchaineth.blockscout.com ↗

Admin
Multisig 3-of-5Verified onchainDetails

Safe multisig 0x8e4cddc4712646ea5222b4f2e959acecefe763c9, threshold 3 of 5 owners: owner() of the token (upgrades; sets pauser, blocklister, rescuer and minterAdmin).

Verified onchaineth.blockscout.com ↗ethereum-rpc.publicnode.com ↗2 ↗

Verified source
YesVerified onchainDetails

Yes: proxy ERC1967Proxy and implementation FiatTokenV1 verified on Blockscout (2025-06-03, Solidity 0.8.11).

Verified onchaineth.blockscout.com ↗2 ↗

Kaia

0xe7c3d8c9a439fede00d2600032d5db0be71c3c29
Upgradeable
Yes; owner not readVerified onchainDetails

Yes. Sourcify resolves the contract as an ERC1967Proxy (exact match) to FiatTokenV1 0xafac17fc3936a29ca2d2787ced3c5d1c52007d2e, upgradable by its owner. Who the owner is on Kaia was not read.

No Kaia RPC or explorer API was reachable from this session (public-en.node.kaia.io, kaiascan.io and others blocked).

Verified onchainsourcify.dev ↗2 ↗

Pause
Yes; pauser not readVerified onchainDetails

The verified FiatTokenV1 implementation has pause()/unpause() for a pauser address; the pauser on Kaia was not read.

Verified onchainsourcify.dev ↗

Freeze / blacklist
Yes; blocklister not readVerified onchainDetails

The verified FiatTokenV1 implementation has blocklist()/unBlocklist() for a blocklister address; the blocklister on Kaia was not read.

Verified onchainsourcify.dev ↗

Mint authority
Allowance; minters not readVerified onchainDetails

The verified FiatTokenV1 implementation mints only within per-minter allowances set by minterAdmin; minters and allowances on Kaia were not read.

Verified onchainsourcify.dev ↗

Burn
Minters, own balanceVerified onchainDetails

Only minters can burn, from their own balance (FiatTokenV1).

Verified onchainsourcify.dev ↗

Admin
Not disclosedChecked

owner() on Kaia could not be read: no Kaia RPC was reachable from this session.

Checkedsourcify.dev ↗

Verified source
Yes (Sourcify)Verified onchainDetails

Yes: proxy and FiatTokenV1 implementation verified on Sourcify (exact match), deployed by 0x11f14c2bfe398379b361019aa440f792c27f9384 at block 215,946,036.

Verified onchainsourcify.dev ↗2 ↗

Polygon

0xe7c3d8c9a439fede00d2600032d5db0be71c3c29
Upgradeable
Yes; Safe 3-of-5Verified onchainDetails

Yes. UUPS (ERC1967Proxy) to FiatTokenV1 0xafac17fc3936a29ca2d2787ced3c5d1c52007d2e; _authorizeUpgrade is onlyOwner, and owner() is Safe 0x8e4cddc4712646ea5222b4f2e959acecefe763c9 (3-of-5). Upgrade and ownership history not read (Polygon RPC log range limit).

Verified onchaineth.blockscout.com ↗polygon.drpc.org ↗

Pause
Yes; Safe 2-of-3Verified onchainDetails

Yes. pause()/unpause() are restricted to pauser() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a pause stops transfers, mints and burns. paused() is false.

Verified onchaineth.blockscout.com ↗polygon.drpc.org ↗

Freeze / blacklist
Yes; Safe 2-of-3Verified onchainDetails

Yes. blocklist()/unBlocklist() are restricted to blocklister() = Safe 0x0f018651bd4c556ed9515379dd314d9fdee21bb9 (2-of-3); a blocklisted address cannot send, receive, approve or mint. There is no wipe or seize function.

Verified onchaineth.blockscout.com ↗polygon.drpc.org ↗

Mint authority
Allowance; minter Safe 2-of-3Verified onchainDetails

Allowance-based (USDC-style). minterAdmin() is MinterAdmin contract 0x029ba134614b61ee129e2dc5ae3ead5f0a215694 (owner Safe 0x5ba1b9aaf56af1b761519f924079681d8d061f94; 2-of-3 on Ethereum), which sets minters and allowances. Minters (isMinter true): Safe 0xcb64c718358e0baf7f00090e8bf687583a651ec3 (2-of-3), remaining minterAllowance 2,100,000,000 JPYC; 0xb808af91bdc577bfb3f9c91470f3286dd076e5c1 (JPYC redemption wallet) with allowance 0. The deployer 0x11f14c2bfe398379b361019aa440f792c27f9384 is no longer a minter.

Verified onchaineth.blockscout.com ↗polygon.drpc.org ↗2 ↗

Burn
Minters, own balanceVerified onchainDetails

Only minters can burn, and only from their own balance (burn is onlyMinters).

Verified onchaineth.blockscout.com ↗

Admin
Multisig 3-of-5Verified onchainDetails

Safe multisig 0x8e4cddc4712646ea5222b4f2e959acecefe763c9, threshold 3 of 5 owners: owner() of the token (upgrades; sets pauser, blocklister, rescuer and minterAdmin).

Verified onchaineth.blockscout.com ↗polygon.drpc.org ↗

Verified source
YesVerified onchainDetails

Yes: implementation FiatTokenV1 verified on Sourcify (exact match). The proxy is not on Sourcify, but its bytecode is identical to the verified Ethereum proxy (same sha256 of eth_getCode).

Verified onchainsourcify.dev ↗polygon.drpc.org ↗

Yield, audits and risks

Yield
Not disclosedChecked
Audits
Not disclosedChecked

JPYC links a GitHub organisation (github.com/jpycoin) from its business page; it was not readable from this session.

Checkedjpyc.co.jp ↗2 ↗3 ↗

Compliance
KYC on JPYC EX; onchain blocklistIssuer-statedDetails

KYC for JPYC EX (My Number card for individuals; representative checks for companies). Onchain, a 2-of-3 Safe can blocklist addresses; one address was blocklisted on Ethereum on 2026-06-09.

Issuer-statedjpyc.co.jp ↗eth.blockscout.com ↗

Disclosed risks
Multisig controls; allowance-capped mintVerified onchainDetails

JPYC's site warns about fake JPYC tokens, phishing and online casinos. Onchain, upgrades need a 3-of-5 Safe and minting is limited by allowances; the minter Safe had 2.0 billion JPYC of allowance left on Ethereum. Kaia controls could not be read.

Verified onchainjpyc.co.jp ↗ethereum-rpc.publicnode.com ↗

Links and contracts

Contracts

JPYC contract addresses (5)

Not on JPYC Inc.'s own pages. Found via block explorers and data aggregators.

Compiled from public issuer, regulator and explorer pages. Not advice. Confirm with the issuer before sending funds. Report a correction.