> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/release-notes/backend/july-2026/july-15.md). # July 15 | Environment | Date | | -------------- | ------------- | | Pre-Production | July 6, 2026 | | Production | July 15, 2026 | ### xPay Enablement #### **Support getTokenInfo for Domestic Payment networks** getTokenInfo API support is added for Domestic schemes as it was available for International Card Schemes. As enhancement FPAN & DPAN has been added to the response of getTokenInfo API. #### **Google Transit : Ping Test between Google and Thales Transit server** To establish and to ensure the connectivity is working fine with Google Server a basic ping API support is added #### **Google Transit : Support provisioning and Enrollment - Push Provisioning and Native Provisioning** **Push Provisioning** \ This feature allows transit issuers to streamline the digitalization of physical transit cards directly from their mobile applications into Google Wallet. By integrating with the D1 Transit platform, issuers can provide users with a frictionless one-tap provisioning **Key Capabilities** * The D1 Transit platform facilitates the generation of encrypted payloads necessary to initiate tokenization with Google, ensuring secure bundle delivery. * The solution supports initial provisioning, retry logic for failed provisioning attempts, and the restoration of existing card accounts. * D1 Transit manages secure timeouts and state tracking. If a provisioning request fails or is not completed within the defined timeframe, the platform automatically notifies the issuer, allowing for timely customer support actions such as re-initiation or account management **Native Provisioning** Native Provisioning allows the transit issuer’s mobile app to act as the primary interface for card digitization. From a D1 Transit scope perspective, our platform serves as the secure backend orchestrator that validates the request, prepares the necessary card data, and manages the tokenization lifecycle with Google, without requiring our own proprietary SDK for the user-facing mobile experience. **Key Capabilities** * Our platform handles the secure data preparation and interaction with Google’s transit provisioning services. It ensures that the card data provided to the wallet is correctly formatted and encrypted according to security standards. * Beyond initial provisioning, the system supports the necessary backend synchronization for card activation, ensuring that the tokenized transit pass is ready for use immediately upon completion. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.payments.thalescloud.io/release-notes/backend/july-2026/july-15.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.