Autofill checkout with a signed, already-validated shipping address.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
A wallet-verified address arrives already validated and signed, which removes the typo failures outright and makes address fraud considerably more expensive. On marketplaces the same mechanism confirms seller legal name, registry number and VAT status, so a trust badge points at a government record instead of a self-declaration.
01
You request specific attributes
02
The user gets the request by QR or deep link
03
The wallet shows exactly what is asked
04
The user approves on their device
05
The wallet presents the signed credential
06
Authbound verifies the presentation
07
Your backend receives a structured result
08
Your existing workflow continues
Step 01
Put a one-tap option next to manual entry that fills name and shipping address from the wallet.
Step 02
The address comes back as signed structured data rather than free text, so there is no normalisation pass.
Step 03
Use the verification as a strong positive signal and relax friction for verified buyers.
Technical flow
const verification = await authbound.verifications.create({
policyId: 'pol_…', // the claims this flow requests
customerUserRef: user.id,
});
// Your webhook then receives verification.completed
// with the verified result and its audit record.Wallet presents
Terms to know
Regulatory context
PSD2 and SCA where payment is involved, GDPR, eIDAS 2.0
There is no rule that requires address verification at checkout. GDPR applies to whatever you collect, so request only the fields you ship with. When payment is involved, PSD2 strong customer authentication is handled by the payment provider as before.
A marketplace checkout that uses verified identity and address proof to reduce fraud and chargebacks.
What it asks the wallet for
What the business gets back
Cartiva is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
No. A verified identity tells you the buyer is who they say. It does not tell you the card is theirs. Use it to reduce friction for verified buyers rather than to retire your scoring.
You can request any subset the credential supports. Shipping usually needs a name on the parcel, but if yours does not, leave it out and store less.
Business credentials carry legal name, registry number, VAT status and registered address, signed by the relevant registry. The badge then reflects a verified record rather than an uploaded PDF.
Yes. Wallet autofill sits next to manual entry, and shoppers choose.
The fields you requested as structured, signed data, typically name and shipping address. You also get a verification ID to attach to the order.
The verified address is their registered one. For gifts or work deliveries, let them enter a different address manually and treat the order with your normal rules.
Not always. Address is optional in the PID and depends on the member state, so manual entry stays available.
Yes. Verification is the same for every EU wallet, so cross-border shoppers get the same autofill.
They type their address as they do today. Nothing breaks.
Every member state has to offer a wallet by 24 December 2026. Private services that are legally or contractually required to use strong user authentication have to accept it from December 2027 when the user asks. Treat wallet autofill as a growing share of checkouts rather than a switch.
E-commerce
Another wallet flow for E-commerce.
Banking & fintech
The same verify integration, applied to KYC.
iGaming
The same verify integration, applied to age verification.
Built on Authbound Identity Verification. One API key covers every flow you add later.
Tell us what you are trying to build. We will map the user journey, the credentials and the wallet interaction to an implementation.