Signing up for an online service often means entering the same personal details again, uploading an ID photo and waiting for someone to verify it. A week later, another provider asks for exactly the same information. BG Wallet is designed to make this process simpler and more secure by giving people a digital identity they can use from their phone.

For businesses, the interesting part is not the mobile app itself. It is the ability to connect a digital identity wallet to websites, customer portals and internal systems, reducing repeated checks, document uploads and manual data entry.

What is BG Wallet?

BG Wallet is Bulgaria’s implementation of the European Digital Identity Wallet (EUDI Wallet). EU Member States will provide interoperable wallets under a common framework so that people can use verified identity information with compatible services across borders.

A digital wallet is not simply a picture of an ID card. It can present verifiable digital credentials, allowing a service provider to check who issued the information and whether it remains valid. When supported, a service that only needs to confirm that someone is over 18 could ask for proof of age without collecting their address or other unnecessary personal details.

What will people be able to do with it?

The main uses are online identification, presenting digital credentials and electronic signing. For example, a user may identify themselves to a service, provide an officially issued credential or sign a document when the applicable law and service support that process.

Not every document and service will be available on day one. Each use case depends on organisations issuing suitable credentials and service providers accepting them. The wallet will not automatically replace every physical document or legally required in-person procedure.

When is BG Wallet expected in Bulgaria?

On 18 November 2026, Bulgaria’s Council of Ministers approved a draft law for the European Digital Identity Wallet, and the Ministry of Innovation and Digital Transformation announced wallet.gov.bg, the official information website. The ministry said deployment would be gradual.

As of 20 November 2026, no exact public launch date for the Bulgarian app has been officially confirmed. Further development is expected in 2027. Launch dates and sandbox announcements for wallets in other countries should not be mistaken for confirmed Bulgarian availability.

What could an actual business integration look like?

Consider a customer portal used to apply for a service. Today, a staff member might receive an identity document by email, check the details and copy them into the CRM. With a wallet integration, the steps could look different:

  1. The portal requests the particular identity attributes needed for the service.
  2. The user sees which organisation is requesting them and why, and decides whether to share them.
  3. The system validates the credential, including its issuer and validity.
  4. The result reaches the CRM. If the process only needs a verified age flag, the business need not automatically retain a full ID document.

This is an illustrative workflow based on the European architecture, not a demonstration of a live Bulgarian app. A useful integration starts with the business process, not a new login button.

Where can businesses benefit?

Online retail and age verification

When a product or service has age restrictions, a retailer may be able to request proof of adulthood rather than an ID scan. The verification must still meet any applicable sector-specific legal requirements.

Banks, insurers and financial services

Digital onboarding often involves document uploads, forms and multiple checks. Verified wallet data may simplify parts of that journey and feed existing onboarding systems. It will not automatically replace KYC or anti-money-laundering obligations. Financial institutions must assess which requirements a particular credential actually satisfies.

CRM, ERP and contract workflows

Businesses with large numbers of applications and customer files may benefit from using validated information to populate records and route contracts to electronic signing workflows. This is particularly useful when the current process moves through emails, spreadsheets and manual re-entry.

Not every service needs strong identity verification. If an email address is sufficient, introducing a wallet might add unnecessary friction. The real value appears when a business genuinely needs to establish identity or verify a particular fact.

Can an ordinary company integrate BG Wallet?

Yes. The European framework expressly includes private-sector service providers. Organisations that request and verify information from the wallet are known as relying parties. They can include retailers, platforms and other digital services, not only banks or government agencies.

A relying party must register under the relevant national procedure, specify the purposes for which it uses credentials and declare which data it intends to request. The European rules also provide mechanisms for a wallet to identify the organisation making a request.

Registration is not merely administrative. A business still needs a lawful basis for processing personal data, data minimisation, security controls and correct credential verification. A user approving a request in their wallet does not, on its own, remove GDPR obligations.

At the time of writing, the EU-level rules are available, but final public instructions for Bulgarian business registration and external sandbox access have not been confirmed. Having European standards does not mean that a public BG Wallet API is already open to every company.

Do businesses need to become qualified trust service providers?

No, not simply to receive and verify wallet credentials. Qualified Trust Service Providers (QTSPs) deliver particular regulated trust services, such as services relating to qualified electronic signatures and certificates. A customer portal that uses the wallet for identification normally acts as a relying party, not as a QTSP.

Likewise, a software company building the integration does not automatically need QTSP status. Its job is to implement the connection and the necessary business logic for the customer.

What does the technical integration involve?

The European Commission provides an Architecture and Reference Framework and reference implementations. Important protocols include OpenID4VP for presenting credentials and OpenID4VCI for issuing them. A service provider that only verifies credentials will focus primarily on requesting, receiving and validating presentations.

The harder questions come after the first successful demo. What happens if a user declines, a credential is invalid or the service is temporarily unavailable? Which details must be retained, for how long and with what audit evidence? A production-ready integration must answer those questions, rather than simply add a “Sign in with BG Wallet” button.

What can a company prepare today?

Start by finding the points where customers currently send copies of identity documents, repeat information or wait for manual checks. Define what the service actually needs to establish: identity, age, authority to act on behalf of an organisation or something else. Only then choose the technical approach.

If you already operate a customer portal, CRM or ERP, you may be able to prepare the part that receives verification results. This does not replace integration tests with the Bulgarian wallet, but it makes future implementation easier once the national requirements and access procedures are published.

How can Sirius Software help?

Sirius Software develops custom business software and integrations between digital platforms, CRM and ERP systems. For BG Wallet, our starting point is a practical question: which customer or internal workflow are we trying to simplify? We can then assess the necessary credentials, data handling and integration architecture.

We can help with process analysis, technical design and preparing existing systems for future wallet connectivity. A live BG Wallet integration will depend on the official Bulgarian registration rules and technical access becoming available.

If your service relies on identification, documents or remote signing, send us a short description of the current workflow. We can help assess whether BG Wallet has a real business case, or whether a different solution fits better. Contact Sirius Software.

Official sources

Information checked on 20 November 2026: Bulgarian ministry announcement, BG Wallet website, Bulgarian draft law, Regulation (EU) 2024/1183, relying-party registration rules and EUDI Wallet technical architecture.