> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Apple Pay domain verification failed

The Apple Pay domain association file may be missing, incorrectly configured, or returning an error.

---

## Example

```json
{
  "error": {
    "type": "request_error",
    "code": "checkout_domain_apple_pay_domain_verification_failed",
    "detail": "Domain verification failed. Make sure the Apple Pay domain association file is publicly accessible at the top-level of your domain, and returns at 200.",
    "documentation_url": "https://developer.paddle.com/errors/checkout-domains/checkout_domain_apple_pay_domain_verification_failed"
  },
  "meta": {
    "request_id": "00000000-0000-0000-0000-000000000000"
  }
}
```

## Details

| Attribute | Value |
| --- | --- |
| Status code | 400 |
| Error code | `checkout_domain_apple_pay_domain_verification_failed` |
| Error message | Domain verification failed. Make sure the Apple Pay domain association file is publicly accessible at the top-level of your domain, and returns at 200. |

## Common causes

- The domain association file is not hosted at the correct URL.
- The file returns a non-200 status (e.g. 404, 500).
- The request to the file is redirected to another URL.
- The file is not accessible to the Apple Pay servers.

## Common solutions

- Download the Apple Pay domain association file from [the developer docs](https://developer.paddle.com/concepts/payment-methods/apple-pay#enable-payment-method-one-click) and upload to your web server.
- Check that your file is served at /.well-known/apple-developer-merchantid-domain-association. For example, if your website is example.com, make the file available at https://example.com/.well-known/apple-developer-merchantid-domain-association.
- Make sure your domains aren't behind a proxy or redirect, and they're publicly available to the [Apple Pay servers](https://developer.apple.com/documentation/apple_pay_on_the_web/setting_up_your_server#3179116).