Skip to main content

Cloudflare Integration ☁️

Connect your Cloudflare account to PayRequest and give your customers the power to manage DNS records and set up domain forwarding — all from within their customer portal. No need to share Cloudflare login credentials or handle DNS changes manually.
Who is this for? If you sell domain subscriptions through PayRequest (using OpenProvider for registration), the Cloudflare integration lets your customers manage their domain settings themselves — saving you time and support tickets.

What You Can Do

DNS Management

Your customers can view, add, edit, and delete DNS records for their domain directly from their subscription page. No more back-and-forth emails about DNS changes.

Domain Forwarding

Customers can redirect their domain to any URL — like a social media page, a new website, or a landing page. Everything is handled through Cloudflare’s redirect system.

Admin Dashboard

As a business owner, you get a full Cloudflare management panel in your dashboard. View all zones, manage DNS records, and configure forwarding for any domain.

Automatic Setup

When customers set up forwarding, the required DNS records are created automatically. No manual configuration needed.

Getting Started

Prerequisites

Before connecting Cloudflare, make sure you have:
  • A Cloudflare account (sign up free)
  • An active OpenProvider connection and domain subscriptions in PayRequest
  • Your Cloudflare Account ID; PayRequest can create a zone when a customer chooses managed DNS
  • An API token with the right permissions

Step 1: Create a Cloudflare API Token

1

Go to your Cloudflare dashboard

Log in at dash.cloudflare.com and click on your profile icon in the top right corner.
2

Navigate to API Tokens

Go to My Profile → API Tokens → Create Token
3

Set up permissions

Create a custom token with the following permissions:Scope the token to the Cloudflare account you connect. Automatic setup needs permission to create zones in that account and manage newly created zones. A token restricted to a fixed list of existing zones may not cover new registrations.A successful connection test does not prove every action is permitted. If zone creation reports a missing account.zone.create permission, update the token’s zone-creation access for the selected account. Forwarding also needs Zone Rulesets: Edit.
4

Copy your token

Click Continue to summary → Create Token. Copy the token — you’ll only see it once!
Keep your token safe! Store it somewhere secure before closing the page. Cloudflare only shows the token once. If you lose it, you’ll need to create a new one.

Step 2: Find Your Account ID

Your Account ID is visible on your Cloudflare dashboard:
  1. Go to dash.cloudflare.com
  2. Click on any domain
  3. Look in the right sidebar under API — you’ll see your Account ID
  4. Copy it
Your Account ID is also visible in the URL when you’re on your Cloudflare dashboard: dash.cloudflare.com/ACCOUNT_ID_HERE

Step 3: Connect in PayRequest

1

Open the App Store

In your PayRequest dashboard, open Services & integrations → Cloudflare.
2

Add your credentials

Click Add Cloudflare Integration and enter:
  • Account ID: The ID you copied from Cloudflare
  • API Token: The token you just created
3

Sync your zones

After connecting, PayRequest will automatically sync all your Cloudflare zones (domains). You’ll see them listed on the Cloudflare management page.
4

Verify the connection

Click Test Connection to make sure everything is working. You should see a green “Connected” badge.

Managing DNS Records

Once connected, DNS management is available for a domain subscription linked to a zone in your connected Cloudflare account. Customers can prepare records while a zone is still waiting for nameserver activation. Those settings become public after the domain uses the assigned nameservers and DNS activates.

DNS choice when ordering a domain

For a new domain, checkout offers: The managed option uses your business name and appears when your Cloudflare integration is available. Nameservers are assigned per zone: do not promise the same pair for every domain. Automatic setup adds only DNS records explicitly configured for the domain product. It does not guess a hosting IP, create mailboxes or invent mail settings. A newly registered domain can therefore have an empty DNS zone. Customers can add records or configure website forwarding later. PayRequest checks pending Cloudflare activation every five minutes. Public DNS caches can take longer to reflect a nameserver change. Existing orders and domains using external DNS are not automatically switched.

