Payment
Last updated
Last updated
Mini Dapps must provide both fiat and crypto payment options on the product purchase screen, with each payment button offered separately.
Payment methods support credit/debit cards (major brands such as VISA, MasterCard, AMEX, JCB, etc.), Apple Pay, Google Play, Naver Pay (KRW only), and Kakao Pay (KRW only).
Payment methods dynamically and automatically change depending on the OS and payment currency of the connected device.
Payment method may change in the future depending on the payment processor's policy.
LINE IAP payment will be available soon.
Fiat payments are supported in both the LIFF and Web versions of Mini Dapp.
Only $KAIA is supported as a payment method.
Crypto payments are supported in both the LIFF and Web versions of Mini Dapp.
Fiat
USD
2
999,999
0.50
KRW
0
999,999
750
JPY
0
999,999
80
TWD(NTD)
2
999,999
17
THB
2
999,999
18
Crypto
$KAIA
4
999,999
0.01
The prices of products sold through the Mini Dapp SDK must be presented to users in both fiat currency and cryptocurrency with a certain level of stability.
This aims to provide a stable purchasing experience for both Web2 and Web3 users, prevent confusion caused by excessive price fluctuations, and balance the needs of Web2 and Web3 users. By doing so, it seeks to create a purchasing environment that is understandable, trustworthy, and reliable for all users.
USD is the default payment currency.
Each Mini Dapp may optionally support additional local currencies (JPY, TWD, THB, KRW) based on user's country information of needed.
Japan
Default : USD, KAIA
Optional : JPY, KAIA
Thailand
Default : USD, KAIA
Optional : THB, KAIA
Taiwan
Default : USD, KAIA
Optional : TWD, KAIA
South Korea
Default : USD, KAIA
Optional : KRW, KAIA
Others
Default : USD, KAIA
When a user selects Fiat payment, Mini Dapp operator must enter a fixed amount based USD to request payment.
When a user selects Crypto payment, Mini Dapp operator must enter a fixed amount based on $KAIA to request payment.
To minimize errors such as duplicate payments or incorrect payments, the Dapp must provide appropriate notification messages to the user immediately so that the user can recognize the results of successful and failed/canceled purchases in a "clear" and "intuitive" manner
Successful purchase
Fiat/Crypto payment successful and item delivered
Successful purchase
Purchase failed/canceled
User requested to process Fiat/Crypto payment but payment failed
Purchase failed
User clicked the "Back" button on the Fiat/Crypto payment screen or exited the screen
Purchase canceled
User clicks the Decline Signature button on the Crypto payment screen
Purchase canceled
User's Crypto balance is insufficient
Insufficient balance
Other errors
Please try again later
Refer to SDK document and provide payment history to the user in the appropriate location.