Monthly revenue comparison showing current month vs last month with interactive chart

``` ## Security Best Practices ### ✅ Do's * **Use descriptive paths** that indicate the purpose * **Monitor analytics** for unusual activity * **Deactivate old campaigns** to prevent confusion * **Test links** before launching campaigns * **Use tags** to track campaign performance * **Set after-payment redirects** for better customer experience * **Use access codes** for links shared publicly that should only work for a specific audience ### ❌ Don'ts * **Don't use paths** that could be guessed (avoid "test", "temp") * **Don't share inactive links** (they'll return 404) * **Don't change paths** during active campaigns (breaks existing shares) * **Don't delete links** with important analytics history * **Don't use generic names** like "link1", "payment2" ## Troubleshooting ### Smart Link Returns 404 **Causes:** 1. Link is inactive (check status badge) 2. Path was changed recently 3. Business handle doesn't match 4. Link was deleted **Solutions:** * Verify link is **Active** in smart links list * Check path spelling (case-sensitive) * Confirm business handle in Settings → Payment Page ### Analytics Not Updating **Check:** 1. Payment completed successfully (check Transactions) 2. Customer paid within same session (session timeout = 2 hours) 3. Smart link ID appears in transaction details **Manual verification:** Navigate to transaction detail page and check "Smart Link" field. ### QR Code Not Scanning **Fixes:** 1. Increase QR code size (minimum 2cm × 2cm for print) 2. Ensure high contrast (black QR on white background) 3. Test with multiple QR scanner apps 4. Regenerate QR code if image is corrupted ### Wrong Amount Showing **For Amount Links:** * Amount is fixed based on smart link configuration * Edit smart link to change amount * Clear browser cache and revisit URL ### Payment Page Shows Wrong Title **Cause:** Session data not loading correctly **Fix:** 1. Clear browser cookies 2. Open link in incognito/private mode 3. Verify smart link description is set ## Examples Library ### Donation Campaign ``` Name: Monthly Donor Program Type: Amount Link Amount: €10.00 Path: monthly-donation URL: https://payrequest.me/charity/monthly-donation ``` ### Event Ticket ``` Name: Tech Conference 2025 Type: Amount Link Amount: €149.00 Path: techconf-2025 After Payment: https://techconf.com/thank-you URL: https://payrequest.me/events/techconf-2025 ``` ### Product Promotion ``` Name: Premium Bundle Sale Type: Product Link Product: Premium Bundle (ID: 1814) Path: premium-bundle Tags: Summer Sale, Products URL: https://payrequest.me/shop/premium-bundle ``` ### Service Deposit ``` Name: Web Design Deposit Type: Amount Link Amount: €500.00 Path: design-deposit Description: 50% deposit for web design project URL: https://payrequest.me/agency/design-deposit ``` ### Security Deposit (Authorization Hold) ``` Name: Airbnb Deposit March 2025 Type: Product Link (Deposit product) Product: Airbnb Borg (€500, 14-day hold) Path: airbnb-borg-march Description: Security deposit for your Airbnb stay URL: https://payrequest.me/hosting/airbnb-borg-march ``` **How it works:** * Customer pays with credit card → €500 is held (not charged) * After checkout inspection → capture €75 for damages or release full amount * Open **Security Deposits** in the dashboard to manage the hold. Click the underlined customer name or **View**, then choose **Capture Full Amount**, **Partial Capture** (if enabled), or **Release Hold** when funds are reserved. * With Stripe, a partial capture is final: capturing €75 from €500 releases the other €425. You cannot capture another amount from the same authorization later. * Customer gets a branded status page to track their deposit See [Security Deposits →](/payment-processing/security-deposits) for full documentation. ### Limited Workshop with SMS Delivery ``` Name: Photography Workshop March 2025 Type: Amount Link Amount: €89.00 Path: photo-workshop-march Payment Limit: Multiple times - 20 Delivery: Select customer → Email + SMS Tags: Workshops, March 2025 URL: https://payrequest.me/studio/photo-workshop-march ``` **Customer receives:** * Email: Professional branded invitation with link * SMS: "Hi John, your photography workshop link: payrequest.me/studio/photo-workshop-march" **Dashboard shows:** * Delivery: Email + SMS badges * Sent at: Mar 1, 2025 10:30 AM * Remaining: 15 of 20 payments left * Analytics: 45 views, 5 payments, 11% conversion ### Invoice Bundle — Multiple Outstanding Invoices ``` Name: Open invoices Q1 2025 Type: Invoice Bundle Link Customer: Acme BV Invoices: INV-2025-041 (€450), INV-2025-042 (€750), INV-2025-043 (€650) Total: €1,850.00 (calculated automatically) Path: acme-open-q1 Delivery: Email + SMS Description: Please settle all outstanding invoices below. URL: https://payrequest.me/yourhandle/acme-open-q1 ``` **After payment:** * All three invoices automatically marked **paid** in PayRequest * Each invoice records the Mollie payment ID * Customer receives a confirmation page ## Frequently Asked Questions **Smart Links** are permanent, reusable URLs with built-in analytics. They're designed for campaigns and marketing. **Dynamic Payment Links** are generated on-demand with query parameters. They're better for personalized payment requests with customer data. Yes! Edit the smart link and modify the "Path" field. However, this will break any existing links you've shared, so only change paths before launching campaigns. Analytics are stored permanently for the lifetime of your smart link. Even if you deactivate a link, historical data remains accessible. Currently, all smart links use the `payrequest.me` domain with your business handle. Custom domain support for smart links is planned for a future update. Deleted smart links cannot be recovered. The URL will return a 404 error, and all analytics data is permanently lost. Consider deactivating instead of deleting. No. Amount links display a disabled amount field. The payment amount is fixed and cannot be modified by customers. This ensures consistent pricing for campaigns. Payment limits control how many successful payments a smart link can accept: * **One-time**: Link disables after first payment * **Multiple**: Set custom limit (1-1000), link disables when reached * **Unlimited**: Default, accepts infinite payments Only successful (paid) transactions count toward the limit. Failed or pending payments are not counted. When the limit is reached, customers see "Payment limit reached" and cannot complete payment. Yes! When creating a smart link, you can select a customer and choose delivery methods: * Email only * SMS only (requires valid phone number with country code) * Both email and SMS SMS messages are sent via MessageBird and include a personalized message with the payment link. The customer must have a valid international phone number (e.g., +31612345678) for SMS delivery to be available. When a smart link reaches its payment limit: 1. Link automatically becomes inactive 2. Customers see "Payment limit reached" error message 3. No more payments can be accepted 4. Analytics show "Limit reached" badge in red 5. You can reactivate by editing the link and increasing the limit All existing analytics data is preserved when the limit is reached. Yes! Edit the smart link and modify the payment limit settings. You can: * Change from unlimited to limited (or vice versa) * Increase or decrease the limit number * Switch between one-time and multiple payments However, existing payment counts remain. If a link already has 5 payments and you set the limit to 3, it will immediately be marked as "limit reached". When you select a customer to send a smart link to, two additional options appear: * **Apply Tag to Customer**: Adds a Customer-type tag to the customer's profile after payment * **Remove Tag from Customer**: Removes an existing tag from the customer after payment Both actions are optional and can be combined. For example, you can remove "Trial User" and add "Paid Customer" in one payment action. The customer tag action fields only appear when you: 1. Select a customer in "Send smart payment link to customer" 2. The tag dropdowns then become visible These features are designed for targeted, customer-specific payment links where you want to automate customer status updates. The "Remove Tag from Customer" dropdown is smart - it only shows: * Tags that the selected customer currently has * Plus any tag you've selected in "Apply Tag" (since it will be added) This prevents confusion and ensures you can only remove tags the customer actually has. If the customer has no tags, you'll see "This customer has no tags to remove". Yes! You can create new tags directly from the smart link form: 1. Click "Create New Tag" in the Smart Link Tags section 2. Enter a name and choose a color 3. Click "Create Tag" The new tag is immediately created and selected. This works for Smart Link tags during creation and editing, as well as in the tag management modal on the detail page. Payment reminders automatically send follow-up messages to customers who haven't paid: 1. Enable reminders when sending a smart link to a customer 2. Choose frequency: Daily, Every 2 days, Every 3 days, Weekly, or Monthly 3. Set maximum reminders (1-50) 4. Reminders are sent via the same method(s) as the original link (Email/SMS) Reminders automatically stop when the customer pays or when the maximum limit is reached. Yes! Edit the smart link and modify the reminder settings: * Enable or disable reminders * Change the frequency * Adjust the maximum reminder count If reminders have already been sent, you'll see a status showing how many were sent and when the next one is scheduled. Payment reminders only appear when: 1. You select a customer in "Send smart payment link to customer" 2. You select at least one delivery method (Email or SMS) Reminders require a customer association because they need somewhere to send the follow-up messages. Public smart links without a customer cannot have reminders. When a customer completes payment through the smart link: * All scheduled reminders are automatically cancelled * No more reminders will be sent * The reminder status shows as complete This prevents customers from receiving unnecessary payment reminders after they've already paid. Every time someone opens your smart link, the following is recorded: * **Timestamp**: Exact date and time of the visit * **IP Address**: Visitor's IP (automatically masked for privacy: last octet hidden) * **Browser/OS**: Detected from user agent (e.g., "Chrome / Windows", "Safari / iOS") * **Referer**: The URL the visitor came from (if available) This data helps you understand when and how people access your payment links. All IP addresses are masked to protect visitor privacy. The activity section on the smart link detail page has four tabs: * **All**: Combined view of all activity types (views, payments, reminders, sent events) * **Views**: Paginated list of all detailed view records with IP, browser, and timestamp * **Payments**: Paginated list of all payments with customer name, amount, and status * **Reminders**: Reminder settings summary and sent/scheduled reminder events Each tab updates in real-time as new activity occurs. Views and Payments tabs support pagination (10 items per page). When you create a Product Link that points to a **Security Deposit** product, the smart link becomes a deposit link. This adds a **Deposits tab** to the detail page where you can: * View all authorization holds from customers * See hold duration progress bars * Capture full or partial amounts * Release holds back to customers * View capture history Deposit links only accept credit card payments (required for authorization holds). See [Security Deposits →](/payment-processing/security-deposits) for full details. When you enable **Protect with access code** on a smart link, visitors must enter the correct code before the payment page is shown: * You set the code (or click **Generate** for a random one) when creating or editing the link * The code is stored securely (hashed) — it can't be retrieved later, only replaced * Visitors see a branded "Access code required" page first; once they enter the correct code, the link works normally for the rest of that browser session * Wrong codes are rate-limited to prevent brute-force guessing This is different from making a link inactive or reaching a payment limit — a protected link is still fully active, it just requires the code first. Access codes are hashed when saved, so PayRequest can't show you the original code. To set a new one, edit the smart link, make sure **Protect with access code** is checked, and type a new code in the field (or click **Generate**). Saving replaces the old code immediately — anyone with the old code will no longer be able to unlock the link. An Invoice Bundle Link groups multiple open invoices for a single customer into one payment page. Instead of chasing the customer for each invoice individually, you create one smart link that shows all outstanding invoices and lets the customer pay the total in a single transaction. When the payment is confirmed by Mollie, **all bundled invoices are automatically marked as paid** in PayRequest — no manual reconciliation needed. Only invoices with status **open**, **sent**, or **overdue** appear in the invoice selector. Invoices that are already **paid** or in **chargeback** status are excluded automatically. After payment succeeds, all selected invoices are marked paid and linked to the Mollie payment ID for full audit traceability. No. An Invoice Bundle Link is always tied to a **single customer**. When you select a different customer while creating the link, the invoice selection resets. This ensures the payment page and email are correctly addressed to the right customer. Yes. Edit the smart link, change the invoice selection, and save. The total amount on the payment page updates automatically. If you re-send the link via the delivery methods on the edit page, the customer receives an updated email with the new invoice list and total. The customer sees a clean, dark-themed payment page with: * Your business name and logo * The smart link title and optional description * A list of all open invoices (invoice number, amount, due date, overdue badge if applicable) * The total amount due * A single **Pay** button that initiates a Mollie checkout If all invoices have already been paid by the time the customer opens the link, the page shows a green confirmation instead of the pay button. ## Need Help? Collect authorization holds for rentals and services Configure your payment page settings Create products for product links Organize with tags Create and manage invoices to bundle into payment links Send payment links directly via SMS Drop a file and get a product + Smart Link in one step # SMS Payment Links Source: https://docs.payreque.st/payment-processing/sms-payment-links Send payment links straight to your customer's phone via SMS, and learn how SMS credits work — 1 free credit to start, plus 1 new credit for every payment you receive # SMS Payment Links Email inboxes get crowded — text messages get read. With SMS delivery, your payment link lands directly in your customer's messages app, with your business name as the sender. It's the fastest way to get paid when you need a customer's attention right away. SMS delivery is available on **every PayRequest account**, no paid plan required. Sending one SMS costs **1 SMS credit** — see [How SMS Credits Work](#how-sms-credits-work) below. ## Why Send Payment Links by SMS? Text messages are typically read within minutes — much faster than email. The SMS arrives with your business name as the sender, so customers know it's you. The message contains your payment link — customers tap it and pay on their phone. The credit system keeps SMS free to use while preventing abuse. ## How It Works Go to **Payment Page → Smart Links** and create a new link, just like you normally would. Under **Send smart payment link to customer**, pick the customer who should receive it. The customer needs a phone number in international format (for example `+31612345678`). Tick the **SMS** option. You'll see the phone number it will be sent to, plus how many SMS credits you have left. As soon as you save the smart link, the SMS goes out. Your customer receives a short personal message with the payment link. You can select **Email and SMS together**. The email is always free — only the SMS uses a credit. ## How SMS Credits Work To keep SMS fair and free for everyone, sending works with credits: | | | | - | - | | **Starting balance** | Every account gets **1 free SMS credit** | | **Earning credits** | You earn **1 new credit for every payment you receive** — any payment, through any payment method | | **Cost per SMS** | Sending one payment link by SMS costs **1 credit** | | **Email delivery** | Always free and unlimited | So the more you get paid, the more SMS messages you can send. An active business never runs out — and if you do run low, the next incoming payment tops you up automatically. If your SMS fails to send (for example because of a network issue), your credit is automatically refunded. ### What Happens When You're Out of Credits? When your balance reaches zero, the **SMS option is temporarily disabled** in the smart link form, and a message explains how to earn more. You don't lose anything — your smart link still works, and you can: * Send the link by **email** instead (always free) * Copy the link and share it any way you like * Receive any payment — your balance goes up by 1 credit immediately ## Frequently Asked Questions Sending a text message costs real money per message, unlike email. The credit system lets us offer SMS to every account — free of charge — while making sure it's used for genuine payment requests and not spam. Every successful payment you receive counts: card payments, iDEAL, bank transfers, PayPal, crypto — anything that lands as a paid transaction in your account earns 1 SMS credit. No. Credits stay on your account until you use them. Not at the moment — credits are earned through payments only. Since every payment earns a credit back, active businesses naturally keep a positive balance. Two possible reasons: the selected customer has no valid phone number in international format (like `+31612345678`), or your SMS credit balance is zero. The form tells you which one applies. Check that the phone number is correct and in international format. Note that some countries (notably the United States) have strict carrier rules that can block business SMS. If an SMS can't be delivered, your credit is refunded — you can always fall back on email delivery. ## Next Steps Everything about creating reusable, branded payment links Automatically follow up on unpaid links Keep phone numbers and contact details up to date See all the ways your customers can pay # Solana Pay Source: https://docs.payreque.st/payment-processing/solana-pay Accept USDC payments via QR code — customers scan with any Solana Pay wallet. No checkout form, instant settlement, 2% fee. # Solana Pay **Solana Pay** is an open payment standard that lets customers pay you by scanning a QR code with their Solana wallet app. The wallet reads the QR, shows the exact USDC amount to pay, and the customer approves — no typing, no copy-pasting addresses, no checkout friction. Solana Pay appears as a dedicated payment option on your checkout page alongside iDEAL, credit card, and bank transfer — once you connect your Solana wallet in Provider Settings. ## Why Use Solana Pay The customer opens their wallet app, points the camera at the QR code, and taps approve. No address copy-paste, no manual amount entry — the wallet fills everything in automatically. Phantom, Solflare, Backpack, Trust Wallet, Coinbase Wallet — any wallet that supports the Solana Pay standard works out of the box. No special setup needed for your customers. Solana confirms in under a second. The USDC is in your wallet almost immediately after the customer approves. Solana Pay is an open protocol — not owned by PayRequest or any single company. Any wallet that implements it can pay you, and competition keeps it free. ## How to Enable Solana Pay You just need a Solana wallet address connected to your account. That's the address customers' payments will land in. In your PayRequest dashboard, go to **Settings → Provider Settings**. Scroll to **Solana Wallet (P2P)** and click **Connect Solana Wallet**. Approve in Phantom, Solflare, or any compatible wallet. Your address is saved. From now on, a **Solana Pay** card shows up in the payment method selector on your checkout page, right alongside iDEAL and bank transfer. No extra configuration needed. The same wallet connection powers both **Solana Pay** (QR checkout) and **P2P wallet payments** (the hero send button on your page). Connect once, get both. ## How It Works for Your Customer When a customer selects **Solana Pay** on your checkout page: The page shows a QR code with the exact USDC amount already encoded — converted from your invoice or product price at the current EUR/USD rate. They open Phantom, Solflare, or any Solana Pay wallet and point the camera. The wallet displays: merchant name, amount in USDC, and a single **Confirm** button. One tap in the wallet sends the USDC. The transaction is signed and broadcast to the Solana network. Within 1–2 seconds the checkout page shows a green confirmation. The invoice is marked paid in your PayRequest dashboard. On mobile devices, a **"Open in wallet app"** link appears below the QR code so customers can tap directly into their wallet without needing to scan. ## Supported Customer Wallets Any wallet that supports the **Solana Pay standard** works — which includes all major Solana wallets: | Wallet | Where to get it | | - | - | | **Phantom** | [phantom.app](https://phantom.app) — most popular, recommended for new users | | **Solflare** | [solflare.com](https://solflare.com) — full-featured, hardware wallet support | | **Backpack** | [backpack.app](https://backpack.app) | | **Coinbase Wallet** | Available on iOS and Android | | **Trust Wallet** | Available on iOS and Android | If a customer doesn't have a wallet yet, **Phantom** is the easiest to get started with — it's available on iOS, Android, and as a browser extension for Chrome, Firefox, and Brave. ## Fees PayRequest charges a **2% platform fee** on each Solana Pay transaction, automatically split at the time of payment: | Example | Amount | | - | - | | Customer pays | **100 USDC** | | You receive | **98 USDC** | | PayRequest fee | 2 USDC | The split is built into the transaction itself — there's no extra step or delay. The customer also pays a tiny Solana network fee (usually under \$0.001). No. The 2% is the only charge. No monthly fee, no currency conversion cost, no chargeback risk. ## Solana Pay vs. Other Payment Methods | | Solana Pay | USDC on Base | iDEAL / Card | Bank Transfer | | - | - | - | - | - | | **How customer pays** | Scan QR in wallet | WalletConnect | Online banking / card | Manual transfer | | **Settlement time** | \~1 second | \~1 second | 1–3 days | 1–3 days | | **Platform fee** | 2% | 2% | Varies | Free | | **Chargeback risk** | None | None | Yes | No | | **Works internationally** | Yes | Yes | Limited | SEPA only | ## Connect Wallet vs. Scan QR When a customer chooses Solana Pay on your checkout, they see two tabs: * **Scan QR Code** — The standard Solana Pay experience. Works with any Solana Pay wallet. Recommended. * **Connect Wallet** — Connects directly via WalletConnect. Best for customers paying from a desktop browser wallet extension who don't want to use their phone camera. Both tabs pay USDC to the same wallet and charge the same 2% fee. The end result is identical. ## Frequently Asked Questions USDC is a **stablecoin** — always worth \$1 USD. Unlike Bitcoin, its value doesn't go up or down. It's issued by Circle, backed by real dollar reserves, and available on most major exchanges. It's the standard currency for Solana payments. No. Any customer with a Solana wallet and USDC can pay — no account, no signup, no email required. They can buy USDC on any major exchange (Coinbase, Kraken, Bitvavo) and send it to their Solana wallet. Most exchanges let you withdraw directly to a Solana wallet address. No. At the moment the QR code is generated, PayRequest converts your invoice amount to USDC at the current EUR/USD rate. The customer sees and approves the exact USDC amount. You receive that amount (minus 2%) in your wallet. Solana transactions are irreversible. To refund a customer, send USDC directly from your wallet to their address. You can find their wallet address and transaction details in your PayRequest transaction history. Yes — once you connect your Solana wallet in Provider Settings, Solana Pay appears on all your payment pages and checkout links automatically. No per-page setup needed. Yes. PayRequest shows all your enabled payment methods as cards on one checkout page. The customer picks the one that works for them. Send your USDC from your Solana wallet to an exchange account (Coinbase, Kraken, Bitvavo), sell it for EUR, and withdraw to your bank. Most exchanges process this within minutes. ## Next Steps Set up your Solana wallet in Provider Settings to activate Solana Pay on your checkout. The same Solana wallet also powers instant P2P payments from your payrequest.me page — no invoice needed. Accept USDC on the Base network via WalletConnect — another crypto option alongside Solana Pay. Get a branded link with your SOL address, QR code, and copy button — great for giveaways and tips. See all payment methods PayRequest supports and how they compare. # AI Prompts Source: https://docs.payreque.st/products-and-pricing/ai-prompts Sell your ChatGPT, Midjourney, Claude, or Suno prompts — buyers see a teaser, then pay to unlock the full prompt instantly # AI Prompts Turn a prompt you've engineered into a product. **AI Prompts** let you sell the exact wording you use with ChatGPT, Midjourney, Claude, Stable Diffusion, Suno, and other AI tools — customers see a short teaser you write yourself, then pay to instantly unlock the full prompt text. AI Prompts are available on all plans. They work for prompts written for text, image, audio, or video AI tools. Works for ChatGPT, Claude, Gemini, Midjourney, Stable Diffusion, DALL·E, Suno, Runway, and more You write the preview text yourself — PayRequest never shows a snippet of the real prompt, so the wording stays yours until it's paid for After payment, the full prompt appears right on the page with a one-click **Copy Prompt** button, and is also emailed as a text file List your prompt on the PayRequest Marketplace under one of 10 categories, so people who don't already know you can discover it ## Creating an AI Prompt Product Navigate to **Products** and click **New Product**. Select **AI Prompt** as the product type. Pick the AI tool your prompt is written for from the dropdown, grouped by what it produces: **Text** (ChatGPT, Claude, Gemini), **Image** (Midjourney, Stable Diffusion, DALL·E, Flux), **Audio/Music** (Suno, Udio), or **Video** (Runway, Pika, Sora). This shows customers which tool to paste your prompt into. Choose the category that best describes what the prompt helps someone accomplish — for example **Marketing & Sales**, **Image & Design**, or **Coding & Automation**. This is used to organize and filter AI Prompt listings. Write a short (up to 280 characters) description of what the prompt does — enough to sell it without giving away the exact wording. For example: "Turns any product photo into a studio-lit ad shot — works with GPT-4o and Nano Banana." This is required, and it's the only thing customers see before they pay. Paste the exact prompt text customers will receive after payment. This is stored privately and never shown to anyone who hasn't paid. Enter your price and save. The product is ready to sell immediately from your shop, your PayRequest Page, or a Smart Link. Write your teaser like ad copy, not like a summary. Describe the *outcome* the prompt produces ("turns rough notes into a polished LinkedIn post") rather than hinting at *how* it's structured — that's the part you're selling. PayRequest never auto-generates a preview from your actual prompt text, not even a partial or masked one. If you leave the teaser blank, customers won't see anything convincing to buy — always write it yourself. ## What Buyers Experience 1. **Browsing** — customers see your teaser and the target AI model badge on the product page, so they know what they're buying and what tool to use it with 2. **Payment** — checkout works exactly like any other PayRequest product, through Mollie or your other connected payment providers 3. **Instant reveal** — right after payment, the full prompt appears on the confirmation page in a copy-friendly box with a **Copy Prompt** button 4. **Email delivery** — the same prompt is also emailed as a `.txt` file, so customers always have a backup copy 5. **Customer portal** — customers can come back to their order history at any time and copy the prompt again, in case they lose the email ## Listing on the Marketplace Every AI Prompt product can optionally be listed on the [PayRequest Marketplace](https://payrequest.me/marketplace) — a public storefront where anyone can discover and buy products from PayRequest sellers, separate from your own shop. Edit the AI Prompt product you want to list. Enable the **List on Marketplace** toggle. Pick a category from the **AI Prompts** group in the searchable category picker: Marketing & Sales, Content & Social Media, Business & Productivity, Ecommerce, Coding & Automation, Image & Design, Video & Animation, Writing & Research, Education & Career, or Audio & Music. The category you pick here is the public **Marketplace category** used for browsing and search on payrequest.me/marketplace. It's a separate setting from the category you chose earlier on the product itself, which only affects how your own listing is organized. ## FAQ No. The teaser is required — it's the only thing customers see before paying, and PayRequest deliberately never generates one from your real prompt text, even a partial or masked version, since that would give away the value you're selling. Past buyers keep access to whatever version they paid for through their order history and the email they received. Editing the product updates what future buyers get. Yes — each media type (Text, Image, Audio/Music, Video) includes an "Other" option for tools not listed by name. No. Marketplace listing uses the same pricing and fees as selling directly from your own shop or PayRequest Page. No. Each AI Prompt is a single prompt sold as one item, so the custom fields step and quantity selection are skipped automatically. ## Next Steps Sell downloadable files with the same secure delivery system AI Prompts are built on A similar teaser-then-unlock model for photos and audio tracks Learn about all product types and settings How customers re-copy a purchased prompt from their order history # Booking Calendar Source: https://docs.payreque.st/products-and-pricing/booking-calendar Accept appointments and reservations with the booking calendar system # Booking Calendar Create bookable products for appointments, consultations, equipment rentals, and services. Customers select available dates and time slots during checkout. ## Overview The booking calendar system allows you to: * Offer time-based services and appointments * Set available days and time slots * Control lead time and maximum advance booking * Manage concurrent bookings * Automatic conflict prevention * Protect appointments with full payment or an upfront deposit * Record the remaining balance and cancellation policy with the order ## No-show protection Booking products can require payment before an appointment is confirmed. Under **Booking Settings → No-show protection**, choose one of these policies: * **Full payment**: collect the complete service price during booking. * **Fixed deposit**: collect a set amount, such as €20. * **Percentage deposit**: collect a percentage of the service price, such as 25%. The checkout shows the service total, the amount due now, and the remaining balance. The booking is only confirmed after the payment succeeds. The order keeps a snapshot of all three amounts, so later product price changes do not alter an existing booking. You can also set a free-cancellation window and a customer-facing cancellation policy. If no custom policy is entered, PayRequest shows the configured number of hours. Booking deposits are real partial payments toward a service. They are different from **Security Deposit** products, which authorize a temporary card hold that can later be captured or released. ## Creating a Booking Product ### Step 1: Create the Product 1. Navigate to **Products** → **New Product** 2. Select **Booking** as the product type 3. Fill in product details: * **Name**: e.g., "1-Hour Consultation" * **Description**: What the booking includes * **Price**: Amount per booking ### Step 2: Configure Availability #### Available Days Select which days of the week accept bookings: * **Weekdays Only**: Monday through Friday (default) * **Custom Selection**: Choose specific days * **Every Day**: Include weekends #### Time Slots Define when bookings can be made: ``` Morning: 09:00 - 12:00 Afternoon: 13:00 - 17:00 Evening: 18:00 - 21:00 ``` **Multiple Time Ranges**: Add separate slots for different periods (e.g., skip lunch hours). ### Step 3: Booking Rules | Setting | Description | Default | | - | - | - | | **Slot Duration** | Length of each booking in minutes | 60 min | | **Buffer Time** | Break between bookings | 0 min | | **Lead Time** | Minimum hours before booking | 24 hours | | **Max Advance** | How far ahead customers can book | 90 days | | **Max Concurrent** | Bookings allowed per slot | 1 | ## Configuration Options ### Slot Duration The length of each booking appointment: * **15 minutes**: Quick consultations * **30 minutes**: Standard meetings * **60 minutes**: Full sessions (default) * **120+ minutes**: Extended services ### Buffer Time Time between bookings for preparation: * **0 minutes**: Back-to-back bookings allowed * **15 minutes**: Quick cleanup/prep * **30 minutes**: Standard buffer ### Lead Time Minimum notice required before a booking: * **1 hour**: Same-day appointments * **24 hours**: Next-day minimum (default) * **48 hours**: Two-day notice * **72+ hours**: Advance planning required ### Maximum Advance Days How far in the future customers can book: * **7 days**: Week ahead only * **30 days**: Month ahead * **90 days**: Quarter ahead (default) * **365 days**: Year ahead ### Concurrent Bookings How many bookings can overlap in the same time slot: * **1**: One customer per slot (default) * **2-5**: Small group sessions * **10+**: Larger capacity events ## Customer Experience ### Shop View When customers view a booking product: 1. **Calendar Display**: Interactive calendar showing available dates 2. **Unavailable Dates**: Grayed out (fully booked, closed days, past dates) 3. **Date Selection**: Click to see available time slots 4. **Time Slots**: Select from available times 5. **Add to Cart**: Booking added with date/time ### Checkout Booking details displayed in cart: * Product name * Selected date * Selected time * Duration * Price ### Confirmation After payment: * Booking confirmation email sent to customer * Booking appears in your dashboard * Calendar automatically updated ## Managing Bookings ### Dashboard View Navigate to **Orders** to see bookings: * Filter by booking status * View booking details * Customer information * Date and time ### Booking Statuses | Status | Description | | - | - | | **Pending** | Awaiting payment confirmation | | **Confirmed** | Payment received, booking active | | **Completed** | Appointment has occurred | | **Cancelled** | Booking was cancelled | | **No Show** | Customer didn't attend | ### Updating Bookings From the order details: * View customer contact information * Add internal notes * Update booking status * Cancel if needed ## Payment Page Bookings Booking products also work on payment pages: 1. Share payment page link with product parameter 2. Customer sees booking calendar on payment page 3. Selects date and time 4. Completes payment 5. Booking confirmed ## Best Practices Give yourself enough notice to prepare for appointments Add buffer between bookings for breaks and prep work Don't allow bookings too far ahead if your schedule changes Set up email reminders for upcoming bookings ## Use Cases ### Consultations * **Duration**: 30-60 minutes * **Lead Time**: 24-48 hours * **Buffer**: 15 minutes * **Concurrent**: 1 ### Equipment Rentals * **Duration**: Full day (480 minutes) * **Lead Time**: 24 hours * **Buffer**: 0 (overnight return) * **Concurrent**: Based on inventory ### Group Classes * **Duration**: 60-90 minutes * **Lead Time**: 2-4 hours * **Buffer**: 30 minutes * **Concurrent**: Class capacity (e.g., 10) ### Meeting Rooms * **Duration**: 30-60 minute blocks * **Lead Time**: 1 hour * **Buffer**: 15 minutes * **Concurrent**: 1 per room ## Timezone Handling All bookings use your configured timezone: * **Default**: Europe/Amsterdam * **Display**: Times shown in customer's local context * **Storage**: All times stored in configured timezone **Timezone Consistency**: Ensure your booking timezone matches your business location to avoid confusion. ## Integration with Orders When a booking is purchased: 1. **Order Created**: Contains booking details in order items 2. **Booking Record**: Separate booking record created 3. **Calendar Updated**: Slot marked as taken 4. **Notifications**: Confirmation emails sent For subscription products with booking: * Initial booking made at checkout * Recurring bookings handled separately ## Troubleshooting ### No Available Slots Showing * Check if all days are marked as unavailable * Verify time slots are configured * Ensure lead time isn't too long * Check if max advance days is too short ### Double Bookings * Verify max concurrent is set to 1 * Check buffer time settings * Ensure proper slot duration ### Booking Not Created After Payment * Check webhook is receiving payments * Verify product type is "booking" * Review order for booking data ## Related Topics Set up different product types Manage orders and bookings Accept bookings via payment links Customize booking confirmations # Commissions Source: https://docs.payreque.st/products-and-pricing/commissions Sell custom-scoped creative and freelance work with a starting price, not a fixed one # Commissions Commissions are for work where the final price depends on what the customer actually needs — illustrations, tattoo designs, custom development, and other bespoke creative or freelance work. Unlike a regular product, a commission is listed with a **starting price** and can be adjusted once you've discussed the details with the customer. Commissions are a product type, so they show up in your existing product catalog and on your [PayRequest Page](/shop-and-checkout/sales-page-styling) — no separate setup required. ## Overview The price you set is shown to customers as "From €X" — not a fixed, final amount Listings are automatically marked with a pink "Commission" badge on your storefront Optionally show customers how long the work usually takes A flat 2% fee, capped at €25, applies to commission sales — regardless of your plan ## How It Works Go to **Products → New Product** and select **Commission** as the product type. Enter the **Starting Price** — the amount you'd typically charge for a simple version of the work. Customers will see this as "From €X". On the **Commission Details** step (or tab, when editing), add a **Typical turnaround** note like "5-7 business days" so customers know what to expect. The commission appears on your PayRequest Page with a pink "Commission" badge, the "From €X" price, and your turnaround note underneath. Once a customer buys, get in touch to confirm exactly what they need. If the final scope costs more than the starting price, send them a separate invoice for the difference. ## Setting Up a Commission Product ### Step 1: Create the Product 1. Navigate to **Products** → **New Product** 2. Select **Commission** as the product type 3. Fill in the product details: * **Name**: e.g., "Custom Character Illustration" * **Description**: What's included, your style, any usage rights * **Image**: A sample of your work ### Step 2: Set the Starting Price The **Starting Price** field works like a normal price field, but it's labeled differently and displayed differently to customers: | Where | What customers see | | - | - | | Storefront card | `From €150` | | Product detail page | `From €150` next to the Commission badge | | Checkout | The exact starting price, charged in full at purchase | Customers are charged the starting price shown at checkout — commissions don't pause payment for you to send a custom quote first. If the final work costs more once scoped, invoice the customer separately for the difference. ### Step 3: Add Commission Details On the **Commission Details** step when creating (or the **Commission Details** tab when editing an existing commission product): * A note explains that the price is shown as a starting price * **Typical turnaround** *(optional)*: free text like "5-7 business days" or "2-3 weeks", shown under the price on your storefront and product page ## The Capped Commission Fee Regular PayRequest transactions use your plan's fee (free plan: 2% per transaction, paid plans: 0%). Commission purchases work differently: | Sale type | Fee | | - | - | | Regular product, any plan | Your normal plan fee | | Commission product purchase | **2%, capped at €25** — regardless of plan | | Cart with a mix of commission and regular products | Your normal plan fee (the capped rate only applies when every item in the order is a commission) | For higher-priced commissions, the €25 cap means you keep more of what you earn — a €2,000 commission is charged €25 in fees instead of the uncapped €40 it would cost as a regular product on the free plan. ## Customer Experience On your PayRequest Page, a commission listing shows: 1. **Commission badge** — a pink badge distinguishing it from regular products 2. **"From €X" price** — signals the price can change based on scope 3. **Typical turnaround** — if you've set one, shown just below the price 4. **Standard checkout** — customers pay the starting price like any other product ## Use Cases * **Illustrators & artists**: Character portraits, tattoo flash designs, book covers * **Developers**: Custom integrations, one-off scripts, small feature builds * **Writers**: Copywriting, ghostwriting, editing packages * **Musicians & voice actors**: Custom tracks, jingles, voiceover work * **Photographers**: Themed shoots, retouching packages ## Best Practices Set your starting price for the simplest version of the work, not the average Always fill in typical turnaround so customers know what they're waiting for Reach out to scope the work as soon as a commission is purchased Use a separate invoice for anything beyond the starting price once scope is confirmed ## FAQ Yes — just treat the starting price as the final price and don't invoice for anything extra. Commissions charge the starting price at checkout. If you need to discuss scope and pricing before any payment happens, create a [Quote](/invoices/creating-invoices) instead and mark it as a commission to get the same capped 2%/€25 fee. Yes — the 2%-capped-at-€25 fee applies the same way across all connected payment providers. Not yet as a dedicated feature — for now, unpublish or archive the product once you're at capacity. ## Related Topics Set up different product types Sell time-based appointments and services Your public storefront where commissions are listed Connect Stripe, Mollie, or PayPal to accept commission payments # Creating Products Source: https://docs.payreque.st/products-and-pricing/creating-products Set up one-time and recurring products with AI-powered descriptions and images # Creating Products Create professional product listings with pricing, descriptions, and custom fields. Use AI to generate compelling product descriptions and product images instantly. Just want to sell a single file right now? [PayRequest Upload](/products-and-pricing/quick-upload) skips this wizard entirely — drop a file, set a price, and get a link in seconds. ## Basic Product Setup ### Creating a New Product 1. Navigate to **Products** in your dashboard 2. Click **New Product** button 3. Fill in the required information: * **Product Name**: Clear, descriptive name * **Description**: Detailed product information (or use AI to generate) * **Price**: Amount in EUR * **Currency**: EUR (default) ### Product Types **One-Time Products** * Single purchase items * Physical or digital goods * Services or consultations * No recurring billing **Recurring Products (Subscriptions)** * Enable **Is Recurring** toggle * Set **Billing Interval**: Daily, Weekly, Monthly, Yearly * Configure **Interval Count**: Charge every X intervals * Example: "Every 3 months" = Monthly interval with count of 3 **Security Deposit Products** *(Business plan)* * Places a temporary authorization hold on the customer's credit card * Amount is reserved but not charged until you capture it * Configure hold duration (1-28 days), partial capture, and deposit instructions * Credit card only — other payment methods are hidden automatically * Best for: Hotels, car rentals, equipment rentals, Airbnb deposits * See [Security Deposits →](/payment-processing/security-deposits) for full documentation **Digital Products** * Choose what you sell: Obsidian vault, Notion template, e-book/PDF, design assets, spreadsheet, or another digital download * Each choice provides matching preparation fields, format checks, and delivery instructions * Upload files up to 500MB, or deliver a Notion or Google Sheets template link through a private buyer guide * Customers receive secure download links after payment, with configurable limits and expiry * See [Digital Products →](/products-and-pricing/digital-products) for preparation steps and buyer delivery details **Pay to Unlock** * Choose **Pay to Unlock (Image)**, **Pay to Unlock (Audio)**, or **Pay to Unlock (Video)** * Images get an irreversible blurred preview; audio and video get physically separate teaser files * Customers preview the content before paying, then receive the private original through a secure download link * See [Pay to Unlock →](/products-and-pricing/pay-to-unlock) for full documentation **AI Prompts** * Sell a prompt written for ChatGPT, Midjourney, Claude, Suno, and other AI tools * Customers see a teaser you write yourself, then pay to unlock the full prompt with copy-to-clipboard * Optional listing on the PayRequest Marketplace under 10 AI Prompt categories * See [AI Prompts →](/products-and-pricing/ai-prompts) for full documentation **Commissions** * For custom-scoped creative/freelance work (illustrations, tattoo designs, bespoke dev work) * Price is shown to customers as a starting price ("From €X"), with an optional typical turnaround note * Capped platform fee: 2%, capped at €25, regardless of your plan * See [Commissions →](/products-and-pricing/commissions) for full documentation **Domain Products** * Domain registration with automatic annual renewal subscriptions * Requires a configured provision provider (OpenProvider) * Customers search for available domains and select TLD * See your admin for domain provider setup **VPN Subscriptions** * Available in the full product wizard after connecting an active VPNresellers account * One VPN account per subscription, delivered after confirmed payment * Paid monthly or yearly plans with an immediate first payment; no free trials, quantity selection or customer pause * Customers manage VPN credentials and download WireGuard, OpenVPN or VLESS configurations in the customer portal * See [VPNresellers](/integrations/vpnresellers) for connection, billing and delivery instructions ## AI-Powered Content 🤖 Generate professional product descriptions and images with one click using AI. ### AI Descriptions Generate compelling, sales-focused product descriptions instantly. **How to Use:** 1. **Enter Product Name**: The AI uses your product name as context 2. **Click the ✨ AI Button**: Located in the description editor toolbar 3. **Review & Edit**: AI generates 2-3 sentences focusing on benefits 4. **Customize**: Edit the generated text to match your brand voice **Features:** * **Benefit-Focused**: Emphasizes what customers get, not just features * **Professional Tone**: Persuasive but authentic copywriting * **Concise**: 2-3 sentences for quick reading * **Sales-Optimized**: Highlights value proposition clearly * **Fast Generation**: Powered by GPT-4o-mini (usually 2-3 seconds) **Example:** ``` Input: "Business Email Hosting" AI Generated: Business Email Hosting provides professional email addresses with your domain name, giving your business a credible and trustworthy image. Enjoy reliable uptime, spam protection, and easy management while keeping customer communications secure and organized. ``` ### AI Image Generation ✨ Generate professional product images using AI - no photography or design skills needed. **How to Use:** 1. **Enter Product Name**: A descriptive name helps generate better images 2. **Add Description** (optional): More context improves image relevance 3. **Click "Generate with AI"**: Button with sparkles icon next to the product image 4. **Wait for Generation**: Usually takes 15-30 seconds 5. **Image Saved Automatically**: Displayed immediately in the product **Features:** * **Professional Quality**: Modern e-commerce style with clean backgrounds * **No Watermarks**: Clean images ready for your shop * **Automatic Upload**: Saved directly to your product * **High Resolution**: 1024x1024px images * **Powered by GPT Image**: OpenAI's latest image generation model **Best Practices:** * Use descriptive product names (e.g., "Premium Leather Wallet" not just "Wallet") * Add a description for more context and better results * Works great for digital products, services, and conceptual items * Physical product images are also generated professionally **During Onboarding**: AI image generation is also available when creating your first product during the onboarding flow - perfect for getting started quickly! ### Best Practices for AI Content **For Best Results:** * Use clear, descriptive product names * Include product type in the name (e.g., "Premium Hosting Plan" not just "Premium") * Generate description first, then image for consistent context * Review and customize generated content for your brand voice * Add technical details manually after AI generation ## Advanced Product Settings ### Pricing Options **Setup Fees** * One-time charge added to first payment * Perfect for onboarding or activation costs * Can have custom name (e.g., "Installation Fee", "Borg") **Quantity-Based Pricing** * Allow customers to select quantity * Total = (Base Price + Add-ons) × Quantity * Useful for seat-based SaaS or multiple licenses **Custom Pricing** * Override standard price when creating subscriptions * Add-ons markup **not included** when custom price is set * Custom price is the final amount ### Trial Periods Configure free trials for recurring products: * **Trial Days**: Number of days customer can test for free * **Trial Description**: Explain what's included in trial * **Automatic Conversion**: Billing starts automatically after trial ends ### Custom Fields Collect additional information from customers: * **Field Types**: Text, email, URL, number, textarea, select, toggle * **Markup Pricing**: Add extra charges to specific options * **Required/Optional**: Control which fields are mandatory * **Public/Dashboard Only**: Control where fields appear See [Custom Fields Guide](/products-and-pricing/custom-fields) for detailed information. ### Order Creation Mode Control when orders are created during checkout. This is especially useful for products with high abandonment rates. **Orders at Checkout (Default)** * Order created when customer starts checkout * Customer registration email sent immediately * Order confirmation email sent immediately * Order appears in dashboard even if payment fails * Standard behavior for most products **Paid-Only Orders** * Order created only after successful payment * No emails sent until payment is confirmed * Reduces spam from abandoned checkouts * Cleaner order data (only paid orders) * Recommended for high-volume or lead-generation products **When to Use Paid-Only Orders**: If you're receiving many "Customer registered" and "New order" emails followed by "Order cancelled" notifications, switch to Paid-Only mode to reduce noise. See [Order Management](/shop-and-checkout/order-management) for more details on how orders work. ## Product Visibility ### Public Products * Visible in your shop * Customers can browse and purchase * Shown in catalog and search results ### Private Products * Only accessible via direct link * Not shown in shop catalog * Perfect for custom quotes or special offers ## Product Photo Gallery Add up to 8 photos per product instead of just one. The first photo is automatically used as the cover everywhere your product appears — shop listings, product cards, and the Marketplace. It's the same **Product Images** field as before, it just holds more than one photo now — there's no separate "gallery" to manage. Available for every product type except **Pay to Unlock (Image)** (the preview is generated automatically), **Pay to Unlock (Audio)**, **Pay to Unlock (Video)**, and **AI Prompts**. Those keep a single image because the image itself is generated or has one specific job. **Supported Formats**: JPG, PNG, WebP, GIF **File Size Limit**: 2MB per photo when creating a product, 1MB per photo when editing — up to 8 photos total ### Upload Your Own Photos * Drag and drop or click to upload — select multiple files at once * The first photo in the gallery is always the cover shown in listings * When editing an existing product, reorder photos with the arrow buttons or remove one with the **×** button * New photos added while editing are appended after your existing ones and saved when you click **Save** ### Generate with AI Don't have product photos? Use AI to generate one: * Click **"Generate with AI"** button (sparkles icon) * AI creates a modern e-commerce style image and adds it as your new cover photo * Based on your product name and description * See [AI Image Generation](#ai-image-generation-) for details ### What Customers See Products with more than one photo show a **carousel** on your checkout page — customers click through with arrows or dots. Products with a single photo (or none) look exactly as before, so simple products stay uncluttered. ### Image Best Practices * Use high-quality product photography when available * Show your product from multiple angles or in different contexts * Put your best, most representative shot first — it's the one customers see in listings * AI-generated images work great for digital products and services * Consistent style across all photos in the gallery ## SEO & Metadata **URL Slug** * Auto-generated from product name * Can be customized for better SEO * Use hyphens, lowercase, no special characters **Meta Description** * Uses product description by default * Keep under 160 characters for search results * Include key benefits and keywords ## Product Organization ### Categories & Tags * Organize products into logical groups * Use tags for filtering and search * Create collections for promotions * Tag-based automation for workflows ### Product Archiving * Archive instead of deleting products * Maintains data integrity for past orders * Can be restored if needed * Archived products hidden from shop ## Next Steps Sell downloadable files with automatic delivery Sell photos and tracks behind a free preview Sell prompts for ChatGPT, Midjourney, Suno, and more Skip this wizard — drop a file and get a link in seconds Add custom fields with markup pricing Answer common questions directly on a product page Configure one-time setup charges Share product links with QR codes Sell custom-scoped creative and freelance work ## Tips & Tricks **Quick Product Creation**: Use AI to generate both descriptions and images while you configure pricing. This saves time and ensures consistent, professional content across all products. **AI Image Tip**: For best results with AI-generated images, use descriptive product names like "Professional SEO Consulting Package" rather than generic names like "SEO Service". **Pricing Changes**: Modifying a product's price doesn't affect existing subscriptions. Existing customers continue paying their original price. **Subscription Products**: Enable "Allow customers to manage subscriptions" to let customers pause, resume, or cancel their own subscriptions from the customer portal. # Custom Fields Source: https://docs.payreque.st/products-and-pricing/custom-fields Collect additional customer information # Custom Fields Custom fields let you collect extra information from customers at checkout — sizes, colors, reference numbers, add-ons, or anything else your product needs. Some field types can also add to the price automatically. Custom fields are configured per product, in the **Custom Fields** step of the product wizard (or the **Custom Fields** tab when editing a product). ## Field Types A single-line text input. Good for names, references, or short notes. A single-line input validated as an email address. A single-line input validated as a URL. A numeric input. Supports **per-unit pricing** — see below. A multi-line text input for longer notes or instructions. A list of options you define. Each option can have its own price markup. An on/off switch — useful for optional add-ons. Can add a fixed markup when enabled. ## Adding a Custom Field In the product wizard (or the product editor's **Custom Fields** tab), click **Add Field**. * **Field Name** — internal identifier (letters, numbers, underscores, hyphens only — no spaces) * **Display Label** — what the customer sees on the payment page Pick one of the seven types above. The configuration options below change depending on the type you pick. * **Show in Shop** — toggle whether the field is visible to customers * **Required Field** — toggle whether customers must fill it in before paying Fields are saved in the order you add them. Use the up/down arrows next to each field to reorder them. ## Pricing: Number Fields (Per-Unit Markup) Number fields can add a price per unit entered — ideal for rental days, seats, or quantities of an add-on. | Setting | Description | | - | - | | **Price per Unit** | Amount added to the total for each unit the customer enters | | **Min** | Minimum value the customer can enter | | **Max** | Maximum value the customer can enter | **Example:** A number field called "Rental Days" with a **Price per Unit** of €16 — a customer entering `5` adds €80.00 to the total (5 × €16.00). You can pre-fill and lock a number field's value using a [dynamic payment link](/payment-processing/payment-page-dynamic-links) with `customfield_fieldname=5&disabled=true`. ## Pricing: Dropdown Options For **Dropdown (Select)** fields, add one or more options, each with: | Setting | Description | | - | - | | **Label** | What the customer sees in the dropdown | | **Value** | The internal value stored with the order | | **Markup** | Price added to the total when this option is selected | **Example:** A "Size" dropdown with options Small (€0 markup), Medium (€5 markup), Large (€10 markup). ## Pricing: Toggle Fields Toggle fields can add a fixed price when switched on: | Setting | Description | | - | - | | **Price when enabled** | Amount added to the total when the customer turns the toggle on | | **Default on** | Whether the toggle starts enabled by default | ## Where Custom Fields Appear Custom fields are shown in the **Additional Information** section on the payment page, alongside the product. Their values are stored with the order and visible on the order detail page in your dashboard. Custom field values can also be pre-filled and locked via URL parameters on a [dynamic payment link](/payment-processing/payment-page-dynamic-links) using the `customfield_*` prefix. ## FAQ Yes. Use the up/down arrow buttons next to each field in the product editor to change the order they appear on the payment page. Yes. Toggle **Required Field** when configuring the field. Customers can't complete payment without filling it in. No, markups from custom fields apply to the product price. Setup fees are configured separately — see [Setup Fees](/products-and-pricing/setup-fees). Turn off **Show in Shop** to hide a field from customers while keeping it configured — useful if you want to enable it later or use it only via a dynamic link with a pre-filled value. ## Next Steps Learn about all product types and settings Pre-fill and lock custom field values via URL Let customers buy multiple units of a product Configure one-time setup charges # Custom Pricing Source: https://docs.payreque.st/products-and-pricing/custom-pricing Offer contract product and domain prices to selected customers ## Overview Price lists let you offer negotiated prices to one or more customers without changing the public product or domain price. Customers receive their custom prices after signing in to the customer portal. Guests continue to see the regular catalog price. ## Create a Price List 1. Open **Settings → Custom Pricing**. 2. Select **New**, enter a recognizable internal name, and assign the customers who should receive it. 3. Set a priority. When a customer has multiple matching lists, the active list with the highest priority wins. 4. Save the price list. ## Add Product Prices Select a product and enter its contract price. You can optionally override its one-time setup fee. Prices are stored as decimal currency amounts; for example, enter `5.00` for €5.00. ## Add Domain Prices Select a TLD and enter one or more prices for registration, renewal, or transfer. A blank operation falls back to the regular TLD price. For example, a `.nl` registration price of €5.00 on a price list assigned to a hosting partner does not change the regular €8.00 public price. ## How Prices Apply * The customer must be signed in and belong to the same business as the price list. * Checkout verifies the current contract price on the server. * Orders and subscriptions keep a snapshot of the accepted price. * Disabling a price list immediately restores normal prices for new checkouts. * Existing subscriptions retain their agreed recurring amount. Coupons and custom-field markups remain separate from contract pricing. A price list changes the base product or domain price. # Digital Products Source: https://docs.payreque.st/products-and-pricing/digital-products Prepare and sell Obsidian vaults, Notion templates, e-books, design assets, and spreadsheets with secure delivery after payment # Digital Products Sell digital files and deliver them automatically to customers after payment. Upload your file once, and PayRequest handles secure download links, expiry, and download limits for every purchase. Digital products are available on all plans. Supported file types include documents, archives, images, audio, video, 3D, and font files — up to **500MB** per file. See the full list below. Customers receive download links instantly after payment — on the success page and in their email Unique tokens per purchase with configurable download limits and expiry dates See how many times each file was downloaded, with per-token and per-product statistics Downloads accessible from success page, order email, customer portal, and direct link ## Creating a Digital Product Navigate to **Products** and click **New Product**. Select **Digital** as the product type. In the product details step, search for or select **Obsidian vault**, **Notion template**, **E-book / PDF**, **Design assets**, **Spreadsheet**, or **Other digital download**. Your choice changes the preparation fields, accepted formats, file checks, and what the buyer receives. Follow the instructions for your product below. Upload a file up to **500MB**, or enter a supported template link. Add any requested software requirements, usage terms, and buyer instructions. Where a buyer guide is generated, open **Preview the guide your buyer receives** to review it before continuing. Enter the price, currency, and applicable tax rate for the digital product. Set how customers can access the file after purchase: * **Max Downloads** — How many times a customer can download the file (1-100, default: 5) * **Link Expiry** — How many days the download link stays active (1-365, default: 30 days) Save the product and make it visible in your shop. Customers can now purchase and receive the file automatically. ## Prepare Your Product | What you sell | What you provide | What the buyer receives | | - | - | - | | Obsidian vault | Vault ZIP and plugin/theme requirements | Original vault files plus a getting-started guide in a ZIP | | Notion template | Published template link, or a prepared buyer guide | A text guide with the link and duplication steps, or your uploaded guide | | E-book / PDF | PDF, EPUB, or a ZIP containing your editions | Your uploaded book file or bundle | | Design assets | Source-file ZIP, required software, and your usage terms | Source files and a buyer guide in a ZIP | | Spreadsheet | XLSX, CSV, or a Google Sheets template link | A file package with instructions, or a text guide with the online template link | | Other digital download | A supported file | Your original uploaded file | ### Obsidian Vaults 1. Create a ZIP of the vault folder, keeping Markdown notes, attachments, and subfolders together. 2. Include the hidden **.obsidian** folder if your product includes vault settings. Check the vault for personal notes and account details before packaging it. 3. Upload the ZIP. PayRequest checks that it contains Markdown notes and shows whether settings are included. 4. Enter the required plugins and theme, or enter **None** when none are needed. 5. Add any extra setup instructions and preview the generated guide. The delivered ZIP preserves your original files and adds instructions for extracting the vault and opening its folder in Obsidian. Existing guide files are not overwritten. ### Notion Templates 1. Publish the template page in Notion and enable **Duplicate as template**. 2. Choose **Template link and instructions** and paste its published `notion.site` or `notion.so` HTTPS link. 3. Test the link with another account. Confirm that the buyer can duplicate the template into their workspace, then check the confirmation box in PayRequest. 4. Add any extra instructions and preview the guide. After payment, the buyer downloads a text guide containing your link and duplication instructions. If you already have a PDF or another supported guide containing the link, choose **Upload a prepared buyer guide** instead. If you also sell the template through Notion Marketplace, use a separate published copy for PayRequest buyers. Notion's paid Marketplace link may lead to its own checkout, and its access-locking feature does not apply to third-party sales. See [Notion's template-selling guide](https://www.notion.com/help/selling-on-marketplace). ### E-books and PDFs Select the delivery format before uploading: * **PDF** for a fixed page layout. * **EPUB** for e-reader apps. * **PDF and EPUB bundle (ZIP)** to deliver editions together. The archive must contain at least a PDF or EPUB file. The uploaded extension must match your selection. PayRequest checks the PDF signature or basic EPUB structure; these checks do not replace reviewing the book in a reader app. Your book file is delivered unchanged. ### Design Assets 1. Put the editable source files and any included exports in a ZIP. For Figma, [save a local `.fig` copy](https://help.figma.com/hc/en-us/articles/8403626871063-Save-a-local-copy-of-files) and include it in the archive. 2. Specify the software and version buyers need. 3. Enter your usage terms, including permitted uses and any third-party assets buyers must license separately. 4. Add import or setup instructions and preview the buyer guide. PayRequest includes your requirements, terms, and instructions in the delivered ZIP. It does not supply a license on your behalf or verify compatibility with every design application. ### Spreadsheets Choose the format that matches your product: * **Excel (.xlsx)**: upload the workbook and specify the software/version buyers need. PayRequest checks the basic workbook structure. * **CSV data file**: upload a non-empty CSV text file. Use this for tabular data; CSV does not retain workbook formatting or multiple sheets. * **Google Sheets template link**: paste the spreadsheet's HTTPS link from `docs.google.com/spreadsheets/d/...`. For Excel and CSV, PayRequest packages the file with a getting-started guide and your instructions. For Google Sheets, set **General access** to **Anyone with the link**, choose **Viewer**, and allow copying. Test the link with another account and confirm that a copy can be made. The buyer receives a text guide with the link and instructions to use **File > Make a copy**. Keep edit access to your original restricted. PayRequest checks template-link formats, but you must test sharing permissions in Notion or Google Sheets. Download limits protect access to the delivery file; they do not prevent a buyer from sharing a template link they have already received. ### File Checks and Upload Issues For the prepared vault, design, e-book, and spreadsheet flows: * The uploaded file must match the selected format. * Archives must be readable and unencrypted, without unsafe paths or symbolic links. * Inspected archives may contain up to **10,000 entries** and **2 GB** of unpacked data. The upload itself must still be no larger than **500MB**. * An Obsidian archive needs Markdown notes; a design archive needs files; an e-book bundle needs a PDF or EPUB. If a check fails, correct or replace the file before creating the product. These are basic format checks, not a guarantee that formulas, plugins, or book formatting work correctly. ## Supported File Types **Other digital download** accepts a single file up to **500MB** in the following formats. The preparation flows above use their own format choices: | Category | Extensions | | - | - | | Documents & archives | pdf, zip, rar, 7z, tar, gz, epub, mobi, doc, docx, xls, xlsx, ppt, pptx, txt, csv, srt | | Images & design files | png, jpg, jpeg, gif, webp, psd, ai, indd, sketch, fig | | Audio | mp3, wav, flac, m4a, ogg, midi, mid | | Video | mp4, mov, webm | | 3D & CAD | fbx, obj, glb, gltf, blend, stl, dwg | | Fonts | ttf, otf, woff, woff2 | To bundle multiple files or file types together, package them into a single ZIP archive and upload that instead. ## How Delivery Works When a customer purchases a digital product, PayRequest automatically creates a unique download token for them. Here's what happens: 1. **Customer pays** — The payment is confirmed through your supported checkout provider 2. **Token created** — A secure, unique download link is generated with the limits you configured 3. **Instant access** — The download link appears immediately on the payment success page 4. **Email delivery** — The order confirmation email includes the download link 5. **Portal access** — The customer can re-download from their order history in the customer portal Download links work across all your domains — your main PayRequest domain, custom domains, and the payrequest.me PayRequest Page. Customers always get a working link regardless of where they purchased. ## Managing Digital Files ### Replacing a File To update the file for an existing digital product: 1. Go to **Products** and open the product 2. Click **Edit** and navigate to the **Digital File** tab 3. Upload the new file — the old file is automatically removed 4. Click **Save** New purchases and existing valid download tokens use the current file for the product. Replacing the file does not reset existing download limits or expiry dates. The product editor replaces the complete delivery file. For vaults, design packs, and spreadsheets, include the buyer guide and usage terms in your replacement ZIP. For a template-link product, upload an updated buyer guide containing the new link. The preparation wizard applies when creating a new product. ### Removing a File In the **Digital File** tab of the product editor, click **Remove** next to the current file. You'll be asked to confirm before the file is deleted. Removing a digital file means existing download tokens for that product will no longer work. Make sure all customers have downloaded their files before removing. ## Download Limits & Expiry Each purchase creates a download token with its own limits: | Setting | Default | Range | Description | | - | - | - | - | | **Max Downloads** | 5 | 1-100 | Number of times the customer can download | | **Link Expiry** | 30 days | 1-365 days | How long the link stays active | When a customer reaches the download limit or the link expires, they see a message explaining that the download is no longer available. Set generous download limits (5-10) so customers can download on multiple devices. The expiry period ensures links don't stay active indefinitely. ## Tracking Downloads ### Product Detail Page Open any digital product to see download statistics in the sidebar and the **Details** tab: * **Tokens issued** — Total number of download tokens created * **Total downloads** — How many times the file was downloaded across all customers * **Active tokens** — Tokens that are still valid * **Exhausted tokens** — Tokens that have expired or reached their download limit ### Order Detail Page Open any order containing a digital product to see a **Digital Downloads** card with: * File name and download count per token * Expiry date * Status (Active, Expired, or Limit Reached) * A **Copy Link** button to share the download URL with the customer ### Customer Portal Customers can view and download their digital files from their order detail page in the customer portal. They can see: * Remaining downloads * Expiry date * Download button (when the token is still valid) ## Payment Page Preview When customers view a digital product on the payment page, they see an **Includes digital file** card showing the filename and an **Instant download** badge. This helps set expectations before purchase. ## Email Delivery Order confirmation emails automatically include download links for any digital products in the order. The links appear in a **Your Downloads** section with the filename for each product. Download links in emails use the same token-based system. They count toward the same download limit as the success page and customer portal links. ## FAQ Currently, each digital product supports one file. To bundle multiple files, create a ZIP archive containing all files and upload that. You can view the customer's download token on the order detail page. If they need more access, you can share the download link directly — or they can re-purchase the product for a new token. Yes. Files are stored on encrypted cloud storage and can only be accessed through valid download tokens. Direct access to the storage is not possible. Yes. Changes to download settings apply to all future purchases. Existing tokens keep the limits they were created with. Yes. Download links work on all domains — your PayRequest dashboard, payrequest.me PayRequest Pages, and custom domains. ## Next Steps Sell photos and tracks behind a free preview Sell prompts for ChatGPT, Midjourney, Suno, and more Drop a file and get a payment link in seconds, no wizard needed Learn about all product types and settings Configure your shop to showcase digital products Customize order confirmation emails How customers access their downloads # Pay to Access Source: https://docs.payreque.st/products-and-pricing/pay-to-access Sell usage-metered access to your own app or website — issue a code that locks itself out after N uses, verified by your own backend via a public API # Pay to Access **Pay to Access** sells metered access to something you host yourself — a web app, a members' page, anything outside PayRequest. After payment, PayRequest issues a random access code with a usage limit (e.g. "5 uses"). Your own backend calls PayRequest's public API each time someone tries to use the code — PayRequest tracks how many uses are left and locks the code out once the limit is reached. Pay to Access is available on all plans. Product type: `pay_to_access`. Unlike Digital Products or Pay to Unlock, nothing is uploaded or stored — PayRequest only issues and tracks the access code Your app decides what "access" means (a login, an API call, a page view) — PayRequest just answers "is this code still valid?" Caps the *number of uses*, not just a subscription window — "paid for 5 logins" locks after the 5th, however many people share the code If a code leaks or an order is refunded, revoke it from the order detail page and it stops working immediately ## Setting Up a Pay to Access Product Navigate to **Products** and click **New Product**. Select **Pay to Access** as the product type. Under **Access Settings**, set **Max Uses** (how many times the code can be verified before it locks) and **Code Expiry** (how many days the code stays active). Enter the price and save. No file upload is required — there's nothing to store. In your own app's backend, call the verify/consume API below at the moment you want to check or burn a use. ## How Delivery Works 1. **Customer pays** — Payment is processed through Mollie. 2. **Code generated** — A random 64-character access token is created with the configured `max_uses` and `expires_at`. 3. **Shown immediately** — The code appears in a copyable "Your Access Code" card on the payment success page, right away — no need to wait for email. 4. **Email delivery** — The order confirmation email also includes the access code (`{{access_codes}}` template variable), so the customer has a backup copy. 5. **Your app verifies it** — Your backend calls the public API below to check the code and burn a use. ## Integrating with Your App These two endpoints are **public and require no OAuth token** — the 64-character code itself is the only secret, the same trust model as PayRequest's existing digital download links. Call them from your own server (not client-side JavaScript, so the code isn't exposed in browser devtools). Unlike the rest of `/api/v1`, these endpoints do not use OAuth. Do not send your PayRequest API token to them — they only need the access code. ### Verify (read-only) Check whether a code is currently valid without consuming a use. Use this to show "you have 3 uses left" before deciding whether to actually grant access. ```bash theme={null} POST /api/v1/access-tokens/{token}/verify ``` The 64-character access code the customer entered ```bash theme={null} curl -X POST "https://payrequest.app/api/v1/access-tokens/YOUR_CODE_HERE/verify" \ -H "Accept: application/json" ``` **Valid code:** ```json theme={null} { "valid": true, "remaining_uses": 3, "max_uses": 5, "expires_at": "2026-08-01T00:00:00+02:00" } ``` **Invalid code:** ```json theme={null} { "valid": false, "reason": "limit_reached" } ``` `reason` is one of: `not_found` (404), `expired` (403), `revoked` (403), `limit_reached` (403). ### Consume (burns one use) Atomically burns one use of the code. Call this the moment you actually grant access (e.g. right when the customer's login succeeds) — every successful call permanently reduces the remaining uses. Don't call it on every page load. ```bash theme={null} POST /api/v1/access-tokens/{token}/consume ``` The 64-character access code the customer entered ```bash theme={null} curl -X POST "https://payrequest.app/api/v1/access-tokens/YOUR_CODE_HERE/consume" \ -H "Accept: application/json" ``` **Successful consume:** ```json theme={null} { "valid": true, "remaining_uses": 2, "max_uses": 5, "expires_at": "2026-08-01T00:00:00+02:00" } ``` **Rejected (limit already reached):** ```json theme={null} { "valid": false, "reason": "limit_reached", "remaining_uses": 0 } ``` Consuming is atomic under concurrent requests — if two requests for the same code arrive at once with only one use left, exactly one succeeds and the other gets `limit_reached`. You'll never see the use count go negative or over the limit. ### Example: gating a login ```javascript theme={null} // Your app's backend, at the moment a customer tries to log in const response = await fetch( `https://payrequest.app/api/v1/access-tokens/${accessCode}/consume`, { method: 'POST', headers: { Accept: 'application/json' } } ); const result = await response.json(); if (!result.valid) { // show "code invalid / no uses left" and stop return; } // grant access - result.remaining_uses tells you how many logins are left ``` ## Managing Issued Codes Open any order containing a Pay to Access product to see its issued code, remaining uses, and expiry. Two actions are available: * **Reset** — sets the use count back to 0 and extends the expiry. Use this if a customer needs more uses. * **Revoke** — immediately invalidates the code (e.g. it leaked, or the order was refunded). A revoked code always returns `reason: "revoked"`, even before its uses or expiry run out. You don't need to hunt through orders to find a code, though — the product page (**Products → \[your Pay to Access product]**) lists the 20 most recently issued codes directly, each with its use count, status, a copy button, and a link to the order it came from. ## FAQ Nothing stops that — the code isn't tied to a single device or browser. It simply stops working once `max_uses` is reached, no matter who used it or how many people shared it. This matches "you paid for 5 uses" rather than "you paid for 1 seat." No. The access code itself is the only secret required, the same as PayRequest's `/download/{token}` links. Keep the call server-side so the code isn't exposed in browser devtools. `verify` is read-only and never changes the remaining uses — good for showing a "uses left" counter. `consume` is the one that actually burns a use, and should only be called at the moment you grant access. Editing the product only changes the default for *future* purchases. To change an already-issued code's limit, use Reset on the order detail page (extends expiry and zeroes the use count) — there's currently no way to change `max_uses` on an existing code without resetting it. No. Each Pay to Access product is a single access code sold as one item, so the custom fields step and quantity selection are skipped automatically. ## Next Steps For selling files instead of metered access For blurred-photo/audio-preview style unlocks Learn about all product types and settings PayRequest's OAuth-protected billing API (separate from the Pay to Access verify/consume endpoints) # Pay to Unlock Source: https://docs.payreque.st/products-and-pricing/pay-to-unlock Sell images, audio, and video behind a free preview — customers pay to unlock the full file # Pay to Unlock Give customers a taste for free, then charge to unlock the real thing. **Pay to Unlock** products show a safe public preview — a blurred image, a short audio clip, or a video teaser — and deliver the full file only after payment. Pay to Unlock is available on all plans. Three content types are supported: **Images** (`unlockable`), **Audio Tracks** (`unlockable_audio`), and **Videos** (`unlockable_video`). Customers see a blurred image, hear a short clip, or watch a video teaser before paying — enough to evaluate the content without receiving the full file Previews are generated on PayRequest's servers from the original file. The original detail is never recoverable from the preview Built on the same secure delivery system as Digital Products — the full file unlocks instantly after payment No custom fields or quantity selection — Pay to Unlock products are a single item at a single price ## Pay to Unlock: Images Upload a photo and PayRequest automatically generates a **blurred preview** to use as the product image. Customers see the blur everywhere your product appears — shop listings, product page, checkout — and only receive the sharp original after paying. Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Image)** as the product type. Upload the original photo (JPG, PNG, WebP, or GIF, up to 25MB). This file is stored privately — it is never served directly. Use the **Blur Level** slider (1–10) to control how much detail is hidden in the public preview. Higher levels hide more. Enter the unlock price and save. The blurred preview is generated immediately and appears wherever the product is shown. The blur is generated by shrinking the photo down to a tiny thumbnail and blurring that — not by applying a CSS filter to the full-size image. This means the original pixels are never sent to the browser before payment, so the blur can't be reversed with browser tools. ## Pay to Unlock: Audio Tracks Upload a full track and PayRequest automatically generates a short, **separate preview clip** customers can listen to for free — like a stock-music or beat-marketplace preview. The full track is delivered only after payment. Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Audio)** as the product type. Upload the full track (MP3, WAV, or FLAC, up to 100MB). It's stored privately, the same way Digital Product files are. Use the **Free preview length** slider (5–60 seconds, default 25s) to choose how much of the track plays for free. Upload a **Cover Image** separately from the track itself — this is the artwork shown on your shop and product pages. Enter the unlock price and save. The preview clip is generated immediately, with the full track's and preview's lengths shown to customers (for example, "0:15 free preview of the 0:27 track"). The preview clip is always a physically shorter, separate audio file — never the full track with playback cut off in the browser. Generating it server-side (with a short fade-out at the end) means the full track's file is never exposed to anyone who hasn't paid. ### Replacing or Updating a Track Open the product, go to the **Unlock Track** tab, and upload a new file — the old track and its preview clip are automatically replaced. Changing the **Free preview length** alone (without uploading a new file) regenerates the preview clip from the stored original at the new length. ## Pay to Unlock: Video Upload the full MP4, MOV, WebM, or M4V and choose a teaser length. PayRequest creates a physically separate MP4 preview for the public product page; the original file remains private and is delivered only after payment. Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Video)** as the product type. Upload an MP4, MOV, WebM, or M4V file up to 500MB. The original is stored privately and is never used as the public player source. Use the **Free preview length** control (up to 60 seconds, default 15s) to choose how much customers can watch before buying. PayRequest detects the uploaded video's duration and never lets the teaser exceed it — a 6-second video can have a maximum 6-second teaser. Upload a cover image for product cards and listings. The playable teaser appears on the product and checkout pages. PayRequest generates a browser-friendly MP4 teaser. Customers can watch it immediately and pay to unlock the original video. The teaser is a physically separate H.264/AAC MP4 at up to 720p. PayRequest never sends the full video to the browser with a client-side time limit, because that would expose the original file URL. ### Replacing or Updating a Video Open the product, go to the **Unlock Video** tab, and upload a replacement. PayRequest removes the previous public teaser and generates a new one. Changing only the preview length regenerates the teaser from the privately stored original. ## How Delivery Works Image, audio, and video unlock products share the same secure delivery mechanism as [Digital Products](/products-and-pricing/digital-products): 1. **Customer pays** — Payment is processed through Mollie 2. **Token created** — A secure, unique download token is generated for the original file 3. **Instant access** — The full image, track, or video is available immediately on the payment success page 4. **Email delivery** — The order confirmation email includes the download link 5. **Portal access** — Customers can re-download from their order history in the customer portal Download limits and link expiry work exactly as they do for Digital Products, and are configurable per product under **Download Settings**. ## FAQ For photo unlock products, the blurred version of your uploaded photo *is* the product image. For audio unlock products, the cover image is separate — it's regular artwork shown alongside the track, not something that gets blurred or unlocked. No. The preview clip is a separate, shorter audio file rendered on PayRequest's servers — it never contains the rest of the track, so there's nothing further to extract from it. No. The player receives only the separately generated teaser MP4. The private original is delivered through a secure download token after successful payment. Images: JPG, PNG, WebP, GIF (up to 25MB). Audio: MP3, WAV, FLAC (up to 100MB). Video: MP4, MOV, WebM, M4V (up to 500MB). Yes. Changing either setting regenerates the public preview from the original file — no need to re-upload. No. Each Pay to Unlock product is a single image, track, or video sold as one item, so the custom fields step and quantity selection are skipped automatically. ## Next Steps The delivery system Pay to Unlock is built on The fastest way to create a Pay to Unlock link — just drop the file Learn about all product types and settings Configure your shop to showcase Pay to Unlock products How customers access their unlocked files # Product FAQs Source: https://docs.payreque.st/products-and-pricing/product-faqs Answer common customer questions directly on your product pages # Product FAQs Add a frequently asked questions section to any product so customers can understand what they are buying before they pay. FAQs are especially useful for delivery details, licence terms, refund policies, compatibility, and other questions that might otherwise delay a purchase. Product FAQs appear on the product's dedicated public product and payment pages. They do not appear on product cards, catalog listings, or Marketplace listings. ## Add FAQs to a Product Go to **Products**, then create a new product or open an existing product and choose **Edit**. In the product details section, find **Frequently asked questions** and click **Add question**. Enter a short customer-facing question. Use the rich-text editor to format the answer with headings, emphasis, lists, and links when helpful. Add up to 20 questions. Use the up and down arrows to control their order, or use the delete button to remove one. Save your changes. The FAQ section is shown automatically when the product has at least one complete question and answer. ## What Customers See The section is titled **Frequently asked questions** and starts with every answer collapsed. A customer selects a question to expand its answer. Opening another question closes the previous one, keeping long product pages easy to scan on desktop and mobile. ## Writing Effective FAQs Keep each question focused on one decision a customer needs to make. Put the most common purchase concern first and keep the answer direct. Explain what the customer receives, how it is delivered, and when it becomes available. State whether personal use, commercial use, redistribution, or client work is permitted. List supported file formats, software versions, devices, or other requirements. Set expectations about refunds, replacements, updates, and how customers can get help. Write questions in the customer's voice, such as “What do I receive after purchasing?” instead of using an internal label such as “Delivery information.” ## Managing Existing FAQs You can edit, reorder, add, or delete FAQs at any time from the product editor. Changes appear on the dedicated public product page after you save. Duplicating a product does not currently copy its FAQs. Add the appropriate questions to the duplicated product separately so its answers stay accurate. ## FAQ Examples List the exact files, service, access, or other deliverables included with the purchase. Explain whether delivery is immediate, sent by email, available as a secure download, or arranged manually. Summarize the licence and link to the complete terms when applicable. Tell customers how to contact you and what information they should include in their request. ## Next Steps Configure product details, pricing, images, and visibility Send customers a direct product link or QR code # Product Sharing Source: https://docs.payreque.st/products-and-pricing/product-sharing Share products via links and QR codes from your dashboard ## Overview Share any product directly from your dashboard using a link or QR code. Product sharing generates a direct URL to your product's shop page that you can send to customers, post on social media, or print on marketing materials. ## How to Share a Product 1. Navigate to **Products** in your dashboard 2. Click on a product to open its detail page 3. Click the **Share** button in the header 4. A modal appears with: * **Product URL** — Direct link to the product in your shop * **QR Code** — Scannable code that opens the product page * **Copy Button** — One-click copy to clipboard The share URL uses your custom domain if configured, otherwise it uses your PayRequest subdomain. ## URL Format **With custom domain:** ``` https://yourdomain.com/product/[product-id] ``` **Without custom domain:** ``` https://payrequest.me/shop/[your-handle]/product/[product-id] ``` ## Smart Links vs. Product Sharing | Feature | Product Share | Smart Link | | - | - | - | | URL type | Direct product link | Custom branded path | | Analytics | No built-in tracking | Views, payments, conversion | | QR code | Yes | Yes | | Payment limits | No | Yes | | Customizable URL path | No | Yes | | Delivery (Email/SMS) | No | Yes | For marketing campaigns where you need analytics and branded URLs, use [Smart Links](/payment-processing/smart-links) instead. Product sharing is best for quick, one-off sharing needs. ## Need Help? Branded links with analytics Product configuration # Quantity-Based Pricing Source: https://docs.payreque.st/products-and-pricing/quantity-based-pricing Seat licenses and volume pricing # Quantity-Based Pricing Let customers choose how many units they want to buy — seat licenses, multi-packs, or anything else typically bought in bulk. The total price scales automatically with the quantity selected. Quantity selection is on by default for **physical/general one-time and recurring products**. It's automatically turned off for product types that are inherently single-item — Digital, Pay to Unlock (Image), Pay to Unlock (Audio), Pay to Unlock (Video), Pay to Access, AI Prompts, Commissions, Deposits, Bookings, and Service products. ## Enabling Quantity Selection In the product wizard or editor, find the **Allow customers to select quantity** toggle. For eligible product types, this defaults to on. Turn it off if you want customers to only ever buy one at a time. Once enabled, customers see a quantity selector on the payment page. ## How the Price Is Calculated ``` Total = (Base Price + Custom Field Markups) × Quantity ``` The customer picks a quantity on the payment page; the price updates live as they change it. Setup fees (if configured) are charged once per order, not multiplied by quantity. **Example:** A €25 seat license with quantity selection enabled — a customer selecting **4 seats** pays **€100.00** total. Combine quantity selection with a **Number** [custom field](/products-and-pricing/custom-fields) if you need more control over per-unit pricing tied to a specific attribute (like rental days), rather than a generic "how many of this product" quantity. ## FAQ Any one-time or recurring product where quantity makes sense — for example general goods, seat-based subscriptions, or multi-packs. It's disabled by default (and can't be re-enabled) for inherently single-item types: Digital, Pay to Unlock (Image), Pay to Unlock (Audio), Pay to Unlock (Video), Pay to Access, AI Prompts, Commissions, Deposits, Bookings, and Service. No. Setup fees are charged once per order regardless of the quantity selected. Use a **Number** custom field with per-unit pricing and Min/Max settings if you need fine-grained quantity limits — see [Custom Fields](/products-and-pricing/custom-fields). Yes — you can pass a pre-set quantity and lock it using URL parameters. See [Payment Page Dynamic Links](/payment-processing/payment-page-dynamic-links). ## Next Steps Learn about all product types and settings Add per-unit pricing with Number fields Configure one-time setup charges Pre-fill and lock quantities via URL # PayRequest Upload Source: https://docs.payreque.st/products-and-pricing/quick-upload Drop a file, set a price, get a payment link — the fastest way to sell a single file on PayRequest # PayRequest Upload **PayRequest Upload** is a one-page, WeTransfer-style shortcut for selling a single file. Drop a file, set a price, and get a shareable payment link in seconds — no product wizard, no shop setup. Available at [payrequest.me/upload](https://payrequest.me/upload) (also reachable at `payrequest.app/upload`). The page itself is open to everyone — you only need a PayRequest account at the final step, to publish the link. Drag and drop almost any file type — audio, video, images, ZIPs, 3D models, fonts, design files — up to 250MB The title is pre-filled from your filename and the file category is detected automatically — both editable For photos and audio tracks, flip on Pay to Unlock to sell behind a free preview instead of an instant download Behind the scenes it creates a normal product and a Smart Link for you — nothing to configure first ## How It Works Go to [payrequest.me/upload](https://payrequest.me/upload) and drag your file into the upload box, or click to browse. Files up to 250MB are accepted, in almost any format. PayRequest fills in a **Title** from your filename and shows the detected file category (e.g. "Audio", "Software & Code"). Adjust the title if you like. Enter what you want to charge. Your account's currency symbol is shown automatically. If you uploaded a photo or an audio track, a checkbox appears: **Activate Pay to Unlock (free preview)**. Turn it on to sell the file behind a blurred preview or a short audio clip instead of delivering it instantly — see [Pay to Unlock](/products-and-pricing/pay-to-unlock) for details. Click **Generate Payment Link**. If you're not signed in yet, you'll be asked to sign in or create a free account first — see below. Once that's done, your link is ready immediately: `payrequest.me/[handle]/[filename]`. ## Signing In Partway Through You don't need an account to fill out the form — only to publish the link. Clicking **Generate Payment Link** while signed out shows a **Sign in or create a free account to publish this link** prompt. Signing in or registering always happens on the main PayRequest app, not on payrequest.me. Once you're authenticated there (including two-factor authentication, if you use it), you're brought straight back to finish publishing — no need to re-select your file. If you don't have a PayRequest Page handle yet, one is created automatically so your link works right away. ## What Gets Created Every link from PayRequest Upload is backed by two ordinary PayRequest records — nothing exotic, and both are fully visible and manageable afterwards: | Created | Where to find it | | - | - | | A product (Digital Product, or Pay to Unlock if you enabled it) | **Products** in your dashboard | | A Smart Link pointing to that product | **Payment Page → Smart Links** | Because it's a normal Smart Link under the hood, everything documented in [Smart Links](/payment-processing/smart-links) — analytics, QR codes, payment limits, reminders — applies to links created via PayRequest Upload too. Uploaded the wrong file, or want to change the price? Edit the product from **Products** in your dashboard — the Smart Link keeps pointing to the same URL. ## FAQ No. You can drop a file, see the detected category, and fill in a title and price without signing in. An account is only required when you click Generate Payment Link. Almost anything except executable and script files (for security). This covers documents, spreadsheets, presentations, images, audio, video, archives, fonts, and common design and 3D formats. Yes — open the product from your dashboard and change its type, the same as any product created through the full product wizard. No. It's a standard product plus a standard Smart Link — you can edit, deactivate, password-protect, or delete it exactly like any Smart Link you create manually. ## Next Steps The delivery system behind every PayRequest Upload link Sell photos and tracks behind a free preview Manage, track, and customize the link PayRequest Upload created The full product wizard, for more control # Setup Fees Source: https://docs.payreque.st/products-and-pricing/setup-fees Add customizable one-time setup fees to products with custom names and descriptions ## Overview Setup fees let you add a one-time charge on top of a product's regular price. This is commonly used for onboarding costs, installation fees, deposits (borg), or activation charges. The setup fee is charged once during the first purchase and does not repeat for subscription renewals. Setup fees are fully customizable — you can change the name and description to match your business terminology. Instead of generic "Setup Fee", show "Borg", "Installation", "Onboarding Fee", or whatever fits your context. ## Enabling Setup Fees ### Step 1: Edit Your Product Navigate to **Products** → select a product → **Edit**. ### Step 2: Enable Setup Fee 1. Toggle **Has Setup Fee** to on 2. Enter the **Setup Fee Amount** (e.g., €25.00) 3. Optionally customize the name and description ### Step 3: Customize Name & Description When the setup fee toggle is enabled, two additional fields appear: **Setup Fee Name** (Optional) * Custom label for the fee * Default: "Setupkosten" (Setup Costs) * Examples: "Borg", "Installation Fee", "Onboarding", "Activation" **Setup Fee Description** (Optional) * Explanation shown alongside the fee * Default: "One-time setup fee for this service" * Examples: "Refundable deposit for equipment", "One-time professional installation" If you leave the name and description blank, the defaults are used automatically. You only need to fill these in if you want custom terminology. ## Where Setup Fees Appear Setup fees are displayed consistently throughout the customer journey: | Location | What's Shown | | - | - | | Shop product page | Fee name + amount below the product price | | Shopping cart | Separate line item with custom name | | Checkout summary | Fee listed with product, before total | | Invoice | Line item with custom name and description | | Order confirmation | Fee amount in order breakdown | ## Common Use Cases ### Borg (Deposit) Dutch businesses commonly use "Borg" for refundable deposits: ``` Product: Office Space Rental (€500/month) Setup Fee: €1,000 Name: "Borg" Description: "Refundable deposit, returned at end of contract" ``` ### Installation Fee For products requiring physical setup: ``` Product: Fiber Internet (€49.99/month) Setup Fee: €75.00 Name: "Installatiekosten" Description: "Professional installation at your location" ``` ### Onboarding Fee For SaaS products with initial setup: ``` Product: CRM Platform (€29/month) Setup Fee: €199.00 Name: "Onboarding Fee" Description: "One-time setup, data migration, and training session" ``` ### Activation Fee For services requiring account activation: ``` Product: Hosting Plan (€9.99/month) Setup Fee: €15.00 Name: "Activation Fee" Description: "One-time account activation and server provisioning" ``` ## Setup Fees with Subscriptions When a product has both a recurring price and a setup fee: 1. **First payment**: Regular price + setup fee 2. **All subsequent payments**: Regular price only The setup fee is clearly separated in the cart and checkout so customers understand it's a one-time charge. Setup fees do not affect subscription billing cycles. They are charged once at the initial purchase and never again, even if the subscription is paused and resumed. ## Frequently Asked Questions Yes. Edit the product, enable the setup fee toggle, and set the amount. New purchases will include the fee. Existing subscriptions are not affected. The setup fee is shown as a separate line item, not added to the product price. Customers see the product price and setup fee as distinct charges in the cart and checkout. Yes. Each product has its own setup fee name and description fields. You can call it "Borg" on one product and "Installation" on another. Yes. The setup fee appears as a separate line item on the invoice with your custom name and description. ## Need Help? Learn about all product configuration options Seat-based and quantity pricing # Trial Periods Source: https://docs.payreque.st/products-and-pricing/trial-periods Offer free trials for subscriptions # Trial Periods Let customers try a subscription product before they're charged. Their payment method is set up when they subscribe, but the first charge only happens automatically once the trial ends. Trial periods are only available for **recurring (subscription) products**. ## Enabling a Trial In the product wizard's pricing step, enable **Is Recurring** and configure your billing interval. A new section appears with trial settings. **Trial Duration (days)** — how many days the trial lasts, from 1 to 365 days. **Trial Description** — a short line explaining what's included, shown to the customer (e.g. "Full access for 14 days"). The trial applies to every new subscription created for this product from now on. Existing subscriptions are unaffected. ## How It Works for Customers 1. The customer subscribes and sets up their payment method (SEPA mandate, card, or other supported method) as normal 2. **No charge happens at signup** — the subscription status is `trial` 3. The customer has full access for the configured number of trial days 4. When the trial ends, PayRequest automatically charges the customer and the subscription moves to `active` 5. From then on, billing follows the product's normal billing cycle The subscription only converts to a paid, active subscription after a **successful** payment at the end of the trial. If the charge fails, the subscription follows your normal [failed payment handling](/subscriptions/failed-payment-handling) flow instead of silently becoming active. ## Where Customers See the Trial * The trial description (if set) is shown on the payment page when the customer subscribes * The customer portal shows the subscription status as **Trial** with the trial end date * Once the trial ends and payment succeeds, the status updates to **Active** ## FAQ No. Trials only apply to recurring/subscription products, since they work by delaying the first automatic charge. They can cancel like any other subscription — see [Cancellation Requests](/subscriptions/cancellation-requests). No charge occurs since the subscription never reached its first billing date. No. Trial settings only apply to new subscriptions created after you enable and configure the trial — existing subscriptions keep their original terms. Changing the trial duration on the product only affects new subscriptions going forward. Customers already in a trial keep the trial end date that was set when they signed up. ## Next Steps Set up recurring billing for your products Understand every subscription status, including Trial What happens if the trial-to-paid charge fails Learn about all product types and settings # Duplicate Products Source: https://docs.payreque.st/products/duplicate-products Learn how to quickly create copies of your existing products to save time when adding similar items to your catalog # Duplicate Products The product duplication feature allows you to quickly create copies of your existing products, saving you time when you need to add similar items with slight variations in name, price, or other details. ## Why Use Product Duplication? Product duplication is perfect when you need to: * Create variations of existing products (different sizes, colors, or versions) * Set up similar service packages with different pricing * Add seasonal or promotional versions of products * Create products with similar configurations but different details ## How to Duplicate a Product ### Step 1: Navigate to Your Product 1. Go to your dashboard 2. Click on "Products" in the sidebar 3. Find the product you want to duplicate 4. Click on the product to open its detail page ### Step 2: Start the Duplication Process 1. On the product detail page, look for the "Duplicate" button 2. Click the "Duplicate" button 3. A modal window will open with duplication options ### Step 3: Customize Your Duplicate In the duplication modal, you can: **Product Name** * The original name is pre-filled with "(Copy)" added * Edit the name to whatever you prefer * Example: "Premium Plan" becomes "Premium Plan (Copy)" **Product Price** * The original price is pre-filled * Change the price if needed for your variation * Keep the same price if it's identical **Other Settings** * All other product settings (description, features, etc.) are copied exactly * You can edit these after the product is created ### Step 4: Create the Duplicate 1. Review your changes 2. Click "Duplicate Product" 3. The new product will be created and you'll be redirected to it 4. Edit any additional details as needed ## What Gets Copied? When you duplicate a product, **everything** is copied including: ### Basic Information * Product description * Category assignment * Product type (physical, digital, service, subscription) * Status (active/inactive) ### Pricing & Billing * Tax rate settings * Currency settings * Subscription settings (if applicable) * Setup fees and trial settings ### Advanced Features * Custom fields configuration * Stock quantity settings * Image (if any) * All metadata and technical settings ### What You Can Immediately Change * **Product name** - Customize in the duplication modal * **Price** - Adjust pricing in the duplication modal * **Everything else** - Edit after creation ## Common Use Cases ### Creating Product Variations **Example: T-Shirt Shop** 1. Create "Basic T-Shirt - Medium" 2. Duplicate it to create "Basic T-Shirt - Large" 3. Change only the name in the duplication modal 4. Repeat for other sizes ### Service Package Tiers **Example: Consulting Services** 1. Create "Basic Consultation Package" 2. Duplicate to create "Premium Consultation Package" 3. Update name and price in duplication modal 4. Edit the full product later to add premium features ### Seasonal Products **Example: Holiday Specials** 1. Have "Regular Website Design" 2. Duplicate to create "Holiday Special - Website Design" 3. Adjust price for holiday discount 4. Update description later to mention holiday terms ### Subscription Plan Variations **Example: Software Plans** 1. Create "Monthly Plan" 2. Duplicate to create "Annual Plan" 3. Change name and adjust pricing 4. Later edit billing frequency settings ## Tips for Effective Product Duplication ### Naming Strategies * Add descriptive suffixes: "(Large)", "(Premium)", "(Annual)" * Use clear differentiators: "Basic vs Pro vs Enterprise" * Include key differences in the name: "With Setup", "No Setup" ### Pricing Considerations * Calculate variations carefully (discounts, premiums) * Consider bulk pricing for quantity differences * Factor in different cost structures for variations ### Post-Duplication Editing After duplicating, remember to: 1. **Update the description** to reflect differences 2. **Change the image** if the product looks different 3. **Adjust custom fields** if they're different for this variation 4. **Review category assignment** - might belong in a different category ### Organization Tips * Use consistent naming patterns across similar products * Group related products in the same category * Consider using tags to identify product families ## Advanced Workflows ### Bulk Product Creation For creating many similar products: 1. Start with one well-configured "template" product 2. Duplicate it multiple times 3. Batch edit the copies with your variations 4. This is faster than creating each from scratch ### Testing New Products Before launching a new product type: 1. Duplicate an existing successful product 2. Modify it to test new pricing or features 3. Launch as a test without affecting the original 4. Keep or remove based on performance ### Seasonal Campaigns For holiday or promotional periods: 1. Duplicate your regular products 2. Add seasonal naming and pricing 3. Set them as inactive until the campaign starts 4. Activate when ready, deactivate when done ## Troubleshooting **Q: I duplicated a product but don't see it in my list** A: Check if the duplicate was created as "inactive". You may need to activate it in the product settings. **Q: Can I duplicate a product to a different category?** A: The duplicate is created in the same category as the original. You can change the category by editing the duplicated product. **Q: What happens to custom fields when I duplicate?** A: All custom field configurations are copied exactly. You can modify them in the duplicated product if needed. **Q: Can I duplicate subscription products?** A: Yes! All subscription settings are copied, including billing frequency, trial periods, and setup fees. **Q: Is there a limit to how many times I can duplicate a product?** A: No, you can duplicate products as many times as needed. **Q: Can I undo a duplication?** A: You can delete the duplicated product if you don't need it. The original product is never affected by duplication. # Audit Logs Source: https://docs.payreque.st/security-and-compliance/audit-logs PayRequest's audit trail lives in the Billing Activity Log — who did what, when, and from where # Audit Logs PayRequest's audit trail is the **Billing Activity Log**, covered in full detail in [Billing Activity Log](/organization-and-automation/activity-tracking). This page is a short pointer for anyone specifically looking for "audit logs" from a security/compliance angle. There isn't a separate "Audit Logs" screen — the Activity Log **is** the audit log. Every entry is immutable, timestamped, and records who performed the action, from which IP address and user agent. ## What It Covers for Compliance Each Activity Log entry captures: | Field | Purpose | | - | - | | `user_id` | Attribution — which team member (or "System" for automated/webhook actions) performed the action | | `action` | What happened (31+ tracked event types across subscriptions, invoices, customers, payments, mandates) | | `ip_address` | Source IP of the request | | `user_agent` | Browser/client that made the request | | `created_at` | Precise timestamp | | `details` | Full JSON context (old/new values, reasons, related IDs) | Entries cannot be edited or deleted — this is what makes the log usable as an audit record rather than just an activity feed. ## Access Navigate to **Activity Log** in your dashboard sidebar. Standard users see only their own actions; admin users on multi-user accounts see activity from the whole team. ## FAQ Not a one-click export today. The Activity Log is view-only in the dashboard — for a formatted compliance export, contact support. Yes, activity logs are retained indefinitely with no automatic deletion. ## Next Steps Full reference: event types, filtering, and examples Secure the accounts that show up in this log # GDPR Compliance Source: https://docs.payreque.st/security-and-compliance/gdpr-compliance The data protection controls PayRequest gives you as a data controller: export, account deletion, customer archiving, and encryption at rest # GDPR Compliance PayRequest is the tool you use to run your billing — for GDPR purposes, **you** (the business using PayRequest) are typically the data controller for your customers' data, and PayRequest acts as a data processor. This page describes the concrete technical controls PayRequest provides; it isn't a legal statement that PayRequest or your use of it is fully GDPR compliant. Talk to your own legal advisor about what your business specifically needs. PayRequest does not currently offer a self-service "delete this customer's data" or "export this customer's data" tool for a single customer record. The controls below operate at the account level (your own PayRequest account) or as bulk exports, not as a per-customer erasure/portability workflow. ## Data Controls Available Today From **Bulk Actions**, you can export customers, subscriptions, products, invoices, and orders as CSV — useful for data portability requests or your own records, covering the fields you'd need to hand over (name, email, phone, company, tags, etc. for customers). From a customer's record, you can archive them (with a reason and note). This flags the customer as inactive and hides them from active lists — it does **not** delete or anonymize their underlying data. All order, invoice, and subscription history for an archived customer remains intact and can be restored by reactivating them. From **Settings → Delete Account**, typing `DELETE` to confirm permanently deletes your PayRequest login, removes your API tokens, and removes your profile photo. This is account-level and applies to your own PayRequest user account. Add [2FA](/security-and-compliance/two-factor-authentication) to reduce the risk of unauthorized access to the customer data stored in your account. ## What's Encrypted at Rest * Two-factor authentication secrets and recovery codes. * API keys, OAuth access tokens, and refresh tokens for connected services and payment providers. * Card data is never stored in the first place — see [PCI Compliance](/security-and-compliance/pci-compliance) for how card payments are handled entirely by your connected payment processor. ## Multi-Tenant Data Isolation Every business's data — customers, orders, invoices, subscriptions — is scoped to that business's account. One PayRequest user cannot query or see another business's customer records. ## FAQ Not as a one-click action. Archiving a customer hides them from active views but keeps their records (needed for invoicing/tax history in most jurisdictions). For a request to fully delete a specific customer's data, contact support to discuss options. Customers can view and download their own invoices and order history from the customer portal. There isn't a dedicated "download all my data" export button distinct from that. Deleting your account removes your own login and account access. Before deleting your account, export any data you need to retain — see the export step above. Contact support directly for DPA requests — this isn't something documented as a self-serve download at this time. PayRequest's database runs on a Hetzner server in the EU. For specifics relevant to your compliance obligations, contact support. ## Next Steps How card payment data is handled Track who accessed or changed what Add a second login factor Reach support for data requests # PCI Compliance Source: https://docs.payreque.st/security-and-compliance/pci-compliance How PayRequest handles card payment security: PayRequest never collects, transmits, or stores raw card numbers # PCI Compliance PayRequest is a billing platform, not a card processor. Every payment method that involves a card — one-time payments and recurring mandates alike — is handled entirely by the connected payment provider (primarily [Mollie](/payment-processing/setting-up-payment-providers), with Stripe, PayPal, and Payoneer available as alternatives). This is a deliberate architecture choice, not just a policy: it's how the checkout code actually works. PayRequest itself does not hold a PCI DSS certification. What follows describes the technical measures in place — Mollie, PayRequest's primary processor, is PCI DSS Level 1 certified for the card data it handles on your behalf. Talk to your own compliance advisor about what this means for your specific business and jurisdiction. ## How Card Data Actually Flows At checkout, PayRequest never renders a card number, expiry, or CVC input field — there is no such form anywhere in the product. Payment collection happens on the processor's own hosted page. PayRequest creates a payment with Mollie (or Stripe/PayPal/Payoneer) and redirects the browser to the `checkoutUrl` / `returnUrl` returned by that provider's API. The customer enters their card details directly on the provider's hosted, PCI-compliant page — never on a PayRequest-controlled page. Once payment completes, the provider sends a webhook with the payment status and a masked reference (e.g. a mandate ID or last-4 digits) — never the full card number. For saved payment methods (mandates), PayRequest stores the provider's mandate ID and the masked card summary it returns (card brand + last 4 digits) so customers can recognize their saved method — for example `•••• 4242`. The full card number and CVC are never transmitted to or stored by PayRequest at any point. ## What This Means in Practice | Question | Answer | | - | - | | Does PayRequest ever see a full card number? | No — card entry happens on the processor's hosted checkout, outside PayRequest's servers. | | Does PayRequest store CVC/CVV? | No — CVC is never collected by PayRequest and is not a field that exists anywhere in the codebase. | | What does PayRequest store for a saved card? | The processor's mandate/token ID and a masked display value (card brand, last 4 digits) — sufficient to show it in the customer's saved payment methods, not to reconstruct the card. | | Are provider API credentials protected? | Yes — connected-provider API keys, OAuth access tokens, and refresh tokens (Mollie, and other integrated services) are encrypted at rest before being written to the database. | | Is this true for every supported payment method? | Yes for card-based methods across all supported processors — Mollie, Stripe, PayPal, and Payoneer are all integrated via redirect/hosted-checkout flows, not embedded card forms. | ## Reducing Your Own Risk Add 2FA to your dashboard login to protect access to payment settings and customer data. Every account and payment-related action is logged with who, what, and when. ## FAQ PayRequest does not directly handle raw cardholder data — that happens on the payment processor's infrastructure. This significantly reduces PayRequest's own PCI scope, but PayRequest doesn't claim its own PCI DSS certification. The certification applies to Mollie (and other connected processors) for the systems that actually touch card data. A mandate/token reference and a masked summary (card brand and last 4 digits) returned by the processor — never the full PAN, expiry, or CVC. Yes. Every supported card-capable processor is integrated through a redirect or hosted-checkout flow, so the same "PayRequest never touches raw card data" model applies regardless of which processor you connect. See Saved Payment Methods for the full mandate lifecycle. # Two-Factor Authentication Source: https://docs.payreque.st/security-and-compliance/two-factor-authentication Protect your PayRequest login with a TOTP authenticator app and recovery codes # Two-Factor Authentication Two-factor authentication (2FA) adds an authenticator-app code as a second step when logging into your PayRequest dashboard, on top of your regular magic-link/password login. PayRequest uses passwordless (magic link) authentication for the initial login step, so enabling 2FA does not require re-entering your password to turn on or off — only the authenticator code itself is required to confirm setup. ## How It Works Go to **Settings → Security** (`/settings?tab=2fa`). PayRequest generates a TOTP secret and shows a QR code plus a manual setup key. Scan the QR code with Google Authenticator (or any TOTP-compatible app) — or enter the setup key manually if you can't scan. Enter the 6-digit code your authenticator app generates to confirm setup. Until you confirm, 2FA isn't actually active on your account. After confirming, PayRequest generates a set of recovery codes. Store them somewhere safe (a password manager) — each one can be used once to log in if you lose access to your authenticator app. ## Logging In With 2FA Enabled After entering your normal login credentials, you're prompted for a 6-digit code from your authenticator app. If you don't have access to your device, you can use one of your recovery codes instead. Login attempts with a 2FA code are rate-limited to prevent brute-forcing the code. ## Managing 2FA | Action | What it does | | - | - | | **Show Recovery Codes** | Reveals your current set of recovery codes (stored encrypted). | | **Regenerate Recovery Codes** | Invalidates your old recovery codes and issues a new set — do this if you suspect a code has been exposed. | | **Disable** | Turns off 2FA entirely and removes the stored secret and recovery codes. | Your 2FA secret and recovery codes are encrypted at rest — they're never stored or displayed in plain text outside of the setup/recovery-codes screen itself. ## FAQ Any standard TOTP app — Google Authenticator, Authy, 1Password, and similar all work since PayRequest uses the standard TOTP protocol. You won't be able to complete the 2FA challenge yourself. Contact support to regain access to your account. No, it's optional but strongly recommended, especially since your dashboard has access to customer data and payment configuration. No — 2FA in PayRequest is for your own dashboard login. The customer-facing portal uses its own separate, session-based login. No. PayRequest uses magic-link (passwordless) authentication, so enabling/disabling 2FA is confirmed with an authenticator code rather than a password. ## Next Steps See every login and account change Data protection controls for your account # Apple Wallet Card Source: https://docs.payreque.st/shop-and-checkout/apple-wallet-card Carry your PayRequest Page as a card in Apple Wallet — show it to customers and let them scan to pay # Apple Wallet Card Add your PayRequest Page to Apple Wallet as a digital card. Instead of pulling up a QR code on screen every time, you hold one card in Wallet that you can show, AirDrop, or simply have ready on your Lock Screen whenever a customer wants to pay you. Apple Wallet Card is available on iPhone. Android/Google Wallet support is planned for a future release. Add your page to Wallet directly from your PayRequest Page settings — no app to install The card includes a scannable QR that opens your PayRequest Page, just like your existing QR code Shows your business name, handle, and tagline in PayRequest's signature blue ## How It Works Go to **PayRequest Page** from the main menu. Next to your QR code, click **Add to Apple Wallet**. On iPhone, this opens the standard Apple Wallet "Add" screen. Tap **Add** to save the card. Open the card from Wallet (or your Lock Screen) any time. Customers scan the QR code on the card with their phone camera to land directly on your PayRequest Page and pay. ## What's on the Card | Section | Shows | | - | - | | Top (small text) | Your business or page name | | Middle (large text) | Your PayRequest Page handle, e.g. `@yourname` | | Below that | Your tagline, if you've set one in [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) | | QR code | Scans to `payrequest.me/yourhandle` — the same link as your existing QR code | | Back of card | A tappable link to your PayRequest Page | The card always uses PayRequest's signature blue background, regardless of your page's accent color — so it reads clearly next to the PayRequest logo no matter how you've styled your page. ## Frequently Asked Questions Not yet. The card is generated at the moment you add it to Wallet. If you change your handle, business name, or tagline afterward, re-add the card from your PayRequest Page settings to get an updated version. Automatic live updates are planned for a future release. The card is meant for you to hold and show to customers — they scan the QR code rather than adding the card themselves. If you'd like to share the link directly instead, use your existing [QR code](/payment-processing/qr-code-payments) or [PayRequest Page link](/shop-and-checkout/sales-page-styling). Not yet — Google Wallet support is planned. Android users can still scan the QR code on your card or your existing PayRequest Page QR code. No special app — Apple Wallet is built into every iPhone. Just tap **Add to Apple Wallet** from your PayRequest Page settings using Safari on your iPhone. ## Related Documentation Customize the name, tagline, and accent color shown on your page More ways to share your payment links via QR code # Celebration GIF Source: https://docs.payreque.st/shop-and-checkout/celebration-gif Show a fun GIF to customers the moment they complete a payment — a small touch that makes paying feel great. # Celebration GIF When a customer finishes paying, why show them a plain checkmark when you can make them smile? The Celebration GIF feature lets you pick a fun animated GIF that plays on the payment success page — right after the money lands. Celebration GIF on payment success page

