> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/roadmap/module-4-identity-and-payments.md). # Module 4 — Identity and payments Connecting a service to the identity block and the Payments block, and why neither is built twice **Written for:** the team that configures the service (Architect register). **Videos:** 6. **What it teaches.** Connecting a service to the identity block and the Payments block, and why neither is built twice. **What you can do afterwards.** Connect a service to the identity block and to the Payments block instead of building either again. **What is built.** Configurations I1 to I7 and P1 to P7 ## Subtopics | # | Subtopic | Class | Demonstration | Single message | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ----- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [4.1](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.1-why-identity-is-built-once.md) | Why identity is built once | Core | — | An identity system is costly to build and to run, so a country builds it once and every service uses it, and a ministry that builds its own pays those costs a second time. | | [4.2](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.2-the-published-identity-block-and-what-the-identity-authority-offers-today.md) | The published Identity block, and what the identity authority offers today | Core | — | The published Identity block verifies who a person is, releases only what that person approves and issues no learner identity, so check what your identity authority really offers before you plan on it. | | [4.3](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.3-generating-the-identity-connection.md) | Generating the identity connection | Core | Yes | A service connects to the identity block as its registered client, asks only for what it needs, and keeps the identifier the block gives to that service, never the national number. | | [4.4](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.4-the-payments-block-and-the-payment-systems-behind-it.md) | The Payments block and the payment systems behind it | Core | — | The Payments block is not a new payment system: it connects government programmes to the payment systems your country already has, so every programme pays through one shared connection. | | [4.5](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.5-generating-the-payment-connection.md) | Generating the payment connection | Core | Yes | To pay through the block you configure the sender, the programme, the beneficiary, the payment and the route for its status, and the proof is one test payment whose status comes back. | | [4.6](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.6-reuse-is-the-return-on-planning.md) | Reuse is the return on planning | Core | — | Learner registration reuses the identity block and the scholarship payment reuses the Payments block, a saving visible only to someone who plans for the whole government, because inside one project building your own looks quicker. | {% hint style="info" %} The reference pages hold what every module uses: [the nine steps](/experience-digital-transformation/roadmap/the-nine-steps.md), [the assessment toolkit](/experience-digital-transformation/roadmap/the-assessment-toolkit.md), [the worked examples](/experience-digital-transformation/roadmap/the-worked-examples.md), [the build plan](/experience-digital-transformation/roadmap/the-build-plan.md), [the frameworks and standards](/experience-digital-transformation/roadmap/frameworks-and-standards.md), [the glossary](/experience-digital-transformation/roadmap/glossary.md) and [the figures](/experience-digital-transformation/roadmap/figures.md). {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/roadmap/module-4-identity-and-payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.