Digital Wallet Platform: turn a document into a pass the customer can carry
A membership, warranty or other approved document is more useful when the customer can find the important details at the moment they need them. The Digital Wallet Platform is designed as a workflow for extracting document information, preparing a branded pass and delivering it to the intended cardholder.
This is a document-to-pass use case. It is not a payment wallet, a cryptocurrency product or a claim that a digital pass replaces the authority of the original issuer.
Begin with a defined document category
The workflow starts with upload of a PDF or image and preparation of a branded card preview for Apple Wallet and Google Wallet. Confirm the supported pass category, issuer requirements and production configuration for your intended use before rollout.
Choose one document type first. Identify the fields the cardholder needs, the source of each value and how the information will be reviewed. A document can contain several dates or reference numbers, so extraction needs a clear definition of which one belongs on the pass.
FI Digital UK / Workflow
Digital Wallet Platform
Illustrative workflow, not a product screenshot or a claim about a client’s production architecture.
Step 5 of 5Resolve with the owner (Needs correction)
Keep scrolling to follow the flow
- Choose a representative taskStep 1
- Review the current productStep 2
- Review and authoriseDecision point
- Agree production responsibilitiesOutcome: Accepted
- Resolve with the ownerOutcome: Needs correction
Make the UK operating requirements explicit
Separate the UK organisation’s requirements from any wider group template. Identify the legal entity, business owner, connected accounts and the people authorised to accept the result. If the workflow relies on financial or employment rules, your qualified advisers should confirm the applicable settings and obligations; software configuration alone does not establish compliance.
Confirm the current local product offer, supported version and commercial terms with FI Digital before planning production use. The group product description does not imply identical availability, hosting or support arrangements in every market.
Review the extracted details
Check names, identifiers, dates and any barcode or reference used by the receiving process. Include poor-quality images and unusual layouts in evaluation. An attractive preview can still contain an incorrect value; visual polish is not evidence of accurate extraction.
The card should not imply rights or validity beyond what the issuing organisation has authorised. A warranty summary, for example, needs to preserve the distinction between convenient access to information and the underlying terms or status held by the issuer.
Confirm delivery and lifecycle behaviour
The intended delivery step emails a link to the cardholder so the pass can be added to the relevant wallet. Validate the actual issuance and add-to-wallet process on supported devices. A visual preview is not proof that a production pass can be issued correctly.
Agree how changes, expiry, revocation and support are handled for the selected use case. Confirm current capabilities rather than promising every lifecycle feature. A pass that contains stale information can create confusion even when the initial delivery worked.
Protect the document and recipient information
Review upload access, processing, storage, retention and delivery with the responsible owners. Use synthetic documents for the first walkthrough. Avoid unnecessary sensitive fields on the pass and confirm who is entitled to receive it.
Request a Digital Wallet Platform walkthrough with FI Digital. Bring one document category and the customer interaction it should improve, then evaluate a complete, approved issuance journey.
Scope and responsibilities
Confirm the current product version, local availability, supported integrations and information-handling arrangements in the walkthrough. No universal price, hosting location or service level is implied.
Frequently asked questions
001Is this a payment or cryptocurrency wallet?
No. This page describes preparing and delivering wallet passes from approved document information. It does not describe holding money, transferring funds or managing cryptocurrency. The distinction matters when evaluating the product: the intended outcome is convenient access to a supported pass, subject to the issuer's authority and the selected wallet platform's requirements.
002Does a wallet preview prove that a pass is ready for production?
No. Validate the complete issuance, signing and add-to-wallet process for the supported category and devices. Confirm the required accounts and issuer configuration. A visual preview helps review content and design, but it is not evidence that a production pass is valid, deliverable or supported throughout its intended lifecycle.
003Which types of documents can be used?
PDFs and images provide the starting material for document-to-pass workflows. Confirm the specific category, layout and issuer requirements you need. Do not assume every identity, travel or financial document can be converted into an officially accepted pass. Start with a use case your organisation is authorised to issue and maintain.
004Can extracted fields be wrong?
Yes. Poor images, unfamiliar layouts or ambiguous labels can lead to incorrect extraction. Review important fields before issuance and test representative exceptions. A formatted card can make an error appear authoritative, so content validation is essential. The first pilot should measure correct extraction and correction effort rather than only the speed of generating previews.
005Does the pass replace the original document?
Not automatically. Its authority and purpose depend on the issuer, document category and relevant acceptance process. The pass should state or preserve the appropriate relationship to the original record. Do not imply that a convenient digital summary changes contractual rights, official status or validity beyond what the authorised issuing organisation has established.
006Can passes be updated or revoked later?
Confirm the current product's supported lifecycle functions and the relevant wallet-platform behaviour for your use case. Include expiry, changed details, revocation and support in the assessment. Do not infer those capabilities from a successful first issuance. The operating process needs a clear owner for keeping customer-facing information accurate after delivery.
007How is the correct recipient verified?
Define the authorised source for the cardholder's identity and delivery address, then test mismatches and correction. Review what the delivery link permits and how access is controlled in the current deployment. Sending an email successfully does not establish that the intended person received or was entitled to the information it contains.
008What should we bring to a walkthrough?
Bring one document type, the fields needed on the pass and the customer action it should support. Use synthetic or approved redacted examples. Identify who can authorise issuance and maintain the information. The walkthrough should confirm current functionality, platform dependencies and handling arrangements before real documents or cardholder details are connected.
Request a product walkthrough
Request a product walkthrough→Tell us about your project
We use the information you provide to respond to this enquiry. Read our Privacy Policy.