Switching an existing domain to managed DNS

An authorized customer can open My services → domain → Domain and choose Prepare DNS and forwarding when the domain is active at OpenProvider and your Cloudflare integration is available.
  1. Preparation creates or reuses the Cloudflare zone without changing the current nameservers.
  2. The customer uses DNS to copy existing website, mail and subdomain records, or uses Forwarding to prepare a redirect.
  3. Review nameserver switch shows current and assigned nameservers and the prepared record count.
  4. The customer confirms that the needed records are complete or not required, then chooses Switch nameservers now.
An empty zone is allowed, including for a domain that does not yet have a website or email. Existing records are not automatically imported from the previous DNS provider. The customer must copy any settings they need before switching. If registry DNSSEC is still enabled, the switch is blocked. Disable the existing DNSSEC first, review the switch again, and enable managed DNSSEC again after activation. A preview expires after ten minutes; changes to DNS or nameservers require a fresh preview. The portal shows progress on the switch button and the result in the Domain tab. PayRequest reads back the registrar’s nameservers before confirming success. If the result is unclear, refresh the preview to check the current state rather than repeatedly submitting the switch.

For Business Owners (Admin Dashboard)

From the Cloudflare app page in your dashboard:
  1. Find the domain in Your Zones
  2. Click Manage DNS to view all DNS records
  3. Edit or delete existing records
  4. Add new records as needed

For Your Customers (Customer Portal)

Your customers will automatically see a DNS tab on their domain subscription page. From there, they can:
  • View all DNS records for their domain
  • Add new records (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA)
  • Edit existing records — change the content, TTL, or proxy settings
  • Delete records they no longer need
  • Refresh to see the latest state from Cloudflare
The primary customer and enabled customer administrators or operations contacts can change DNS and forwarding. Billing and viewer contacts have read-only DNS access. Every change checks ownership and permissions again.

Google Workspace mail template

In the customer DNS tab, choose Google Workspace → Preview mail settings → Apply Google Workspace template. The template uses Google’s current MX setup: MX @, priority 1, destination smtp.google.com, TTL Auto. It also adds TXT @ v=spf1 include:_spf.google.com ~all if no SPF record exists.
  • Existing Google MX records, including working legacy aspmx records, are kept.
  • MX records for another mail provider are listed for replacement and require explicit customer confirmation. Incoming mail will then go to Google Workspace.
  • Existing SPF is preserved. If it does not authorize Google, the portal asks the customer to review it alongside other mail senders. The template does not add a second SPF record.
  • Website records, subdomain MX, verification TXT, DKIM and DMARC records are preserved.
Domain verification and DKIM need values from the customer’s own Google Admin console. Add those TXT records separately and finish Gmail and DKIM activation there. Applying the template does not create a Google Workspace subscription or mailbox.
DNS changes are applied through Cloudflare’s network and typically take effect within minutes, though full global propagation can take up to 48 hours.

Domain Forwarding

Domain forwarding lets your customers redirect their entire domain to another URL. This is one of the most requested features for domain customers.

Common Use Cases

  • Social media redirect: Forward mybrand.com to instagram.com/mybrand
  • Website migration: Redirect an old domain to a new one
  • Short URL: Use a short domain as a branded redirect to a longer URL
  • Coming soon: Point a domain to a temporary page while a website is being built

How It Works

1

Customer opens their subscription

From the customer portal, your customer navigates to their domain subscription and clicks the Forwarding tab.
2

Enter the target URL

They enter the URL they want their domain to forward to — for example, https://www.instagram.com/mybrand.
3

Choose redirect options

  • Redirect Type: Permanent (301) or Temporary (302)
  • Preserve Path: If enabled, domain.com/about forwards to target.com/about
  • Preserve Query String: If enabled, domain.com?ref=abc forwards to target.com?ref=abc