## How It Works Once you've set a GIF, every customer who successfully pays through your PayRequest Page or invoice link will see it on the confirmation screen. It replaces the default success icon and appears above the payment details. No extra setup needed on the customer side — it just shows up automatically. ## Setting It Up 1. Go to **PayRequest Page** in the main menu 2. Click the **Settings** tab 3. Scroll down to the **Celebration GIF** section 4. Search for a GIF or browse the suggestions (default shows celebratory and payment-themed GIFs) 5. Click any GIF to select it — you'll see a green preview confirming your choice 6. Click **Save Settings** Search terms like "celebrate", "money", "happy", "congrats", or "party" work great for payment success moments. ## Changing or Removing a GIF To swap the GIF, simply click a different one from the grid and save. To remove it entirely, click the **Remove GIF** button that appears next to your active preview, then save. The success page will revert to the standard checkmark icon. ## Where Customers See It The GIF appears on: * **Your payment success page** — shown immediately after a customer completes payment via your PayRequest Page link * **Your invoice payment page** — when a customer opens an invoice link (`payrequest.me/yourhandle?invoice=...`) for an invoice that's already been paid The GIF is only shown when a payment is confirmed as **paid**. Pending or processing payments show the standard success screen. ## Tips for Picking a Good GIF A creative agency might go for something quirky and fun. A financial consultancy might prefer something more understated — a subtle confetti or thumbs-up. Pick what fits your vibe. The best GIFs are short (2–4 seconds) and loop cleanly. Long GIFs can feel distracting after the third replay. Flashing or very fast-moving GIFs can be uncomfortable. The success page is a calm, positive moment — keep the energy warm rather than chaotic. ## Powered by KLIPY GIFs are served by [KLIPY](https://klipy.com), a high-performance GIF and media platform. The GIF picker searches the KLIPY library directly from your settings panel. ## Related Customize your avatar, colors, and layout Success messages and other checkout settings # Checkout Customization Source: https://docs.payreque.st/shop-and-checkout/checkout-customization What the shop checkout page collects, how payment method options adapt to the cart, and how to pre-fill or lock fields via URL # Checkout Customization The shop checkout page (`/shop/{yourshop}/checkout`) adapts to what's actually in the customer's [cart](/shop-and-checkout/shopping-cart) — the fields shown, the payment method options, and the amount charged all depend on the products being purchased. This page covers the multi-product shop checkout. Single-product PayRequest Page checkouts have their own styling options — see [PayRequest Page Styling](/shop-and-checkout/sales-page-styling). ## How It Works Every checkout collects name, email, address, city, postal code, and country. If a customer is already logged into the [customer portal](/customer-management/customer-health), these fields are pre-filled from their saved profile. * **Only one-time products in the cart** → customer pays once, no mandate needed. * **A recurring product is in the cart** → checkout asks for a payment mandate. Logged-in customers with an existing mandate can reuse it (**Existing Mandate**); otherwise they set up a **New Mandate** (credit card or automatic/direct debit, depending on what payment methods you've enabled). * **A deposit product is in the cart** (authorization hold) → payment method is locked to **credit card**, since that's the only method supporting the manual-capture flow deposits rely on. See [Security Deposits](/payment-processing/security-deposits). The methods offered at checkout mirror what you've enabled in [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) — checkout doesn't have its own separate method list. On submit, the order (and invoice, if **Auto Create Invoices** is on for your shop) is created, spam protection checks run, and the customer is redirected to complete payment. ## Pre-Filling and Locking Fields via URL Checkout links can pre-fill (and optionally lock) customer details and products by appending query parameters, useful for embedding pre-built checkout links elsewhere: | Parameter | Effect | | - | - | | `name`, `email`, `address` (or `adress`), `city`, `postal`, `country` | Pre-fills the matching billing field | | `product` + `quantity` | Adds a specific product (and quantity) to the cart on load | | `cf_{fieldname}`, `customfield_{fieldname}`, or `product_customfield_{fieldname}` | Sets a custom field value for the product being added | | `disabled=true` | Greys out the billing fields so the pre-filled values can't be edited | Products added via `?product=` skip the "is this product currently visible" check, so a direct checkout link keeps working even for a product you've hidden from the shop listing — useful for private/unlisted offers, but worth remembering if you expect a hidden product to be fully unreachable. For single-product links with more options (locking quantity, generating shareable links from the dashboard), see [Payment Page Dynamic Links](/payment-processing/payment-page-dynamic-links). ## Shop-Wide Checkout Settings These are configured once on the [Shop Setup](/shop-and-checkout/shop-setup) page and apply to every checkout: * **Tax Display** — inclusive or exclusive pricing shown at checkout. * **Auto Create Invoices** — whether an invoice is generated automatically per order. * **Allow Invoice Subscriptions** — whether recurring products can be paid by invoice instead of an automatic mandate. ## Fraud & Abuse Protection Every checkout submission is checked against your [Spam Protection](/shop-and-checkout/spam-protection) settings (honeypot field, rate limiting, country blocking) before the order is created. If a customer abandons checkout without completing payment, [Checkout Recovery](/shop-and-checkout/checkout-recovery) can follow up automatically. ## FAQ Not on the shop cart checkout — name, email, and full address are always required there. If you need a lighter checkout, a single-product PayRequest Page checkout link may fit better depending on the product type. Not currently — the cart checkout doesn't have a coupon/discount code field. That product is a deposit (authorization hold) product. Mollie's manual-capture flow, which deposits require, is only supported for credit card, so checkout restricts the whole cart to that method when a deposit product is present. Yes — URL parameters take priority and pre-fill over the customer's saved profile data. ## Next Steps How products get added and priced Block bots and unwanted traffic Win back abandoned checkouts Enable payment methods # Checkout Recovery Source: https://docs.payreque.st/shop-and-checkout/checkout-recovery Recover lost sales by automatically tracking abandoned checkouts and sending personalized recovery emails ## Overview Checkout Recovery helps you recover lost sales by tracking customers who start but don't complete their checkout. When a customer abandons their cart or payment, you can send them a personalized email with a direct link to resume exactly where they left off. Studies show that abandoned cart emails have an average open rate of 45% and can recover 10-15% of lost sales. Enabling Checkout Recovery can significantly boost your revenue. ## Key Features * **Automatic Tracking**: Every checkout attempt is tracked automatically across payment pages, shop checkout, and smart links * **Recovery Emails**: Send personalized emails with a direct link to complete the order * **Recovery Analytics**: Track recovered revenue and conversion rates * **Multiple Reminders**: Send up to 3 reminder emails per abandoned checkout * **Source Tracking**: See where customers abandoned (payment page, shop, or smart link) * **Conversion Attribution**: Know whether customers converted organically or from a recovery email ## How It Works 1. **Customer starts checkout** - When a customer enters their email and begins the payment process, a checkout attempt is recorded 2. **30 minutes of inactivity** - If no payment is completed within 30 minutes, the checkout is marked as abandoned 3. **You send recovery email** - From the Checkout Attempts page, send a recovery email with one click 4. **Customer completes order** - The email contains a direct link that resumes their checkout with all details pre-filled 5. **Revenue recovered** - The system tracks the conversion and attributes it to your recovery efforts Checkout attempts are only created when a customer provides their email address. Anonymous visitors who don't enter contact details cannot receive recovery emails. ## Enabling Checkout Recovery Navigate to **Settings** → scroll down to find the **Checkout Recovery** section. 1. Toggle **Enable Checkout Recovery** to on 2. Click **Save Settings** Once enabled, the system will automatically start tracking checkout attempts across all your payment pages and shop. PayPal checkouts started from a Smart Link are included. PayRequest records the attempt when the buyer provides enough checkout information and starts the PayPal order. Tracking only begins after **Enable Checkout Recovery** is turned on; enabling it later does not recreate older abandoned attempts. ## Understanding Checkout Statuses Each checkout attempt has one of three statuses: | Status | Description | Color | | - | - | - | | **In Progress** | Customer is actively in checkout (less than 30 min) | Amber | | **Abandoned** | No activity for 30+ minutes, no payment completed | Red | | **Converted** | Payment was successfully completed | Green | ## Viewing Checkout Attempts Navigate to **Checkout Attempts** from your dashboard sidebar to see all tracked checkouts. ### Stats Overview At the top of the page, you'll see key metrics for the current month: * **This Month**: Total checkout attempts started * **Abandoned**: Checkouts that weren't completed * **Converted**: Successfully completed payments * **In Progress**: Active checkout sessions * **Recovered Revenue**: Total revenue from recovered checkouts ### Filtering Options Use the filters to find specific checkout attempts: **Search**: Find by customer email or name **Status Filter**: * All Statuses * In Progress * Abandoned * Converted **Source Filter**: * Payment Page * Shop * Smart Link **Date Filter**: * Today * This Week * This Month * All Time ## Sending Recovery Emails To send a recovery email for an abandoned checkout: 1. Go to **Checkout Attempts** 2. Filter by **Abandoned** status to see recoverable checkouts 3. Find the checkout you want to recover 4. Click the **Send Recovery Email** button (envelope icon) You can send a maximum of 3 recovery emails per checkout attempt. The "Reminders" column shows how many have been sent. ### What Customers Receive The recovery email includes: * **Personalized greeting** with the customer's name * **Order summary** showing the product and amount * **Prominent "Complete Your Order" button** linking directly to their checkout * **Urgency messaging** that increases with each reminder **First reminder**: Friendly notification that items are waiting **Second reminder**: Gentle follow-up with reminder of what they selected **Third reminder**: Final notice with urgency about session expiration ### Recovery Link The email contains a secure recovery link that: * Pre-fills the customer's information * Restores their cart contents * Takes them directly to the payment step * Expires after 24 hours for security ## Conversion Tracking When a customer completes their checkout, the system tracks how they converted: | Conversion Source | Description | | - | - | | **Organic** | Customer returned and paid on their own | | **Reminder Email** | Customer clicked the recovery email link | | **Manual** | You marked the checkout as converted manually | Use conversion tracking to measure the effectiveness of your recovery emails. If most conversions come from reminder emails, your recovery strategy is working! ## Manual Conversion Sometimes a customer may complete their purchase through a different channel (phone call, new checkout, bank transfer). You can manually mark a checkout as converted: 1. Find the abandoned checkout 2. Click the **...** menu 3. Select **Mark as Converted** This helps keep your analytics accurate and prevents sending recovery emails for orders that were already completed. ## Best Practices ### Timing Your Recovery Emails **First email**: Send within 1-2 hours of abandonment for best results **Second email**: Wait 24 hours before the second reminder **Third email**: Send 48-72 hours after the first, with urgency messaging ### Writing Effective Recovery Emails The default recovery email is professionally designed, but here are tips for maximizing success: * **Act quickly**: The sooner you send, the higher the conversion rate * **Be helpful, not pushy**: Position it as a reminder, not a sales pitch * **Include the product**: Remind them what they were about to purchase * **Make it easy**: The one-click recovery link removes all friction ### When NOT to Send Recovery Emails * If the customer contacted you about an issue * If you know they completed the purchase another way * If too much time has passed (more than a week) * If you've already sent 3 reminders ## Analytics in Business Insights Checkout recovery metrics also appear in your **Business Insights** dashboard: * **Abandoned Today**: Number of checkouts abandoned in the last 24 hours * **Recovered This Week**: Checkouts converted after abandonment * **Recovered Revenue**: Total value of recovered sales * **Abandonment Rate**: Percentage of checkouts that don't complete Use these metrics to: * Identify patterns in abandonment timing * Measure recovery email effectiveness * Spot issues with your checkout flow * Track improvement over time ## Source Types Checkouts are tracked from three sources: ### Payment Page Direct payment links where customers enter an amount or pay for a specific product. ### Shop Checkout Your online shop's checkout process when customers add items to cart and proceed to payment. ### Smart Link Branded payment links you've created for campaigns, social media, or QR codes. Tracking works automatically for all three sources once Checkout Recovery is enabled. No additional configuration needed. ## Deleting Checkout Attempts To remove a checkout attempt from your records: 1. Click the **...** menu on the checkout row 2. Select **Delete** 3. Confirm the deletion Deleted checkout attempts cannot be recovered. Only delete records you're certain you don't need. ## Troubleshooting ### Recovery emails not sending **Check:** 1. Checkout Recovery is enabled in Settings 2. The checkout has a valid email address 3. You haven't exceeded 3 reminders 4. Your email configuration is working (Settings → Email) ### Customer says they didn't receive the email **Solutions:** 1. Ask them to check spam/junk folder 2. Verify the email address is correct 3. Try sending another reminder (if under limit) 4. Contact them through another channel ### Checkout shows as "In Progress" indefinitely **Cause:** The 30-minute timeout hasn't elapsed yet, or the system check hasn't run. **Solution:** Wait for the next system check (runs every few minutes) or check back later. ### Customer converted but still showing as abandoned **Cause:** Payment may have been processed through a different checkout or the connection was lost. **Solution:** Use "Mark as Converted" to manually update the status. ## Frequently Asked Questions Checkout attempts are stored indefinitely so you can track historical patterns and analytics. You can manually delete individual attempts if needed. The recovery email uses a professional template with your business name and branding colors. Custom email templates for checkout recovery will be available in a future update. Yes, as long as the customer enters their email address during checkout. The email address is required to send recovery emails. No. Recovery emails are sent manually by you. This gives you control over when and which customers receive reminders. Automated recovery sequences may be added in a future update. If a customer clicks an expired recovery link (after 24 hours), they'll be taken to your normal checkout page. Their details won't be pre-filled, but they can still complete the purchase. Yes, the checkout attempt record includes the product name and amount. For shop checkouts with multiple items, the full cart contents are preserved. Yes. Checkout tracking only captures information the customer actively provides (email, name). The data is stored securely and can be deleted upon request. Include mention of checkout recovery in your privacy policy. Compare your "Recovered Revenue" metric against "Abandoned" checkouts. A healthy recovery rate is typically 10-15% of abandoned checkouts. Track this over time to optimize your recovery timing. ## Need Help? Create branded payment links Configure your online shop Set up payment pages Configure email settings # Coffee Tips Source: https://docs.payreque.st/shop-and-checkout/coffee-tips Turn Donation Mode into a 'Buy Me a Coffee'-style tip jar with a drinks menu, donor messages, GIFs, and automatic X (Twitter) profile pictures. # Coffee Tips Coffee Tips is a friendlier flavor of [Donation Mode](/shop-and-checkout/donation-mode) built for creators, streamers, open-source maintainers, and anyone who wants small, casual support instead of a formal "donate" ask. Instead of typing a random amount, supporters pick a drink from a menu — an Espresso, a Latte, a Cappuccino — and it shows up in a public feed as **"Alex bought a Cappuccino"**. Coffee Tips is a style switch inside Donation Mode, not a separate product or page type. Everything from your [PayRequest Page](/shop-and-checkout/sales-page-styling) — your avatar, tagline, and accent color — stays exactly as it is; only the tipping experience changes. ## Overview Pick from 8 ready-made drinks (Espresso, Americano, Cappuccino, Latte, Mocha, Iced Coffee, Hot Chocolate, and plain Coffee), each with its own fixed price and a hand-drawn cup icon. Supporters can leave a short thank-you note and pick a GIF to go with it, straight from a built-in GIF search. If a supporter shares their X (Twitter) link, their real name, profile photo, and verified badge appear automatically — no upload needed. Supporters can choose to stay anonymous, but by default their message, GIF, and social link are shown publicly — most people want the shoutout. ## How It Works Open **PayRequest Page** from the dashboard, scroll to **What to show on your page**, and click the **Donation goal** tab. Under **Donation style**, switch from **Generic** to **Coffee Tips**. Your goal card, progress bar, and donor feed all switch to the coffee-themed wording ("Recent coffees", "Be the first to buy a coffee!"). A **Coffee** entry is added by default. Add or remove drinks from the fixed catalog — each card shows its name, price, and cup icon. There's no free-text pricing; every drink's price is set by PayRequest so the menu stays simple and consistent for supporters. Give the goal a title like "Help keep the servers running" or "Coffee fund for late-night updates" — it appears above the progress bar. Same as regular Donation Mode: pick a target amount and choose **Monthly** (auto-resets on the 1st) or **One-time**. Your page at `payrequest.me/` now shows the drinks menu instead of a plain amount field. ## What Supporters See Instead of typing an amount, visitors pick a drink card from the menu — each shows its own cup icon, name, and price. After picking a drink and paying, they can optionally: * **Leave a message** — a short note (up to 500 characters), shown under their name in the feed * **Add a GIF** — searched right from the checkout page, no external links needed * **Share a social link** — X (Twitter), Instagram, GitHub, YouTube, Twitch, and more (see below) * **Choose visibility** — a checkbox, checked by default, for showing their message/GIF/social link publicly. Unchecking it keeps their name, drink, and amount in the feed but hides the message, GIF, and link. ## The X (Twitter) Integration This is the feature that makes the feed feel alive: when a supporter pastes their X profile link (`x.com/yourname` or `twitter.com/yourname` — with or without `https://`), PayRequest looks them up and automatically shows: * Their **real profile photo**, pulled live from X — no need to upload anything * Their **display name**, auto-filled into the name field if they hadn't typed one * A **blue verified checkmark** next to their name in the feed, if their account is verified Supporters don't need an X account to tip — the social link is entirely optional. It's simply a shortcut so regulars and fans get recognized properly in the feed instead of showing up as a plain "Anonymous" or a typed name. The same auto-avatar trick works for other platforms too — Instagram, TikTok, GitHub, YouTube, Twitch, Discord, Telegram, Reddit, and a dozen more. X is the only one that also pulls the display name and verified badge; the others show the profile picture only. ## The Coffee Feed Each paid tip shows up as one card in the feed: ``` [avatar] Alex ✓ 5m ago bought ☕ Cappuccino €3.50 "Keep the good work coming!" [ GIF ] ``` * **Avatar** — the supporter's X profile photo (if shared), or a generated placeholder * **Name + verified badge** — clickable through to their profile if a social link was shared * **Drink badge** — the exact drink they bought, with its cup icon * **Amount** — the drink's fixed price * **Message and GIF** — shown only if the supporter left one and kept visibility on. Click any GIF to see it full-size. Anonymous or privacy-toggled tips still show the drink and amount — only the message, GIF, and social link are hidden, keeping the feed honest without exposing anyone who wants to stay private. ## Best Practices **Keep the menu short.** 3–5 drinks is plenty — Coffee, Cappuccino, and one "big tip" option like a Mocha or Hot Chocolate covers most budgets without overwhelming the choice. **Ask supporters to share their X link.** A feed full of real faces and names feels far more like a community than a list of "Anonymous — €3.50" rows. Mention it in your page tagline or stream/community rules. **Reply to messages publicly.** Since messages and GIFs default to public, screenshotting a favorite one and thanking the supporter (on stream, in a newsletter, in Discord) encourages the next person to leave one too. **Pair it with a monthly goal.** "X coffees to cover this month's hosting" is a concrete, relatable ask that resets automatically — no manual bookkeeping needed. ## Frequently Asked Questions Not yet — drinks come from a fixed catalog (name, price, and cup icon are pre-set) so the menu stays simple and consistent for supporters. You choose which of the 8 drinks to offer, not their price. No. The social link is entirely optional. Without one, supporters just type a name (or leave it blank for Anonymous) and their message/GIF still appear normally, just without a profile photo or verified badge. Tips still work exactly the same — supporters still pick a drink, leave a message, and pay. The feed (and the coffee-bought badges) simply won't be shown publicly on your page. Yes. Unchecking the visibility option keeps their name, drink, and amount in the feed but hides the message, GIF, and social link — a middle ground between fully public and fully anonymous. Yes, at any time from the same **Donation style** toggle. Your goal amount, reset period, and past tips all stay exactly as they are — only the wording and drinks menu change. X (Twitter), Instagram, TikTok, GitHub, YouTube, Twitch, Discord, Telegram, Snapchat, Spotify, WhatsApp, Facebook, Reddit, SoundCloud, Substack, and Pinterest. X is the only one that also shows the real display name and verified badge. ## Next Steps The base fundraising goal, progress bar, and donor feed that Coffee Tips builds on. Brand your coffee page with an avatar, tagline, and accent color. See how PayRequest's built-in GIF search works elsewhere in the checkout flow. Use your own domain for your coffee/tip page instead of payrequest.me. # Community Source: https://docs.payreque.st/shop-and-checkout/community Build a community-first PayRequest Page with free members, paid memberships, pinned posts, and protected content. # Community Community turns your PayRequest Page into a community-first home for visitors, free members, and paying members. Visitors can join for free with verified email access, free members can read selected posts and participate in their comments, and paying members unlock the complete protected library. Your public Community URL is `payrequest.me//community`. Community is built into your existing PayRequest Page. It automatically reuses its banner, avatar, theme, profile information, and navigation instead of creating a separately styled website. ## What You Can Build Introduce new members with formatted text and an optional YouTube or Vimeo video. Organize posts into topics such as Breakfast, Lunch, Dinner, Tutorials, or Tips & tricks. Publish protected articles with text, images, links, and supported video embeds. Let visitors join with verified email access before they decide to purchase the paid membership. Keep one important announcement, challenge, or start-here post at the top of the Community. Unlock content after successful membership payment and lock it when membership access ends. ## Set Up Your Community Go to **Community** in the dashboard. This feature is available on Premium and higher plans. Create or connect the membership customers buy. Its name, description, image, price, interval, and benefits form the public Community offer. Add a welcome heading, formatted introduction, instructions, and optionally a YouTube or Vimeo URL. Add a public **Headline** and **Short pitch** explaining who the Community is for and what members can achieve. Enable **Make community my homepage** to open Community before products when someone visits `payrequest.me/`. Add sections to keep a growing content library easy to browse. You can edit, reorder, or remove sections without deleting their posts. Turn on **Published** and save. Customer login stays enabled automatically while the Community is published. Keep **Show in Page navigation** enabled to promote Community on your public Page. Turn it off for an invite-only or direct-link experience; the `/community` URL and logged-in member account menu continue to work. Use **Preview as member** on the Community dashboard to inspect the complete logged-in experience without creating a customer or paid subscription. Use **View public community** to check the visitor experience separately. ## Community-First Homepage When **Make community my homepage** is enabled, your normal `payrequest.me/` link opens Community first. Visitors see your pitch, membership benefits, recurring price, recent locked-post previews, free-member signup, and join action before any products. The Community uses the membership product for its paid plan name, price, image, interval, and benefits. The separate public headline and short pitch explain the outcome without creating a second product or pricing configuration. On mobile, PayRequest keeps the paid join action available in a sticky bar while visitors explore the page. ## Free and Paid Members Community supports three access levels: | Visitor type | Access | | - | - | | Visitor | Public posts and safe locked-post previews | | Free member | Public posts and posts marked **Free and paid members** | | Paid member | Public, free-member, and **Active members only** posts | Visitors select **Join free** and confirm their email address. The confirmation creates or links their customer profile for this Page and signs them in through a secure one-time link. The same customer profile is retained if they later upgrade to the paid membership. Free membership includes consent to receive Community updates by email. Unsubscribing removes both those emails and free-member access. A paid subscription remains independent and continues according to its own billing status. ## Add Content Community content uses the existing Posts editor: Open **Posts** and start a new post. Choose **Everyone**, **Free and paid members**, or **Active members only**. Assign the post to a section. Leave it unassigned if it should appear without a category. Active and trial members can now open the complete post. Other visitors see the membership offer or a login action. ## Pin an Important Post Open **Posts**, use the three-dot menu on a published post, and select **Pin post**. The pinned post moves to the top of Community and receives a **Pinned** badge. Only one post can be pinned per PayRequest account. Pinning another post replaces the previous pin. Returning the pinned post to Draft removes its pin automatically. Deleting a section does not delete its posts. Those posts become uncategorized and remain available according to their publication and access settings. ## Visitor and Member Experience Before joining, visitors see the Community landing page, free-member signup, and paid membership offer. Locked previews may reveal a title, section, and publication date, but never protected post content. After payment, PayRequest activates the subscription, lets the member log in using a magic link, and unlocks the welcome page, sections, and protected posts. Access is checked again whenever protected content is opened. Direct product links keep Page navigation visible, including Community, so visitors understand what their membership unlocks. ## Login, Cancellation, and Downloads * Customer login cannot be hidden while Community is published. * Logged-in customers can open **Community** directly from the account dropdown. * Active and trial memberships unlock protected content. * Cancellation keeps access until the subscription actually ends. * When access expires, members-only content is locked automatically. * Logged-in customers can use **My downloads** for digital products they previously purchased. Digital product purchases do not automatically grant Community access. Community access comes from the connected membership subscription; downloads come from paid digital-product orders. Joining for free uses email confirmation. After confirmation, PayRequest signs the member in and shows **Free member** status. Existing confirmed followers of a published Community are treated as free members when they log in with the same email address. ## Community or Telegram? PayRequest Community is a hosted content area inside your PayRequest Page. The optional Telegram integration grants timed access to an external Telegram group or channel. You can use either feature independently or combine them as separate membership benefits. ## Frequently Asked Questions Community provides a welcome page plus sections that organize your posts. This creates a simple mini-site structure without requiring a separate website builder. Yes. It reuses the same banner, avatar, theme, profile, and navigation as your normal PayRequest Page. Visitors may see a safe locked preview, but never the protected body. Free-member posts require confirmed free or paid membership; paid posts require an active or trial subscription. Yes. Signed-in free members can comment on posts they may read. They cannot open or comment on paid members-only posts. Not from that purchase alone. The customer can log in to retrieve the e-book under My downloads, but Community requires the connected membership subscription. Access normally continues through the paid period and ends when the subscription becomes inactive. ## Next Steps Configure pricing, billing, benefits, and access rules. Create and organize protected content. Sell files customers retrieve from their download library. Learn what logged-in customers can manage. # Crypto Page Themes Source: https://docs.payreque.st/shop-and-checkout/crypto-page-themes Give your payrequest.me page a crypto-native look with the Solana or Crypto Native theme — one click in the PayRequest Page editor # Crypto Page Themes Stand out with a payment page that feels at home in the crypto world. PayRequest offers two premium crypto-aesthetic themes — **Solana** and **Crypto Native** — that transform your page background, card style, and inputs into a visually striking experience for Web3 visitors. Themes are available for all PayRequest accounts and apply only to your public **payrequest.me** page. They work alongside your existing **Accent Color** setting — pick both together for a fully branded look. ## The Two Themes Deep dark background with a vivid **purple-to-green** radial glow — inspired by the Phantom wallet and Solana's brand palette. The card glows with a soft purple border and light blur effect. An animated gradient mesh background (cyan, violet, and green) with a **glassmorphism card** — frosted glass with a neon cyan `#00D4FF` accent. The most striking and modern of the two. ## How to Set a Theme From the main dashboard, go to **PayRequest Page** and click the **Styling** tab. Scroll down to the **Page Theme** section — it appears directly above the **Accent Color** card. You'll see three visual mini-previews: Default, Solana, and Crypto Native. Click any theme card to select it instantly. The mini-preview shows a thumbnail of what the background and card will look like. Click **Save Styling** at the bottom of the page. Your live `payrequest.me` page will update immediately. ## Combining Themes with Accent Color Themes and accent colors work together — they control different parts of the page: | Setting | Controls | | - | - | | **Page Theme** | Page background, card style, input field borders | | **Accent Color** | Pay button color, avatar border, selected product highlight | Try **Solana theme** + **purple accent** (`#9945FF`) for a fully Solana-branded page, or **Crypto Native theme** + **cyan accent** (`#00D4FF`) for a sleek, modern look. Both combinations look great. ## Default Theme Selecting **Default** removes any crypto theme and returns to the standard PayRequest dark style. Your accent color still applies — only the background and card styling are reset. ## How It Looks to Visitors When a visitor lands on your page with a theme applied: * The **background** changes from the standard dark grey to the theme-specific design (radial glow or animated mesh) * The **payment card** gets the themed border, background tint, and blur effect * **Input fields** take on a subtle tinted border matching the theme palette * Everything else — your name, products, payment methods — stays exactly the same The theme is purely visual and has no effect on payment flows or amounts. ## Frequently Asked Questions Yes — the mini-preview cards in the editor give you a visual sample of each theme's background and card style. Click a theme to select it, check the preview thumbnails, and click **Save** when you're happy. Yes. If you've connected a custom domain to your PayRequest Page, the theme applies there too. Yes — the gradient animation on the Crypto Native theme works on mobile browsers. On slower devices it may run at a lower frame rate, but it remains visible. Absolutely. Themes are purely visual — they don't require a connected wallet or any crypto features to be enabled. Yes, more themes are planned. The two current themes were designed around the most popular Web3 aesthetics — Solana and a chain-agnostic "Crypto Native" style. ## Next Steps Full guide to avatar, tagline, accent color, and social links on your PayRequest Page. Let other PayRequest users send USDC directly to your wallet from your page. Accept USDC payments from any Phantom or Solflare wallet on your page. Use your own domain for your branded payment page. # Custom Domains Source: https://docs.payreque.st/shop-and-checkout/custom-domains Set up your own domain for a professional branded shop experience that builds trust and improves SEO # Custom Domains 🌐 Transform your PayRequest shop from a subdomain into a professional branded storefront with your own custom domain. Custom domains enhance your brand credibility, improve SEO rankings, and provide a seamless customer experience. **Professional Branding**: Custom domains like `shop.yourbusiness.com` appear more trustworthy than subdomains and can significantly improve conversion rates. ## 🎯 Why Use Custom Domains? Custom domains provide substantial benefits for your online business: **Professional Appearance** * Match your main website branding * Consistent customer experience * Enhanced brand recognition * Improved customer trust **Search Engine Optimization** * Better search rankings * Domain authority building * Improved click-through rates * Enhanced local SEO **Security & Credibility** * SSL certificate included * Professional appearance * Reduced cart abandonment * Higher conversion rates **Tracking & Insights** * Google Analytics integration * Unified tracking across domains * Better attribution data * Enhanced reporting capabilities ## 🛠️ Domain Setup Process Setting up a custom domain is straightforward with PayRequest's guided configuration: **Subdomain Approach (Recommended)** * `shop.yourbusiness.com` * `store.yourbusiness.com` * `buy.yourbusiness.com` **Subdirectory Alternative** * `yourbusiness.com/shop` * `yourbusiness.com/store` * Requires additional DNS configuration Navigate to **Shop** → **Settings** → **Custom Domain** **Domain Settings:** * Enter your chosen domain/subdomain * Enable custom domain usage * Configure redirect preferences * Set up SSL certificate (automatic) Add DNS records with your domain provider (detailed instructions below) * Verify domain connectivity * Test SSL certificate * Confirm redirect behavior * Validate all shop pages ## 🔧 DNS Configuration Guide Configure your DNS settings based on your chosen domain strategy: **For shop.yourbusiness.com:** Add a **CNAME record** with your DNS provider: ``` Type: CNAME Name: shop (or your chosen subdomain) Value: payrequest.app TTL: 3600 (or your provider's default) ``` **Example DNS Configurations:** **Cloudflare:** * Type: CNAME * Name: shop * Target: payrequest.app * Proxy status: DNS only (gray cloud) **Namecheap:** * Type: CNAME Record * Host: shop * Value: payrequest.app **GoDaddy:** * Type: CNAME * Name: shop * Value: payrequest.app **Important**: Ensure proxy/CDN features are disabled initially. You can enable them after verifying the basic setup works. **For yourbusiness.com/shop:** Add an **A record** pointing to PayRequest's IP: ``` Type: A Name: @ (root domain) Value: [PayRequest IP - provided in dashboard] TTL: 3600 ``` **Additional Configuration:** * Set up URL forwarding for `/shop` path * Configure server-side redirects * Ensure proper SSL certificate coverage **Note**: Root domain setup requires additional coordination with PayRequest support for proper routing configuration. **Multiple Subdomains:** ``` shop.yourbusiness.com → CNAME → payrequest.app store.yourbusiness.com → CNAME → payrequest.app buy.yourbusiness.com → CNAME → payrequest.app ``` **International Domains:** ``` shop.yourbusiness.nl → CNAME → payrequest.app shop.yourbusiness.de → CNAME → payrequest.app boutique.yourbusiness.fr → CNAME → payrequest.app ``` **CDN/Proxy Configuration:** * Enable after basic setup verification * Configure caching rules appropriately * Ensure payment processing routes work * Test webhook delivery functionality ## ⚙️ PayRequest Dashboard Configuration Configure your custom domain settings in the PayRequest dashboard: **Navigation**: Shop → Settings → Custom Domain **Configuration Options:** * **Domain Name**: Enter your full domain (shop.yourbusiness.com) * **Enable Custom Domain**: Toggle to activate custom domain usage * **Force HTTPS**: Automatically redirect HTTP to HTTPS * **Default Redirect**: Set behavior for payrequest.app URLs **SSL Certificate:** * Automatically provisioned by PayRequest * Let's Encrypt or equivalent certificate authority * Auto-renewal every 90 days * Covers all configured subdomains **Redirect Scenarios:** **Subdomain to Custom Domain:** * `payrequest.app/shop/yourshop` → `shop.yourbusiness.com` * Permanent 301 redirects for SEO preservation * Automatic redirect of all shop pages **Custom Domain Fallback:** * Maintain payrequest.app URLs as backup * Useful during DNS propagation * Ensures continuous shop availability **Cross-Domain Consistency:** * Product links work on both domains * Payment processing functions correctly * Customer portal integration maintained **Domain-Matched Emails:** * Configure `From` email addresses to match domain * Use `noreply@yourbusiness.com` for automated emails * Maintain brand consistency in communications **DKIM/SPF Configuration:** * Add email authentication records * Improve email deliverability * Prevent emails from being marked as spam * Enhance professional appearance ## 🧪 Testing & Verification Ensure your custom domain setup is working correctly: ### Pre-Launch Testing Checklist **Check DNS Propagation:** * Use online DNS checker tools * Verify CNAME/A record resolution * Test from multiple geographic locations * Confirm TTL settings are appropriate **Tools to Use:** * DNS Checker (dnschecker.org) * What's My DNS (whatsmydns.net) * Dig command-line tool * Browser developer tools **Certificate Verification:** * Check certificate validity * Verify domain coverage * Test HTTPS enforcement * Validate certificate chain **Browser Testing:** * Green padlock icon visible * No certificate warnings * Proper certificate details * Mixed content issues resolved ### Functional Testing * Access shop homepage via custom domain * Navigate through product categories * Test search functionality * Verify responsive design on mobile * View individual product pages * Add products to cart * Modify cart quantities * Test custom field inputs * Complete checkout flow * Test payment processing * Verify order confirmation * Check automated emails * Verify meta tags and structured data * Test Google Analytics tracking * Check social media sharing * Validate sitemap.xml accessibility ## 🚨 Common Issues & Troubleshooting ### DNS Propagation Issues **Symptoms:** * Domain not resolving consistently * Works in some locations but not others * Intermittent connectivity issues **Solutions:** * Wait 24-48 hours for full propagation * Reduce TTL values temporarily * Clear local DNS cache * Test with different DNS servers (8.8.8.8, 1.1.1.1) **Commands for Troubleshooting:** ```bash theme={null} # Check DNS resolution nslookup shop.yourbusiness.com # Trace DNS path dig shop.yourbusiness.com +trace # Clear local DNS cache (Windows) ipconfig /flushdns # Clear local DNS cache (macOS) sudo dscacheutil -flushcache ``` **Common Mistakes:** * Wrong CNAME target (should be payrequest.app) * A record instead of CNAME for subdomain * Missing DNS records * Conflicting DNS entries **Verification Steps:** 1. Double-check DNS record type (CNAME vs A) 2. Verify target/value exactly matches requirements 3. Remove conflicting or duplicate records 4. Confirm DNS changes are saved and published **Quick Fixes:** * Delete and recreate DNS records * Contact DNS provider support * Try alternative DNS record configurations * Temporarily use A record with PayRequest IP ### SSL Certificate Problems **Common Problems:** * Certificate not generating automatically * Browser security warnings * Mixed content errors * Certificate mismatch errors **Resolution Steps:** 1. Verify DNS is properly configured first 2. Wait for automatic certificate generation (up to 24 hours) 3. Contact PayRequest support if certificate doesn't generate 4. Check for mixed HTTP/HTTPS content on pages 5. Ensure all resources load via HTTPS **Prevention:** * Configure DNS correctly before enabling domain * Allow time for certificate provisioning * Test with modern browsers * Use HTTPS for all embedded content ## 🌟 Advanced Custom Domain Features ### Multiple Domain Support **Multi-Country Setup:** * shop.yourbusiness.com (global) * shop.yourbusiness.nl (Netherlands) * shop.yourbusiness.de (Germany) * boutique.yourbusiness.fr (France) **Benefits:** * Localized customer experience * Improved local SEO rankings * Country-specific branding * Regional payment method optimization **Multiple Brand Support:** * shop.mainbrand.com * store.subbrand.com * marketplace.company.com **Use Cases:** * Multi-brand businesses * Separate product lines * B2B vs B2C storefronts * Regional brand variations ### Domain-Based Customization **Customization Options:** * Different color schemes per domain * Unique logos and branding elements * Domain-specific product catalogs * Localized content and languages **Implementation:** * Configure themes in PayRequest dashboard * Upload domain-specific assets * Set up conditional content rules * Test cross-domain consistency **Tracking Setup:** * Google Analytics 4 with multiple domains * Cross-domain tracking configuration * Attribution modeling across domains * Conversion tracking and optimization **Advanced Analytics:** * Domain-specific performance metrics * Customer journey analysis * Revenue attribution by domain * A/B testing across domains ## 💰 Cost & Performance Considerations ### Custom Domain Pricing **PayRequest Pricing**: Custom domains are included in all PayRequest plans at no additional cost. You only pay for your domain registration with your chosen domain registrar. **Annual Costs:** * .com domains: \$10-15/year * .org/.net domains: \$12-18/year * Country TLDs: \$15-50/year * Premium domains: \$50-500+/year **Included Free:** * Let's Encrypt certificates * Automatic renewal * Wildcard support available * Multi-domain certificates **Optimization:** * CDN integration supported * Caching configuration * Global edge locations * Sub-100ms response times ### Performance Optimization Enable content delivery network for faster global performance Configure appropriate cache headers for static resources Use WebP format and responsive images for faster loading Implement uptime monitoring and performance tracking ## 📞 Support & Resources Need help with custom domain setup? **Technical Assistance** * DNS configuration help * Propagation troubleshooting * Record verification * Provider-specific guidance **Migration Services** * Existing domain transfer * Zero-downtime migration * SEO preservation * Redirect management **Speed & SEO** * CDN configuration * Performance auditing * SEO optimization * Analytics setup ## 🎓 Next Steps Complete your shop configuration and customize the customer experience Optimize how your products are presented to customers Customize the checkout flow for better conversion rates Set up comprehensive analytics and tracking for your custom domain *** **Pro Tip**: Set up your custom domain early in your shop development process. This ensures all SEO benefits accumulate to your branded domain from day one, and customers become familiar with your professional web presence. # Donation Mode Source: https://docs.payreque.st/shop-and-checkout/donation-mode Run a fundraising goal on your PayRequest Page with a live progress bar, a public donor feed, and monthly auto-reset. # Donation Mode Turn your PayRequest Page into a crowdfunding page. Set a goal amount, let visitors contribute any amount they want, and show a live progress bar plus a public feed of recent donors — perfect for community servers, creator support, or covering recurring costs. Donation Mode is one of three PayRequest Page display modes, alongside **Products & services** and **Amount buttons**. Switch between them any time from the **Page Mode** card in the **Overview** tab sidebar for a one-click change, or from the **Settings** tab if you also want to adjust the mode's other options in the same step. ## Overview Shows total raised vs. your goal in real time, with a percentage and remaining-to-go amount. A monthly goal resets on the 1st of each month — no manual reset, no cron jobs. Recent donations appear below the bar with name, amount, and relative time. Donors can give exactly what they want. Optional preset amounts (€2, €5, €10…) appear as one-click buttons. ## How It Works Open **PayRequest Page** from the dashboard, scroll to **What to show on your page**, and click the **Donation goal** tab. Enter the amount you want to raise (e.g. `10.00`, `100.00`, `2500.00`). Use the currency configured on your business profile. Choose **Monthly** (resets on the 1st of every month, ideal for recurring costs like server hosting) or **One-time** (no reset — runs until you switch it off, ideal for a fixed campaign). Enable **Show recent donor feed** to display a public list of donations under the bar. Set how many donors to show (1–50, default 10). Add quick-pick amount buttons (e.g. €1, €5, €10) under **Add suggested amount**. Donors can still type any amount they like in the custom field. Click **Save Settings** — your live page at `payrequest.me/` now shows the goal, progress bar, and donor feed. The URL stays permanent; the goal resets on its own. ## What Visitors See Once enabled, every visitor lands on a page with this structure (in order): 1. **Your avatar, name, tagline, and bio** — same as the other PayRequest Page modes 2. **Donation goal card** — an optional title, a days-left counter (for monthly goals), a big "€X of €Y" headline, a progress bar, and a "X% funded • €Z to go" status line 3. **Donor feed** — recent donors with name + amount + how long ago they gave 4. **Payment form** — preset amount buttons (if configured), custom amount input, name/email fields, and the Pay button The progress total is calculated live from your paid invoices linked to the page. Refunds and chargebacks automatically reduce the total — no manual reconciliation needed. ## Reset Periods | Period | Resets | Best for | | - | - | - | | **Monthly** | Automatically on the 1st of each month | Recurring costs (server hosting, subscriptions, community fees) | | **One-time** | Never (runs until you change it) | Fundraising campaigns, equipment funds, charity drives | Switching from monthly back to one-time resets the start date to "now", so the new one-time window starts fresh. Switching the other way is also safe — the monthly window picks up at the start of the current month. ## When the Goal is Reached When the total hits or exceeds your goal: * The progress bar fills to 100% and turns green * A **Goal reached!** badge appears next to the total * The status line changes to "**Thank you! Extra donations are still welcome.**" * Donations continue to accept normally — the form stays live so supporters who want to overshoot the goal can For a monthly goal, hitting the target early just means the next month starts at €0 on the 1st as usual. Communities often overshoot and "bank" momentum into the following month emotionally, even though the counter resets. ## The Donor Feed The feed shows each completed donation as one row: ``` Lasse €5.00 • 15m ago Anna B. €2.50 • 3h ago Mark €10.00 • 12h ago Jeroen van Dijk €1.00 • 1d ago Sophie €3.50 • 2d ago ``` * **Name** is whatever the donor typed into the form. If they leave it blank, it shows as **Anonymous**. * **Amount** is the actual donation amount in your page's currency. * **Time** is shown as a relative timestamp ("3 hours ago"), so the feed always feels fresh. The feed updates automatically as donations come in — no refresh needed for new visitors. To turn off public visibility, switch off **Show recent donor feed** in settings. ## Best Practices **Pick a realistic goal.** A €10 monthly server-hosting goal is far more motivating than a €1,000 one — donors love seeing the bar fill up. You can always raise the goal later once you've built momentum. **Add 3–5 preset amounts**. Small amounts like €1, €2, €5 lower the bar to participate. Most donors pick a preset rather than typing a custom amount. **Write your bio to explain the cause.** Donors give more when they understand the "why". Mention what costs you're covering, who benefits, and why their contribution matters. Two short sentences is enough. **Share the link in communities.** Donation Mode shines when shared in Discord servers, gaming communities, newsletters, and social bios — anywhere supporters already gather. ## Frequently Asked Questions Yes, if you pick **Monthly**. On the 1st of each month, the progress bar starts at €0 again — no action needed. **One-time** goals never reset; they keep counting until you switch modes or change settings. They stay in your transaction history and analytics — they're just no longer counted toward the current month's progress total. You can always view the full historical list in **Transactions**. Yes — if they leave the name field blank, they show as **Anonymous** in the feed. You can also turn off the feed entirely if your audience prefers privacy. Yes. The full donor list (with email, exact timestamp, transaction ID, and payment method) is always in your **Transactions** page — the public feed is a curated public-facing view, not the full ledger. Yes. The total is computed live from invoices marked **Paid**. If you refund a donation, it drops out of the total automatically and disappears from the feed. Yes, freely. Your goal settings stay saved on the page — switch back to Donation Mode any time and the goal picks up where it left off (monthly) or from the saved start date (one-time). The currency configured on your business profile. All donations are recorded in the same currency for clean totals. ## Next Steps Brand your donation page with an avatar, tagline, and accent color. Use your own domain for your donation page instead of payrequest.me. Connect Mollie, Stripe, or PayPal so donors can pay through their preferred method. Build pre-filled donation links for specific tiers or campaigns. A friendlier "Buy Me a Coffee"-style version of Donation Mode with a drinks menu, GIFs, and X profile pictures. Add a badge to your GitHub README that shows your live donation total and links to your page. # Memberships Source: https://docs.payreque.st/shop-and-checkout/memberships Create the recurring plan that grants paying members access to your PayRequest Community. # Memberships A membership is the recurring product customers buy to enter your private Community. Each PayRequest Page connects to one membership product. That product is the single source of truth for the plan name, description, image, price, billing interval, and benefits. Membership setup lives under **Community** in the dashboard. There is no separate Membership tab under PayRequest Page when you use Community. ## Membership and Community | Membership product | Community | | - | - | | Defines what customers buy | Provides the private members area | | Stores name, description, image, price, and benefits | Stores the welcome page, sections, and members-only posts | | Creates and renews the subscription | Checks that the customer still has active access | | Appears as the plan for visitors | Appears inside your normal PayRequest Page | Build the welcome page, organize content into sections, and preview the private members area. ## Availability Memberships and Community are included with **Premium** and higher plans. Before accepting members, connect at least one supported recurring payment provider: * **Mollie** — the first payment creates a mandate for future recurring charges. Enable **SEPA Direct Debit** in Mollie. * **Stripe Connect** — subscriptions run directly on your verified connected Stripe account. * **PayRequest Merchant of Record** — PayRequest processes the Stripe payment and transfers your proceeds to your verified payout account. PayPal does not currently support PayRequest Page memberships. It can still process supported one-time purchases. ## Create or Connect a Membership In the PayRequest dashboard, go to **Community**. Click **Enable membership**. PayRequest creates a membership product if you do not have one. If membership products already exist, select the one that belongs to this Page. Add the name and description customers should see. The membership name also labels the Community tab on your public Page. Choose a daily, weekly, monthly, or yearly recurring price. Price changes apply to new members; existing subscriptions retain their current price. Enter one benefit per line and optionally upload an image or reuse your Page avatar. Click **Save membership**. Configure and publish the members area on the same Community screen. ## How Joining Works Visitors open the Community tab on your PayRequest Page and see the membership offer. After they click **Become a member** and complete the first recurring payment, PayRequest creates an active subscription and unlocks the Community. Visitors can also select **Join free** before purchasing. Free membership is confirmed by email and unlocks posts marked **Free and paid members**. Upgrading keeps the same customer identity and adds access to paid members-only content. The public offer can show the membership name, description, image, recurring price, interval, benefits, and join or login action. Membership products do not show a quantity selector because one customer purchases one membership. ## Login and Access Publishing a Community automatically keeps customer login visible on your PayRequest Page. Members receive a single-use magic login link and can immediately open protected content. Access is granted only when: * The customer belongs to the business that owns the Page * The subscription belongs to the Page's connected membership product * The subscription is active or in trial If the subscription ends, protected Community content is locked automatically. Cancellation normally preserves access until the end of the paid billing period. ## Member Self-Service Logged-in customers can manage their subscription from their Page account, including cancellation where the product permits it. They can also open **My downloads** to retrieve digital products purchased from PayRequest creators. ## Frequently Asked Questions Not currently. Each PayRequest Page connects to one membership product, keeping the offer and access rules simple. Use **Community** in the dashboard. Membership products remain visible under Products, but Community is the central setup screen. Yes. The new price applies to future members. Existing subscriptions keep the price already attached to them. Free members can read public posts and posts marked **Free and paid members**. Only active or trial paying members unlock posts marked **Active members only**. Not yet. Use Mollie, Stripe Connect, or PayRequest Merchant of Record. ## Next Steps Create the private welcome page and organize members-only content. Write public or members-only posts. Customize the shared banner, avatar, colors, and Page profile. Learn how recurring subscriptions move through their statuses. # Order Management Source: https://docs.payreque.st/shop-and-checkout/order-management Process and track customer orders from checkout to fulfillment # Order Management Manage customer orders from placement through fulfillment. Track payment status, create invoices, and handle order lifecycle efficiently. ## Order Overview Orders are created when customers purchase products through your shop, payment page, or smart links. Each order contains: * **Order Number**: Unique identifier (e.g., ORD-1234567890-1) * **Customer Information**: Name, email, address * **Order Items**: Products, quantities, prices * **Payment Status**: Pending, Paid, Failed, Refunded * **Order Status**: Pending, Completed, Cancelled ## Order Creation Modes Control when orders are created based on your business needs. This setting is configured per product. ### Orders at Checkout (Default) The standard behavior where orders are created immediately when a customer starts checkout. **Flow:** 1. Customer adds products to cart 2. Customer enters checkout details 3. **Order created immediately** 4. Customer registration email sent 5. Order confirmation email sent 6. Customer redirected to payment 7. On payment success: Order marked as paid 8. On payment failure: Order marked as cancelled **Best For:** * Products requiring immediate order tracking * Businesses needing visibility into abandoned carts * Standard e-commerce workflows ### Paid-Only Orders Orders are only created after successful payment. No records or emails until payment is confirmed. **Flow:** 1. Customer adds products to cart 2. Customer enters checkout details 3. Cart data stored temporarily (24 hours) 4. Customer redirected to payment 5. On payment success: **Order created now**, emails sent 6. On payment failure: No order created, no emails **Best For:** * High-traffic products with many abandoned checkouts * Reducing email noise and spam notifications * Cleaner order data (only paid orders appear) * Lead generation products where unpaid leads aren't valuable **How to Enable**: Go to your product settings and find "Order Creation" in the Custom Fields step. Select "Paid-only orders" to enable this mode. ## Order Statuses ### Payment Status | Status | Description | | - | - | | **Pending** | Awaiting payment confirmation | | **Paid** | Payment successfully received | | **Failed** | Payment failed or was declined | | **Refunded** | Payment was refunded to customer | ### Order Status | Status | Description | | - | - | | **Pending** | Order placed, awaiting fulfillment | | **Completed** | Order fulfilled and delivered | | **Cancelled** | Order was cancelled | ## Managing Orders ### Viewing Orders 1. Navigate to **Orders** in your dashboard 2. Use filters to find specific orders: * Date range * Payment status * Order status * Customer name or email ### Order Details Click any order to view: * Complete order information * Product line items with quantities * Custom field values submitted by customer * Payment history and transaction IDs * Associated invoice (if created) * Related subscription (for recurring products) * **Digital downloads** — Download tokens with file name, usage count, expiry, status, and copyable link (for [digital products](/products-and-pricing/digital-products)) ### Order Location Tracking PayRequest automatically detects and displays customer location information for each order. This helps you understand where your customers are located geographically. **What's Captured:** * **Country**: Automatically detected from the customer's IP address * **IP Address**: The customer's IP at time of order * **Visual Map**: Interactive map showing the customer's country **How It Works:** 1. When a customer places an order, PayRequest detects their location using Cloudflare headers (most accurate) or IP geolocation services 2. The country code and IP address are stored with the order 3. On the order detail page, you'll see an **Order Location** card displaying: * Country flag emoji (e.g., 🇪🇸 for Spain) * Full country name with code (e.g., "Spain (ES)") * Visual map centered on the country * Customer's IP address Location detection uses Cloudflare's geolocation headers when available, providing highly accurate country detection. This works automatically for orders from your shop, payment pages, and smart links. **Supported Countries:** The map display supports 24+ countries including all major European countries (Netherlands, Belgium, Germany, France, Spain, Italy, UK, etc.), North America (US, Canada, Mexico), and other regions (Australia, Japan, Brazil, etc.). **Privacy Note:** IP addresses and location data are only visible to you as the business owner. This information is not shared with other customers or third parties. ### Creating Invoices from Orders Invoices can be automatically or manually created from orders: **Automatic Invoice Creation:** * Enable in Shop Settings * Invoice created when order is paid * Invoice number auto-generated **Manual Invoice Creation:** 1. Open the order details 2. Click "Create Invoice" 3. Review and customize if needed 4. Invoice linked to order automatically ## Email Notifications ### Orders at Checkout Mode | Event | Email Sent | | - | - | | Checkout started | Customer Registration (if new) | | Order created | Order Confirmation | | Payment received | Order Completed | | Order cancelled | Order Cancelled | ### Paid-Only Orders Mode | Event | Email Sent | | - | - | | Checkout started | None | | Order created (after payment) | Order Confirmation + Order Completed | | Payment failed | None (no order exists) | **Reducing Email Noise**: If you're getting too many "Customer registered" and "New order" notifications from abandoned checkouts, switch affected products to "Paid-only orders" mode. ## Order Subscriptions Manage subscriptions directly from the order detail page. The **Order Subscriptions** card appears when an order contains recurring products. ### Automatic Subscription Creation When orders contain recurring products: 1. Payment is processed 2. Order marked as completed 3. Subscription automatically created and linked to the order 4. Customer receives subscription confirmation 5. Future billings handled by subscription system ### Creating Subscriptions Manually If a subscription wasn't created automatically (e.g., manual order entry): 1. Open the order detail page 2. Find the **Order Subscriptions** card in the sidebar 3. Products without subscriptions show a **Create** button 4. Click **Create** to generate a new subscription linked to this order ### Linking Existing Subscriptions Connect an existing unlinked subscription to an order. This is useful when: * A subscription was created separately and needs to be associated with an order * You're reconciling historical data * A subscription was accidentally unlinked **To link a subscription:** 1. Open the order detail page 2. In the **Order Subscriptions** card, find "Or link an existing subscription to this order" 3. Use the searchable dropdown to select from available subscriptions 4. The dropdown shows: Product name, Subscription ID, Amount, Interval, and Status 5. Click **Link Subscription to Order** Only subscriptions belonging to the same customer and matching the order's product types appear in the dropdown. Subscriptions already linked to other orders won't be shown. ### Viewing Linked Subscriptions Subscriptions linked to an order display with: * Green background indicating active link * Product name and pricing * Current status (Active, Paused, etc.) * **View Subscription** button to open full subscription details ## Order Tags Organize and categorize orders using tags. Tags help you segment orders by source, campaign, customer type, or any custom classification. ### Viewing Tags Tags appear in the sidebar of the order detail page, below Order Notes. Each tag displays with its assigned color for easy identification. ### Managing Tags 1. Open an order's detail page 2. Find the **Order Tags** section in the sidebar 3. Click **Manage** to open the tag modal 4. Select or deselect tags using the searchable dropdown 5. Click **Save Tags** to apply changes ### Creating New Tags From the tag management modal: 1. Click **Create New Tag** 2. Enter a tag name 3. Select a color 4. Click **Create Tag** The new tag is automatically selected and added to the order. ### Tag Types Order tags use the **Order** and **Support** tag types. These are separate from product, customer, or invoice tags, allowing you to maintain organized tag categories. ### Use Cases | Tag Example | Purpose | | - | - | | **Marketing Campaign** | Track orders from specific promotions | | **Priority** | Flag orders needing urgent attention | | **Sales Channel** | Identify source (Website, Social, Referral) | | **Issue** | Mark orders with problems to resolve | | **VIP** | Highlight high-value customer orders | **Bulk Tagging**: For tagging multiple orders at once, use the Orders list view with filters to identify orders, then tag them individually from their detail pages. ## Order Channels Orders can come from multiple sources: ### Shop Checkout * Full cart experience * Multiple products per order * Custom field collection * Supports both order creation modes ### Payment Page * Single product or custom amount * Quick checkout flow * Supports both order creation modes ### Smart Links * Shareable payment links * Redirects to appropriate checkout * Inherits product's order creation mode ## Best Practices Track checkout-to-payment conversion rates to identify issues Enable for high-volume products to reduce noise, keep default for premium products Always create invoices for paid orders to maintain financial records Use tags to organize orders by source, campaign, or customer type ## Troubleshooting ### Order Not Created After Payment For paid-only mode products: * Check if payment was actually successful in your payment provider * Verify webhook is receiving payment notifications * Order may take a few seconds to appear after payment ### Duplicate Order Emails * Each order sends one confirmation email * Duplicate emails may indicate webhook issues * Check webhook logs in Settings > Webhooks ### Customer Not Found on Order * Customer was created during checkout * Check customer list with the email used * Customer may have used different email than expected ## Related Topics Set up products with order creation modes Learn about organizing with tags Customize your checkout experience Create shareable payment links # Posts Source: https://docs.payreque.st/shop-and-checkout/posts Publish news, updates, changelogs, sales, and member-focused announcements on your PayRequest page. # Posts Posts let you turn your PayRequest page into more than a payment page. You can share product news, launch updates, special offers, changelogs, or membership announcements directly on your public page at `payrequest.me//posts`. Visitors can open the **Posts** tab from your PayRequest page, read your updates, and continue to your products or payment options without leaving your page. Posts are useful for creators, SaaS businesses, consultants, communities, and anyone who wants a simple public update feed next to their products and payment options. ## What You Can Publish Each post has a type so visitors can quickly understand what kind of update they are reading. Share general announcements, business updates, launch notes, or important changes. Tell customers what improved, what changed, or what is coming next. Keep a simple history of product improvements, fixes, and new features. Promote limited-time offers, discounts, bundles, or seasonal campaigns. Share updates for supporters, subscribers, members, or private communities. Add a product to a post so readers can view it and buy directly from the update. ## Create a Post From your PayRequest dashboard, go to **Posts**. Start a new update and give it a clear title. Pick the type that best matches the post: **News**, **Update**, **Changelog**, **Sale**, or **Membership**. Use the editor to format text, add headings, create lists, insert links, add emoji, or embed a YouTube video. If the post is about a product, choose it under **Embedded product**. The product will appear inside the post with a button to view it. Choose **Public** when the post is ready. Choose **Draft** if you want to keep working on it privately. ## Drafts and Public Posts Posts can have two statuses: * **Draft** — only visible to you in the dashboard. Use this while writing or reviewing an update. * **Public** — visible on your PayRequest page and available through a direct post link. You can switch a post between Draft and Public at any time. ## Members-Only Posts Choose an access level for every post: * **Everyone** — anyone can read the complete post. * **Free and paid members** — confirmed free members and paying members can read it. * **Active members only** — only customers with an active or trial paid membership can read it. Visitors without the required access see a locked state and the appropriate free-join, paid-join, or login action. When Community is enabled, select a **Community section** such as Breakfast, Lunch, Dinner, or Tips & tricks. Sections organize the protected library without changing the post's direct URL. Removing a section leaves its posts intact and uncategorized. ## Comments and Emoji Logged-in customers can comment below content they may read. Free members can comment on public and free-member posts. Paid members can also comment on active-members-only posts. Readers can type any Unicode emoji or use the quick emoji buttons below the comment field. Comments display the customer's safe display name and are scoped to the creator and post. Customers can delete their own comments. Guests can read comments on content they may access, but must log in before joining the conversation. When notifying the members audience, the email contains only a short excerpt and a link. PayRequest checks membership access again when the reader opens the post. Set up your recurring plan, benefits, payment provider, member login, and protected content. Create a community-first page for visitors, free members, and paying members. ## Pin a Post Use the three-dot menu on a published post and select **Pin post** to keep it above newer posts in Community. A **Pinned** badge identifies it to visitors and members. Each account can pin one post at a time. Pinning another published post automatically unpins the previous one. Moving a pinned post back to Draft also removes the pin. ## Where Posts Appear Depending on their access, posts can appear in four places: * **Posts dashboard** — manage, edit, delete, and open your posts. * **Public Posts tab** — visitors can browse your public posts at `payrequest.me//posts`. * **Direct post link** — each public post has its own URL, such as `payrequest.me//posts/my-update`. * **Community** — public, free-member, and paid-member posts appear according to each reader's access inside `payrequest.me//community`. Share direct post links in newsletters, social media, Discord, WhatsApp, or customer emails. The post keeps your profile, description, and navigation visible, so readers always know they are still on your official PayRequest page. ## Product Embeds When a post is connected to a product, PayRequest shows a compact product block inside the post. This is useful when you want to: * Announce a new product * Explain why a product changed * Promote a sale * Link a changelog entry to a paid upgrade * Send customers from an update straight to checkout The product embed includes the product name, short details, price, image if available, and a button to view the product. ## YouTube Videos You can add YouTube videos to posts from the editor. Click the YouTube button, paste the video URL, and insert it into the post. When the post is viewed publicly, PayRequest turns supported YouTube links into an embedded video player. ## Tips for Better Posts **Use clear titles.** A title like "July Product Update" or "Summer Sale: 20% Off Business Plan" is easier to understand than a vague title like "Update". **Keep the first paragraph useful.** Visitors often skim. Start with the main point before adding details. **Use the right post type.** Sales, changelogs, and membership posts feel different to readers. The type helps set expectations. **Embed the product when there is a clear action.** If the post is about buying, subscribing, upgrading, or trying something new, attach the product so readers do not need to search for it. ## Frequently Asked Questions Yes. Set the post status to **Draft**. Draft posts stay private until you change them to **Public**. Yes. Share `payrequest.me//posts` to send visitors directly to your public posts. Yes. Open the post from your dashboard and copy its public URL. Currently, a post can show one embedded product. If you want to mention more products, add normal links in the post text. Free-member posts require a confirmed free signup or paid membership. Paid members-only posts additionally require an active or trial paid subscription. One per account. Pinning a different post replaces the current pinned post. No. Posts and Community are built into your PayRequest Page. Your home page, products, Community, and payment options remain available. ## Next Steps Customize the profile, description, color, and social links shown above your posts. Learn how products appear on your public page and checkout flow. Create a Buy Me a Coffee-style support page with messages and public activity. Use your own domain instead of the default payrequest.me link. # Product Display Layout Source: https://docs.payreque.st/shop-and-checkout/product-display Choose between a scrollable carousel or a classic grid to showcase your products on your PayRequest Page # Product Display Layout Your PayRequest Page can show your products in two layouts: a horizontal **Carousel** that lets visitors scroll through cards like a storefront, or the classic **Grid** that groups everything in a collapsible panel. Pick the one that matches how you want customers to experience your offerings. Product layout only applies to **PayRequest Pages** in **Products mode** (i.e. pages where you've selected specific products to showcase). It has no effect on donation mode or amount-button mode. ## The Two Layouts Horizontal scrollable row — always visible, no click to expand. A header shows the product count with **‹ ›** controls on the right. Cards peek at the edge to signal more content. Classic collapsible panel with a 3-column card grid inside. Visitors click **Services & Products (N)** to expand. The default for all pages. ## How to Switch Layouts Go to **PayRequest Page** in the main menu, then click the **Settings** tab. Scroll down to the **Products** block. Below the product checkboxes you'll see a **Product layout** picker with two buttons: **Grid** and **Carousel**. Click **Carousel** or **Grid** — the button highlights instantly to confirm your selection. Click **Save Settings** at the bottom. Your public PayRequest Page reflects the change immediately. ## Carousel Layout The carousel is inspired by the "popular stays" style of browsing — a section heading on the left, navigation arrows on the right, and a row of cards that visitors swipe or click through. ### What It Looks Like ``` Services & Products (6) ‹ › ────────────────────────────────────── ┌──────────┐ ┌──────────┐ ┌──────────┐ … │ [photo] │ │ [photo] │ │ [photo] │ │ Name │ │ Name │ │ Name │ │ Desc… │ │ Desc… │ │ Desc… │ │ €49 │ │ €129 │ │ €15/mo │ └──────────┘ └──────────┘ └──────────┘ ``` * Always **open** — no accordion, no click needed * Cards peek at the right edge to signal there are more * **Fade effect** at the edges blends content in and out * Each card has a large product image (if set), name, short description, price, and a **Subscription** or **Booking** badge where applicable * Clicking any card goes to that product's detail page Carousel works best when your products have **images**. Without images a grey placeholder fills the card. Even a simple product photo makes a big difference. ## Grid Layout (Default) The grid collapses behind a heading so it doesn't dominate the page when a specific product is already selected (e.g., when a customer arrives via a direct product link). * Opens automatically when no product is pre-selected * Closes automatically when a product is active (so the form takes center stage) * Three columns on desktop, two on tablet, one on mobile * Shows the same product card with image, name, description, price, and badges ## Choosing the Right Layout | Situation | Recommended layout | | - | - | | Products have photos | **Carousel** — images shine in the large card format | | 4 or fewer products | **Grid** — no need to scroll; everything fits | | 6+ products | **Carousel** — browsing many items is more natural horizontally | | Service / portfolio page | **Carousel** — feels like a professional showcase | | Direct payment links (single product) | Either — the section is hidden when a product is pre-selected | | Customers on mobile | **Carousel** — swipe feels natural; grid can get long | ## Related Documentation Customize your avatar, tagline, accent color, and social links Cards, List, and Price Table layouts for product categories in your shop Add images, descriptions, and pricing to your products Carry your PayRequest Page as a scannable card in Apple Wallet # README Badge Source: https://docs.payreque.st/shop-and-checkout/readme-badge Get a copy-paste badge that links to your PayRequest Page — perfect for a GitHub README, a website footer, or anywhere else that supports images and links. # README Badge Add a small, professional badge to your project's README, website, or bio that links straight to your PayRequest Page. It's a one-click copy from your dashboard — no design work, no image hosting, nothing to maintain. The badge is available for every PayRequest Page that has a handle set (your `payrequest.me/your-handle` link). If you haven't chosen a handle yet, do that first from **PayRequest Page → Overview**. ## Overview Grab a ready-made snippet from your dashboard — nothing to write or format yourself. GitHub, GitLab, npm packages, blogs, forums — anywhere that renders Markdown or plain images and links. The badge reflects your page live — if you're running a donation goal, it shows the amount raised right now. The wording adapts automatically depending on whether your page is set to Products, Amounts, or Donation mode. ## How to Get Your Badge Go to **PayRequest Page** from the main menu — you'll land on the **Overview** tab by default. In the left-hand sidebar, look for the **README badge** card, just below the **Page Mode** card. This only appears once your page has a handle. Click the copy icon in the field — it copies a ready-to-paste snippet that already includes your handle and links to your live PayRequest Page. Drop it into your GitHub README, your website, or anywhere else — see below for specific examples. ## Adding It to GitHub On GitHub, click the pencil (edit) icon on your `README.md` file, or edit it locally and push the change. Paste the copied snippet near the top of the file, or under a **Support** / **Sponsor** heading further down — both are common conventions. Commit directly to your default branch, or open a pull request if that's your project's convention. Open the repository page on GitHub — your badge should appear as a small clickable image. Clicking it takes visitors straight to your PayRequest Page. A common pattern is to place it right after your project title and description, alongside other badges like build status or version — that's usually the first thing visitors see. ## Adding It Elsewhere The snippet is standard Markdown, so it works anywhere Markdown is supported: | Where | How | | - | - | | **GitLab / Bitbucket** | Same as GitHub — paste into `README.md` | | **npm / PyPI package README** | Paste into the README file that ships with your package | | **Blog posts** | Most blogging platforms (Ghost, Dev.to, Hashnode) accept the same Markdown snippet | | **Forum signatures** | If the forum only accepts an image + link (not Markdown), use the plain image address shown next to the snippet and wrap it in your forum's own link format | | **A plain website** | Use the badge as a normal `` tag pointing to the same image address, wrapped in a link to your PayRequest Page | If a platform doesn't support Markdown, you can still use the badge — it's just a small image. Right-click the rendered badge on your own page (or ask a developer friend) to grab the direct image address, then use it with that platform's own image + link syntax. ## What the Badge Shows The text on the badge updates automatically based on your [Page Mode](/shop-and-checkout/donation-mode): | Page Mode | Badge shows | | - | - | | **Products & services** or **Amount buttons** | "Pay with PayRequest" | | **Donation mode** (no goal set) | "Support me · PayRequest" | | **Donation mode** (goal set) | "Support me · €X raised" — the live total for your current goal period | You don't need to update the badge yourself when your donation total changes — anyone viewing your README or website always sees the current amount, refreshed every few minutes. ## Frequently Asked Questions Yes. Your handle is what makes your PayRequest Page URL (`payrequest.me/your-handle`) and it's also part of the badge image address. Set one from **PayRequest Page → Overview** if you haven't already. Not currently — the badge uses a consistent PayRequest style so it's instantly recognizable, and the wording is chosen automatically based on your Page Mode. No. It's a tiny image, similar in size to any other status badge you might already be using. Update the badge snippet with your new handle — old links using the previous handle will stop matching your page, so re-copy the snippet from your dashboard after a handle change. Yes — the badge has its own fixed background color, so it stays legible in both GitHub's light and dark themes. ## Next Steps Turn your page into a fundraising goal with a live progress bar and donor feed — your badge shows the running total. Brand your page with an avatar, tagline, accent color, and social links. A friendlier "Buy Me a Coffee"-style version of Donation Mode with a drinks menu and GIFs. Use your own domain for your PayRequest Page instead of payrequest.me. # PayRequest Page Styling Source: https://docs.payreque.st/shop-and-checkout/sales-page-styling Customize your PayRequest Page appearance with a Profile Banner, avatar, tagline, accent color, social links, and live preview # PayRequest Page Styling Customize your PayRequest Page to reflect your brand identity. The Styling tab provides a live preview that updates in real-time as you make changes, so you can see exactly how your page will look to visitors. ## Overview Your PayRequest Page is your public-facing profile where customers can browse your products and make purchases. The Styling tab lets you personalize: * **Profile Avatar** - Your photo or logo * **Profile Banner** - A branded cover image with separate desktop and mobile crops * **Name & Tagline** - Your business identity * **Bio/Description** - Tell visitors about yourself * **Page Theme** - Crypto-native background and card style (Solana or Crypto Native) * **Accent Color** - Your brand color for buttons and highlights * **Social Links** - Connect up to 25 social platforms and contact options Changes in the Styling tab update the preview in real-time. No need to save to see how it looks! ## Accessing the Styling Tab 1. Navigate to **PayRequest Page** from the main menu 2. Click the **Styling** tab (between Dynamic Links and Settings) 3. The page displays a two-column layout: * **Left**: Live preview of your PayRequest Page * **Right**: Styling options and controls ## Live Preview The left column shows a real-time mockup of your PayRequest Page. This preview: * Updates instantly as you type * Shows your Profile Banner, avatar, name, tagline, and social links * Displays your selected products * Mirrors the dark theme of your actual PayRequest Page The preview stays fixed while you scroll through the styling options, so you always see your changes. To see your actual live page, click **View Live Page** button to open it in a new tab. ## Profile Avatar Your avatar appears prominently at the top of your PayRequest Page. You have two options: ### Option 1: Use Social Profile Avatar If you've added social links, PayRequest can automatically fetch your avatar from those platforms: | Platform | How It Works | | - | - | | X (Twitter) | Uses your X profile picture | | GitHub | Uses your GitHub avatar | | YouTube | Uses your channel avatar | | Twitch | Uses your Twitch profile picture | | Substack | Uses your Substack author photo | | Telegram | Uses your Telegram profile picture | | SoundCloud | Uses your SoundCloud avatar | | Website | Uses your website's favicon | Simply click on any available avatar to select it. A blue checkmark indicates your current selection. ### Option 2: Upload Custom Avatar 1. Scroll to **"Or upload your own"** section 2. Drag and drop an image, or click to browse 3. Supported formats: JPG, PNG (up to 10MB) For best results, use a square image at least 200x200 pixels. ### Removing Your Avatar Click the **Remove** button next to your current avatar to revert to the default placeholder. ## Profile Banner Add a wide cover image to the top of your public PayRequest Page. Your avatar overlaps the lower edge of the banner, keeping your profile identity visible while giving your page more room for your brand, artwork, or campaign image. Profile Banner is available on every PayRequest plan, including Free. Pages without a custom banner automatically use the PayRequest default banner. ### Uploading a Banner 1. Open **PayRequest Page** and select the **Styling** tab 2. Find the **Profile Banner** card 3. Drag and drop an image, or click the upload area to choose one 4. Adjust the desktop and mobile crop positions Supported formats are **JPG, PNG, WebP, and AVIF**, with a maximum file size of **15MB**. For a sharp result, use an image of at least **1500 × 500 pixels**. ### Desktop and Mobile Crops PayRequest uses a fixed responsive banner shape so it stays consistent across screen sizes: | Preview | Aspect Ratio | Best For | | - | - | - | | **Desktop** | 3:1 | Wide browser and laptop layouts | | **Mobile** | 16:9 | Narrow phone layouts | Use the horizontal and vertical position controls below each preview to choose which part of the same image remains visible. This lets you keep a face, logo, or important text centered on both desktop and mobile without uploading two separate files. Keep essential content away from the extreme edges. Check both crop previews before you finish, especially when your banner includes text or a logo. ### Replacing or Removing a Banner Upload another image from the Profile Banner card to replace the current banner. Click **Remove** and confirm the action to hide the banner completely. You can bring the PayRequest default back later with **Use default banner**. The Profile Banner appears on your main public PayRequest Page, individual post pages, and invoice payment pages. It is not added to product, quote, or dynamic-amount pages. ## Tagline & Bio ### Your Name / Business Name This is the main heading on your PayRequest Page. It appears large and prominent below your avatar. * Use your personal name for freelancer pages * Use your company name for business pages * Keep it concise and recognizable ### Tagline A short subtitle that describes what you do. Examples: * "Creator of Laravel" * "Web Development & Design" * "Premium Coffee Roasters" * "Digital Marketing Expert" Your tagline appears directly below your name in a lighter color. Keep it under 50 characters for best display. ### Description A longer bio that tells visitors about you or your business. This appears below your social links and before your products. Tips for a good description: * Explain what you offer * Highlight your expertise or unique value * Keep it 2-3 sentences max * Include a call to action if appropriate ## Page Theme Give your page a crypto-native aesthetic with one of two premium themes. The **Page Theme** card sits directly above the Accent Color card in the Styling tab. | Theme | Look | | - | - | | **Default** | Standard PayRequest dark style — clean and neutral | | **Solana** | Deep dark bg with purple-to-green radial glow, glowing purple card border | | **Crypto Native** | Animated gradient mesh (cyan/violet), glassmorphism frosted-glass card | Themes control the background and card styling. Your accent color still applies on top — so you can combine a **Solana theme** with a purple accent for a fully Solana-branded page. See the full [Crypto Page Themes guide](/shop-and-checkout/crypto-page-themes) for screenshots and combination tips. ## Accent Color Pick a brand color that's used across your PayRequest Page for buttons, highlights, and your avatar border. If you leave it unset, the page falls back to the default blue. ### Picking a Color The Accent Color card gives you three ways to choose: | Method | When to Use | | - | - | | **Swatch palette** | Pick from a curated set of 10 brand-friendly colors (Blue, Indigo, Violet, Pink, Red, Amber, Emerald, Teal, Sky, Black) | | **Native color picker** | Click the small color square to open your operating system's color picker — useful for matching an exact brand color | | **Hex input** | Type or paste a hex value like `#f59e0b` directly | A ring around the active swatch shows your current selection. The live preview updates instantly as you change colors. ### Where the Accent Appears When you set a custom accent color, it's applied to: * **The "Pay" button** on your PayRequest Page * **Your avatar border** (the ring around your profile picture) * **Selected product highlights** — the ring around the product card you've chosen * **Other primary call-to-action buttons** in the customer flow Pick a color with strong contrast against the dark page background. Pure black or very dark colors can blend into the page; bright or saturated colors stand out best. ### Clearing the Color Click **Clear** next to the picker to reset to the default. Your PayRequest Page will revert to the standard blue accent. Accent color is a per-page setting. If you have multiple businesses or pages in the future, each can have its own accent. ## Social Links Social links serve two purposes: 1. **Display on your PayRequest Page** - Visitors can click each platform's brand icon to visit your profiles 2. **Avatar selection** - PayRequest fetches avatars from supported platforms Your page supports **25 platforms** — everything from creator platforms like Instagram, TikTok, and OnlyFans to professional networks and direct contact options like email and phone. Each link appears on your public page with its official brand icon. ### Available Platforms **Primary platforms** (always visible in the editor): * Instagram * TikTok * Twitter/X * YouTube * Website **More platforms** (click **Add More** to expand): | Category | Platforms | | - | - | | Streaming & Gaming | Twitch, Kick, Discord | | Creator & Content | Snapchat, Spotify, SoundCloud, Substack, Pinterest, Patreon, OnlyFans | | Social & Community | Facebook, Reddit, Telegram | | Professional | LinkedIn, GitHub, Calendly | | Direct Contact | Email, Phone, WhatsApp, Signal | The **Add More** section includes a search field — start typing a platform name to filter the list instantly instead of scrolling. ### Adding Social Links The five most popular platforms are always visible. Click **Add More** to reveal the full list, and use the search field to jump straight to a platform. Paste the full URL (e.g., `https://instagram.com/username`) or just type the address without `https://` — PayRequest adds it automatically. For **Email**, enter your address (e.g., `hello@example.com`) and for **Phone**, your number (e.g., `+31 6 12345678`). Visitors who click these icons get a ready-to-send email or phone call — PayRequest converts them to `mailto:` and `tel:` links automatically. Every link you add appears instantly in the preview with its brand icon, exactly as visitors will see it. Only add links to profiles you actively maintain. Broken links create a poor impression. ## Saving Your Changes Click **Save Styling** at the bottom of the right column to save all your changes. While the preview updates in real-time, your changes aren't saved until you click the save button. The actual live page only updates after saving. ## Best Practices Your avatar is the first thing visitors see. Use a clear, well-lit photo or a clean logo. Avoid blurry images or complex graphics that don't scale well. Your tagline should instantly communicate what you do. Avoid jargon or overly clever phrases. Clear and simple wins. Quality over quantity. It's better to have 2-3 active profiles than 8 dormant ones. Remove links to profiles you no longer use. Think about who visits your PayRequest Page. What do they need to know? Focus on benefits and outcomes, not just features. After saving, visit your PayRequest Page on your phone to ensure everything looks good on smaller screens. ## Frequently Asked Questions Avatar options only appear for platforms where you've entered a valid social link. Add your social profile URLs first, then the avatar options will become available. The URL handle is configured in the **Settings** tab, not the Styling tab. Go to Settings and update the "PayRequest Page Handle" field. Yes — the **Accent Color** card on the Styling tab lets you pick any brand color (from the curated swatches, your OS color picker, or a hex value) for buttons, highlights, and your avatar border. The rest of the page uses a consistent dark theme; for deeper customization see [Custom CSS](/advanced-features/custom-css). The preview updates in real-time, but the actual live page only updates after you click **Save Styling**. Make sure to save your changes. Avatars are displayed at 96x96 pixels on desktop. Upload an image at least 200x200 pixels for crisp display on high-resolution screens. The email address and phone number you add are visible to anyone who visits your page — that's the point, visitors can contact you with one click. If you prefer not to share them publicly, simply leave those fields empty. Yes. PayRequest Pages are built for creators — OnlyFans, Twitch, Kick, Discord, Patreon, Snapchat, and more are all supported with their official brand icons. Click **Add More** in the Social Links card and search for the platform. ## Related Documentation Solana and Crypto Native themes for your payrequest.me page Carry your PayRequest Page as a card in Apple Wallet Let visitors send USDC directly to your wallet from your page Use your own domain for your PayRequest Page Configure your business information Switch between carousel and grid for your product showcase See how many people visit your PayRequest Page each day (Premium) # Search Command Palette Source: https://docs.payreque.st/shop-and-checkout/search-command-palette Powerful search functionality for customers to quickly find products, invoices, orders, and subscriptions in your shop ## Overview The Search Command Palette provides customers with a powerful, keyboard-driven way to search across all available content in your shop. Similar to developer tools like VS Code, customers can quickly find products, their personal invoices, orders, and subscriptions using a modern command palette interface. ## Accessing the Search ### Keyboard Shortcut The fastest way to open search: * **Windows/Linux**: `Ctrl + K` * **Mac**: `⌘ + K` ### Click Interface Customers can also click the search icon (🔍) in the shop's top navigation bar. ### Mobile Support On mobile devices, customers can tap the search icon to open the full search interface. ## Search Capabilities ### Public Search (All Visitors) **Products**: Anyone can search your product catalog * Product names and descriptions * SKU codes * Custom product fields * Product categories ### Personal Search (Logged-in Customers) When customers are logged in, they can also search their personal data: * **Invoices**: Invoice numbers, amounts, statuses * **Orders**: Order numbers, statuses, payment statuses * **Subscriptions**: Subscription names, statuses, custom fields ## Search Features ### Intelligent Results Results are grouped and sorted by relevance: * **Exact matches** appear first * **Partial matches** follow * **Results grouped by type** (Products, Invoices, Orders, Subscriptions) * **Status badges** with color coding * **Price information** for products ### Real-time Search * **Live typing**: Results update as customers type * **Debounced input**: Optimized for performance (300ms delay) * **Minimum 2 characters** required for search * **Maximum 10 results** shown with option to be more specific ### Custom Fields Support The search includes custom fields data: * **Product custom fields**: Any additional product information * **Subscription custom fields**: Domain names, special configurations, notes ## User Interface ### Welcome Screen When opening search without typing, customers see: * **Search instructions**: "Search your products, invoices, orders, and subscriptions" * **Login prompt**: Non-logged customers see invitation to log in for personal search ### No Results When no matches are found: * **Clear messaging**: "No results found" * **Helpful suggestion**: "Try a different search term" ### Quick Actions Panel Logged-in customers see quick navigation options: * **⌘I**: View All Invoices * **⌘O**: View All Orders * **⌘S**: View All Subscriptions * **⌘P**: Profile Settings ## Search Examples ### Product Search * Type: `"skateboard"` → Finds all products containing "skateboard" * Type: `"SK-001"` → Finds product with SKU "SK-001" * Type: `"monthly"` → Finds monthly subscription products ### Personal Item Search (Logged-in) * Type: `"INV-123"` → Finds invoice with number INV-123 * Type: `"active"` → Finds all active subscriptions * Type: `"pending"` → Finds pending orders and invoices * Type: `"smartskate.nl"` → Finds subscriptions with custom domain field ## Status Badge Colors The search results show colored status badges: ### Products * **Green**: Price information (€29.99) ### Invoices * **Green**: Paid status * **Yellow**: Pending status * **Gray**: Other statuses ### Orders * **Green**: Completed orders * **Blue**: Processing orders * **Gray**: Other statuses ### Subscriptions * **Green**: Active subscriptions * **Blue**: Trial subscriptions * **Gray**: Other statuses ## Technical Details ### Search Performance * **Optimized queries**: PostgreSQL ILIKE for case-insensitive search * **Indexed searches**: Fast performance even with large datasets * **Result limitations**: Maximum 10 results to maintain speed * **Smart caching**: Efficient data retrieval ### Multi-tenant Security * **Shop isolation**: Customers only see data from their shop * **Personal data**: Only logged-in customers see their own invoices/orders * **Secure queries**: All searches properly scoped to prevent data leaks ### Custom Domain Support * **Seamless URLs**: Works perfectly with custom domains * **Proper routing**: All result links work correctly regardless of domain setup ## Best Practices ### For Business Owners **Product Optimization**: * Use clear, descriptive product names * Add relevant keywords to product descriptions * Utilize custom fields for additional searchable information * Keep SKU codes organized and meaningful **Customer Experience**: * Educate customers about the ⌘K shortcut * Encourage use of search for faster navigation * Consider search patterns when organizing your catalog ### For Customers **Search Tips**: * Use specific terms for better results * Try different keywords if first search doesn't match * Use status terms like "active", "pending", "paid" * Remember keyboard shortcuts for quick access ## Accessibility ### Keyboard Navigation * **Full keyboard support**: Navigate entirely with keyboard * **Standard shortcuts**: Follows common keyboard conventions * **Escape to close**: Easy exit from search interface ### Screen Reader Support * **Semantic HTML**: Proper markup for screen readers * **Alt text**: All icons have descriptive text * **Focus management**: Logical tab order and focus handling ### Mobile Optimization * **Touch-friendly**: Large touch targets for mobile users * **Responsive design**: Adapts to all screen sizes * **Swipe gestures**: Natural mobile interaction patterns ## Troubleshooting ### Search Not Working 1. **Check connection**: Ensure stable internet connection 2. **Refresh page**: Try reloading the shop page 3. **Clear browser cache**: Clear browser data if needed 4. **Try different terms**: Use alternative search keywords ### Results Not Appearing * **Minimum characters**: Ensure you've typed at least 2 characters * **Check spelling**: Verify search terms are spelled correctly * **Login status**: Personal items require customer login * **Wait briefly**: Allow 300ms for search to complete ### Keyboard Shortcuts Not Working * **Browser compatibility**: Ensure modern browser version * **Focus state**: Click in the page before using shortcuts * **Operating system**: Verify correct modifier key (Ctrl vs ⌘) *** *Last updated: September 2025* # Shop Setup Source: https://docs.payreque.st/shop-and-checkout/shop-setup Create and configure your PayRequest shop — the multi-product storefront customers browse at /shop/{yourshop} # Shop Setup Your PayRequest shop is a full storefront at `payrequest.app/shop/{yourshop}` where customers can browse multiple products, add them to a cart, and check out in one go — separate from single-product [PayRequest Pages](/shop-and-checkout/product-display). Setup happens in one place: **Shop** in your dashboard sidebar. Every account can have one shop. Once created, the same page is used to edit settings — there's no separate "shop settings" screen. ## How It Works Navigate to **Shop** and pick a name. It's automatically lowercased and can only contain lowercase letters, numbers, and hyphens — this becomes your URL: `payrequest.app/shop/your-name`. Names must be unique across all PayRequest shops. Set a shop description and pick a default language (English, Dutch, French, or Spanish). New shops are created offline by default. Flip the **Shop Status** toggle to make it publicly visible and start accepting orders. In the **Branding** tab, upload a logo and set a portal accent color (hex code) that's used across your shop and customer portal. In the **Custom Domain** tab, point your own domain at the shop. See [Custom Domains](/shop-and-checkout/custom-domains) for DNS steps. Configure tax display, signup, and invoicing behavior in **Shop Settings**, and add Terms & Privacy content in **Legal Pages** if you want to publish your own policies. ## Shop Settings Reference | Setting | What it does | | - | - | | **Shop Status** | Turns the shop online/offline. Offline shops return a "store not found" to visitors. | | **Allow Signup** | Lets customers create their own login for the customer portal. Turn off to keep checkout guest-only. | | **Auto Create Invoices** | Automatically generates an invoice for every order placed through the shop. | | **Allow Invoice Subscriptions** | Permits subscription products to be sold via invoice (not just automatic recurring payment). | | **Tax Display** | `inclusive` (prices shown include tax) or `exclusive` (tax shown separately at checkout). Applies shop-wide. | | **Accent Color** | A single hex color used to theme the shop and customer portal. Clear it to fall back to the default theme. | | **Logo** | Uploaded image (max 10MB), stored on R2 and shown in the shop header. | Tax display, accent color, and logo also affect the customer portal (order history, invoices, subscriptions) since it shares the same shop branding. ## Legal Pages The **Legal Pages** tab lets you paste in your own Terms of Service and Privacy Policy content, stored per-shop and shown to customers at checkout. Leaving these empty is fine — PayRequest doesn't require them to operate the shop, but publishing your own is good practice, especially alongside [GDPR Compliance](/security-and-compliance/gdpr-compliance) considerations. ## Related Shop Features Once your shop is live, these are configured separately: * **Vacation Mode** — pause new orders temporarily. See [Vacation Mode](/shop-and-checkout/vacation-mode). * **Spam Protection** — block bots and unwanted countries at checkout. See [Spam Protection](/shop-and-checkout/spam-protection). * **Product Display** — carousel vs. grid layout for your product catalog. See [Product Display Layout](/shop-and-checkout/product-display). ## FAQ Yes, from the same **Shop** page — just note the URL changes with it, so update any shared links. No, each PayRequest account has a single shop tied to your user ID. Single-product PayRequest Pages are a separate, unlimited alternative if you need multiple standalone checkout pages. Existing orders, invoices, and subscriptions are unaffected — offline only blocks new visitors from reaching the storefront and starting a new checkout. No. It only hides the option for new customers to register; customers who already have portal accounts can still log in. ## Next Steps See what customers experience at checkout How multi-product carts work Put your shop on your own domain Pause orders temporarily # Shopping Cart Source: https://docs.payreque.st/shop-and-checkout/shopping-cart How the session-based cart lets customers combine multiple shop products into a single checkout # Shopping Cart Customers browsing your [shop](/shop-and-checkout/shop-setup) can add multiple products to a cart and pay for everything in a single checkout, instead of buying one product at a time. The cart lives in the visitor's session — no account or login required to start one. The cart is separate from single-product [PayRequest Page](/shop-and-checkout/product-display) checkouts, which are for one product (or one product plus custom fields) at a time. ## How It Works Customers add a product from the shop or a product page. If the product has custom fields (options, add-ons), those are stored per cart line along with the quantity. For products with quantity selection enabled, adding the same product again increases its quantity. For products with quantity selection **disabled**, the product can only appear once in the cart — adding it again just updates its custom field values instead of creating a duplicate line. On the checkout page, customers can edit quantity and custom fields per line, or remove an item entirely, before paying. Checkout collects billing details and payment method once for the whole cart — see [Checkout Customization](/shop-and-checkout/checkout-customization). ## How Totals Are Calculated Each cart line's price is `(product price + custom field markup) × quantity`. The cart then adds up all lines plus any setup fees: ``` Subtotal = Σ (line totals across all products) Setup Fees = Σ (one-time setup fee per recurring/service product with a setup fee, not multiplied by quantity) Tax = Σ (line tax + setup fee tax, calculated per product's tax rate — skipped entirely if the customer is tax-exempt) Total = Subtotal + Setup Fees + Tax ``` Custom field markups follow the field's own pricing configuration — a fixed markup for toggles/select options, or quantity × per-unit price for number fields with per-unit pricing (see [Custom Fields](/products-and-pricing/custom-fields)). Setup fees are only counted once per order line, not once per unit — a €10 setup fee on a product with quantity 3 still only adds €10, not €30. ## Cart Persistence & Recovery * The cart is stored in the browser session, not tied to a customer account — it survives page reloads but not across devices or after the session expires. * Adding a product via a [dynamic link](/payment-processing/payment-page-dynamic-links) (a URL with `?product=` and quantity/custom-field parameters) adds it to the cart automatically when the checkout page loads. * If a customer abandons checkout, PayRequest can send a recovery link that restores their exact cart contents — see [Checkout Recovery](/shop-and-checkout/checkout-recovery). * The cart auto-migrates from any older stored format, so nothing breaks if the cart structure changes between visits. ## FAQ Yes. If any product in the cart is recurring, checkout switches to collecting a payment mandate (new or existing) instead of a one-time payment. See [Checkout Customization](/shop-and-checkout/checkout-customization). Checkout re-loads live product data on every visit, so removed or price-changed products reflect current data. An empty cart automatically redirects the customer back to the shop. Yes — if a logged-in customer is marked tax-exempt, tax is excluded from every line and the setup fee for that cart. Yes, for products where that's needed (e.g. domain products with different pricing per option), the cart can add the same product as distinct lines rather than merging them. ## Next Steps What happens after "Checkout" Recover abandoned carts automatically Configure per-product quantity selection Add priced options to products # Spam Protection Source: https://docs.payreque.st/shop-and-checkout/spam-protection Protect your checkout from bots, fake orders, and unwanted traffic from specific countries # Spam Protection Keep your checkout safe from spam, bots, and fraudulent orders. PayRequest's built-in spam protection helps you focus on real customers while automatically blocking suspicious activity. ## Why Use Spam Protection? Without protection, your checkout can be targeted by: * **Bots**: Automated scripts that create fake orders * **Card Testers**: Fraudsters testing stolen credit cards * **Spam Submissions**: Fake names and emails cluttering your data * **Unwanted Regions**: Orders from countries you don't serve Enabling spam protection reduces these issues and keeps your order data clean. ## Getting Started 1. Go to **Settings** in your dashboard 2. Click **Spam Protection** in the sidebar 3. Toggle the main **Protection** switch to enable Once enabled, you'll see additional options to customize your protection. Spam protection is disabled by default. Enable it when you start receiving unwanted orders or want to proactively protect your checkout. ## Protection Methods PayRequest uses multiple techniques to identify and block spam: ### CAPTCHA (Cloudflare Turnstile) An invisible security check that runs in the background. Most real customers won't notice it, but bots will be blocked. * **Best for**: Stopping automated bot attacks * **Customer impact**: Minimal - runs silently for most users ### Honeypot A hidden field that's invisible to humans but gets filled in by bots. If filled, the order is blocked. * **Best for**: Catching simple bots * **Customer impact**: None - invisible to real customers ### Name Analysis Detects randomly generated or suspicious names that don't look like real customer names. * **Best for**: Blocking gibberish entries like "asdfJKL123" * **Customer impact**: None for legitimate names ### Rate Limiting Limits how many checkout attempts can come from the same IP address or email in one hour. * **Best for**: Preventing rapid-fire spam attacks * **Customer impact**: Only affects users making many attempts quickly ## Country Blocking Block orders from specific countries where you don't do business or where you see high fraud rates. ### How to Block Countries 1. Go to **Settings** → **Spam Protection** 2. Enable **Country Blocking** in the Protection Methods section 3. Click the dropdown and search for a country 4. Click the **+** button to add it to your blocked list 5. Repeat for other countries you want to block ### What Customers See When someone from a blocked country tries to checkout, they'll see a friendly message: > "Orders from \[Country] are currently not accepted. Please contact support if you need assistance." This gives legitimate customers a way to reach out if they believe they were blocked in error. ### Removing a Country To unblock a country: 1. Find the country badge in your blocked list 2. Click the **×** on the badge 3. The country is immediately unblocked Start by blocking countries where you've seen the most spam or fraud. You can always adjust later based on your blocked attempts log. ## Sensitivity Settings Adjust how strict the spam detection should be: | Level | Description | | - | - | | **Low** | Only blocks obvious spam. Best if you're seeing false positives. | | **Medium** (Default) | Balanced protection for most businesses. | | **Strict** | Aggressive blocking. May catch some edge cases. | Higher sensitivity may occasionally block legitimate customers with unusual names or email patterns. Monitor your blocked attempts if you increase sensitivity. ## Rate Limits Control how many checkout attempts are allowed: * **Max IP attempts/hour**: How many orders from the same IP address (default: 10) * **Max email attempts/hour**: How many orders using the same email (default: 5) * **Block duration**: How long blocked IPs stay blocked in minutes (default: 30) Most businesses can use the defaults. Increase limits if you have many customers from shared networks (offices, universities). ## Whitelists Ensure trusted customers always get through by whitelisting their email or domain. ### Whitelist an Email 1. In the **Whitelisted Emails** section, enter the email address 2. Press Enter or click **+** 3. That email will bypass all spam checks ### Whitelist a Domain 1. In the **Whitelisted Domains** section, enter the domain (e.g., `yourcompany.com`) 2. Press Enter or click **+** 3. All emails from that domain bypass spam checks Whitelist your own company domain and any trusted partners who order frequently. ## Viewing Blocked Attempts The **Blocked Attempts** section shows all orders that were stopped by spam protection: * **Date**: When the attempt occurred * **IP Address**: Where it came from * **Email**: The email used (if provided) * **Name**: The name entered * **Reason**: Why it was blocked (Bot Detected, Rate Limited, Country Blocked, etc.) * **Risk Score**: How suspicious the attempt was (higher = more suspicious) ### Filtering Blocked Attempts Use the search box and dropdown to filter: * Search by IP, email, or name * Filter by reason (CAPTCHA Failed, Country Blocked, etc.) ### Unblocking an IP If a legitimate customer gets blocked: 1. Click **Unblock IP** in Quick Actions 2. Enter their IP address 3. Click **Unblock** They can immediately try checkout again. ## Statistics At a glance, see how your protection is performing: * **Blocked (24h)**: Attempts blocked in the last day * **Blocked (7 days)**: Attempts blocked in the last week * **Unique IPs**: Different IP addresses that were blocked * **Avg. Risk Score**: Average suspiciousness of blocked attempts ## Best Practices The default sensitivity and rate limits work well for most businesses. Only adjust if you see issues. Check regularly to ensure you're not blocking legitimate customers. Look for recognizable emails or company names. If you have key accounts or partners, whitelist their email domains so they never get blocked. Only block countries where you genuinely don't do business or see consistent fraud. Don't block countries where you have real customers. Remember that VPN users may appear to be from different countries. Consider keeping your contact information visible for edge cases. ## Frequently Asked Questions No. The checks happen instantly in the background. Customers won't notice any delay. They'll see an error message asking them to try again or contact support. You can unblock their IP manually, or whitelist their email for future orders. Country detection is based on the customer's IP address. If someone uses a VPN, they'll appear to be from the VPN's location. This is why the blocked message includes contact information for support. Whitelisted emails bypass all checks. For others, protection only applies to new checkout attempts - existing orders and subscriptions are not affected. Yes. The blocked attempts log shows the exact reason, risk score, and any issues detected for each blocked attempt. Very accurate. PayRequest uses Cloudflare's infrastructure when available, which provides reliable country detection. IP-based lookups are used as a fallback. No. Spam protection only applies to shop checkout. Customers paying invoices through payment links are not affected. ## Need Help? If you're seeing unexpected blocks or need help configuring spam protection, contact us at [support@payrequest.io](mailto:support@payrequest.io). # Vacation Mode Source: https://docs.payreque.st/shop-and-checkout/vacation-mode Temporarily pause orders for your shop and PayRequest Pages during holidays or maintenance # Vacation Mode Take a break without worrying about incoming orders. Vacation Mode lets you temporarily disable all new orders from your shop and PayRequest Page links while keeping your storefront visible. ## When to Use Vacation Mode Vacation Mode is perfect for: * **Holidays**: Going on vacation and can't fulfill orders * **Inventory**: Restocking products and need to pause sales * **Maintenance**: Updating your shop or products * **Seasonal Breaks**: Closing during off-season periods * **Personal Time**: Taking time off from your business ## How It Works When Vacation Mode is enabled: * **Shop**: Customers can still browse your products but cannot place orders * **PayRequest Pages**: Direct product links show a vacation message instead of checkout * **Existing Orders**: Current orders and subscriptions are not affected * **Invoice Payments**: Customers can still pay existing invoices Vacation Mode only blocks **new** orders. Existing subscriptions continue to bill normally, and customers can still pay outstanding invoices. ## Enabling Vacation Mode 1. Go to **Shop** in your dashboard 2. Click the **Shop Settings** tab 3. Find the **Vacation Mode** card 4. Toggle the switch to enable ### Setting an End Date You can optionally set an automatic end date: 1. Enable Vacation Mode 2. Click the date picker under "Auto-disable vacation mode on" 3. Select the date when you want to resume accepting orders 4. Click **Save Vacation Settings** When the end date passes, Vacation Mode automatically disables and your shop resumes normal operation. Leave the end date empty if you want to manually re-enable orders when you're ready. ### Custom Message Personalize the message your customers see: 1. Enable Vacation Mode 2. Enter your message in the "Custom message for customers" field 3. Click **Save Vacation Settings** **Example messages:** * "We're on holiday until January 2nd. Happy New Year!" * "Closed for inventory. Back next week!" * "Summer break - see you in September!" If you don't set a custom message, customers will see a default vacation notice. ## What Customers See ### On Your Shop Customers visiting your shop will see an amber notification banner at the top of the page with your vacation message and end date (if set). ### On PayRequest Page Product Links When customers try to purchase via a direct product link, they'll see a vacation notice instead of the payment form. The product information is still visible, but checkout is disabled. ## Monitoring Vacation Mode When Vacation Mode is active: * A **Vacation** badge appears on the Shop Settings tab * The Vacation Mode card has an amber border * A warning message reminds you that orders are blocked ## Disabling Vacation Mode To resume accepting orders: 1. Go to **Shop** → **Shop Settings** tab 2. Toggle the Vacation Mode switch off 3. Orders are immediately accepted again Alternatively, if you set an end date, Vacation Mode disables automatically at midnight on that date. ## Best Practices If possible, announce your vacation period through email or social media before enabling Vacation Mode. Use the custom message to tell customers exactly when you'll be back and accepting orders again. Before enabling Vacation Mode, make sure you've fulfilled or addressed any pending orders. Set an end date so you don't forget to re-enable orders when you return. ## Frequently Asked Questions No. Active subscriptions continue to bill normally. Vacation Mode only prevents new orders and subscriptions from being created. Yes. Existing invoices can still be paid during Vacation Mode. Only new product purchases are blocked. Your shop remains fully visible. Customers can browse products and view prices - they just can't complete checkout. Currently, Vacation Mode applies to your entire shop. To disable individual products, set their status to "Archived" or toggle "Show in shop" off. The end date uses your business timezone (Europe/Amsterdam). Vacation Mode disables at midnight on the selected date. # Archiving Subscriptions Source: https://docs.payreque.st/subscriptions/archiving-subscriptions Permanently shelve subscriptions you no longer need — keep your list clean while preserving all history # Archiving Subscriptions Over time, your subscription list fills up with entries that are no longer relevant: customers who switched to a different plan, one-time projects that ended, businesses that closed down. Canceling keeps them visible in your list and in the customer portal. Archiving removes them from view entirely — while keeping every invoice, transaction, and note intact for your records. Archived subscriptions are hidden from the customer portal, excluded from billing, and not counted in MRR calculations. They stay in your database for audit and reference purposes. ## When to Archive Archiving is the right choice when a subscription has run its course and no longer needs to be in your day-to-day view. A customer moved from **Basic** to **Professional**. The old subscription is canceled but still clutters your list. Archive it to keep focus on the active plan. A customer left permanently — they closed their business, moved to a competitor, or simply don't need the service anymore. Archive their subscription to keep your list current. A fixed-term project or seasonal subscription (event hosting, campaign website, temporary license) is finished. Archive it instead of leaving it in your canceled list. Two companies merged, or a customer restructured and consolidated multiple subscriptions into one. Archive the old entries to avoid confusion. ### More Use Cases * **Product discontinued** — You stopped offering a service. Archive all subscriptions for that product so they don't show up in reports or confuse your team. * **Free trial that never converted** — The customer tried your service, never paid, and the trial expired months ago. Archive it to separate real customers from leads that didn't convert. * **Billing dispute resolved** — After a chargeback or dispute, you agreed to end the service. Archive the subscription to signal it's fully resolved — not just canceled. * **Internal or test subscriptions** — Subscriptions you created for demos, testing, or internal use that are no longer needed. * **Seasonal customer** — A customer only needs your service during summer or a specific quarter. Archive between seasons to keep your active list focused, reactivate when they return. * **Duplicate from migration** — After importing subscriptions from another system, duplicates may exist. Archive the extras without losing their payment history. Archiving is not the same as canceling. Canceled subscriptions still appear in the customer portal and in your subscription list. Archived subscriptions are hidden from both. ### Archiving vs. Canceling vs. Deleting | | **Cancel** | **Archive** | **Delete** | | - | - | - | - | | Visible to customer | Yes | No | No | | Visible in subscription list | Yes | Only in Archived tab | Gone | | Invoices & transactions | Preserved | Preserved | Lost | | Can be reactivated | Yes | Yes | No | | Counted in reports | As canceled | Not counted | Not counted | | **Best for** | Customer might come back | Done permanently, keep records | N/A (not supported) | ## How to Archive a Subscription Go to **Subscriptions**, find the subscription, and open its detail page. A subscription must be **canceled** before it can be archived. If it's still active, cancel it first. On a canceled subscription, click the **Archive Subscription** button below the Reactivate button. A confirmation dialog explains what archiving does. Click **Archive Subscription** to confirm. The archive button only appears on canceled subscriptions. This two-step flow (cancel → archive) prevents accidentally archiving an active subscription. ## What Happens When You Archive * **Billing stops** — `next_billing_at` is cleared, the billing job skips it * **Hidden from customer portal** — the customer no longer sees this subscription * **Moved to Archived tab** — visible only under **Subscriptions > Archived** with a zinc/gray badge * **MRR excluded** — not counted in your revenue calculations * **Bulk action protected** — cannot be resumed or canceled via bulk actions * **Duplicate detection cleared** — new subscriptions for the same customer + product are allowed * **All data preserved** — invoices, transactions, orders, tags, and notes remain intact * **Activity logged** — the archive action appears in the subscription's history ## Viewing Archived Subscriptions Go to **Subscriptions** and click the **Archived** tab. The zinc-colored badge shows the count. On the subscription detail page, archived subscriptions show: * A **zinc/gray "Archived" badge** in the header * An info message explaining no actions are available * A **Reactivate Subscription** button for when you need to bring it back ## Reactivating an Archived Subscription Sometimes a customer comes back, or you archived something by mistake. You can always reactivate: 1. Go to **Subscriptions > Archived** tab 2. Click the subscription to open its detail page 3. Click **Reactivate Subscription** 4. Set up the billing details (next billing date, payment mandate) 5. The subscription returns to **Active** status Reactivation is the only action available on archived subscriptions. This prevents accidental status changes on subscriptions that should stay shelved. ## Best Practices Don't archive immediately after canceling. Wait until any pending invoices are paid or resolved, chargebacks are settled, and the customer confirms they don't need reactivation. Then archive. Tag subscriptions before archiving to make them easier to find later. For example: "churned-2026-Q1", "migrated-to-pro", or "dispute-resolved". Tags are preserved after archiving. Once a quarter, glance at the Archived tab to verify nothing was archived by mistake. The count badge makes this easy — if it suddenly jumps, investigate. When you stop offering a product, cancel all related subscriptions first, then archive them together. Use tags to mark the reason (e.g., "product-discontinued"). ## FAQs No. Archived subscriptions are completely hidden from the customer portal. No. Only active subscriptions are counted in MRR and revenue reports. No. All linked data is preserved. Archiving only changes the subscription status. You can still view all invoices and transactions on the subscription detail page. No. You need to cancel it first, then archive. This two-step process prevents accidentally hiding a subscription that's still billing. PayRequest doesn't support deleting subscriptions because of linked invoices and transactions. Archiving gives you the same clean-list result without breaking any data relationships. Yes. Use the **Archived** tab in the subscription list, or search by customer name — archived subscriptions appear when you're on the Archived tab. Open invoices are not automatically canceled when you archive from the UI. Review and cancel any open invoices manually before archiving, or they will remain open but unbilled. ## Related Articles Understand all subscription statuses and transitions Tag subscriptions for easy filtering and organization Structured cancellation with notice periods Temporarily halt service for non-paying customers # Billing Cycles Source: https://docs.payreque.st/subscriptions/billing-cycles Configure payment intervals, timing, and billing behavior for subscriptions ## Overview Billing cycles determine when and how often customers are charged for their subscriptions. PayRequest supports flexible billing intervals, custom timing, and automatic billing date management. Choose billing cycles that match your business model. Monthly billing provides steady cash flow, while annual billing reduces churn and administrative overhead. ## Supported Billing Intervals PayRequest supports the following billing intervals: | Interval | Billing Frequency | Common Use Cases | | - | - | - | | **Monthly** | Every 30 days | SaaS, memberships, retainers | | **Quarterly** | Every 3 months | Enterprise contracts, seasonal services | | **Yearly** | Every 12 months | Annual subscriptions, domain renewals | The billing interval is configured on the **product** level. All subscriptions using that product follow the same interval. ## How Billing Works ### Billing Date Calculation When a subscription is created, PayRequest calculates the first and subsequent billing dates: **Without Trial:** ``` Creation date: December 5, 2025 Interval: Monthly First billing: January 5, 2026 Next billing: February 5, 2026 ``` **With Trial:** ``` Creation date: December 5, 2025 Trial period: 14 days Trial ends: December 19, 2025 First billing: December 19, 2025 Next billing: January 19, 2026 ``` **With Custom Start Date:** ``` Creation date: December 5, 2025 Custom start: January 1, 2026 First billing: January 1, 2026 Next billing: February 1, 2026 ``` ### The Billing Process Each day at **03:00 (Europe/Amsterdam timezone)**, PayRequest processes due subscriptions: 1. **Identify Due Subscriptions**: Find all active subscriptions where `next_billing_at` is in the past 2. **Validate Billing**: Check subscription status (active, not paused, not completed) 3. **Check Trial Status**: Skip billing if subscription is still in trial period 4. **Process Payment**: Charge via mandate or generate invoice 5. **Update Next Billing**: Calculate next billing date based on interval 6. **Record Transaction**: Create transaction record for payment tracking Billing runs automatically. You don't need to manually trigger payments - just ensure subscriptions are set up correctly. ## Configuring Product Intervals Set the billing interval when creating or editing a product: ### Step 1: Navigate to Products Go to **Products** in the sidebar and click **Create Product** or edit an existing one. ### Step 2: Enable Recurring Toggle **"Is Recurring"** to enable subscription billing for this product. ### Step 3: Set Interval Choose the billing interval: * **Monthly**: Charged every month * **Quarterly**: Charged every 3 months * **Yearly**: Charged every 12 months ### Step 4: Set Interval Count (Optional) For custom intervals, set the interval count: | Interval | Count | Result | | - | - | - | | Monthly | 1 | Every month | | Monthly | 2 | Every 2 months | | Monthly | 6 | Every 6 months | | Yearly | 1 | Every year | | Yearly | 2 | Every 2 years | Changing a product's interval only affects **new** subscriptions. Existing subscriptions retain their original billing interval. ## Billing Date Management ### Viewing Billing Dates Each subscription shows: * **Last Billed At**: Date of most recent successful payment * **Next Billing At**: Date of upcoming payment View these in: * Subscription list table * Subscription detail page * Customer profile (subscription section) ### Modifying Billing Dates To change a subscription's next billing date: 1. Go to **Subscriptions** → Click the subscription 2. Click **Edit** 3. Modify **Next Billing Date** 4. Save changes **Common reasons to modify billing dates:** * Align multiple subscriptions to bill on the same day * Accommodate customer payment cycles * Correct an incorrectly set date * Provide billing grace period Changing the next billing date only affects that one cycle. Subsequent billing dates are calculated from the new date using the standard interval. ### Billing Date Alignment For customers with multiple subscriptions, you may want to align billing dates: **Before:** ``` Subscription A: Bills on 5th Subscription B: Bills on 12th Subscription C: Bills on 23rd Result: 3 separate payments per month ``` **After alignment:** ``` Subscription A: Bills on 1st Subscription B: Bills on 1st Subscription C: Bills on 1st Result: 1 combined payment per month (or 3 same-day payments) ``` PayRequest doesn't automatically combine payments. Each subscription generates its own payment, even if billing on the same day. ## Trial Period Impact Trial periods affect the billing cycle: ### How Trials Work 1. **Subscription created** → Status = "Trial" 2. **Trial period counts down** → No billing occurs 3. **Trial ends** → Status changes to "Active" 4. **First billing** → Payment collected on trial end date ### Trial End Behavior When a trial ends: | Mandate Status | Result | | - | - | | Active mandate | Payment collected automatically | | No mandate | Subscription moves to "Pending Mandate" | | Failed payment | Subscription moves to "Failed" | ### Configuring Trials Set trial periods on the product: 1. Go to **Products** → Edit product 2. Enable **"Has Trial"** 3. Set **Trial Days** (e.g., 14) 4. Optionally add **Trial Description** (shown to customers) Common trial lengths: 7 days (quick evaluation), 14 days (standard), 30 days (complex products). ## Payment Timing ### Automatic Billing (Mandate-Based) For mandate-based subscriptions: **Daily Schedule:** * **03:00**: Billing job runs, identifies due subscriptions * **03:00-04:00**: Payments created in Mollie * **Within 1-3 business days**: SEPA Direct Debit settles **Payment Status Flow:** ``` Created → Open → Pending → Paid ↓ Failed (if declined) ``` ### Invoice-Based Billing (Manual Payment) For subscriptions set to **manual payment** (no mandate assigned): **Daily Schedule:** * **03:00**: Billing job identifies due subscriptions * **03:00**: Invoice generated and emailed to customer * **Customer action**: Customer pays via bank transfer, iDEAL, or payment link **Invoice Due Date:** * Default: 14 days from invoice date * Configurable in invoice settings You can switch any subscription between automatic and manual payment at any time. See [Payment Methods for Subscriptions](/subscriptions/payment-methods) for details. ### Billing Period on Invoices Subscription invoices automatically display the billing period so customers know exactly what they're paying for: | Interval | Period Format | Example | | - | - | - | | **Monthly** | Month name + Year | "November 2025" | | **Quarterly** | Quarter + Year | "Q4 2025" | | **Yearly** | Year | "2025" | | **Other** | Date range | "20-11-2025 - 19-12-2025" | **Where the period appears:** 1. **Invoice Reference**: The period is stored in the invoice reference field 2. **Invoice Item Description**: Each line item shows "Abonnement - November 2025" 3. **Customer Communications**: Email and PDF invoices include the period **Example Invoice Item:** ``` Product: Directadmin Hosting Description: Abonnement - November 2025 Quantity: 1 Unit Price: €15.00 Tax (21%): €3.15 Total: €18.15 ``` The billing period helps with accounting reconciliation and reduces customer questions about which period an invoice covers. ## Fixed-Term Subscriptions ### Payment Limits Set a maximum number of payments for fixed-term contracts: ``` Product: 12-Month Premium Plan Payment limit: 12 Interval: Monthly ``` **Behavior:** * After 12 payments, subscription status → "Completed" * No further billing occurs * Customer retains access based on your business logic ### Tracking Payments Each subscription tracks: * **Payments Made**: Number of successful payments * **Payments Total**: Payment limit (if set) * **Remaining**: Payments Total - Payments Made View this information in the subscription detail page. ## Proration (Not Supported) PayRequest does not currently support prorated billing. Full billing periods are charged regardless of when the subscription starts or changes. **Workarounds:** * Use custom pricing for partial first periods * Offer credit notes for cancelled subscriptions * Align subscription changes to billing cycle dates ## Billing Failures When a billing attempt fails: ### Automatic Retry PayRequest automatically retries failed payments: | Retry | Timing | | - | - | | 1st attempt | Immediately (billing date) | | 2nd attempt | 2 days later | | 3rd attempt | 2 days after 2nd | | Final | 2 days after 3rd | After max retries (default: 3), subscription status → "Failed" ### Manual Retry To manually retry a failed payment: 1. Go to **Subscriptions** → Click failed subscription 2. Review failure reason 3. Click **Retry Payment** ### Common Failure Reasons | Reason | Solution | | - | - | | Insufficient funds | Wait and retry, or contact customer | | Mandate revoked | Request new mandate authorization | | Account closed | Contact customer for new payment method | | Technical error | Retry automatically, contact support if persistent | See [Failed Payment Handling](/subscriptions/failed-payment-handling) for complete dunning configuration. ## Pausing and Billing When a subscription is paused: * **Billing stops** immediately * **Next billing date** is preserved * **Resume behavior** depends on configuration: ### Resume Options **Option A: Resume at next billing date (default)** ``` Paused on: December 10 Next billing: January 5 Resumed on: December 20 Next billing: January 5 (unchanged) ``` **Option B: Resume with new cycle** ``` Paused on: December 10 Original next billing: January 5 Resumed on: December 20 New next billing: January 20 (recalculated) ``` Configure resume behavior when pausing the subscription. ## Billing Reports ### Monthly Summary View subscription billing summaries in **Analytics** → **Subscriptions**: * **MRR (Monthly Recurring Revenue)**: Total monthly subscription value * **Active Subscriptions**: Count by status * **Upcoming Billings**: Next 30 days projection ### Transaction History All subscription payments appear in **Transactions**: * Filter by "Subscription" source * Export to CSV for accounting * Link transactions to specific subscriptions ## Best Practices ### ✅ Do's * **Bill on consistent dates** when possible (1st or 15th of month) * **Monitor failed payments** daily and follow up quickly * **Test billing** with a test subscription before going live * **Set appropriate trial lengths** - long enough to evaluate, short enough to convert * **Document billing terms** clearly for customers ### ❌ Don'ts * **Don't change intervals** on active subscriptions without customer communication * **Don't ignore failed payments** - they indicate customer or mandate issues * **Don't set billing dates** on dates that don't exist (e.g., 31st for monthly) * **Don't modify billing dates** right before a scheduled billing run ## Troubleshooting ### Subscription Didn't Bill **Causes:** 1. Subscription status is not "Active" 2. Subscription is paused 3. Trial period not ended 4. Next billing date is in the future 5. Payment limit reached (completed) **Solution:** * Check subscription status and next billing date * Verify trial end date if applicable * Review subscription details page for status ### Wrong Amount Charged **Causes:** 1. Quantity changed after subscription creation 2. Custom field markup not calculated 3. Price override was set **Solution:** * Review subscription recurring amount * Check transaction details for breakdown * Edit subscription if amount needs correction ### Billing Date Keeps Shifting **Causes:** 1. Month-end dates on 31st shift to 28th/30th 2. Manual billing date modifications 3. Billing failures causing date adjustments **Solution:** * Use dates that exist in all months (1st-28th) * Avoid modifying billing dates unless necessary * Review billing history for patterns ## Related Documentation Set up new subscriptions Configure dunning and retries Temporary subscription stops Configure free trials ## Frequently Asked Questions Yes! Use the "Custom Start Date" option when creating a subscription. Set it to the desired day of the month, and subsequent billing will follow that pattern. For months with fewer days, billing occurs on the last day of the month. February 28th (or 29th), April 30th, etc. This can cause billing date drift over time. Currently, you cannot change the interval of an existing subscription. You would need to cancel and create a new subscription with the desired interval. The billing job runs daily at 03:00 Europe/Amsterdam timezone. Subscriptions with `next_billing_at` in the past are processed. Billing runs every day, including weekends and holidays. However, SEPA Direct Debit settlement may be delayed during bank holidays - payments are still created, just settled later. Edit the subscription and move the `Next Billing Date` forward by the desired grace period. The customer won't be billed until that new date. # Cancellation Requests Source: https://docs.payreque.st/subscriptions/cancellation-requests Handle subscription cancellations with notice periods, reason collection, and automatic domain management # Cancellation Requests Instead of instantly canceling subscriptions, PayRequest lets you collect cancellation requests with a configurable notice period. This gives you time to retain customers, properly wind down services, and automatically disable domain auto-renewals. Cancellation requests integrate with the [Support Requests](/customer-management/support-requests) system. Each request creates a support ticket you can review and respond to before the cancellation takes effect. ## Overview Configurable notice period (default 30 days) before the subscription actually cancels Customers select a reason and can leave a message explaining why they're canceling Linked domain auto-renewals are automatically disabled when a cancellation is requested ## How It Works From the customer portal subscription detail page, the customer clicks **Cancel Subscription**. A modal asks for their cancellation reason and an optional message. The system calculates the effective cancellation date as the later of: * Today + the configured notice period (default: 30 days) * The next billing date (so the customer gets what they've already paid for) A **Cancel Subscription** support request is automatically created with the customer's reason and message, linked to the specific subscription. When submitting from the portal, the subscription selection is required — the dropdown shows subscription names with amounts and status for easy identification. You can review the request from the Support Requests page. If the subscription has a linked domain registration with auto-renew enabled, it's automatically turned off at the domain registrar (OpenProvider). A daily scheduled job checks for subscriptions past their effective cancellation date and cancels them automatically. The linked support request is marked as resolved. ## Cancellation Reasons When requesting cancellation, customers choose from these reasons: | Reason | Description | | - | - | | **Too Expensive** | Price is a concern | | **Switching Provider** | Moving to a different service | | **No Longer Needed** | Service is no longer required | | **Other** | Custom reason with free text | Customers can also add a personal message explaining their situation in more detail. ## Product-Level Settings Each product has its own cancellation configuration. Edit a product and scroll to the **Cancellation Settings** section: | Setting | Options | Default | | - | - | - | | **Cancellation Mode** | Request (with notice period) / Immediate | Request | | **Notice Period** | 1–365 days | 30 days | | **Allow Cancel** | Enable/disable the cancel button in the portal | Enabled | | **Allow Pause** | Enable/disable the pause button in the portal | Enabled | Set **Cancellation Mode** to **Immediate** if you want the old behavior where clicking cancel stops the subscription right away — no notice period, no support request. ## Managing Pending Cancellations ### Customer Portal When a cancellation is pending, the customer sees: * An amber banner showing the requested date and effective cancellation date * A **Withdraw Cancellation** button if they change their mind * The cancel button is hidden while a request is pending ### Admin Dashboard On the **subscription detail page**, admins see: * A cancellation pending callout with requested and effective dates * **Withdraw Cancellation** — cancels the request and keeps the subscription active * **Cancel Now** — immediately cancels without waiting for the notice period * A link to the related support request for review and communication On the **support request detail page**, the linked subscription shows a hover popover with status, amount, billing interval, next billing date, and cancellation details. Two dedicated action buttons let you handle the request directly: * **Approve & Cancel** — Cancels the subscription and resolves the support request in one click * **Reject & Keep Active** — Clears the cancellation fields from the subscription and rejects the request The approve/reject buttons appear only while the request is still open or in review. Use these for quick decisions without navigating to the subscription detail page. ## Automatic Processing A scheduled command runs daily at 06:15 to process cancellation requests: * Finds all active subscriptions where the effective cancellation date has passed * Cancels each subscription automatically * Closes the linked support request as resolved Once a subscription is automatically canceled after the notice period, it cannot be undone. Use the **Withdraw Cancellation** option before the effective date if the customer wants to stay. ## Frequently Asked Questions The effective cancellation date is always the later of the notice period end and the next billing date. This ensures customers aren't charged again after requesting cancellation while still getting the service they've already paid for. Yes. On the subscription detail page, you can use the regular **Cancel Subscription** action for immediate cancellation, or use **Cancel Now** on a pending cancellation request. The cancellation request is removed, the support request is closed, and the subscription continues as normal. If a domain auto-renew was disabled, you may need to re-enable it manually. The cancellation creates a support request, so you can communicate with the customer through the ticket. You can also send email notifications from the support request detail page. ## Next Steps Temporarily pause subscriptions instead of canceling Manage cancellation requests alongside other support tickets Configure what customers can do in the portal Understand the full subscription status flow # Creating Subscriptions Source: https://docs.payreque.st/subscriptions/creating-subscriptions Set up recurring billing for your customers with automatic payment collection ## Overview Subscriptions enable you to automatically collect recurring payments from customers at regular intervals. PayRequest handles the entire subscription lifecycle: from initial setup and payment authorization, through billing cycles, to pausing, resuming, and cancellation. Subscriptions are ideal for SaaS products, memberships, retainers, maintenance contracts, and any service with regular billing. ## Key Features * **Flexible Billing Intervals**: Monthly, quarterly, or yearly billing * **Free Trials**: Offer trial periods before billing starts * **SEPA Direct Debit**: Automatic payments via bank mandate * **Invoice-Based Billing**: Send invoices instead of automatic collection * **Quantity Support**: Bill per seat, user, or unit * **Custom Pricing**: Override product prices per subscription * **Custom Start Dates**: Schedule subscriptions to start in the future * **Payment Limits**: Set fixed number of payments (e.g., 12-month contracts) * **Custom Fields**: Collect additional information per subscription ## Prerequisites Before creating subscriptions, ensure you have: 1. **Payment Provider Connected**: Mollie account configured in Settings → Payment Providers 2. **Recurring Product**: At least one product marked as "Recurring" or type "Subscription" 3. **Customer Record**: The customer you want to bill Products must have **"Is Recurring"** enabled or product type set to **"Subscription"** to appear in the subscription product dropdown. ## Creating a Subscription (Dashboard) Navigate to **Subscriptions** in the sidebar, then click **Create Subscription**. ### Step 1: Select Customer Choose the customer who will be billed for this subscription. **Customer Selection Tips:** * Search by name or email * Customer must have a valid email address * For mandate-based billing, customer needs a linked Mollie customer ID (created automatically on first payment) ### Step 2: Select Product Choose a recurring product from your catalog. **What appears here:** * Products with "Is Recurring" enabled * Products with type "Subscription" * Only active products are shown When you select a product, the form automatically loads: * Base price and billing interval from product settings * Trial period configuration (if product has trial enabled) * Custom fields defined on the product ### Step 3: Configure Subscription Details #### Quantity Set the number of units to bill. Common uses: * **Per seat pricing**: Charge per user (e.g., 5 users × €10/month = €50/month) * **Tiered quantity**: Higher quantities for bigger packages * **Default**: 1 unit #### Custom Price (Optional) Enable **"Use custom price"** to override the product's default price: ``` Product price: €49/month Custom price: €39/month (promotional pricing) ``` Custom pricing is per unit. Total = Custom Price × Quantity. #### Trial Period If the product has a trial period configured, it applies automatically. You can also manually set trial days: ``` Trial days: 14 Result: Customer can use service for 14 days before first charge ``` **Trial Behavior:** * Subscription status = "Trial" during trial period * No payment collected during trial * First billing occurs when trial ends * Trial end date shown clearly in subscription details #### Custom Start Date Enable **"Use custom start date"** to schedule when billing begins: **Use cases:** * Start billing on the 1st of next month * Align with customer's fiscal year * Replace an expiring subscription seamlessly ``` Today: December 5, 2025 Custom start date: January 1, 2026 Result: First payment collected on January 1, 2026 ``` ### Step 4: Payment Method Choose how payments will be collected: #### Mandate-Based (Automatic) **How it works:** 1. Customer authorizes payments via SEPA Direct Debit 2. PayRequest automatically charges their bank account each billing cycle 3. No action needed from customer after initial authorization **Requirements:** * Customer must complete mandate authorization (via email link or checkout) * Mollie payment provider configured * Supported: SEPA Direct Debit, credit cards (with recurring capability) **Mandate Status Scenarios:** | Scenario | Result | | - | - | | Customer has active mandate | Subscription starts immediately | | No mandate exists | Email sent to customer to authorize | | Mandate pending | Subscription status = "Pending Mandate" | #### Invoice-Based (Manual) **How it works:** 1. PayRequest generates an invoice each billing cycle 2. Invoice emailed to customer with payment link 3. Customer pays invoice manually (iDEAL, bank transfer, card, etc.) **When to use:** * Customers prefer to review charges before paying * Business customers requiring invoice approval * Markets where SEPA Direct Debit isn't common Invoice-based subscriptions require Shop settings to enable this option. Go to **Shop Settings** → **Enable Invoice Subscriptions**. ### Step 5: Custom Fields If the product has custom fields configured, fill them in: **Common custom field types:** * **Text**: Company name, project reference * **Email**: Technical contact email * **URL**: Website being hosted * **Number**: Additional seats, storage GB * **Toggle**: Add-on features with extra cost * **Select**: Service tier, support level Toggle and select fields can have **price markup** - enabling them automatically increases the recurring amount. ### Step 6: Review Summary Before creating, review the summary panel showing: * **Customer name** * **Product and quantity** * **Recurring amount** (including any markup from custom fields) * **Billing interval** (monthly/quarterly/yearly) * **Trial period** (if applicable) * **First billing date** * **Payment method** (mandate or invoice) ### Step 7: Create Click **Create Subscription** to finalize. **What happens next:** | Payment Method | Customer Has Mandate | Result | | - | - | - | | Mandate | Yes | Subscription active, billing scheduled | | Mandate | No | Email sent to customer with authorization link | | Invoice | N/A | Invoice created and emailed (if billing soon) | ## Creating Subscriptions via Shop Checkout Customers can self-subscribe through your shop: ### Customer Flow 1. Customer visits your shop 2. Selects a recurring product 3. Proceeds to checkout 4. Completes payment (first payment or mandate authorization) 5. Subscription created automatically ### Shop Configuration Configure subscription checkout behavior in **Shop Settings**: * **Allow trial signups**: Let customers start trials without payment * **Show billing cycle**: Display "€49/month" or "€499/year" clearly * **Require immediate payment**: Collect first payment at checkout * **Enable invoice subscriptions**: Allow invoice-based billing ## Subscription Statuses After creation, subscriptions progress through various statuses: | Status | Meaning | Actions Available | | - | - | - | | **Active** | Billing normally | Pause, Cancel, Edit | | **Trial** | In free trial period | Convert early, Cancel | | **Pending Mandate** | Awaiting payment authorization | Resend email, Cancel | | **Paused** | Temporarily stopped | Resume, Cancel | | **Failed** | Payment collection failed | Retry, Update payment method | | **Canceled** | Permanently ended | Reactivate (create new) | | **Completed** | Reached payment limit | N/A | See [Subscription Lifecycle](/subscriptions/subscription-lifecycle) for detailed status transitions. ## Use Cases ### 1. SaaS Monthly Subscription ``` Product: Pro Plan Price: €49/month Trial: 14 days Payment: Mandate (automatic) ``` **Result**: Customer gets 14-day trial, then €49 charged automatically each month. ### 2. Annual Retainer ``` Product: Maintenance Contract Price: €2,400/year Custom start: January 1 Payment: Invoice ``` **Result**: Invoice sent on January 1 each year for customer to pay. ### 3. Per-Seat Pricing ``` Product: Team Plan Price: €10/user/month Quantity: 15 Custom field: Company Name = "Acme Corp" ``` **Result**: €150/month charged automatically for 15 seats. ### 4. Fixed-Term Contract ``` Product: 12-Month Premium Price: €99/month Payment limit: 12 payments ``` **Result**: 12 monthly payments, then subscription automatically completes. ### 5. Domain Renewal ``` Product: Domain Registration Price: €15/year (based on TLD) Custom field: Domain = "example.nl" Interval: Yearly ``` **Result**: Annual renewal charged automatically for domain. ## Best Practices ### ✅ Do's * **Use clear product names** that explain what's being billed * **Set appropriate trial lengths** (7-30 days typical) * **Configure payment reminders** for invoice-based subscriptions * **Use tags** to organize subscriptions by type, customer segment, or sales rep * **Review "Pending Mandate" subscriptions** regularly - follow up if not completed * **Test the flow** by creating a test subscription for yourself ### ❌ Don'ts * **Don't create duplicate subscriptions** for the same service * **Don't use trial for invoice-based** (customers might not pay after trial) * **Don't forget setup fees** - configure them on the product if applicable * **Don't ignore failed payments** - configure [dunning](/subscriptions/failed-payment-handling) * **Don't change product prices** without considering existing subscriptions ## After Creation Once a subscription is created: 1. **Monitor the dashboard** for status updates 2. **Check transaction history** for payment records 3. **Review customer portal** - customers can see their subscriptions 4. **Set up automations** for status changes (failed payment notifications) ## Troubleshooting ### Customer Didn't Receive Mandate Email **Causes:** 1. Invalid email address 2. Email in spam folder 3. Mail delivery issues **Solutions:** * Verify customer email address * Ask customer to check spam * Resend mandate email from subscription detail page * Check email delivery logs in Settings ### Subscription Stuck at "Pending Mandate" **Causes:** 1. Customer hasn't clicked authorization link 2. Customer abandoned the mandate process 3. Bank rejected the mandate **Solutions:** * Contact customer to complete authorization * Resend mandate email * Consider switching to invoice-based billing * Check Mollie dashboard for mandate errors ### Wrong Amount Being Charged **Causes:** 1. Product price changed after subscription creation 2. Custom field markup not calculated correctly 3. Quantity mismatch **Solutions:** * Edit subscription to update amount * Subscription amounts are fixed at creation (product price changes don't affect existing subscriptions) * Update quantity if seats changed ### Trial Not Applied **Causes:** 1. Product doesn't have trial configured 2. Trial days set to 0 3. Customer already had a trial (if trial-once logic exists) **Solutions:** * Check product settings for trial configuration * Manually set trial days when creating subscription * Create new subscription with correct trial settings ## Related Documentation Understand status transitions SEPA authorization management Configure payment intervals Handle payment failures ## Frequently Asked Questions Yes! Edit the subscription and update the recurring amount. The new price applies from the next billing cycle. Customers are not automatically notified of price changes - consider sending a manual email. SEPA mandates don't expire, but they can be revoked by the customer or bank. If this happens, the subscription status changes to "Failed" and you'll need to request a new mandate authorization. Yes, customers can have unlimited active subscriptions. Common scenarios include multiple products, different billing entities, or separate projects. Create subscriptions manually for each customer. Set a custom start date to align with their current billing cycle. For mandate-based billing, they'll need to authorize payments once. Yes! If a subscription was created separately and needs to be associated with an order, go to the **Order Detail** page. In the **Order Subscriptions** card, use the "Link an existing subscription" dropdown to select and connect the subscription. This is useful for reconciling historical data or fixing accidentally unlinked subscriptions. Yes! Use the "Custom price" option when creating each subscription. This lets you offer promotional pricing, grandfathered rates, or negotiated enterprise pricing. **Pausing** temporarily stops billing - the subscription can be resumed later and retains all settings. **Canceling** permanently ends the subscription - to restart, you'd create a new subscription. ## Need Help? Create recurring products Configure free trials Link subscriptions to orders Connect Mollie/Stripe # Crypto Recurring Payments Source: https://docs.payreque.st/subscriptions/crypto-recurring-payments Use USDC on Base for subscription billing — customers pay each invoice manually from their crypto wallet # Crypto Recurring Payments Subscriptions can now be paid with **USDC on the Base network**. When a subscription uses crypto as its payment method, an invoice is generated each billing cycle and the customer pays it from their own crypto wallet — directly to your wallet, with no intermediary holding the funds. This is an **invoice-based recurring flow**, not a mandate-based automatic charge. The customer receives an invoice each period and pays it manually with USDC. Crypto subscriptions use the same [FeeSplitting smart contract](/payment-processing/crypto-payments#how-the-feesplitting-contract-works) — 98% goes straight to your wallet, 2% covers the platform fee. ## Why Use Crypto for Subscriptions USDC payments are irreversible once confirmed on-chain. No disputes, no chargeback fees, no refund fraud — even for recurring billing. Crypto works everywhere. No country restrictions, no currency conversion. Anyone with USDC on Base can subscribe — even without a bank account or credit card. The smart contract sends 98% directly to your wallet in the same on-chain transaction. PayRequest never holds your subscription revenue. SEPA mandates or credit card tokens aren't required. Your customer just needs a wallet with USDC on Base — no banking relationship necessary. ## How It Works When creating or editing a subscription, set the payment method to **Crypto (USDC)**. If the customer doesn't have a crypto payment preference yet, you can switch an existing subscription to crypto anytime. On each billing date, PayRequest creates an invoice with the subscription amount and sends it to the customer. The invoice includes a **Pay with Crypto** option — just like a one-time payment. The customer opens the invoice link, selects **Pay with Crypto**, scans the WalletConnect QR code with their wallet app, and confirms the USDC amount. The transaction is signed and sent to the Base network. The FeeSplitting contract splits the payment atomically: 98% goes directly to your wallet, 2% to PayRequest — all in one on-chain transaction. Base confirms it in under a second. The invoice is marked as paid automatically. **No action needed from you.** The entire payment flow — from invoice generation to on-chain confirmation — happens automatically. You'll see the payment reflected in your dashboard and your wallet balance within seconds. ## Setting Up Crypto for a Subscription ### New Subscriptions 1. Create or edit the product and ensure **Crypto (USDC)** is enabled in your [Provider Settings](/payment-processing/crypto-payments#connect-your-wallet) 2. When creating a subscription for a customer, select **Crypto (USDC)** as the payment method 3. Complete the subscription creation — the customer will receive an invoice at the next billing date with a crypto payment option ### Existing Subscriptions 1. Open the subscription detail page 2. Click **Change** next to the current payment method 3. Select **Crypto (USDC)** from the payment method options 4. Save — the next billing cycle will generate a crypto-payable invoice Switching to crypto doesn't affect the current billing period. The change takes effect from the next billing date. Any pending mandate on the subscription stays on file but won't be charged. ## Customer Experience Your customers don't need a bank account or SEPA mandate — just a wallet with USDC on Base. Here's what they see: The invoice email includes a **Pay with Crypto** button alongside any other active payment methods. A WalletConnect QR code appears on the invoice payment page. Customers scan it with MetaMask, Coinbase Wallet, or any WalletConnect-compatible wallet. The exact USDC amount is shown. The customer reviews and confirms the transaction in their wallet. Gas fee is minimal (under \$0.01 on Base). Base confirms the transaction in under 1 second. The invoice updates to paid automatically. The next billing date is calculated normally. ## When to Use Crypto for Subscriptions ### Good Fit For * **International customers** who don't have access to SEPA or iDEAL * **Privacy-conscious customers** who prefer not to share bank details * **High-value subscriptions** where chargeback protection matters * **Digital products and services** with a tech-savvy customer base * **Customers without a bank account** or credit card ### Less Suitable For * **Fully automatic billing** — crypto is invoice-based (customer must manually pay each period) * **Very small amounts** (under \~€5) — the Base gas fee, while minimal, may feel noticeable relative to the invoice total * **Non-crypto-native customers** who may find wallet setup unfamiliar ## Switching Between Crypto and Other Methods You can switch a subscription between crypto and other payment methods at any time: * **Crypto → Automatic (Mandate):** Switch to a SEPA or credit card mandate for hands-off billing * **Crypto → Manual (Bank Transfer):** Send invoices that customers pay via regular bank transfer * **Automatic → Crypto:** Switch to crypto when a mandate expires or the customer prefers wallet payments Switching methods doesn't delete the previous payment configuration. A saved mandate remains on file even when crypto is active, so you can switch back seamlessly. ## Frequently Asked Questions No — crypto payments are **invoice-based**, not mandate-based. Each billing cycle generates an invoice that the customer pays manually from their wallet. This is similar to how manual bank transfer subscriptions work, but with instant on-chain settlement instead of 1–3 day bank delays. Yes. The customer needs a WalletConnect-compatible wallet with USDC on the Base network. Popular options include MetaMask, Coinbase Wallet, and Rabby. See the [supported wallets guide](/payment-processing/crypto-supported-wallets) for details. Yes. If a product has a free trial and the subscription uses crypto as payment method, the trial works normally. When the trial ends, an invoice is generated that the customer can pay with USDC. The invoice remains unpaid. PayRequest handles unpaid invoice management the same way as any other payment method — you can send reminders, apply late fees, or suspend the subscription based on your business rules. No extra fees. The same 2% platform fee applies to each crypto payment, enforced on-chain by the FeeSplitting contract. There are no monthly minimums, no statement fees, and no chargeback fees. Not currently. Each billing cycle requires the customer to approve and sign a new transaction. Most wallets don't support recurring automated transactions. If fully automatic billing is essential, use SEPA Direct Debit or credit card mandates instead. The invoice shows a fixed USDC amount (converted from EUR at the time of invoice creation). The payment page locks this amount — the customer must pay exactly the invoiced USDC amount. Any exchange rate fluctuation between invoice creation and payment doesn't affect the total. Yes! Each subscription has its own payment method setting. A customer could have one subscription on automatic SEPA, another on crypto, and a third on manual bank transfer — all at the same time. ## Related Documentation Full guide to USDC payments on Base — wallet setup, smart contract details, and supported wallets. Overview of all subscription payment methods — automatic, manual, and crypto. How subscriptions work from creation to cancellation. Which wallets work with PayRequest's crypto payment system. # Customer Self-Service Source: https://docs.payreque.st/subscriptions/customer-self-service Configure what subscription actions customers can perform from the customer portal # Customer Self-Service Control which subscription management actions are available to your customers in the customer portal. You can independently enable or disable pausing and canceling per product. Self-service settings are configured per product. Go to **Products** > edit a product > **Customer Portal Actions** to manage these settings. ## Portal Actions Customers can temporarily pause their subscription from the portal. Billing stops until they resume. Customers can request cancellation. Depending on the cancellation mode, this either creates a cancellation request with a notice period or cancels immediately. ## Configuring Per Product Each product has two independent toggles in the **Customer Portal Actions** section: | Setting | What It Controls | Default | | - | - | - | | **Allow Subscription Pause** | Shows/hides the Pause button in the customer portal | Enabled | | **Allow Subscription Cancel** | Shows/hides the Cancel button in the customer portal | Enabled | These toggles work independently — you can allow pausing but not canceling, or vice versa. For high-value subscriptions, consider disabling self-service cancellation and directing customers to contact you directly. You can keep the pause option enabled as a middle ground. ## Cancellation Modes [VPNresellers subscriptions](/integrations/vpnresellers) do not support customer pausing. New VPN products use immediate cancellation, while VPN access remains available until the end of the already-paid period. Credential management and configuration downloads are available to authorized customers in the subscription's **VPN** tab while access is active. When cancellation is enabled, you can choose between two modes: ### Request Mode (Default) The customer submits a cancellation request with a reason and optional message. A support ticket is created, and the subscription remains active during the notice period. This gives you the opportunity to: * Understand why the customer is leaving * Offer alternatives or discounts * Properly wind down linked services (domains, etc.) See [Cancellation Requests](/subscriptions/cancellation-requests) for full details. ### Immediate Mode The subscription is canceled instantly when the customer clicks cancel, after a confirmation prompt. No notice period, no support request. ## What Customers See ### When Both Actions Are Enabled The subscription detail page shows both **Pause Subscription** and **Cancel Subscription** buttons in the actions area. ### When Only Pause Is Enabled Only the **Pause Subscription** button appears. Customers who want to cancel need to contact you through support. ### When Only Cancel Is Enabled Only the **Cancel Subscription** button appears. ### When Both Are Disabled No self-service action buttons are shown. Customers must contact support for any subscription changes. ## Next Steps Set up notice periods and reason collection for cancellations Learn how subscription pausing works Overview of the full customer portal experience Manage customer communications and cancellation requests # Failed Payment Handling Source: https://docs.payreque.st/subscriptions/failed-payment-handling How PayRequest automatically handles failed subscription payments and chargebacks # Failed Payment Handling PayRequest automatically handles failed subscription payments and chargebacks to help you recover revenue without manual intervention. ## How Automatic Retries Work When a subscription payment fails (due to insufficient funds, expired card, or chargeback), PayRequest automatically schedules retry attempts. ### Retry Schedule * **First Retry**: 3 days after the failed payment * **Second Retry**: 10 days after the failed payment * **Default Maximum**: 2 retry attempts (configurable per subscription) Your billing schedule stays the same. Retries don't affect your regular monthly billing dates. ## What Triggers a Retry? PayRequest creates automatic retry attempts for specific failure reasons: * **Insufficient Funds (AM04)**: Not enough money in customer's bank account * **Multiple Reasons (MS03)**: Can indicate insufficient funds or similar recoverable issues * **Payment Method Error**: Temporary payment processing issues Not all chargebacks trigger retries. Fraud, customer disputes, or irreversible chargebacks will mark the subscription as "Payment Failed" without scheduling retries. ## Viewing Retry Status On the **subscription detail page**, you'll see a **Payment Retry Status** card when there are failed payments. The same retry information also appears on the **invoice detail page** when an invoice has chargeback status, so you can see the full picture without navigating between pages. The retry card shows: * **Failed Attempts**: Current failures vs maximum allowed (e.g., "1 / 2") * **Last Failure**: When the most recent failure occurred * **Next Retry Scheduled**: When the next automatic retry will happen * **Retry History**: Complete timeline of all retry attempts ## Retry History The retry history shows every attempt with: * Attempt number * Date and time * Status (Chargeback, Pending, Paid) * Failure reason (e.g., "Insufficient funds") * Amount This gives you full visibility into payment recovery efforts. ## Configuring Retry Attempts You can customize the maximum number of retry attempts per subscription: 1. Go to **Subscriptions** in your dashboard 2. Click on a subscription 3. Navigate to the **Settings** tab 4. Change **Max Retry Attempts** (1-5 attempts) 5. Click **Save Changes** For high-value subscriptions, consider increasing retry attempts to 3-4 for better recovery rates. ## What Happens After Max Retries? When all retry attempts are exhausted: * Subscription status changes to **Payment Failed** * You'll see a warning: "Max retry attempts reached - Subscription requires attention" * No further automatic retries will occur * You can manually contact the customer or cancel the subscription ## Understanding Billing vs Retry Dates Retries don't change your regular billing schedule. ### Example Timeline Let's say you have a monthly subscription that bills on the 5th of each month: | Date | Event | Billing Date | | - | - | - | | **Sept 5** | Regular monthly billing | Next: Oct 5 | | **Sept 11** | Chargeback received | Next: Oct 5 ✓ | | **Sept 14** | First retry attempt (3 days later) | Next: Oct 5 ✓ | | **Sept 21** | Second retry attempt (10 days after failure) | Next: Oct 5 ✓ | | **Oct 5** | Next regular billing as scheduled | Next: Nov 5 | Your regular billing dates remain unchanged regardless of retry attempts. ## When the Retry Payment is Successful Once a retry payment is confirmed: * **Failed Attempts**: Reset to 0 * **Retry Fields**: Cleared automatically * **Subscription Status**: Returns to "Active" * **Retry Card**: Hidden (no active failures) * **Next Billing**: Remains on original schedule The subscription continues normally from the next scheduled billing date. ## Chargebacks When a customer disputes a payment through their bank: 1. PayRequest receives the chargeback notification 2. Invoice status changes to **Chargeback** 3. Subscription is marked with a failed attempt 4. System checks the chargeback reason code: * **AM04 / MS03** (Insufficient funds) → Automatic retry scheduled (3 days later) * **Other reasons** (Fraud, dispute, etc.) → Subscription marked "Payment Failed" without retry 5. You're notified in your activity log Only chargebacks with recoverable reasons (insufficient funds) are automatically retried. Fraud or customer disputes require manual intervention. ## Notifications You'll be notified when: * A payment fails or is charged back * A retry attempt is scheduled * All retry attempts are exhausted * A retry payment is successful Check your **Activity Log** for complete payment recovery tracking. ## Best Practices * **Standard subscriptions**: 2 retries * **High-value subscriptions**: 3-4 retries * **Annual subscriptions**: 4-5 retries Check subscriptions with active retries weekly to: * Identify patterns (same customer, same failure reason) * Reach out to customers proactively * Update payment methods before max retries If the first retry fails, consider: * Sending a friendly reminder email * Asking them to update their payment method * Offering alternative payment options For subscriptions that exhausted all retries: * Contact the customer directly * Offer a manual payment link * Consider pausing instead of canceling ## FAQs No. Each retry is a separate payment attempt. The customer is only charged once when a payment succeeds. Yes. Go to the subscription detail page and click "Process Payment" to create an immediate payment attempt. The next scheduled retry will automatically use the updated payment method. No. Retry attempts are included in PayRequest at no additional cost. Yes. Set "Max Retry Attempts" to 0 in the subscription settings to disable automatic retries. If the subscription was canceled before the retry, the retry will not be attempted. ## Related Articles * [Managing Mandates](/subscriptions/managing-mandates) * [Subscription Lifecycle](/subscriptions/subscription-lifecycle) * [Handling Chargebacks](/payment-processing/handling-chargebacks) * [Customer Self-Service](/subscriptions/customer-self-service) # Managing Mandates Source: https://docs.payreque.st/subscriptions/managing-mandates Set up and manage SEPA Direct Debit authorizations for automatic subscription payments ## Overview A mandate is a payment authorization that allows you to automatically collect payments from a customer's bank account. PayRequest uses SEPA Direct Debit mandates via Mollie to enable automatic subscription billing without requiring customer action each billing cycle. Mandates are the foundation of automated subscription billing. Once a customer authorizes a mandate, you can collect payments automatically - no payment links, no waiting. ## How Mandates Work ### The Authorization Flow 1. **Customer receives email** with mandate authorization link 2. **Customer clicks link** and lands on Mollie's secure payment page 3. **Customer completes authorization** via iDEAL (creates SEPA mandate) or enters card details 4. **Mandate created** in Mollie, linked to customer 5. **Subscription activated** - automatic payments enabled ### Mandate Types PayRequest supports mandates created via: | Payment Method | Mandate Type | Speed | Fees | | - | - | - | - | | **iDEAL** | SEPA Direct Debit | 1-3 business days | Lower | | **Credit Card** | Card recurring | Instant | Higher | | **Bancontact** | SEPA Direct Debit | 1-3 business days | Lower | iDEAL is the most common method in the Netherlands. When a customer pays with iDEAL, Mollie automatically creates a SEPA mandate from the bank account used. ## Viewing Customer Mandates ### From Customer Profile 1. Go to **Customers** → Select customer 2. View the **Mandates** section 3. See all active and expired mandates ### From Subscription 1. Go to **Subscriptions** → Select subscription 2. View **Mandate** in subscription details 3. Click mandate ID to see details ### Mandate Information Displayed | Field | Description | | - | - | | **Mandate ID** | Mollie mandate reference (e.g., `mdt_xxx`) | | **Method** | iDEAL, Credit Card, etc. | | **Status** | Valid, Pending, Invalid | | **Account** | Last 4 digits of bank account (SEPA) | | **Created At** | When mandate was authorized | ## Creating New Mandates ### Method 1: During Subscription Creation When creating a subscription for a customer without an existing mandate: 1. Create subscription with **Payment Method: Mandate** 2. If no mandate exists, email sent automatically to customer 3. Customer completes authorization 4. Subscription changes from "Pending Mandate" to "Active" ### Method 2: Via First Payment Mandates are created automatically when customers make a first payment via: * **Shop checkout** (recurring product purchase) * **Payment page** (first subscription payment) * **Invoice payment** (using iDEAL) ### Method 3: Dedicated Mandate Request Request mandate authorization without creating a subscription: 1. Go to **Customers** → Select customer 2. Click **Request Mandate** 3. Customer receives email with authorization link 4. Once completed, mandate available for future subscriptions ## Mandate Status Lifecycle ``` Customer Notified → Pending → Valid → Used for Payments ↓ Failed/Expired ``` ### Status Definitions | Status | Meaning | Can Bill? | | - | - | - | | **Valid** | Authorization complete, ready to use | ✅ Yes | | **Pending** | Authorization in progress | ❌ No | | **Invalid** | Revoked or failed | ❌ No | | **Expired** | No longer usable | ❌ No | ## Managing Mandate Issues ### Customer Without Mandate **Symptoms:** * Subscription status: "Pending Mandate" * Cannot create mandate-based payments **Solutions:** 1. **Resend authorization email**: * Go to Subscription → Click **Resend Mandate Email** 2. **Switch to manual payment**: * Go to Subscription → Click **Change** next to payment method * Select **Manual Payment** → Save * Customer will receive invoices to pay via bank transfer * See [Payment Methods for Subscriptions](/subscriptions/payment-methods) for details 3. **Contact customer**: * Verify email address is correct * Ask customer to check spam folder ### Mandate Revoked by Customer Customers can revoke mandates through their bank. When this happens: **Impact:** * Next payment attempt fails * Subscription status → "Failed" * No automatic payments possible **Solutions:** 1. Contact customer to understand reason 2. Request new mandate authorization 3. Consider switching to invoice-based billing ### Mandate Revoked by Bank Banks may revoke mandates for: * Account closure * Fraud prevention * Customer request through bank **Detection:** * Payment failure with "mandate revoked" reason * Mandate status changes to "Invalid" **Resolution:** * Contact customer for new mandate * Verify customer's payment details ## Synchronizing Mandates ### Automatic Sync PayRequest automatically syncs mandate status with Mollie: * **Every 8 hours**: Full mandate sync for active customers * **On payment failure**: Immediate mandate status check * **On subscription billing**: Mandate verification before payment ### Manual Sync To manually refresh mandate data: 1. Go to **Settings** → **Payment Providers** 2. Find Mollie provider 3. Click **Sync Mandates** Manual sync is rarely needed. Automatic sync handles most scenarios. ## Customer Portal Mandate Management Customers can manage their mandates through the Customer Portal: ### What Customers Can Do * **View saved payment methods**: See their active mandates * **Add new payment method**: Create additional mandate via new payment * **See mandate details**: View account info (last 4 digits) ### What Customers Cannot Do * **Revoke mandates directly** (must go through bank) * **Edit mandate details** (mandates are immutable) * **Transfer mandates** (tied to specific bank account) ### Enabling Customer Portal Mandate Access Configure in **Shop Settings** → **Customer Portal**: * **Show saved payment methods**: Display mandates to customers * **Allow new payment method**: Let customers add methods ## Mandate Best Practices ### ✅ Do's * **Use iDEAL for Dutch customers** - Creates SEPA mandate automatically * **Send reminders** for pending mandate authorizations * **Monitor "Pending Mandate" subscriptions** - Follow up within 48 hours * **Keep customer contact info updated** - Ensures emails are delivered * **Explain the authorization process** - Customers unfamiliar with mandates may hesitate ### ❌ Don'ts * **Don't create multiple pending mandates** for the same customer * **Don't ignore mandate failures** - They indicate customer or bank issues * **Don't assume mandates last forever** - Monitor for revocations * **Don't use mandates for one-time payments** - Use direct payment instead ## Troubleshooting ### Authorization Email Not Received **Causes:** 1. Incorrect email address 2. Email in spam/junk folder 3. Email delivery failure **Solutions:** * Verify customer email in profile * Ask customer to check spam folder * Resend authorization email * Check email delivery status in logs ### Mandate Authorization Stuck at Pending **Causes:** 1. Customer started but didn't complete authorization 2. Bank verification pending 3. Technical issue during authorization **Solutions:** * Resend authorization email * Contact customer to complete process * Wait 24-48 hours for bank processing * Check Mollie dashboard for status ### Payment Failing Despite Valid Mandate **Causes:** 1. Insufficient funds in customer account 2. Bank temporarily blocking debits 3. Mandate about to be revoked (not yet updated) **Solutions:** * Check Mollie payment failure reason * Contact customer about bank account status * Retry payment after a few days * Request new mandate if issues persist ### Customer Has Multiple Mandates This is normal and expected. Customers may have mandates from: * Different payment methods (iDEAL vs card) * Multiple bank accounts * Previous authorizations **PayRequest behavior:** * Uses most recently created valid mandate * You can select specific mandate when creating subscription ## Technical Details ### Mandate Data Stored PayRequest stores minimal mandate data for efficiency: ``` mandate_id: "mdt_xxxxxxxxxxxxx" customer_id: "cst_xxxxxxxxxxxxx" method: "directdebit" status: "valid" ``` Full mandate details are retrieved from Mollie API when needed. ### Mandate Verification Before Billing Before each billing attempt, PayRequest: 1. Checks mandate status in database 2. Verifies with Mollie API (if billing imminent) 3. Fails gracefully if mandate invalid 4. Updates subscription status accordingly ### Webhook Integration Mandate status changes trigger webhooks: * **Mandate created**: Activates pending subscriptions * **Mandate revoked**: Marks subscriptions for attention * **Mandate expired**: Updates customer records ## SEPA Direct Debit Specifics ### Settlement Timeline | Day | Event | | - | - | | Day 0 | Payment created | | Day 1-2 | Bank processes debit | | Day 2-3 | Payment status → Paid | | Day 3-5 | Funds available in Mollie | SEPA Direct Debits are not instant. Plan for 2-3 business day settlement time. ### Chargeback Window Customers can dispute SEPA Direct Debits: * **8 weeks**: Unconditional refund right for authorized debits * **13 months**: For unauthorized debits (mandate issues) **Impact:** * Chargeback creates negative transaction * Customer may lose access (configure your policy) * Review and contact customer ### Cross-Border Payments SEPA mandates work across the Single Euro Payments Area: **Supported Countries:** All EU countries, plus Iceland, Liechtenstein, Norway, Switzerland, Monaco, San Marino, Andorra, Vatican City. **Limitations:** * EUR currency only (for SEPA Direct Debit) * Some banks may have slower processing ## Related Documentation Switch between automatic and manual payment Set up subscriptions with mandates Handle payment failures Configure Mollie integration ## Frequently Asked Questions SEPA mandates don't expire automatically. They remain valid until revoked by the customer through their bank, or if the bank account is closed. It's good practice to verify mandate status periodically. Yes, customers can have multiple mandates from different payment methods or bank accounts. PayRequest uses the most recently created valid mandate by default, but you can select a specific mandate when creating subscriptions. The next billing attempt will fail, and the subscription status will change to "Failed". You'll need to contact the customer to understand why they revoked and potentially request a new mandate or switch to invoice-based billing. Yes! Mandates are linked to customers, not subscriptions. When creating a new subscription for a customer with an existing valid mandate, that mandate is automatically available for use. Some banks require additional verification after mandate creation. This can take 24-48 hours. Wait and retry, or check Mollie dashboard for specific error messages from the bank. Yes, SEPA mandates work across all SEPA member countries (EU and some additional European countries). However, the mandate must be in EUR currency, and some banks may have slower processing times for cross-border debits. Unfortunately, banks don't notify merchants before mandate revocation. You'll find out when the next payment fails. Regular communication with customers and prompt follow-up on failed payments helps catch issues early. A **mandate** is a standing authorization to collect payments. A **payment method** is how a specific payment is made (iDEAL, card, etc.). When a customer pays with iDEAL, both a payment and a mandate are created. The mandate enables future automatic payments. ## Need Help? Customer payment method management Understand subscription states Configure your payment provider Debug payment issues # Pausing & Resuming Source: https://docs.payreque.st/subscriptions/pausing-and-resuming Temporary subscription holds with optional auto-resume # Pausing & Resuming Pausing a subscription temporarily stops billing without canceling. This is useful when a customer wants to take a break, or when you need to hold billing for a specific period. ## Pausing a Subscription 1. Go to **Subscriptions** and click on the subscription 2. Click **Pause Subscription** in the Subscription Actions card 3. The subscription status changes to **Paused** (blue badge) Billing stops immediately. The customer's payment mandate remains active for when you resume. ### Auto-Resume You can optionally set a **resume date** when pausing. When the date arrives, the subscription automatically returns to Active and billing resumes on the normal schedule. ## Resuming a Subscription 1. Go to the paused subscription's detail page 2. Click **Resume Subscription** 3. The subscription returns to **Active** status Billing resumes from the next scheduled billing date. ## Who Can Pause? Both admins and customers (via the customer portal) can pause subscriptions. The activity log records who initiated the pause. ## Pausing vs. Suspending If you need to halt service because a customer isn't paying, use **Suspension** instead of pausing. Suspension: * Sends the customer an email notification * Shows an orange badge (instead of blue) * Auto-reactivates when the overdue invoice is paid * Appears in the Insights dashboard Action Required section Learn more: [Suspending Subscriptions](/subscriptions/suspending-subscriptions) ## Related Articles * [Subscription Lifecycle](/subscriptions/subscription-lifecycle) * [Suspending Subscriptions](/subscriptions/suspending-subscriptions) * [Customer Self-Service](/subscriptions/customer-self-service) # Payment Methods for Subscriptions Source: https://docs.payreque.st/subscriptions/payment-methods Choose between automatic payments and manual invoicing for each subscription, and switch between them at any time ## Overview Every subscription in PayRequest can be billed in one of two ways: **automatically** via a payment mandate (SEPA Direct Debit or credit card), or **manually** by sending invoices that the customer pays via bank transfer. You can switch between these methods at any time from the subscription detail page. **Automatic payments** are ideal when customers have authorized a mandate — payments are collected without any action needed. **Manual payments** work well for customers who prefer bank transfers, or when no mandate is available. ## Payment Method Options | Method | How It Works | Best For | | - | - | - | | **Automatic Payment** | Customer is charged automatically via their saved mandate (SEPA or credit card) | Recurring SaaS, memberships, ongoing services | | **Manual Payment** | An invoice is generated and emailed each billing period — customer pays via bank transfer | Customers without mandates, large invoices, B2B clients | ## Viewing the Current Payment Method On each subscription detail page, you'll see the current payment method displayed: * **Mandate assigned**: Shows the mandate reference (e.g., `mdt_jLqzL4cB6H`), payment type (Credit Card, SEPA), and status (Valid) * **Manual Payment**: Shows a blue "Manual Payment (Bank Transfer)" label * **No payment method**: Shows a red "No mandate assigned" warning ## Switching Payment Methods You can switch between automatic and manual payment at any time. ### Step 1: Open Payment Method Settings Go to **Subscriptions** → click on the subscription → click **Change** next to the payment method display. This opens the **Manage Payment Method** modal. ### Step 2: Choose Payment Type At the top of the modal, you'll see two options: * **Automatic Payment** — Charge customer automatically via SEPA or credit card mandate * **Manual Payment** — Send invoice each period for customer to pay via bank transfer Select the option you want. ### Step 3: Configure **If switching to Automatic Payment:** 1. Select a mandate from the dropdown list 2. Only valid mandates for this customer are shown 3. Review the mandate details (method, status, signature date) 4. Click **Save Payment Method** **If switching to Manual Payment:** 1. No additional configuration needed 2. Review the info box confirming how manual billing works 3. Click **Save Payment Method** When you switch to manual payment, the existing mandate is not deleted — it's just unlinked from this subscription. You can switch back to automatic payment at any time using the same mandate. ### Step 4: Confirm After saving, the subscription detail page updates to reflect the new payment method. An activity log entry is created to track the change. ## How Each Method Affects Billing ### Automatic Payment Billing When a subscription with a mandate reaches its billing date: 1. PayRequest creates a payment via Mollie using the linked mandate 2. The customer's bank account or credit card is charged automatically 3. A transaction is recorded and the invoice is marked as paid 4. Next billing date is calculated based on the interval **No action required** from you or the customer. ### Manual Payment Billing When a subscription without a mandate reaches its billing date: 1. PayRequest generates an invoice for the billing period 2. The invoice is emailed to the customer with a payment link 3. The customer pays via bank transfer, iDEAL, or other available method 4. Once payment is received, the invoice is marked as paid 5. Next billing date is calculated based on the interval With manual payment, there may be a delay between the billing date and when the customer actually pays. Monitor unpaid invoices and send reminders if needed. ## When to Use Each Method ### Use Automatic Payment When: * Customer has authorized a SEPA mandate or saved a credit card * You want hands-off billing with no manual follow-up * Payment reliability is important (e.g., monthly SaaS) * Customer prefers not to pay manually each month ### Use Manual Payment When: * Customer prefers paying via bank transfer * No mandate is available and customer doesn't want to authorize one * Large B2B invoices that require internal approval before payment * Customer wants to review each invoice before paying * You're using the **Allow Manual Payment (Bank Transfer)** product setting ## Manual Payment on Invoices When you manually mark an invoice as paid (for example, after receiving a bank transfer), PayRequest now automatically: 1. **Updates the invoice** status to paid 2. **Updates the linked order** status to completed (if applicable) 3. **Creates a subscription** for recurring products in the order 4. The subscription is set to **active** if the product allows manual payment, or **pending mandate** if automatic payment is expected This means you can accept orders for subscription products via bank transfer — just mark the invoice as paid, and everything is set up automatically. ## Managing Payment Methods in Bulk If you need to switch multiple subscriptions to the same payment method: 1. Go to each subscription's detail page 2. Click **Change** next to the payment method 3. Select the desired method and save Bulk payment method changes are currently done one subscription at a time. This ensures you can verify each change individually. ## Common Scenarios ### Customer Lost Their Mandate **What happened**: The customer's bank revoked their mandate, or their card expired. **Solution**: 1. Open the subscription → **Change** payment method 2. Switch to **Manual Payment** temporarily 3. Send the customer a new mandate request 4. Once they authorize a new mandate, switch back to **Automatic Payment** ### Moving from Manual to Automatic **What happened**: A customer who was paying manually now wants automatic payments. **Solution**: 1. Ensure the customer has a valid mandate (check the mandate dropdown in the modal) 2. If no mandate exists, send a mandate request from the customer profile 3. Once the mandate is valid, open the subscription → **Change** → select **Automatic Payment** → choose the mandate ### Customer Wants Bank Transfer Instead **What happened**: A customer with an active mandate prefers to pay manually. **Solution**: 1. Open the subscription → **Change** payment method 2. Select **Manual Payment** 3. Save — the mandate stays on file but won't be charged for this subscription ## Best Practices ### ✅ Do's * **Start with automatic payments** when possible — it reduces admin work * **Switch to manual** if a customer consistently has payment failures * **Monitor manual payment subscriptions** — follow up on unpaid invoices * **Keep mandates on file** even when using manual payment — easy to switch back ### ❌ Don'ts * **Don't leave subscriptions without any payment method** — either assign a mandate or use manual payment * **Don't forget to check invoice status** for manual payment subscriptions * **Don't switch payment methods** right before a billing date — wait until after billing completes ## Frequently Asked Questions No. The mandate remains valid and on file. It's simply unlinked from this subscription. You can switch back to automatic payment using the same mandate at any time. The change takes effect from the next billing date. If a payment has already been processed for the current period, it won't be affected. Yes! Each subscription has its own payment method setting. A customer could have one subscription on automatic payment and another on manual payment. No automatic notification is sent. If you switch to manual payment, the customer will notice when they receive an invoice instead of being charged automatically. Consider informing them proactively. If no valid mandates exist, you can either: * Use **Manual Payment** and send invoices * Send a **Mandate Request** email so the customer can authorize a new mandate * The customer can also add a payment method through their Customer Portal Yes! When you mark an invoice as paid for an order containing recurring products, PayRequest automatically creates the subscription. If the product allows manual payment, the subscription is set to active. Otherwise, it's set to pending mandate. ## Related Documentation Set up and manage SEPA mandates Configure billing intervals and timing Accept bank transfer payments Handle failed automatic payments # Bulk Price Adjustments Source: https://docs.payreque.st/subscriptions/price-adjustments Apply inflation adjustments and price increases to multiple subscriptions at once with scheduling, rounding, and customer notifications. # Bulk Price Adjustments Adjust subscription prices in bulk to keep up with inflation, cost changes, or new pricing tiers. The price adjustment wizard lets you preview the impact before applying, schedule changes for the future, and notify customers automatically. Bulk price adjustments are available from the **Bulk Actions** page at **Dashboard > Bulk Actions > Subscriptions > Apply Inflation Adjustment**. Increase by percentage, fixed amount, or set a specific new price Round results to the nearest EUR 0.50, EUR 1.00, or EUR 5.00 Apply immediately, on a specific date, or at each subscription's next renewal Built-in Dutch law compliance with 30-day notice and cancellation rights ## How It Works Go to **Bulk Actions** and select **Subscriptions** as the entity type. Choose the subscriptions you want to adjust — either manually or by filtering with tags. Select **Apply Inflation Adjustment** as the action, then configure: * **Increase method** — Percentage, fixed amount, or set specific price * **Rounding** — Optional rounding to keep prices clean * **Price cap** — Optional maximum price after increase * **Schedule** — When the change should take effect * **Customer notification** — Whether to send an email Review the price change preview showing each subscription's current and new price, plus MRR impact cards showing total revenue change. Review the summary and execute. For scheduled changes, the prices will be applied automatically on the configured date. ## Increase Methods Choose how to calculate the new price for each subscription: | Method | Description | Example | | - | - | - | | **Percentage** | Increase by a percentage of the current price | 5.2% on EUR 19.99 = EUR 21.03 | | **Fixed Amount** | Add a fixed euro amount to each subscription | +EUR 2.00 on EUR 19.99 = EUR 21.99 | | **Set Specific Price** | Override all selected subscriptions to one price | Set to EUR 24.99 regardless of current price | ## Rounding Options After calculating the new price, you can apply rounding to keep prices clean: | Option | Direction | Example (EUR 21.37) | | - | - | - | | **Round to nearest EUR 0.50** | Nearest | EUR 21.50 | | **Round to nearest EUR 1.00** | Nearest | EUR 21.00 | | **Round to nearest EUR 5.00** | Nearest | EUR 20.00 | | **Round up to EUR 0.50** | Always up | EUR 21.50 | | **Round up to EUR 1.00** | Always up | EUR 22.00 | | **Round up to EUR 5.00** | Always up | EUR 25.00 | | **Round down to EUR 0.50** | Always down | EUR 21.00 | | **Round down to EUR 1.00** | Always down | EUR 21.00 | | **Round down to EUR 5.00** | Always down | EUR 20.00 | Use **Round up to EUR 1.00** for the cleanest pricing. This avoids awkward amounts like EUR 21.37 and rounds up to EUR 22.00. ## Price Cap Set an optional **Maximum Price Cap** to prevent subscriptions from exceeding a certain amount after the increase. This is useful when you have a mix of price tiers and want to ensure no subscription goes above a specific limit. For example, with a 10% increase and a cap of EUR 50.00, a subscription at EUR 48.00 would increase to EUR 50.00 instead of EUR 52.80. ## Scheduling Options Control when the price change takes effect: | Schedule | Description | Best For | | - | - | - | | **Immediately** | Price updates right away, takes effect on the next billing cycle | Urgent corrections | | **On a Specific Date** | Price changes on a future date you choose | Annual inflation adjustments | | **At Next Renewal** | Each subscription changes at its own next billing date | Customer-friendly rollout | Scheduled price increases are processed automatically every day at 04:45 AM (before billing runs at 05:00 AM). This ensures the new price is in place before the next invoice is generated. ## Customer Notifications When enabled, PayRequest automatically sends a price increase notification email to each affected customer. The email includes: * **Current and new price** clearly displayed * **Effective date** of the price change * **Cancellation link** to the customer portal * **Business contact information** ### Dutch Law Compliance Dutch consumer law (ACM guidelines) requires a **minimum 30-day advance notice** for subscription price increases. The notification must include the customer's right to cancel before the increase takes effect. PayRequest helps you stay compliant: * A warning is shown if the scheduled date is less than 30 days away * The notification email automatically includes a cancellation link * Validation checks flag subscriptions with renewals too close to the effective date The email template can be customized from **Settings > Email Templates** under the **Subscription Price Increase** type. Available variables include `{{old_price}}`, `{{new_price}}`, `{{effective_date}}`, and `{{cancel_link}}`. ## MRR Impact Preview Before executing, the validation step shows a full impact analysis: * **Current MRR** — Total monthly recurring revenue from selected subscriptions * **New MRR** — Projected MRR after the price change * **MRR Increase** — Absolute euro increase * **Percentage Change** — Overall percentage impact Each subscription is listed with its current price, new price, and the difference. This lets you spot outliers and verify the changes before applying. The MRR calculation normalizes all billing intervals to monthly. Weekly subscriptions are multiplied by 4.33, quarterly divided by 3, and yearly divided by 12. ## Audit Trail Every bulk price adjustment is recorded in the **Bulk Action History** at the bottom of the Bulk Actions page. The history includes: * Which subscriptions were affected * Old and new prices for each subscription * The increase method, value, and rounding used * Whether it was applied immediately or scheduled * Whether customer notifications were sent Immediately applied changes cannot be automatically reversed. You can use the bulk action again with a decrease (negative fixed amount or lower set price) to revert. Scheduled increases that haven't been applied yet can be found in the database and cancelled. Scheduled increases are automatically skipped for subscriptions that are no longer active. The increase status is set to "cancelled" and no change is applied. The bulk action applies the same rate to all selected subscriptions. To apply different rates, run the wizard multiple times with different selections and configurations. Use tags to organize subscriptions into groups for easier selection. PayRequest manages its own billing cycle. Price changes update the subscription amount in PayRequest, which is used when generating the next invoice. There is no reverse sync to Mollie subscription objects. ## Next Steps Learn about all available bulk actions Understand how billing intervals work Customize the price increase notification email Organize subscriptions with tags for targeted adjustments # Subscription Lifecycle Source: https://docs.payreque.st/subscriptions/subscription-lifecycle Understand subscription statuses and how they transition # Subscription Lifecycle Every PayRequest subscription moves through a series of statuses during its lifetime. Understanding these statuses helps you manage billing, handle edge cases, and communicate clearly with your customers. ## Subscription Statuses | Status | Color | Description | | - | - | - | | **Pending Mandate** | Amber | Waiting for customer to set up a payment method | | **Trial** | Purple | Free trial period active, no billing yet | | **Active** | Green | Subscription is live and billing normally | | **Paused** | Blue | Temporarily on hold (voluntary), billing stopped | | **Suspended** | Orange | Service halted by admin due to non-payment | | **Failed** | Red | Payment failed, may be retrying automatically | | **Completed** | Emerald | Fixed-term subscription finished all payments | | **Canceled** | Red | Permanently ended, no further billing | | **Archived** | Zinc | Removed from view, hidden from customer portal | ## Status Flow ``` ┌──────────────────┐ │ Pending Mandate │──→ Active ──→ Paused ──→ Active └──────────────────┘ │ ▲ │ │ │ ▼ ├──→ Suspended ─────────┤ Trial ──→ Active │ (auto on payment) │ │ │ ├──→ Failed ─────────────┘ │ (auto retry / manual) │ ├──→ Completed │ └──→ Canceled ``` ## Status Details ### Pending Mandate The subscription has been created but the customer hasn't set up their payment method yet. You can send a mandate activation email from the subscription detail page. **Transitions to:** Active, Trial, Canceled, Failed ### Trial The customer is in a free trial period. No payments are collected during the trial. When the trial ends, the subscription automatically transitions to Active and billing begins. **Transitions to:** Active, Canceled, Expired ### Active The subscription is live. Payments are collected automatically on the billing schedule using the customer's payment mandate. **Transitions to:** Paused, Suspended, Failed, Completed, Canceled, Archived ### Paused A voluntary hold — either requested by the customer or set by the admin. Billing stops while paused. You can optionally set a resume date for automatic reactivation. **Transitions to:** Active, Canceled Learn more: [Pausing & Resuming](/subscriptions/pausing-and-resuming) ### Suspended An admin-initiated hold for customers who aren't paying. Unlike pausing, suspension: * Sends the customer an email notification * Shows an orange badge (distinct from blue "paused") * Auto-reactivates when the overdue invoice is paid via Mollie * Appears in the Insights dashboard Action Required section **Transitions to:** Active (manual or auto on payment), Canceled Learn more: [Suspending Subscriptions](/subscriptions/suspending-subscriptions) ### Failed A payment attempt failed (insufficient funds, expired card, chargeback). PayRequest can automatically retry payments based on your retry settings. **Transitions to:** Active (after successful retry), Suspended, Canceled Learn more: [Failed Payment Handling](/subscriptions/failed-payment-handling) ### Completed For fixed-term subscriptions (payment plans) that have reached their total number of payments. This is a terminal state. ### Canceled The subscription has been permanently ended. No further billing occurs. Canceled subscriptions can be reactivated by an admin if needed. **Transitions to:** Archived ### Archived The subscription has been shelved and is hidden from the customer portal. Used for cleaning up ghost or duplicate subscriptions without deleting data. All linked invoices and transactions are preserved. **Transitions to:** Active (reactivation only) Learn more: [Archiving Subscriptions](/subscriptions/archiving-subscriptions) ## Automatic Transitions Several status changes happen automatically: | Trigger | From | To | | - | - | - | | Trial period ends | Trial | Active | | Payment fails | Active | Failed | | Retry payment succeeds | Failed | Active | | Overdue invoice paid | Suspended | Active | | Resume date reached | Paused | Active | | All payments completed | Active | Completed | ## Billing Behavior by Status | Status | Bills automatically? | Included in MRR? | | - | - | - | | **Active** | Yes | Yes | | **Trial** | No (until trial ends) | No | | **Paused** | No | No | | **Suspended** | No | No | | **Failed** | Retry attempts only | Yes (until canceled) | | **Completed** | No | No | | **Canceled** | No | No | | **Archived** | No | No | ## Related Articles * [Creating Subscriptions](/subscriptions/creating-subscriptions) * [Suspending Subscriptions](/subscriptions/suspending-subscriptions) * [Pausing & Resuming](/subscriptions/pausing-and-resuming) * [Failed Payment Handling](/subscriptions/failed-payment-handling) * [Archiving Subscriptions](/subscriptions/archiving-subscriptions) * [Billing Cycles](/subscriptions/billing-cycles) # Suspending Subscriptions Source: https://docs.payreque.st/subscriptions/suspending-subscriptions Halt service for non-paying customers with automatic reactivation on payment # Suspending Subscriptions Suspension is an admin-initiated status for customers who are not paying. Unlike **pausing** (which is a voluntary hold the customer can request), **suspension** signals that service has been halted due to non-payment and notifies the customer via email. Suspended subscriptions are automatically reactivated when the overdue invoice is paid. No manual action required. ## When to Use Suspension Use suspension when a customer has overdue invoices and you want to: * **Halt their service** (e.g., disable their Google Workspace, hosting, or domain) * **Notify them** that their subscription is on hold due to non-payment * **Track the status** in PayRequest so your team knows what's happening * **Auto-reactivate** once they pay — no manual follow-up needed ### Suspension vs. Pausing vs. Cancellation | Action | Initiated by | Color | Billing | Auto-reactivate | Email sent | | - | - | - | - | - | - | | **Pause** | Customer or admin | Blue | Stops | On resume date | No | | **Suspend** | Admin only | Orange | Stops | On invoice payment | Yes | | **Cancel** | Customer or admin | Red | Stops permanently | No | No | ## How to Suspend a Subscription 1. Go to **Subscriptions** and click on the subscription you want to suspend 2. In the **Subscription Actions** card on the right, click **Suspend Subscription** 3. Optionally enter a reason (e.g., "Non-payment of invoice INV-2026-001") 4. Click **Confirm Suspension** The subscription status changes to **Suspended** (orange badge), and the customer receives an email notification. Suspension only changes the status in PayRequest. You still need to manually disable the actual service (e.g., suspend their Google Workspace account, disable hosting, etc.). PayRequest tracks the status so your team knows what's been suspended. ## What Happens When You Suspend When you suspend a subscription: * **Status** changes from Active to **Suspended** (orange) * **Suspended at** timestamp is recorded * **Suspension reason** is saved (if provided) * **Customer email** is sent with details about the suspension and how to pay * **Activity log** records the suspension * **Billing stops** — the subscription won't be billed while suspended * **Insights dashboard** shows suspended subscriptions in the Action Required section ## Suspended Subscription View On the subscription detail page, you'll see: * An **orange "Suspended" badge** in the header * A **warning callout** showing when it was suspended and the reason * **Unsuspend** and **Cancel** buttons in the actions card * **Suspended At** and **Suspension Reason** in the dates section ## Auto-Reactivation on Payment When the customer pays their overdue invoice through Mollie (iDEAL, credit card, etc.): 1. PayRequest receives the payment webhook 2. The subscription is automatically set back to **Active** 3. `suspended_at` and `suspension_reason` are cleared 4. An activity log entry records the auto-reactivation 5. Billing resumes on the normal schedule You don't need to manually unsuspend — just send the customer their overdue invoice link and let the system handle the rest. ## Manual Unsuspend If you want to reactivate a suspended subscription manually (e.g., the customer paid via bank transfer): 1. Go to the subscription detail page 2. Click **Unsuspend Subscription** 3. The subscription returns to **Active** status immediately ## Suspension Email When a subscription is suspended, the customer receives an email with: * The subscription name and amount due * A notice that their service has been suspended * Instructions to pay the outstanding invoice to restore service * Your business contact information You can customize this email template under **Settings > Email Templates > Subscription Suspended**. Email deduplication prevents the same suspension email from being sent multiple times within a short period. ## Monitoring Suspended Subscriptions ### Subscription Table The subscription list has a dedicated **Suspended** tab (orange) showing all currently suspended subscriptions with a count badge. ### Insights Dashboard The **Action Required** section on the Insights page shows suspended subscriptions as an amber alert item: * Shows the count of suspended subscriptions * Subtitle: "Service halted, awaiting payment" * Click to navigate directly to the suspended subscriptions tab ## Status Transitions Suspended subscriptions can transition to: * **Active** — via manual unsuspend or auto-reactivation on payment * **Canceled** — if you decide to cancel instead of waiting for payment Subscriptions can be suspended from: * **Active** — the most common case * **Failed** — when payment retries have been exhausted ## Best Practices When suspending, include the specific invoice number in the reason field (e.g., "Non-payment of INV-2026-042"). This makes it easy for your team to identify which invoice triggered the suspension. Make sure the customer has received their invoice and payment reminders before suspending. The suspension email tells them to pay, but they need to know where to pay. For long-overdue accounts, consider opening a [debt collection case](/debt-collection/overview) alongside the suspension. This gives you a structured escalation process while the service is suspended. The Action Required section shows suspended subscriptions. Review these weekly to follow up with customers or decide whether to cancel. ## FAQs No. Suspension is admin-only. The customer can only resolve it by paying the overdue invoice, which triggers automatic reactivation. No. Suspended subscriptions are excluded from billing. Billing resumes only after reactivation. You'll need to suspend each subscription individually from its detail page. Yes. Go to **Settings > Email Templates** and edit the "Subscription Suspended" template to match your tone and branding. The subscription will show as "Suspended" in the customer's portal view, but they can still access the portal and pay invoices. ## Related Articles * [Subscription Lifecycle](/subscriptions/subscription-lifecycle) * [Pausing & Resuming](/subscriptions/pausing-and-resuming) * [Failed Payment Handling](/subscriptions/failed-payment-handling) * [Debt Collection Overview](/debt-collection/overview) * [Business Insights Dashboard](/analytics-and-reporting/insights-dashboard) # Sync Product Changes Source: https://docs.payreque.st/subscriptions/sync-product-changes Understand what happens to existing subscriptions when you edit a product, and how to selectively sync custom field changes. # Sync Product Changes When you edit a product, PayRequest does **not** automatically change any existing subscriptions built from that product. Prices and custom fields are captured on the subscription at the moment it's created — editing the product afterward only affects *new* subscriptions going forward. Existing subscriptions are never silently changed by a product edit. If you need to update existing subscribers, use one of the tools below — both require you to explicitly opt in. ## What Gets Captured at Creation The subscription's `recurring_amount` is set once when the subscription is created and stored independently — it does not reference the product's current price. The subscription stores its own copy of the product's custom field configuration at signup time. ## Updating Prices on Existing Subscriptions Product price changes don't propagate to existing subscriptions automatically. To intentionally change the price on subscriptions that already exist, use the **Bulk Price Adjustments** wizard — see [Bulk Price Adjustments](/subscriptions/price-adjustments) for the full guide covering percentage/fixed/set-price increases, scheduling, rounding, and required customer notice periods. ## Syncing Custom Fields to an Existing Subscription If you add, modify, or remove a custom field on a product, subscriptions created before that change keep their original field configuration. The **Sync with Product** tool on each subscription's detail page lets you review and selectively apply those differences — one subscription at a time. Go to the subscription's detail page. The **Sync with Product** card shows whether it's **In Sync** or **Out of Sync** with the product's current custom field configuration — this is checked automatically every time you load the page. Click **Sync Fields** (or **Check for Updates** if already in sync) to open the sync modal. Each difference is labeled: * **New Field** — exists on the product but not on this subscription * **Modified** — the field exists on both but its configuration differs * **Removed from Product** — exists on this subscription but no longer on the product Check the boxes for the changes you want to apply. New and modified fields are pre-selected by default; removed fields are not. Applying a "Removed" change deletes the field's current value from this subscription. Click to sync the selected fields. Only this subscription is updated. Sync changes apply to **that subscription only** — other subscriptions on the same product are not affected. There is no bulk version of this tool; to sync many subscriptions, you'd repeat this per subscription. ## FAQ No. The new price only applies to subscriptions created after the change. To update existing subscriptions, use [Bulk Price Adjustments](/subscriptions/price-adjustments). No. Use the **Sync with Product** tool on each subscription's detail page to add it manually. Not currently — the Sync with Product tool works one subscription at a time from that subscription's detail page. Applying a "Removed from Product" change deletes that field's value from the subscription along with its configuration. The sync modal shows a warning with the current value before you confirm. ## Next Steps Push price changes to existing subscriptions in bulk Learn how custom fields work on products Understand subscription statuses and billing # Common Issues Source: https://docs.payreque.st/troubleshooting/common-issues Quick fixes for frequent problems # Common Issues Quick answers to problems that come up often. For anything more specific, use the other troubleshooting pages linked below. ## Shop Shows "Vacation Mode" / Customers Can't Order If your shop displays a vacation message and blocks new orders, **Vacation Mode** is turned on in **Shop Settings**. While it's active, customers can't place new orders through your shop or direct payment links. * Toggle it off from **Shop Settings → Vacation Mode** * If you set an end date, it turns off automatically on that date — otherwise it stays on until you disable it manually ## Amounts Look Wrong / Wrong Currency Symbol PayRequest displays amounts in your business's preferred currency, set in your business details. If a product or invoice shows an unexpected currency symbol, check the currency configured there rather than assuming a display bug — amounts are stored as decimal values (never in cents), so a mismatch is almost always a currency-setting issue rather than a calculation error. ## Transaction/Subscription Data Looks Out of Date If a transaction, customer, or subscription from Mollie or PayPal isn't showing up or shows a stale status, this is a provider sync issue rather than data loss. See [Sync Problems](/troubleshooting/sync-problems) for the manual sync actions available on each page (Mollie Transactions, Customers, Subscriptions, Chargebacks, and individual transaction/mandate detail pages). ## A Payment Shows as Failed, Canceled, or Expired These are three different outcomes with different causes — see [Payment Failures](/troubleshooting/payment-failures) for how to tell them apart and what to check first (including the per-transaction **Sync with Mollie**/**Sync with PayPal** action). ## Emails to Customers Aren't Arriving Check whether the customer's email address has an active bounce or complaint suppression — see [Email Delivery Issues](/troubleshooting/email-delivery-issues) for how to find and fix it. Use the **Email Issues** filter on the Customers page to spot affected customers quickly. ## Custom Domain Not Working Custom domain setup depends on DNS records propagating correctly at your registrar/DNS provider, which can take time after you first configure it. See [Custom Domains](/shop-and-checkout/custom-domains) for the required DNS setup and how to verify it. ## Subscription Stuck in "Payment Failed" This means all automatic retry attempts were exhausted. See [Failed Payment Handling](/subscriptions/failed-payment-handling) for the retry schedule, what triggers a retry vs. not, and how to manually reprocess a payment from the subscription detail page. ## FAQ Most changes in PayRequest save immediately. If something provider-synced (a Mollie/PayPal transaction, customer, or subscription) looks stale, it's a sync timing issue — see [Sync Problems](/troubleshooting/sync-problems) for the manual sync action on that specific page. Use your support channel to report it with as much detail as possible: the exact page, what you expected vs. what happened, and (if relevant) the customer/transaction/invoice ID involved. ## Next Steps Fix provider data that looks out of date Diagnose declined or stuck payments Fix bounced or undelivered customer emails DNS setup for your shop or payment page domain # Email Delivery Issues Source: https://docs.payreque.st/troubleshooting/email-delivery-issues Diagnose and fix email bounces, spam complaints, and delivery failures in PayRequest # Email Delivery Issues When emails fail to reach your customers, PayRequest's bounce suppression system kicks in to protect your sender reputation. This guide helps you understand why emails bounce and how to resolve delivery problems. PayRequest uses [Resend](https://resend.com) for email delivery and automatically tracks bounces, complaints, and failures via webhooks. *** ## Common Bounce Reasons | Error Message | Meaning | Fix | | - | - | - | | `550 5.1.1 ... does not exist` | Email address doesn't exist | Ask the customer for their correct email and update it | | `550 5.2.1 ... mailbox full` | Recipient's mailbox is full | Wait and retry later, or contact the customer via other channels | | `421 ... temporarily unavailable` | Server is temporarily down | Usually auto-resolves — the **Failed** status will clear on next successful delivery | | `User marked as spam` | Customer clicked "Report Spam" | Contact the customer directly to resolve; they may need to whitelist your address | *** ## How to Fix a Bounced Customer Navigate to **Customers** and click the affected customer. A red **Email Delivery Blocked** warning appears at the top. The warning shows the bounce type, date, and SMTP error message. Use this to determine whether the email is permanently invalid or temporarily unreachable. If the address is wrong, click **Edit Customer** and enter the correct email. This automatically clears the suppression and removes any "Invalid Email" tags. If the email address is correct (e.g., a temporary issue was resolved), click **Clear Suppression** to resume sending. *** ## Finding Affected Customers Use the **Email Issues** filter on the customer list to quickly find all customers with active bounce or complaint issues: 1. Go to the **Customers** page 2. Open the **Status** filter dropdown 3. Select **Email Issues** (only appears when issues exist) 4. Customers with active suppression show a red **Bounced** badge *** ## Preventing Bounces Set up the **Email Bounce → Add Invalid Email Tag** automation in your automations settings. This automatically tags customers when their email bounces, making them easy to find and fix in bulk. * **Validate emails at entry** — Use proper email validation on your shop checkout and customer forms * **Monitor the Email Issues filter** regularly to catch and fix bounce issues early * **Keep contact info updated** — Ask customers to confirm their email when they log into the portal *** ## Delivery Confirmation PayRequest tracks when Resend confirms delivery of invoice reminders. Look for the green **Email Delivered** event in the invoice timeline to verify a reminder reached the customer. If a reminder shows as sent but never shows a delivery confirmation, the email may have been silently dropped by the recipient's mail server (e.g., caught by a spam filter without generating a bounce). *** ## Next Steps Full guide to the bounce suppression system Configure automatic reminder schedules # Payment Failures Source: https://docs.payreque.st/troubleshooting/payment-failures Debugging declined payments # Payment Failures When a payment doesn't go through, the first step is figuring out which of PayRequest's status buckets it landed in — that tells you whether it's worth retrying, whether the customer needs to act, or whether it's already handled automatically. This page is about diagnosing a single failed payment as a merchant. For automatic retry behavior on **subscriptions**, see [Failed Payment Handling](/subscriptions/failed-payment-handling) — that page covers the retry schedule and chargeback reason codes in detail and isn't repeated here. ## Reading the Status Transactions and Mollie payments use a small set of statuses. On the **Transactions** page or a transaction's detail view, look for: | Status | Meaning | | - | - | | **Paid** | Payment completed successfully | | **Pending** | Payment is initiated but not yet confirmed (e.g. bank transfer in progress) | | **Open** | Checkout was started but not yet completed by the customer | | **Failed** | The payment attempt was declined or errored | | **Canceled** | The customer (or you) canceled the payment before completion | | **Expired** | The checkout session timed out before the customer completed it | | **Refunded** | Payment was completed and later refunded | **Failed**, **Canceled**, and **Expired** are all "didn't result in money" outcomes, but they mean different things: Failed usually means the payment method itself was declined (e.g. by the customer's bank or card issuer); Canceled means someone actively backed out; Expired means the customer simply never finished the checkout session in time. ## Diagnosing a Specific Payment Find it under **Transactions**, or from the related customer/invoice/order. The detail view shows `Failed Date` or `Canceled Date` where applicable, alongside the payment method used. Mollie-based transactions have a **Sync with Mollie** action on their detail page that re-fetches the latest status directly from Mollie — useful if you suspect PayRequest's copy hasn't caught up yet. PayPal transactions have an equivalent **Sync with PayPal** action. One failed payment from one customer is usually just a declined card or an abandoned checkout. Multiple failures across different customers in a short window is more likely a provider-side or configuration issue — check your payment provider's own dashboard/status page. ## Common Causes * **Card declined by the issuing bank** — insufficient funds, fraud flags, or the card being blocked for online/international payments. The customer needs to contact their bank or use a different method. * **iDEAL/bank redirect abandoned** — the customer started the bank redirect flow but didn't complete authorization; this typically shows as **Canceled** or **Expired** rather than **Failed**. * **Checkout session expired** — the customer took too long to complete the payment page. * **Chargeback/dispute on a subscription payment** — handled by the automatic retry system; see [Failed Payment Handling](/subscriptions/failed-payment-handling). ## Abandoned Checkouts If a customer starts a checkout but never completes it (no payment attempt was even made, so there's no Failed/Canceled transaction at all), that's tracked separately as an abandoned checkout, with optional recovery reminders. See [Checkout Recovery](/shop-and-checkout/checkout-recovery). ## FAQ Use the **Sync with Mollie**/**Sync with PayPal** action on the transaction to pull the latest status directly from the provider — PayRequest's copy may just be behind. If the provider also shows it as failed, the customer's bank likely reversed an authorization that never settled; ask them to check with their bank. Don't do this to "fix" a status — Transaction records should reflect what actually happened at the provider. If you received payment by another means (e.g. a manual bank transfer), record it through the appropriate manual payment flow rather than editing a failed transaction's status. Only for subscriptions, and only for specific recoverable reasons (insufficient funds). One-off payment page or Smart Link payments do not auto-retry — the customer needs to try again. ## Next Steps Automatic retries and chargeback handling for subscriptions Recover abandoned checkouts before they become failed payments When transaction data looks out of date # Performance Tips Source: https://docs.payreque.st/troubleshooting/performance-tips Optimize your account # Performance Tips Most "PayRequest feels slow" reports come down to working with large lists one row at a time. These are practical habits — not code-level tuning — for keeping your dashboard fast and your workflow efficient as your customer, product, and transaction counts grow. ## Use Tags to Narrow Down Large Lists Rather than scrolling through hundreds of customers, subscriptions, or products, tag records into meaningful groups (e.g. "Enterprise", "Annual Review", "Legacy Pricing") and filter by tag. This is faster to work with and makes [Bulk Actions](/organization-and-automation/bulk-operations) selection much quicker too, since tag filters support AND/OR logic. ## Use Bulk Actions Instead of One-by-One Edits If you're about to make the same change to more than a handful of records — a price adjustment, a status change, a tag — do it once through [Bulk Actions](/organization-and-automation/bulk-operations) rather than opening each record individually. It's faster for you and produces a single auditable entry in the action history instead of dozens of individual edits. ## Export Instead of Browsing Thousands of Rows For analysis, reporting, or just reviewing large volumes of data, export to CSV via [Export Functions](/analytics-and-reporting/export-functions) and work in a spreadsheet. Paging through thousands of dashboard rows is slower than filtering/sorting the same data locally once it's exported. ## Search and Filter Rather Than Scroll List pages (Transactions, Customers, Products) support search and status/method filters — use them instead of paging through results manually, especially on accounts with a long transaction history. ## Keep Automations and Tags Purposeful A very large number of tags or automation rules can make the dashboard itself harder to navigate (not technically slower, just noisier). Periodically review and retire tags/automations you no longer use. ## FAQ Large datasets naturally take more time to query and render than small ones. Using the built-in search/filter to narrow what's displayed, or exporting to CSV for offline analysis, is usually faster than scrolling through everything. There's no documented hard limit tied to your plan tier for these — if you're operating at a scale where dashboard performance is a real bottleneck, contact support so we can look at your specific account. Not meaningfully on its own, but an unwieldy tag list makes tag-based selection slower to use effectively. Keep tags purposeful and periodically prune ones you no longer need. ## Next Steps Make mass changes instead of editing records one at a time Organize large datasets for faster filtering Work with large datasets offline # Sync Problems Source: https://docs.payreque.st/troubleshooting/sync-problems Resolving data synchronization # Sync Problems PayRequest keeps a local copy of data from connected providers (Mollie, PayPal) so your dashboard loads fast. Most of the time this happens automatically in the background, but if something looks out of date — a transaction stuck as "pending" when it was actually paid, or a subscription missing from your list — most areas that pull from an external provider have a manual sync action you can trigger yourself. Sync problems are almost always about one connected provider's data lagging behind, not about PayRequest's own core records (invoices, customers, orders), which are updated directly and don't need "syncing." ## Signs You Might Have a Sync Problem * A transaction's status in PayRequest doesn't match what you see in your Mollie or PayPal dashboard * The Transactions page shows a **"Sync gap detected"** banner * A subscription, customer, or mandate that exists in your provider account doesn't show up in PayRequest ## Manual Sync Actions These are available directly on the relevant page: | Where | Action | What it does | | - | - | - | | **Mollie Transactions** page | **Fill Gap** | Appears when a gap is detected between your last full sync and your most recent transactions; re-syncs the missing range | | **Mollie Transactions** page | **Reset Sync** | Clears a sync that appears stuck, so you can retry | | A single transaction's detail page | **Sync with Mollie** / **Sync with PayPal** | Re-fetches that one transaction's current status directly from the provider | | **Mollie Customers** page | **Sync Customers** | Pulls customer records from Mollie | | **Mollie Subscriptions** page | **Sync Subscriptions** | Pulls subscription records from Mollie | | **Mollie Chargebacks** page | **Sync Chargebacks** | Pulls chargeback records from Mollie | | A mandate's detail page | **Re-Sync Mandate** | Re-fetches that mandate's current status from Mollie | | Mollie connection settings | **Sync Now** | Kicks off a background sync of your Mollie customers after (re)connecting | If the **Mollie Transactions** page shows "Sync in progress," it's importing transactions in the background and will update automatically — you don't need to do anything unless it looks stuck, in which case use **Reset Sync**. ## The "Sync Gap Detected" Banner This appears on the Mollie Transactions page when PayRequest notices your last full sync happened a while ago, but you have transactions from more recently than that — meaning there could be transactions in between that were never pulled in. Click **Fill Gap** to sync that specific date range. ## Why Sync Can Lag * The webhook from your provider didn't arrive or was delayed (see [Webhook Configuration](/organization-and-automation/webhook-configuration) if you're troubleshooting your own outgoing webhook — this is about PayRequest's *incoming* sync with Mollie/PayPal, which is separate) * A background sync job is still running for a large account * The provider connection needs to be re-authorized (check your provider connection status in Settings) ## FAQ Give it a minute — most syncs run in the background and the page updates once complete. If a transaction-level sync (e.g. "Sync with Mollie") still shows stale data after that, double-check the same payment's status directly in your Mollie dashboard; if Mollie itself shows the old status, PayRequest is correctly reflecting it. Use **Fill Gap** when you suspect specific transactions are missing (the gap banner will tell you this). Use **Reset Sync** only if a sync appears stuck/in-progress for an unreasonably long time and you need to clear it before retrying. No — your provider (Mollie/PayPal) remains the source of truth for what actually happened with a payment. A sync problem just means PayRequest's local copy hasn't caught up yet; running the relevant sync action pulls the current state back in. ## Next Steps Diagnose a specific declined or stuck payment Your own outgoing payment notifications, separate from provider sync