Set up Verify with Wallet on the Web in Apple Business Connect
Websites that require age or identity verification can use the Verify with Wallet on the Web API to quickly and securely verify a person’s information using their ID in Apple Wallet.
For more information, see the WWDC25 session, Verify Identity documents on the web.
Streamline your verification process
Verify with Wallet on the Web lets people share information from their ID in Apple Wallet and other third-party Wallet apps for an easier and faster verification experience with your website. Instead of requiring cumbersome activities, such as scanning documents or taking selfies, websites can reduce friction and abandonment by letting people complete verification with a user-friendly and simple experience.
Verified and authenticated identity data
Identity information that your website gets using Verify with Wallet on the Web is verified by an issuing authority. For example, a state department of motor vehicles. To add an ID to Apple Wallet, the user needs to prove ownership of a valid ID. During this proofing process, the issuing authority confirms that the user’s ID card is authentic and belongs to that user. Additionally, to present their ID information to your website, the user needs to authenticate with the same Face ID or Touch ID that they originally used to add the ID to Apple Wallet.
Preserving user privacy
When you integrate with Verify with Wallet on the Web, you disclose the identity information your website requests and for how long. Your website then receives permission to request only the specific data required to address your use case. This prevents users from having to overshare their identity information. Neither the state issuing authority nor Apple can see when and where a user shares their ID.
Before you begin
Consider these best practices before you set up Verify with Wallet on the Web for your brand:
Ask for only data you need: People may lose trust in the experience if you ask for more data than you need to complete the current verification. For example, if you need to ensure that a customer is at least a minimum age, use a request that specifies an age threshold; avoid requesting the customer’s current age or birthdate.
Ask for identity information only at the precise moment you need it: People can be suspicious of a request for personal information if it doesn’t seem to be related to their current action. If your website needs identity verification, for example, wait to ask for this information when people are completing the process or transaction that requires it. For example, don’t request verification before people are ready to start the process or when they’re simply creating an account.
Clearly indicate whether you will keep the data and—if you need to keep it—specify how long you’ll do so: To help people trust your website, it’s essential to explain how long you might need to keep the personal information they agree to share with you. When you specify a duration—such as a particular period, indefinitely, or only as long as it takes to complete the current verification—the system automatically displays explanatory content in the verification sheet.
Provide a button that initiates the verification process: Use a label like Verify Age on a button that performs a simple age check, or Verify Identity for a more detailed identity data request. Don’t include the Apple logo in any button label. See the table below for examples.
Button label | Example usage |
|---|---|
Verify Age | Your website can complete the current transaction after you verify a person’s age. For example, the transaction is age-restricted deliveries. |
Verify Identity | Your website can complete the current transaction after you verify a person’s identity. For example, the transaction is a car rental. |
Requirements
Verify with Wallet on the Web requires iOS 26 on an iPhone 11 or later.
Availability
The following Apple Business Connect categories can use Verify with Wallet on the Web:
Services:
Financial
Government
Rentals:
Car
Scooter
Purchases:
Alcohol purchases (order ahead and delivery)
Access (physical security)
Air travel
Gig economy
Healthcare
Hospitality
Insurance
Ticketing
About the request form
You need to complete a permissions request form that lets Apple know what type of verification you require, and what goods or services your business offers that require that type of verification.
Verification types
Age verification, which can be any of the following:
Age over N flag: Verifying whether the user is over a specific age (for example, over 21).
Age in years: Verifying whether the user is a specific age (for example, exactly 40 years old).
Issuing authority: Identifying the government entity (for example, state, province, or country) that issued the ID.
ID photo: Verifying the user’s physical appearance.
Identity verification, which can be any of the following as it appears on a person’s ID:
Given name: The user’s first name.
Family name: The user’s last name or surname.
Address: The user’s residential address.
Date of birth: The listed birthdate for the user.
Eye color: The listed eye color.
Hair color: The listed hair color.
Height: The listed height
Weight: The listed weight.
Sex: The listed sex.
Organ donor status: Whether the user is registered as an organ donor.
Veteran status: Whether the user is recognized as a veteran.
Document number: The unique number assigned to the ID by the issuing authority.
Document issue date: The date the ID was issued.
Document expiration date: The date the ID expires.
Driving privileges: The types of vehicles the user is licensed to drive.
DHS compliance (Real ID): Whether the ID complies with U.S. Real ID requirements.
Usage information
You need to describe the following:
The good or service you offer through your website that requires age or identity verification.
The current process your website uses to verify age or identity.
Issuing authority certificates
To verify a payload from a user’s state issuing authority, you need to download and use its IACA certificate from their website.