4

Save and done

Click Set Up Forwarding. PayRequest automatically:
  1. Creates the required DNS record for Cloudflare to handle the redirect
  2. Sets up the redirect rule in Cloudflare
  3. Shows a confirmation with the active forwarding details
For a domain that still uses external DNS, forwarding can be prepared before the switch. Complete the nameserver switch from the Domain tab and wait for activation before expecting the redirect to work publicly. Saving forwarding can replace an existing root A record; review the warning if that record currently serves a website. Share the step-by-step domain guide with your customers.

Redirect Types Explained

Not sure which to pick? Use Permanent (301) if the redirect will stay forever (like forwarding to a social media page). Use Temporary (302) if you plan to use the domain for something else later.

Managing Forwarding as a Business Owner

You can also manage forwarding from the admin Cloudflare dashboard:
  1. Go to Services & integrations → Cloudflare
  2. Find the zone in Your Zones — domains with active forwarding show a purple Forwarding badge
  3. Click Edit Forwarding to change settings, or Set Up Forwarding to configure a new one

What Your Customers See

When a customer has a domain subscription and the domain is managed in Cloudflare, their subscription page gets extra tabs:
Shows domain information: domain name, expiry date, nameservers, authorization code, and auto-renewal status. This tab is always available for domain subscriptions.
A full DNS record table where customers can view, add, edit, and delete records. Uses a clean table layout with record type badges, proxy status indicators, and action buttons.
A simple form to set up or manage domain forwarding. Shows the current forwarding status (active or not configured), the target URL, and all forwarding options.
The DNS and Forwarding tabs appear for linked active or pending Cloudflare zones. For an eligible domain with external DNS, customers can prepare a zone from the Domain tab first. Preparing settings does not make them public before nameserver activation.

Troubleshooting

This means your Cloudflare API token is missing the Zone Rulesets: Edit permission. DNS features will still work, but forwarding requires this extra permission.Fix: Go to your Cloudflare dashboard → My Profile → API Tokens → edit your token → add Zone Rulesets: Edit permission.
These tabs only show when:
  1. The subscription is for a domain product
  2. The domain has a domain registration linked to it
  3. The domain exists as an active or pending zone in your connected Cloudflare account
  4. Your Cloudflare integration is connected and active in PayRequest
Check each condition. Sync existing zones from the Cloudflare app page, or let an eligible customer choose Prepare DNS and forwarding in the Domain tab.
  • Double-check your API token — make sure you copied the full token
  • Verify the Account ID — it should match what’s in your Cloudflare dashboard URL
  • Check token permissions — automatic setup needs zone-creation access in the selected account, DNS: Edit, and Zone Rulesets: Edit for forwarding
  • Token expired? — Cloudflare tokens can have expiry dates. Create a new one if needed.
Click Refresh Zones on the Cloudflare management page. If zones still don’t appear:
  • Make sure your domains are added to Cloudflare
  • Check that the API token has access to the correct zones
  • Check the zone’s status; pending zones can be prepared, but need their assigned nameservers before activation

Best Practices

Use Descriptive Token Names

Name your Cloudflare API token something like “PayRequest Integration” so you can easily find it later in your Cloudflare dashboard.

Limit Token Scope

Only give the token access to the zones you manage through PayRequest. This follows the principle of least privilege and keeps your other domains safe.

Monitor Forwarding Usage

Check the Cloudflare dashboard for zones with active forwarding. The purple “Forwarding” badge in PayRequest makes it easy to see which domains have redirects configured.

Educate Your Customers

Let your customers know they can manage DNS and forwarding themselves. This reduces support requests and gives them more control over their domains.

App Store

Manage all your integrations

Customer Portal

Learn about the customer experience

Subscriptions

Set up domain subscriptions

Quick Access: Manage your Cloudflare integration anytime from Settings → App Store → Cloudflare in your PayRequest dashboard.