On October 27, 2026, Shinhan Card announced an offline crypto payment pilot with Dunamu, using the public Kiya Chain and the Shinhan Card Dunamu Kiya Wallet combination. The test, reported by Bloomingbit, uses a proprietary token issued on Kiya Chain and begins at a merchant inside Shinhan Card’s headquarters. For founders and finance leads managing a fiat crypto payment stack, the signal isn’t another wallet launch—it’s the back office.
Table of Contents
- What just happened: a card issuer tested offline crypto payments
- Why this matters now for founders and finance leads
- Web3 payments in plain terms
- The back-office gap most Web3 payment guides skip
- Recommended actions for operators
- What to watch next and open questions
- Frequently asked questions
- Key Takeaways
What just happened: a card issuer tested offline crypto payments
The pilot, dated and attributed
Shinhan Card said on Oct. 27 it will launch an offline payment pilot with Dunamu using the public blockchain Kiya Chain and digital wallet Kiya Wallet. According to Bloomingbit, the test will use a proprietary token issued on Kiya Chain to process employee payments at a merchant on the first basement level of Shinhan Card’s headquarters, with Dunamu supporting the blockchain network. Shinhan Card noted it’s the first time a South Korean card company has tested the Shinhan Card Dunamu Kiya Wallet setup in a real payment environment. The pilot is issuer-led, not peer-to-peer.
| Pilot fact | Reported detail |
|---|---|
| Date announced | Oct. 27, 2026 |
| Card issuer | Shinhan Card |
| Blockchain partner | Dunamu |
| Public chain | Kiya Chain |
| Wallet | Kiya Wallet |
| Payment instrument | Proprietary token issued on Kiya Chain |
| Initial participants | Shinhan Card employees |
| Initial merchant | Merchant on first basement level of Shinhan Card HQ |
| Stated next steps | Expand merchants; link with global blockchain networks |
Why a card-industry first is a meaningful signal
This isn’t another crypto payment gateway. A major issuer is testing a proprietary token on a public chain delivered through a digital wallet for offline crypto payments at a physical point of sale. The bottleneck is shifting from wallets to the issuer and acquiring layer.
Why this matters now for founders and finance leads
From crypto-native apps to issuer-led acceptance
Most web3 payment explainers assume a crypto-native merchant with a wallet or gateway. An issuer-led blockchain payment pilot changes that frame: the card issuer manages the token, wallet support, and the merchant relationship. If this scales, businesses might accept or make web3 payments without a separate crypto gateway, moving closer to the card-network model but with different settlement and custody risk. Coinbase’s stablecoin payments push already shows non-bank players targeting acceptance share; Shinhan’s pilot shows issuers responding.
The back-office consequence for global teams and DAOs
A card-based web3 payment at a merchant still must be reconciled, taxed, and recorded. For a global business or DAO operating a fiat crypto payment stack, the pilot raises a practical question: can your finance stack handle a token-denominated card transaction that settles to a crypto wallet while payroll still runs in fiat and stablecoin payroll payments? The compliance stakes are real; operational mistakes around crypto payroll quickly become legal problems, as detailed in crypto payroll after the Stripe Bitcoin fraud case. The back office is the real bottleneck.
Web3 payments in plain terms
What changes with blockchain-based payment rails
Web3 payments use blockchain networks to record and settle value. Unlike card rails, where a network coordinates authorization and settlement among banks, blockchain rails carry programmable tokens, record transactions on a shared ledger, and settle according to the chain’s finality. Ethereum.org’s explanation of Web3 provides a starting point, but operations require understanding finality, custody, and compliance—not just wallets.
Offline acceptance is the part to watch
Most crypto payment infrastructure handles online checkout. Physical point-of-sale demands offline authorization, terminal integration, speed, and dispute handling. The Shinhan pilot tests a proprietary token inside a digital wallet for offline crypto payments. Offline acceptance is the missing last mile for widespread web3 payments outside e-commerce.
The back-office gap most Web3 payment guides skip
Reconciliation across fiat and crypto
A transaction on a public blockchain may be final in seconds, but that doesn’t map it to an invoice, a card settlement file, a token valuation, and a bank statement. Without a single ledger view, you create a shadow ledger. Reconciliation is the first thing to break when adding a new rail. Finance leads should require a view that ties each crypto transaction to a fiat value and invoice ID. Resources like QuickNode’s guide to web3 payment tools are not accounting systems. A publishing service like Joyrise, which plans, writes and publishes illustrated SEO articles to your Webflow blog every day, won’t close the reconciliation gap either.
Spend controls, invoicing, and multi‑currency settlement
A reliable fiat crypto payment stack needs corporate cards with per-card or per-vendor limits, multi‑currency crypto accounts, invoicing that can quote fiat or stablecoin, and automated settlement. Without spend controls, an employee‑payment pilot quickly becomes uncontrolled if it expands to contractors or vendors. Multi‑currency crypto accounts matter because Shinhan’s proprietary token isn’t a widely accepted stablecoin; most suppliers still invoice in KRW, USD, or EUR.
DAO treasury operations across payment workflows
For DAOs, governance isn’t optional. Payment workflows need role-based permissions so a core team can execute while token holders retain control. DAO treasury operations should require multiple approvals for large disbursements, automated recurring payroll in stablecoins (stablecoin payroll payments), and a clear audit trail across fiat and crypto. If offline crypto payments become common, DAOs will inherit the same reconciliation burden plus governance constraints.
Recommended actions for operators
Audit your fiat crypto payment stack now
Run a structured audit before issuer-led adoption reaches your suppliers or customers.
| Area | Question to ask | Red flag |
|---|---|---|
| Reconciliation | Can you match each crypto transaction to an invoice and fiat settlement? | Off-chain manual spreadsheet |
| Spend controls | Do corporate cards have per-card limits and approval rules? | Shared card with no limits |
| Invoicing | Can you issue invoices in fiat and stablecoin? | Single-currency only |
| Custody | Are digital assets held in qualified custody with MFA? | Hot wallet with no policy |
| Multi-currency | Can you hold USD, EUR, CAD and convert to/from crypto? | Separate bank and exchange |
| DAO roles | Can you assign role-based permissions for payment approvals? | One private key controls treasury |
Use custody and compliance as selection criteria
Treat custody and compliance as hard filters. Look for segregated accounts, encryption, mandatory MFA, and institutional-grade digital asset custody. The regulatory direction is moving: the OCC’s stablecoin move for community banks shows deposit-taking institutions being pulled into tokenized payments, and the GENIUS Act update from October 2026 frames the compliance baseline. Custody and compliance are selection criteria, not add‑ons. Don’t pick a payment tool because it supports a specific token; pick it because you can demonstrate who controls the assets and how money moves.
Prepare for multi‑currency crypto accounts and on/off‑ramps
If card‑network‑scale adoption arrives, you’ll need to move between fiat and crypto continually. Open multi‑currency crypto accounts in the currencies you actually pay, and confirm your on/off‑ramp fees and processing times. A unified platform reduces operational burden; for example, OneSafe provides fiat multi‑currency accounts in USD, Euro, and CAD, with crypto on/off‑ramps and DAO‑specific roles. The point is to prepare before an issuer or supplier forces the issue.
What to watch next and open questions
Merchant expansion and global blockchain network links
Shinhan Card plans to gradually expand participating merchants and link with global blockchain networks. Watch whether the pilot moves beyond employees to public customers, and whether Kiya Chain connects to other networks or stablecoin standards. That will determine if this remains a closed campus test or grows into a real acceptance network. Also emerging is AI agents initiating stablecoin payments, adding another potential buyer to the mix.
Whether proprietary tokens become stablecoin‑compatible standards
Many web3 payment explainers imply payments are peer‑to‑peer, non‑custodial, and instant. The Shinhan pilot is issuer‑driven, uses a proprietary token on a public chain, and is limited to employee payments at one merchant. The realistic position: public‑blockchain rails can coexist with issuer‑issued tokens and offline crypto payments. Operators should prioritize finality, reconciliation, and compliance over ideological purity. Treat the instrument as a payment obligation to be accounted for, not merely as a crypto asset.
Regulatory and commercial follow‑through
Even if the technical pilot works, commercial expansion will depend on anti‑money‑laundering rules, token issuer obligations, and card‑network rules. The OCC’s stablecoin move and the GENIUS Act update from October 2026 are early indicators of how regulators will treat tokenized payments at institutions. Finance leads should track those rules alongside technical pilots.
Frequently asked questions
What are Web3 payments?
Web3 payments are blockchain‑based payment transactions that settle on a distributed ledger rather than through a traditional card network or bank messaging system. They can use programmable tokens, smart contracts, and crypto wallets, but the commercial question is who bears reconciliation and custody responsibility.
What just happened with Shinhan Card and Dunamu?
On Oct. 27, 2026, Shinhan Card announced an offline crypto payment pilot with Dunamu using the Shinhan Card Dunamu Kiya Wallet combination on Kiya Chain. The test uses a proprietary token, starts with employee payments at a merchant in Shinhan Card’s headquarters, and may later expand to more merchants and global blockchain networks, according to Bloomingbit.
Why does an offline crypto payment pilot matter for my business?
Because offline acceptance moves web3 payments from crypto‑native checkout to card‑issuer infrastructure. If that scales, your company may need to accept or make token‑denominated payments at physical merchants while still reconciling them in fiat, managing spend controls, and satisfying audit requirements.
What does a fiat crypto payment stack actually require?
Reconciliation across fiat and crypto ledgers, multi‑currency crypto accounts, corporate cards with spend limits, invoicing in fiat and stablecoin, secure crypto custody, and role‑based permissions for treasury or DAO workflows. Missing any one of those creates operational risk.
What should finance leads do now?
Audit your current payment stack, treat custody and compliance as non‑negotiable filters, and prepare multi‑currency crypto accounts with proven on/off‑ramps. A unified platform that gives a single view of fiat and crypto transactions reduces the stitching‑together of separate bank and exchange relationships.
What should I watch for next?
Watch whether Shinhan Card expands the pilot beyond employees, whether Kiya Chain links to global blockchain networks, and whether proprietary tokens become stablecoin‑compatible. Also track how regulators apply stablecoin and tokenized payment rules to card issuers and their partners.
Key Takeaways
- Shinhan Card’s Oct. 27, 2026 blockchain payment pilot with Dunamu is an issuer‑led offline test of web3 payments, not a peer‑to‑peer crypto checkout demo.
- The practical risk for global businesses and DAOs is back‑office reconciliation, not wallet technology.
- Public‑blockchain rails can coexist with proprietary issuer tokens; operators should prioritize finality, reconciliation, and compliance.
- Finance leads should audit spend controls, multi‑currency crypto accounts, custody, and DAO treasury operations before issuer‑led adoption touches their suppliers.
- Watch merchant expansion, global network links, and regulatory follow‑through before assuming this becomes a standard acceptance model.
If you’re ready to manage fiat and crypto from one account, sign up for OneSafe to see whether it fits your payment stack.
