Verify with Wallet on the Web FAQ
Use this page to troubleshoot any issues you have with Verify with Wallet on the Web.
How can I test my integration with the API?
On an iPhone, install the Wallet and Apple mDL Developer Integrator profile, which provides mock data with a real device signature (but no issuer signature for testing). For more information, see Wallet and Apple mDL Developer Integrator Profiles and Logs on the Apple Developer website.
What is the difference between the ISO 18013-5 and AAMVA namespaces?
The ISO 18013-5 specification supports namespaces that enable diverse element sets within identity documents, with standard elements under the org.iso.18013.5.1 namespace. The AAMVA namespace includes additional data specific to U.S. driver’s licenses. For more information, see the Mobile Driver’s License Implementation Guidelines, Version 1.5 on the American Association of Motor Vehicles Administrators website.
What is an IACA certificate, and which should I support?
An IACA certificate is the root of trust verifying an identity document’s valid issuer, such as a department of motor vehicles (DMV). The Verify with Wallet on the Web API requires that your server trust these specified IACA certificates for authentication. For more information, see Issuing authority certificates.
How do I identify the issuer of an identity document?
Request the issuing authority element or use the corresponding IACA certificate to determine the issuer, such as a state’s DMV. There is no mechanism to detect the document provider app.
When should I update or resubmit my request form for using Verify with Wallet on the Web?
Update the request form to inform Apple if your business (which already has permissions) plans to broaden the use of ID verification on your website under any of these conditions:
You plan to extend verification to additional business needs or user groups.
You intend to conduct verification in new geographic regions or enterprise environments that have legal compliance standards.
You want to apply verification to new categories of goods or services.
You require access to more data elements due to business requirements or legal compliance standards.
Is it possible to remove a domain that currently has an active certificate?
To remove a domain with an active certificate, you first need to revoke the certificate associated with the domain, and then you can proceed to delete the domain from your app. Keep in mind that removing the domain requires you to verify the domain again with a new TXT record.
Is it possible to remove a brand if it currently has an active certificate?
To remove a brand with an active certificate, you first need to revoke the certificate, and then you can proceed to remove the brand from the Brands tab.
Important: Any features (like Branded email) that link to the brand no longer display the brand after removal.
Why isn’t the new logo for my brand visible on the user’s device during the ID verification process?
After installing the Verify with Wallet on the Web certificate on your website, if your brand name and logo aren’t appearing on a user’s iPhone, ensure the device is properly connected to the internet using Wi-Fi or a cellular connection. It may take up to 24 hours for the brand to appear. If you continue to encounter issues, contact Apple Business Support for assistance. For more information, contact Apple Business Connect Support.
What is the timeframe for a certificate revocation to complete?
Certificate revocation may take up to 48 hours. After this period, Verify with Wallet on the Web is no longer available on your website.
I received an email from Apple Business Connect about a domain issue. What steps should I take?
Apple regularly checks for a TXT record in your domain’s root directory to confirm ownership and to identify potential security threats. If Apple finds any issues, you receive a notification by email. You also receive reminders before any revocation occurs.
For critical issues, which indicate significant security vulnerabilities, you have 7 days to resolve the issue. If necessary, consult a developer in your company. If the issue remains unresolved after 7 days, Apple revokes the certificate to maintain security.
For noncritical issues, you have 60 days to resolve the issue. If the issue remains unresolved after 60 days, Apple revokes the certificate to maintain security.