> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pcibooking.net/llms.txt
> Use this file to discover all available pages before exploring further.

# White Label Email Domain

> Send Card by Link emails from your own domain. DKIM and SPF configuration for branded email delivery.

By default, emails sent by PCI Booking (such as [Card By Link](/capture-cards/card-by-link) requests) come from the `pcibooking.net` domain. You can configure your own email domain so these emails appear to come from your company, increasing trust and reducing the chance of them being flagged as spam.

## Why Use White-Label Emails

When cardholders receive an email asking them to enter payment details, the sender domain plays a major role in whether they trust the message. Emails from an unfamiliar domain are more likely to be ignored, marked as spam, or flagged by corporate email filters.

White-label email addresses this by sending messages from your own domain. Benefits include:

* **Brand trust.** Cardholders see your company name and domain in the "from" address, making them more likely to open the email and complete the card capture.
* **Better deliverability.** Emails sent from a properly configured domain with SPF records are less likely to be caught by spam filters or quarantined by corporate mail gateways.
* **Consistent branding.** Combined with [custom templates](/account-setup/card-by-link-templates), white-label emails give cardholders a fully branded experience from sender address to landing page.

## What Changes for the Cardholder

Once white-label is configured, the cardholder sees your domain in the email "from" address instead of `pcibooking.net`. The email content, links, and card capture page function identically. The secure card capture link still points to PCI Booking's hosted page, keeping card data out of your systems.

## Setup

<Warning>
  Before enabling this feature, contact [support@pcibooking.net](mailto:support@pcibooking.net) and provide the email addresses from your domain for verification. Do not enable white-label emails until you receive confirmation that verification is complete.
</Warning>

### 1. Add SPF Record

SPF (Sender Policy Framework) tells receiving mail servers that PCI Booking is authorized to send emails on behalf of your domain. Add the following to the SPF TXT record of your domain:

```
include:pcibooking.net
```

A complete SPF record might look like:

```
v=spf1 include:pcibooking.net include:amazonses.com ~all
```

### 2. Wait for DNS Propagation

Changes take effect after your domain's TTL (Time to Live) period. If the email domain is not configured correctly, emails fall back to the PCI Booking domain automatically.

### 3. Test

After configuring the SPF record and receiving confirmation from support, send a test Card By Link request. Verify that the email arrives from your domain rather than `pcibooking.net`.

<Info>
  Configuration changes propagate according to the TTL set in your DNS TXT record. Allow sufficient time before testing.
</Info>

## Troubleshooting

If emails are still arriving from `pcibooking.net` after configuration:

* **DNS propagation delay.** SPF record changes can take up to 48 hours to fully propagate, depending on your domain's TTL setting.
* **Incorrect SPF syntax.** Verify your SPF record includes `include:pcibooking.net` and does not exceed the 10-lookup limit imposed by the SPF specification.
* **Verification not complete.** Confirm with PCI Booking support that your domain verification has been finalized on their end.