เครือข่ายการชำระเงินขนาดใหญ่ส่วนใหญ่อนุญาตให้ใช้ ODA เพื่อวัตถุประสงค์ในการขนส่งสาธารณะ ข้อกำหนดในการใช้งาน ODA จะแตกต่างกันไปตามเครือข่ายการชำระเงิน เราขอแนะนำให้คุณทำงานร่วมกับเครือข่ายการชำระเงินเพื่อทำความเข้าใจข้อกำหนดของ ODA และนำไปใช้งานตามข้อกำหนดเฉพาะ
มีการจัดการข้อมูลบนอุปกรณ์เคลื่อนที่อย่างไร
Google Wallet ใช้คีย์และใบรับรองจากเครือข่ายการชำระเงินและธนาคารที่เป็นผู้ออกบัตร ช่วงเวลานี้
อนุญาตให้ตรวจสอบสิทธิ์กับเครื่องชำระเงินในโหมดออฟไลน์
[null,null,["อัปเดตล่าสุด 2025-07-25 UTC"],[[["\u003cp\u003eFare capping ensures riders pay the lowest possible fare by automatically applying the best-priced pass based on their trip frequency.\u003c/p\u003e\n"],["\u003cp\u003eOffline data authentication (ODA) allows for faster transit payments by verifying card and network authenticity directly on the device, but balance checks still occur later.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Wallet leverages payment network and bank-issued keys to facilitate offline authentication between your device and the transit terminal.\u003c/p\u003e\n"],["\u003cp\u003eTransit agencies can implement receipt rollups in Google Wallet to provide users with clear breakdowns of their fare-capped transactions.\u003c/p\u003e\n"]]],["Fare caps ensure users pay the lowest possible fare based on usage, without needing to buy passes. Transit agencies collect ride data and dynamically calculate the optimal charge at day's end. Offline Data Authentication (ODA) uses certificates for device and terminal verification but cannot check account balances. ODA implementation requires collaborating with payment networks. Google Wallet uses payment network keys and certificates on the device for offline authentication and exchanges data during tap interactions.\n"],null,["# Frequently asked questions\n\nWhat are fare caps?\n\n: A fare cap is a practice in which users are charged for their rides over a period of time.\n The combined fares over multiple rides can't be more than if they had purchased the optimal\n period pass based on their usage. When the user rides and taps on the terminal that has a\n fare cap, the transit agency backend collects all taps and decides how much to charge\n dynamically at the end of the day. The aim is to give the user the best fare without the need\n to explicitly purchase any passes.\n\n For example, suppose users can buy the following fares:\n\n - Single trip: $1\n - One day unlimited pass: $10\n - One week unlimited pass: $25\n\n With fare caps in place, users always get the best fare possible. The following examples show\n the fares charged to the user in various circumstances:\n\n - One trip: $1\n - Three trips: $3\n - Thirteen trips in one day: $10\n - Thirty trips in one week: $25\n\n Many transit agencies have implemented fare caps to discount users' fares on their behalf. To\n better communicate the results of these transactions to users, Google Wallet allows you\n to implement receipt rollups. For more details, see\n [Rollups when fare capping](/wallet/tickets/open-loop/mobile-features/transaction-receipts#rollups-when-fare-capping).\n\nHow does Offline data authentication (ODA) work?\n: The Android-powered mobile device and the payment terminal use certificates to verify the\n authenticity of the card issuer and the card network. However, they can't verify whether the\n card account has an available balance or is under the account's limit. If a card gets declined\n later when the transaction is processed, then we recommend that you add the account to your\n denylist so that no further use is allowed.\n\nHow do I implement ODA?\n: Most large payment networks allow the use of ODA for transit purposes. ODA implementation\n specifications vary by payment network. We recommend that you work with the payment networks to\n understand their requirements for ODA and implement it by their specifications.\n\nHow is data handled on the mobile device?\n\n: Google Wallet uses keys and certificates from the payment network and issuing bank. This\n allows authentication with the payment terminal in offline mode.\n\n The following table describes the keys and certification details used by the\n Android-powered device:\n\n | | Secret | Shared with terminal during tap |||\n | Device | Card Private Key | Network Key ID | Card Certificate (and Public Key) | Issuer Certificate (and Public Key) |\n | | The card's private key remains on the device and is used to authenticate that the device is genuine. | Identifies which network the card belongs to. | Issuer-signed card certificate and public key for Google Wallet. | Each card has a certificate, and corresponding public key, that's signed by the issuer's private key, which is signed by the card network. |\n |--------|------------------------------------------------------------------------------------------------------|-----------------------------------------------|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|\n\nHow does the mobile device communicate with the payment terminal?\n\n: The following diagram shows the specific sequence that allows the Android-powered device and\n the payment terminal to exchange data and authenticate each other.\n\n **Figure 1.** Data exchanged between the user's device and the terminal.\n\n \u003cbr /\u003e"]]
