# PayRequest > This file is very large and may be truncated. For an index of this content, please refer to https://docs.payreque.st/llms.txt instead. > Practical guides for businesses, customers and developers using PayRequest. # Bulk Data Operations Source: https://docs.payreque.st/advanced-features/bulk-data-operations Import/export workflows # Bulk Data Operations "Bulk data operations" in PayRequest today means two things: mass-updating existing records with **Bulk Actions**, and pulling records out to CSV with **Export**. Both live in the same place and share the same selection tools. > [!NOTE] > > There is currently no CSV **import** tool for creating customers, products, invoices, or orders in bulk — records are created individually or through the checkout/API flow. If you need to migrate a large dataset into PayRequest, contact support. ## Where to Find It Go to **Dashboard → Bulk Actions** (`/bulk`). From there you can: * Select items manually, or filter by tag with AND/OR logic * Apply a mass action (price adjustments, pause/resume/cancel subscriptions, tag changes, status updates, and more depending on entity type) * Export the selected items to CSV For the full list of supported actions per entity, see [Bulk Operations](/organization-and-automation/bulk-operations). For CSV export details (columns, filters, file naming), see [Export Functions](/analytics-and-reporting/export-functions). ## Working With Larger Datasets > [!TIP] > > Use tags to segment large datasets before running a bulk action. Tagging a group first (e.g. "Q3 Price Review") lets you select exactly the right records with AND/OR tag logic instead of paging through everything manually. * Every bulk action is validated before it runs — errors block execution, warnings let you proceed with caution * Every action is logged in the Bulk Actions history with the entity type, action, item count, and result, so large changes stay auditable * For read-only analysis of large datasets, export to CSV and work in a spreadsheet rather than paging through the dashboard ## FAQ > [accordion] Can I bulk-import customers or products from a CSV? > > Not today. PayRequest doesn't have a self-service CSV import tool for customers, products, invoices, or orders. If you're migrating from another platform, reach out to support. > [accordion] What's the difference between this page and Bulk Operations / Export Functions? > > They're the same feature described from different angles. This page is a quick pointer; [Bulk Operations](/organization-and-automation/bulk-operations) covers every mass-update action in detail, and [Export Functions](/analytics-and-reporting/export-functions) covers CSV export specifically. > [accordion] Is there an API for bulk data operations? > > You can read and write records programmatically via the [API](/api/overview), which is often a better fit for scripted, recurring, or large-scale data operations than the dashboard UI. ## Next Steps > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > Full list of mass actions by entity type > [card] [Export Functions](/analytics-and-reporting/export-functions) > > CSV export details and column reference # Custom CSS Source: https://docs.payreque.st/advanced-features/custom-css Shop styling and branding # Custom CSS PayRequest doesn't currently offer a free-form CSS editor for your shop or payment pages. Instead, branding is handled through a set of built-in controls: your logo, an accent color, and a library of preset page themes — no CSS knowledge required, and nothing that can break your checkout layout. > [!NOTE] > > If you were looking for a way to inject your own stylesheet, that isn't available today. This page documents the styling controls that do exist. ## Logo Upload your shop logo from **Shop Settings**. It's used across your storefront and (via your business details) on invoices. ## Accent Color Set an accent color in **Shop Settings** to tint buttons and highlights across your storefront to match your brand. ## Page Themes PayRequest Pages support a set of preset visual themes that change the page background and card styling, layered on top of your accent color. Pick a theme from the **Page Theme** picker when editing a PayRequest Page. | Theme | Notes | | - | - | | Default | Standard dark PayRequest look | | Solana | Free for all accounts | | Crypto Native | Free for all accounts | | Neon Pop | Premium | | Minimal Light | Premium — light background | | Midnight Glass | Premium | | Cyber Arcade | Premium | | Fintech Trust | Premium | | Zen Earth | Premium — light background | > [!NOTE] > > Most themes use a dark background; **Minimal Light** and **Zen Earth** use a light background instead. Premium themes require a Premium (or higher) subscription — see [PayRequest Plans](/business-settings/payrequest-plans) for what's included in each plan. ## FAQ > [accordion] Can I write my own CSS for my shop or payment page? > > Not currently. Styling is limited to logo, accent color, and the preset theme library above. If custom CSS is important for your use case, let support know — it helps prioritize the roadmap. > [accordion] Do themes apply to the customer portal (account/login area) too? > > Page themes apply to PayRequest Pages. Check your specific page in the dashboard to confirm how a theme renders across its different states before relying on it for a launch. > [accordion] Will a theme change affect my checkout functionality? > > No — themes only affect visual styling (background and card appearance). Your product listings, forms, and payment flow behave the same regardless of theme. ## Next Steps > [card] [Shop & Checkout](/shop-and-checkout/custom-domains) > > Pair your branding with a custom domain > [card] [PayRequest Plans](/business-settings/payrequest-plans) > > See which plan unlocks Premium themes # JavaScript Snippets Source: https://docs.payreque.st/advanced-features/javascript-snippets Advanced tracking and customization # JavaScript Snippets PayRequest doesn't have a general-purpose custom JavaScript field (no place to paste in Google Analytics, Meta Pixel, or a custom tracking script that runs on your shop or payment pages). What does exist today is a copy-paste **embed snippet** for Smart Links, which puts a "buy button" on your own website. > [!NOTE] > > If you're looking for third-party analytics/tracking injection on your PayRequest Page or shop, that isn't available yet. This page covers the embeddable Smart Link button, which is the closest existing feature. ## Embeddable Buy Buttons Every [Smart Link](/payment-processing/smart-links) can generate an embed snippet — a small HTML block (a stylesheet link plus a styled `` button) that you paste into your own website to link straight to that Smart Link's checkout. **1. Open a Smart Link** Go to **Smart Links**, and open the one you want to embed. **2. Find the embed section** Scroll to **Embed button on your website**. **3. Pick a style** Choose between **Default**, **Dark**, or **Outline** button styles. **4. Copy the snippet** Click to copy — it's a `` tag pulling PayRequest's button stylesheet plus an `` tag styled as a button, linking to your Smart Link URL. **5. Paste it into your site** Drop the snippet into your website's HTML wherever you want the buy button to appear. > [!NOTE] > > This is a plain HTML link styled as a button — there's no JavaScript to configure, and nothing to maintain beyond pasting the snippet once. If you change the Smart Link's price or product later, the embedded button keeps working since it just links to the Smart Link URL. ## Tracking Conversions Elsewhere Since there's no native pixel/analytics field, two practical options if you need to track conversions from PayRequest payments on your own site or ad platform: * **Webhooks**: Use the [`payment.succeeded` webhook](/organization-and-automation/webhook-configuration) to fire your own server-side conversion event when a payment completes. * **On-success redirect**: Some Smart Link configurations support an on-success action/URL — if yours redirects to a page on your own domain after payment, you can place tracking scripts on that landing page itself. ## FAQ > [accordion] Can I add Google Analytics or a Facebook Pixel to my PayRequest Page? > > Not as a built-in settings field today. The most reliable way to track conversions is the `payment.succeeded` webhook, handled server-side. > [accordion] Is the embed snippet just a link, or does it load a script? > > It's a stylesheet link plus a plain HTML button/link — no JavaScript executes on your page beyond what your own site already runs. > [accordion] Can I customize the embed button's colors beyond the three preset styles? > > Not currently — Default, Dark, and Outline are the available styles. ## Next Steps > [card] [Smart Links](/payment-processing/smart-links) > > Create and manage the links you can embed > [card] [Webhook Configuration](/organization-and-automation/webhook-configuration) > > Track payments server-side instead of client-side # Webhook Development Source: https://docs.payreque.st/advanced-features/webhook-development Build custom integrations # Webhook Development This page covers developer-facing details for building against PayRequest's webhook — signature verification in more than one language, local testing, and how to build a resilient receiver given the delivery model. Start with [Webhook Configuration](/organization-and-automation/webhook-configuration) first if you haven't set up your webhook URL yet — this page assumes you already have a URL and signing secret configured. > [!NOTE] > > PayRequest currently sends one event, **`payment.succeeded`**, to a single webhook URL per account. Everything below builds on that. ## Signature Verification in Other Languages Every request carries an `X-PayRequest-Signature` header formatted as `sha256={hmac}` — an HMAC-SHA256 of the raw request body, signed with your webhook secret. The PHP example is in [Webhook Configuration](/organization-and-automation/webhook-configuration#verifying-the-signature); here's the same check in Node.js and Python. **Node.js (Express)** ```javascript theme={null} const crypto = require('crypto'); app.post('/webhooks/payrequest', express.raw({ type: 'application/json' }), (req, res) => { const signature = req.headers['x-payrequest-signature'] || ''; const expected = 'sha256=' + crypto .createHmac('sha256', process.env.PAYREQUEST_WEBHOOK_SECRET) .update(req.body) .digest('hex'); const sigBuffer = Buffer.from(signature); const expectedBuffer = Buffer.from(expected); if (sigBuffer.length !== expectedBuffer.length || !crypto.timingSafeEqual(sigBuffer, expectedBuffer)) { return res.status(401).send('Invalid signature'); } const event = JSON.parse(req.body); // handle event.data... res.status(200).send('ok'); }); ``` **Python (Flask)** ```python theme={null} import hashlib import hmac @app.route('/webhooks/payrequest', methods=['POST']) def payrequest_webhook(): signature = request.headers.get('X-PayRequest-Signature', '') expected = 'sha256=' + hmac.new( WEBHOOK_SECRET.encode(), request.data, hashlib.sha256 ).hexdigest() if not hmac.compare_digest(expected, signature): return 'Invalid signature', 401 event = request.get_json() # handle event['data']... return 'ok', 200 ``` > [!WARNING] > > In every language, compare signatures with a constant-time comparison function (`hmac.compare_digest`, `crypto.timingSafeEqual`, PHP's `hash_equals`) — never `==`/`===`, which leaks timing information. ## Idempotency With a single event type today, duplicate-processing risk is lower than on platforms with dozens of event types, but it's still worth guarding against — a network retry on your own infrastructure, a webhook.site relay, or a manual reconciliation script could all deliver the same `payment.succeeded` event more than once. * Use `data.id` (the PayRequest transaction ID) as your idempotency key * Before acting on an event, check whether you've already processed that transaction ID * Because delivery isn't automatically retried by PayRequest (see below), you're more likely to see a *missing* event than a *duplicate* one — but your handler should tolerate both ## Delivery Model (Recap) As covered in [Webhook Configuration](/organization-and-automation/webhook-configuration#delivery-behavior): dispatch is asynchronous via a queued job, requests time out after 10 seconds, and delivery is **best-effort** — there's no automatic retry if your endpoint is down or errors. Don't build an integration that assumes every payment will arrive as a webhook; reconcile periodically against the [API](/api/overview) or dashboard as a safety net, especially for anything revenue-critical. ## Testing Locally There's no built-in test-send button, so the practical way to develop against the webhook is to trigger a real payment (testmode where your provider supports it) and inspect what arrives. **1. Expose your local server** Use [ngrok](https://ngrok.com) (`ngrok http 3000`) or a similar tunnel to get a public HTTPS URL pointing at your local dev server. **2. Or inspect payloads first with webhook.site** Before wiring up real handler code, point your webhook URL at a fresh [webhook.site](https://webhook.site) endpoint to see the exact payload shape and headers PayRequest sends. **3. Set the URL in PayRequest** Go to **Settings → API Tokens**, paste your ngrok or webhook.site URL, and save. **4. Trigger a payment** Complete a real (or testmode) payment against your account and confirm the request arrives, the signature verifies, and your handler processes it correctly. **5. Switch back to your production URL** Remember to update the webhook URL back to your real endpoint before going live — there's only one URL per account, so a URL left pointed at a tunnel or webhook.site stops your production integration from receiving events. ## FAQ > [accordion] Should I process the webhook synchronously or queue it on my end? > > Queue it. Your endpoint has 10 seconds to respond before PayRequest's request times out — do the minimum work needed to acknowledge receipt (verify signature, store/queue the event) and process the business logic asynchronously on your side. > [accordion] Can I filter which events I receive? > > Not currently — there's only one event type (`payment.succeeded`), so there's nothing to filter yet. > [accordion] What should my endpoint return? > > A 2xx status code to acknowledge receipt. Since PayRequest doesn't automatically retry failed deliveries, returning an error won't trigger a redelivery — it will just be logged as failed on PayRequest's side. ## Next Steps > [card] [Webhook Configuration](/organization-and-automation/webhook-configuration) > > Set up your webhook URL and see the full payload reference > [card] [API Reference](/api/overview) > > Reconcile transaction state directly instead of relying solely on webhooks # Application Fee Summary Source: https://docs.payreque.st/analytics-and-reporting/application-fee-summary View your platform fee totals by payment provider, currency, and time period, with euro estimates # Application Fee Summary PayRequest now provides a detailed summary of the platform fees your business earns from payments across multiple payment providers, including Stripe, PayPal, Mollie, and crypto payments. ## What It Shows * **Recorded fees**: Actual platform fees charged and recorded from integrated payment methods. * **Estimated fees**: Calculated fees based on each transaction's amount and the business's fee percentage for cases where recorded fees are not available. * **Breakdown by payment provider (PSP)**: See platform fees separately for Stripe, PayPal, Mollie, crypto, and others. * **Currency and fee kind**: Fees are grouped by currency and whether they are recorded or estimated. * **Time periods**: Fees are summarized for multiple periods including today, yesterday, this week, this month, last month, this year, and lifetime totals. ## How It Works * Data is sourced from your paid transactions, Mollie payments, and completed crypto payments with fees. * Historical Mollie fee data uses saved provider fee amounts. * Recorded and estimated fees are never combined; they are displayed separately. * Crypto payments fees use USDC amounts. ## Euro Cost Estimate * An indicative euro estimate is provided alongside fee totals. * Conversion uses current exchange rates retrieved through the ExchangeRateService. * USDC amounts are treated as proxy USD for conversion. * If a required exchange rate is unavailable or invalid, euro totals will be marked as unavailable. ## Accessing the Summary * The Application Fee Summary is available in the Business Insights Dashboard on the Overview tab. * It displays fee totals for today, yesterday, this week, this month, last month, and this year with a euro estimate. * Clicking on the specific period's fee total links to the detailed Application Fee tab for deeper analysis. ## Use Cases * Quickly monitor the platform fees earned across your payment providers. * Compare fees across time periods and currencies. * Use euro estimates for consolidated financial overviews. ## Limitations * Estimates are indicative and never change actual recorded payments or settlement currency. * Fees are based on paid transaction data; pending or failed payments are excluded. * Exchange rates used for euro estimates are current values and may differ from rates at the time of transactions. ## See Also * [Business Insights Dashboard](/analytics-and-reporting/insights-dashboard) * [Transaction Reports](/analytics-and-reporting/transaction-reports) * [Export Functions](/analytics-and-reporting/export-functions) *** # Bookkeeping Source: https://docs.payreque.st/analytics-and-reporting/bookkeeping Set up your bookkeeping, record sales and purchases, match payments, review Dutch VAT and export reports from PayRequest. Bookkeeping brings your sales invoices, supplier documents, bank transactions and financial reports into a separate workspace in PayRequest. Review each posting before it enters the ledger, then use the reports to understand your business and prepare your quarter-end review. > [!NOTE] > > The current Bookkeeping beta requires a **Business account**. Free access is planned but is not enabled yet. The ledger currently supports **Dutch bookkeeping in EUR using the invoice basis**. A translated interface does not add another country's accounting or tax rules. ## Open the workspace Choose **Bookkeeping** in the PayRequest sidebar, or open [payrequest.app/bookkeeping](https://payrequest.app/bookkeeping). The sidebar link opens a separate tab. The top navigation contains **Overview**, **Bank transactions**, **Purchases**, **Sales** and **VAT overview**. Open **More** for payment matching, quarter review, reports, administration settings, bank accounts, the expense tracker and historical bank VAT. On mobile, use the navigation button. Use the account menu on the right to return to PayRequest or switch between light and dark mode. Access is currently for the account owner; team-member sessions do not have access to this workspace. ## Start your administration Choose your start date and opening balances before posting documents. Opening Bookkeeping does not automatically convert your historical transactions or activate a new ledger. **1. Choose a start date** Open **More → Administration settings**, select your start date and confirm that you use the invoice basis in EUR. Check which earlier periods have already been reported before activating the administration. The activated start date cannot be changed through the settings form. **2. Record the opening balances** Enter debit balances as positive amounts and credit balances as negative amounts. Their total must be exactly zero. Add the source of the opening balance, review the proposed journal and confirm it. For a new business with no assets, liabilities, receivables or bank balances on the start date, explicitly confirm a zero opening balance instead. If that confirmation proves incorrect, revoke it with a reason before recording the opening balances. **3. Bring in the source documents** Review existing sales invoices under **Sales**, add supplier documents under **Purchases**, and match the relevant bank transactions under **More → Match payments**. Only confirmed postings enter the ledger. Older invoices that were still outstanding on the start date can be brought in as opening receivables or payables after explicit confirmation. These opening items do not create new revenue, costs or VAT. Avoid also including the same amounts in an aggregate opening receivables or payables balance. ## Record purchases and evidence Use **Purchases** for supplier invoices and supplier credit notes. A saved draft remains outside the ledger until you review and confirm its posting. 1. Enter the supplier, invoice number, invoice date, received date and document type. 2. Attach the original document, or record a specific location where you retain the external evidence. 3. Add the net amount, VAT treatment, actual VAT amount, deductible percentage and ledger account for each line. 4. Save the draft, then choose **Controleren & boeken** to review it. 5. Check the source, dates, amounts and proposed debit and credit entries. Tick the confirmation and choose **Definitief boeken**. Attachments support PDF, JPG, PNG and WebP, with a maximum of **10 MB per file** and **200 MB of document uploads per administration**. Uploaded evidence is stored privately and can be downloaded from the purchase inbox. The supported purchase treatments are Netherlands 21%, Netherlands 9%, no deductible VAT, and domestic, EU or non-EU reverse charge at 21%. You can also record partial VAT deduction and classify a purchase as a fixed asset. Choose the treatment from the actual supplier document and your circumstances; a supplier name or bank description does not determine it. Purchase posting uses the later of the invoice date and received date. Supplier credit notes reverse the relevant amounts. The purchase inbox displays the latest 100 documents. ## Bring sales invoices into the ledger Open **Sales** to review your existing PayRequest invoices and credit notes. Search by invoice number when you need an older document. The list shows up to 100 invoices not yet imported through the end of the selected quarter. For a supported EUR invoice, review its posting proposal and confirm it. The proposal uses the saved invoice lines, amounts and VAT rather than deriving revenue from a bank payout. For zero-rated lines, choose the relevant supported reporting section. Correct an unsupported rate or inconsistent source total before trying again. > [!NOTE] > > Importing an invoice into Bookkeeping does not send it, change its payment status or trigger service provisioning. A credit note retains its negative amounts. ## Match payments without counting revenue twice Open **More → Match payments** after the relevant sales or purchase documents have been posted. Select a final EUR bank transaction and enter the allocation against the intended invoice postings. * A partial payment can settle part of an outstanding ledger item. * One bank transaction can cover several selected invoice postings when the amounts reconcile. * Enter receipts as positive amounts and outgoing payments as negative amounts. Credit notes use the opposite sign. * The invoice posting must be dated on or before the bank transaction. Advance payments require separate review. ### Record a withheld payment-provider fee Record the fee separately when a provider pays out less than the invoice amount. For example, with a fictional **EUR 121 invoice**, **EUR 3 fee** and **EUR 118 bank receipt**, allocate EUR 121 to the invoice and record EUR 3 as the withheld fee. The payout is not another sale. Enter any actual deductible VAT on the fee separately and provide the cost-invoice reference. If the cost invoice is unavailable, enter zero VAT rather than inferring it from the payout. ### Handle transfers and clearing accounts Other processing options include transfers, owner/private movements, bank costs without VAT, and Mollie, Stripe or PayPal clearing accounts. Add a clear explanation. A transfer or provider payout is not automatically revenue; the underlying documents remain the source for revenue, costs and VAT. Choose **Aansluiting controleren**, review the complete proposal and explicitly confirm the posting. Previews expire after ten minutes. If records change or the preview expires, prepare a fresh proposal. > [!WARNING] > > Bookkeeping matching updates the ledger only. It does **not** mark the original PayRequest invoices paid or stop their reminders. To settle eligible open invoices from a received bank payment, use the separate [Allocate to invoices workflow](https://docs.payreque.st/payment-processing/reconcile-bank-payments). Check existing ledger allocations before recording any further accounting entry. ## Review VAT and close a quarter **VAT overview** shows the VAT figures from confirmed ledger postings for the selected year and quarter. It includes signed credit-note amounts and the corresponding reverse-charge entries where applicable. The dashboard uses the ledger VAT figures after you activate the administration. **More → Historical bank VAT** retains the earlier bank-date report. Do not add the two reports together or assume the historical report proves that a return was submitted. Bank cash flow also includes transfers and is not the same as profit or the balance of your accounts. Open **More → Quarter review** to check unposted sales invoices, purchase drafts, unmatched bank transactions, changed source records, the opening balance and outstanding clearing or transfer balances. Checks cover the period from the administration's start through the selected quarter-end. Resolve the blocking items before preparing the closing preview. Closing requires a completed quarter, no blocking review items, reconciled clearing balances and your explicit confirmation. A saved snapshot and the action history preserve the closing record. > [!NOTE] > > Closing a quarter does not submit a VAT return or initiate a tax payment. Submit the return separately. A clear review list cannot identify documents you have not supplied or guarantee that every tax choice is correct. ## Reports, exports and corrections Open **More → Reports** for the balance sheet, profit and loss, trial balance, current open ledger items, recent journals and action history. | Report or CSV export | Period covered | | - | - | | Journal, profit and loss, VAT sections | Selected quarter | | Balance sheet and trial balance | Cumulative through the selected quarter-end | | Current open items | Current outstanding ledger items across all dates | CSV exports can be shared with your accountant. They are not XAF files, and a dedicated accountant login is not included in this module. To correct a posted entry, add a reason and prepare a reversal in **Reports**. Posted journals are retained rather than edited or deleted. If a document already has bank allocations, reverse those allocations first. A purchase draft can be edited before posting; a reversed purchase can be revised and posted again after review. Closed periods must be reopened with a reason before affected entries can be changed. Reopen later closed quarters first, since closing a quarter also freezes earlier posting dates. Reopening preserves the original snapshot. ## Current scope Bookkeeping currently supports a Dutch administration in EUR using the invoice basis. It does not include payroll, automatic depreciation, multi-currency bookkeeping, cash-basis accounting, XAF export or direct tax filing. The expense tracker and historical bank categories remain separate from confirmed ledger postings. ## Related guides * [Connect and sync your bank with Ponto](https://docs.payreque.st/payment-processing/bank-sync-ponto) * [Allocate a bank payment to invoices](https://docs.payreque.st/payment-processing/reconcile-bank-payments) * [Create invoices](https://docs.payreque.st/invoices/creating-invoices) * [Expense Tracker](https://docs.payreque.st/analytics-and-reporting/expense-tracker) * [PayRequest plans](https://docs.payreque.st/business-settings/payrequest-plans) # Customer Analytics Source: https://docs.payreque.st/analytics-and-reporting/customer-analytics Lifetime value and churn # Customer Analytics Understand which customers matter most, which ones need attention, and which have gone quiet — combining per-customer lifetime value with AI-assisted segmentation via the Billing Agent. ## Per-Customer Lifetime Value Every customer's detail page shows a financial overview calculated from their real payment history: | Metric | How it's calculated | | - | - | | **Total Revenue** | Sum of paid invoices + completed orders for this customer | | **Outstanding Balance** | Sum of unpaid/overdue invoices | > [!NOTE] > > This is a true lifetime-to-date figure based on actual paid transactions — not an estimate or projection. Open any customer from **Customers** in your dashboard to see this breakdown alongside their orders, invoices, and subscriptions. ## AI-Assisted Segmentation (Billing Agent) PayRequest doesn't calculate a single "churn rate" percentage. Instead, the **Billing Agent** (an in-dashboard AI assistant) can find and tag customers matching specific risk or value criteria on demand: > [card] At-Risk Customers > > Customers with an invoice overdue by more than 7 days, or a subscription with a `failed` status. Ask the Billing Agent to "tag at risk" to find and tag them in one step. > [card] Inactive Customers > > Customers with no new invoices, orders, or subscriptions in the last 60 days. Ask "inactive customers" to surface them. > [card] Top Customers > > Customers ranked by total paid invoice revenue — your highest-value relationships. Ask "top customers" to see the list. > [card] Missing Data > > Customers missing an email address, so you can clean up your contact data. Ask "missing email". > [!TIP] > > The Billing Agent responds to natural-language requests — try phrases like "churn risk", "dormant customers", or "highest revenue" and it will match the closest action. ## FAQ > [accordion] Is there a single churn rate metric? > > Not as a standalone percentage today. Use the Billing Agent's "at risk" and "inactive" segments as your churn signal, and act on them by tagging and following up. > [accordion] Does lifetime value include subscription revenue? > > Yes — it's based on paid invoices and completed orders, which includes invoices generated by subscription billing cycles. > [accordion] Can I export a list of at-risk or top customers? > > The Billing Agent can tag matching customers, and tagged customers can then be exported via [Export Functions](/analytics-and-reporting/export-functions) filtered by that tag. ## Next Steps > [card] [Customer Profiles](/customer-management/customer-profiles) > > See the full customer record, including LTV and outstanding balance > [card] [Tags System](/organization-and-automation/tags-system) > > Segment customers with tags for exports and automation > [card] [Export Functions](/analytics-and-reporting/export-functions) > > Export a tagged customer segment to CSV # Daily Business Summary Source: https://docs.payreque.st/analytics-and-reporting/daily-business-summary Receive an automated daily morning email with overnight activity, payments, orders, and key business metrics from the last 24 hours # Daily Business Summary Start every workday with a clear picture of what happened in your business. The Daily Business Summary is an automated email report delivered each morning at 8:00 AM, covering the last 24 hours of activity — including overnight billing jobs, payments, new customers, and your current business health. > [!TIP] > > The Daily Business Summary is **opt-in** — it's disabled by default. Enable it in **Settings → Notifications** under the **Reports & Digests** category. ## What's Included in Your Summary The daily email is organized into four clear sections so you can quickly scan what matters most. ### Overnight Activity Every night, PayRequest runs automated jobs to keep your billing running smoothly. The summary tells you exactly what happened: | Job | What It Tracks | | - | - | | **Subscription Renewals** | How many subscriptions were billed and total revenue collected | | **Renewal Failures** | Subscriptions that failed to renew (payment issues) | | **Trial Conversions** | Free trials that converted to paid subscriptions | | **Invoice Reminders Sent** | Automated payment reminders sent to customers | | **Debt Collection Notices** | Debt collection emails processed | > [!NOTE] > > Overnight jobs run on a fixed schedule: subscription billing at 5:00 AM, trial conversions at 6:00 AM, debt collection at 7:00 AM, and invoice reminders at 9:00 AM. The daily summary is sent at 8:00 AM covering the last 24 hours, so it includes the current night's billing and trial jobs plus yesterday's reminders. The summary includes smart alerts: * **All renewals successful** — a green confirmation so you know everything is healthy * **Renewal failures detected** — a warning with the count, prompting you to check your subscriptions dashboard ### Payments & Revenue A quick snapshot of money flowing through your business: * **Payments Received**: Total number of successful payments * **Revenue**: Total amount collected * **Failed Payments**: Payments that didn't go through * **Chargebacks**: Disputes initiated by customers (count and amount) * **Refunds**: Refunds processed (count and amount) ### Customers & Orders Track your business growth day by day: * **New Customers**: Customers who registered or were added * **New Orders**: Orders placed (with total value) * **New Subscriptions**: Recurring subscriptions started * **Cancelled Subscriptions**: Subscriptions ended by customers ### Current Status A real-time health check of your business at the time the report is generated: * **Active Subscriptions**: Total active recurring subscriptions * **Outstanding Invoices**: Unpaid invoices (count and total amount) * **Overdue Invoices**: Past-due invoices that need attention (count and total amount) > [!WARNING] > > When you have overdue invoices, the summary includes a direct **"View Invoices"** button so you can take action immediately. ## Enabling the Daily Summary The Daily Business Summary is disabled by default. To enable it: 1. Navigate to **Settings** in your dashboard 2. Click on the **Notifications** tab 3. Scroll to the **Reports & Digests** section 4. Toggle **"Daily Business Summary"** to ON > [!TIP] > > You can enable or disable the summary at any time. Changes take effect for the next morning's delivery. ## Delivery Schedule | Detail | Value | | - | - | | **Delivery Time** | 8:00 AM daily | | **Reporting Period** | Last 24 hours | | **Sent To** | Your registered account email | | **Queue** | Processed via the emails queue | ### What the 24-Hour Window Covers Since the email is sent at 8:00 AM, the reporting window runs from **yesterday 8:00 AM to today 8:00 AM**. This means each summary includes: * **Yesterday's daytime**: Customer sign-ups, orders, payments throughout the day * **Last night's jobs**: Subscription billing (5:00 AM), trial conversions (6:00 AM), debt collection (7:00 AM) This ensures you never miss overnight activity in your morning briefing. ## Daily Summary vs Monthly Report PayRequest offers two automated reports that complement each other: | Feature | Daily Business Summary | Monthly Subscription Report | | - | - | - | | **Frequency** | Every day at 8:00 AM | 1st of each month at 8:00 AM | | **Period** | Last 24 hours | Previous calendar month | | **Focus** | Operational overview | Strategic subscription analytics | | **Includes** | Payments, orders, customers, overnight jobs | MRR, ARPU, growth rate, churn rate, top products | | **Best For** | Daily operations monitoring | Monthly business review | | **Default** | Off (opt-in) | On (opt-out) | > [!TIP] > > For the best insights, enable both reports. Use the **Daily Summary** to stay on top of day-to-day operations, and the **Monthly Report** for strategic planning and trend analysis. ## Making the Most of Your Daily Summary ### Morning Routine Spend 2 minutes each morning to: 1. **Check overnight billing**: Were all renewals successful? Any failures to address? 2. **Review payments**: How much revenue came in yesterday? 3. **Spot issues early**: Any chargebacks, refunds, or failed payments? 4. **Track growth**: New customers and orders trending up or down? 5. **Handle overdue invoices**: Click through to follow up on past-due payments ### When to Take Action | Signal | Action | | - | - | | Renewal failures > 0 | Check failed subscriptions, contact customers about payment methods | | Chargebacks received | Review disputed transactions, improve payment descriptions | | Overdue invoices growing | Send manual reminders or enable automated reminders | | No new customers in days | Review marketing efforts, check shop availability | | Failed payments increasing | Investigate payment provider issues | ## Frequently Asked Questions > [accordion] Will I receive a summary on days with no activity? > > Yes. A summary with zero activity is still valuable — it confirms your systems are running and nothing needs attention. The "Current Status" section always shows your live business metrics. > [accordion] Can I receive the summary at a different time? > > Currently, the summary is sent at 8:00 AM (Europe/Amsterdam timezone). This timing is optimized to include overnight billing results (5:00-7:00 AM) while arriving before your workday starts. > [accordion] Does the daily summary affect my email quota? > > The daily summary uses the same email system as all PayRequest emails (Postmark). It counts as one transactional email per day per account. > [accordion] What's the difference between the daily summary and real-time notifications? > > Real-time notifications (like "Payment Received" or "New Order") are sent immediately when events occur. The daily summary is a consolidated overview of everything that happened in the last 24 hours, including background job results that don't trigger individual notifications. > [accordion] Can I customize which sections appear in the summary? > > Currently, all sections are included in every summary. The email is designed to be a quick scan — sections with zero activity take up minimal space. ## Next Steps > [card] [Monthly Subscription Report](/analytics-and-reporting/monthly-subscription-report) > > Enable the monthly report for deeper subscription analytics and strategic insights. > [card] [Insights Dashboard](/analytics-and-reporting/insights-dashboard) > > View real-time business metrics directly in your dashboard. > [card] [Email Automations](/organization-and-automation/email-automations) > > Set up automated emails for customer communication and payment follow-ups. > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > Learn strategies to recover failed subscription payments. *** *The Daily Business Summary keeps you informed without checking your dashboard. Enable it today and never miss what happened overnight.* # Expense Tracker Source: https://docs.payreque.st/analytics-and-reporting/expense-tracker Keep track of your business expenses and see where your money goes each month # Expense Tracker 💳 Never lose track of your business expenses again! The Expense Tracker automatically finds your recurring costs and shows them in a simple calendar view, so you always know what's being charged and when. ## What is the Expense Tracker? For purchase invoices, evidence, VAT, payment matching and financial reports, use the separate [Bookkeeping workspace](https://docs.payreque.st/analytics-and-reporting/bookkeeping). Expense tracking does not replace confirmed ledger postings. Think of it as your automatic expense diary. Once you connect your bank account, PayRequest looks at your transactions and finds things you pay for regularly - like software subscriptions, hosting, and services. No more spreadsheets or manual tracking needed! ### Why You'll Love It > [card] 🤖 Finds Expenses Automatically > > Connect your bank and let PayRequest discover your recurring costs for you. > [card] 📊 See Where Money Goes > > Visual breakdown shows exactly what you're spending on each category. > [card] ⚠️ Spot Price Increases > > Get alerted when a service raises their price so you can decide what to do. > [card] 🏷️ Organize by Category > > Tag expenses like "Marketing" or "Software" to understand your spending better. ## Getting Started ### Opening Your Expense Calendar 1. Click **Expenses** in your dashboard menu 2. You'll see a monthly calendar with all your expenses **What's on the screen:** * 💰 **Summary cards** at the top show your current balance and monthly costs * 📅 **Calendar view** displays all expenses organized by date * 🎨 **Colored cards** show different expense types at a glance > [!TIP] > > You need a **bank connection** (Ponto) for automatic expense detection. Set this up in Settings → Integrations first. ### Understanding the Colors The calendar uses colors to help you see what's happening: * **🟢 Green cards**: Recurring expenses that were paid this month * **🔵 Blue cards**: One-time purchases * **🟠 Orange cards**: Expenses that haven't been paid yet * **🟣 Purple cards**: Multiple expense types on the same day > [!NOTE] > > Click any colored card to see more details about that expense. ## Finding Your Recurring Expenses ### Let PayRequest Do the Work Instead of entering each expense manually, let PayRequest find them for you: 1. Click the **"Detect Recurring Expenses"** button 2. Wait a few seconds while PayRequest scans your bank transactions 3. A summary shows what was found **You'll see:** * How many recurring expenses were found * How many new ones were added * How many existing ones were updated > [!NOTE] > > PayRequest looks at your last 6 months of bank transactions to find patterns. It can even spot when you have multiple subscription tiers for the same service! ### What Gets Detected? PayRequest automatically finds: * 📱 Software subscriptions (Netflix, Spotify, etc.) * 🖥️ Hosting and servers * 📧 Email and marketing services * 💳 Payment processing fees * 🔧 Business tools and licenses * 📊 Analytics and monitoring services > [!TIP] > > Run detection once a month to catch new subscriptions and keep your expense list up to date. ## Adding Expenses Manually If something isn't detected automatically, you can add it yourself: **1. Click 'Add Expense'** Find the button at the top of your expense calendar **2. Fill in the Details** * **Name**: What's the expense? (e.g., "Spotify Premium") * **Amount**: How much does it cost? * **Next Due Date**: When's the next payment? * **Frequency**: Weekly, Monthly, or Yearly? **3. Save** Click "Add Expense" and it appears on your calendar ## Organizing with Tags ### Why Use Tags? Tags help you group expenses by category so you can see: * How much you spend on marketing vs hosting * Which categories are growing over time * Where you might be able to cut costs **Popular categories:** * 🖥️ Hosting * 🛠️ Software & Tools * 📧 Marketing & Ads * 💳 Payment Processing * 📊 Analytics * 🔒 Security ### Tagging an Expense **1. Open the Expense** Click on any expense in your calendar **2. Click the Tag Icon** Look for the 🏷️ icon next to the expense name **3. Choose or Create Tags** * Select from existing tags * Or click "Create New Tag" to add a new category **4. Save** Your tags will appear as colored labels on the expense > [!TIP] > > Create your main expense categories first (Hosting, Marketing, Tools), then tag expenses as you review them. ## Viewing Your Spending Breakdown ### See Where Your Money Goes Click the **"💰 Spending"** button to open your spending analysis. **What you'll see:** * **Total monthly expenses** in one number * **Breakdown by category** with percentages * **Visual bars** showing spending distribution * **Expense counts** for each category **Example:** ``` Your Monthly Spending Total: €1,247.50 🖥️ Hosting €450 (36%) ████████░░ 6 expenses 🛠️ Tools €320 (26%) ██████░░░░ 5 expenses 📧 Marketing €180 (14%) ████░░░░░░ 3 expenses 📊 Analytics €120 (10%) ███░░░░░░░ 2 expenses ``` > [!NOTE] > > This updates automatically as you add or edit expenses, so you always have an accurate picture of your spending. ### Using Spending Insights **Weekly check-in:** * Are you staying within budget? * Any unexpected charges? * New services you forgot about? **Monthly review:** * Which categories are growing? * Where can you optimize costs? * Any subscriptions you don't use anymore? ## Price Increase Alerts ### Automatic Monitoring PayRequest watches your expenses and alerts you when a service increases their price by more than 5%. ### Where You'll See Alerts **1. On the expense itself:** When you click an expense that increased in price, you'll see: ⚠️ **Price Increase Detected (+46%)** This expense increased from **€17** (Aug 1) to **€25** (Oct 1) over **2 months**. **2. In the expense list:** * Orange badge shows the percentage: **"+46%"** * Trending arrow icon appears next to the name **3. Summary alert:** At the top of your expense manager: > ⚠️ **2 expenses with price increases detected** ### What to Do About It When you spot a price increase: 1. **Check your email** for announcements from the service 2. **Review if you still need it** - maybe downgrade to a cheaper plan? 3. **Look at alternatives** - are competitors cheaper now? 4. **Negotiate** - contact them and ask about discounts 5. **Update your budget** to reflect the new cost > [!WARNING] > > Some services like cloud hosting charge based on usage. If you see an "increase", check if you're just using more resources rather than the price actually going up. ## Managing Your Expenses ### Editing an Expense 1. Click on the expense in your calendar OR open "Manage Expenses" 2. Click the ✏️ (pencil) icon 3. Update any information (name, amount, date, frequency) 4. Save your changes ### Deleting an Expense If you cancel a subscription or want to remove something: 1. Open the expense 2. Click the 🗑️ (trash) icon 3. Confirm you want to delete it The expense disappears from your calendar but doesn't affect your bank transactions. ### Viewing All Expenses Click **"Manage Expenses"** to see a complete list of everything you're tracking: * All expense names and amounts * Next payment dates * Categories (tags) * Whether they were auto-detected or manually added This is great for getting an overview or quickly editing multiple expenses. ## Filtering Your View Use the filter buttons to focus on specific expense types: * **All**: Shows everything * **🔁 Recurring**: Only subscription-type expenses (your true monthly burn rate) * **One-time**: Only single purchases > [!TIP] > > Filter to "Recurring" to see your actual monthly costs without one-off purchases cluttering the view. ## Common Questions > [accordion] Why isn't my expense showing up? > > **If automatic detection missed it:** > > * It might be too new (needs at least 2 payments to detect a pattern) > * The merchant name varies too much between charges > * It's a one-time purchase, not recurring > > **Solution:** Just add it manually! Click "Add Expense" and enter the details. > [accordion] An expense shows as unpaid but I know it was charged > > **This usually happens when:** > > * The bank transaction description is different from your expense name > * The amount changed and is outside the matching range > * Your bank sync is delayed > > **Solution:** Edit the expense name to match what shows on your bank statement exactly. > [accordion] I see the same expense twice > > **Why this happens:** > > * PayRequest found different subscription tiers (like Basic and Pro plans) > * You added it manually and then detection also found it > * The service charges on multiple dates > > **Solution:** Go to "Manage Expenses" and delete the duplicate entry. > [accordion] How does PayRequest find expenses automatically? > > PayRequest looks at your bank transactions and finds patterns - things you pay regularly with similar names and amounts. It can even recognize when "DigitalOcean" and "DIGITAL OCEAN INC" are the same service. > [accordion] Can I track one-time expenses? > > Yes! While the automatic detection focuses on recurring costs, you can manually add any expense you want to track. One-time purchases from your bank also show up in blue on the calendar. ## Tips for Success ### 1. Check Your Expenses Weekly Make it a Monday morning habit: * Scan the calendar for any surprises * Review what's coming up this week * Spot any price increases early ### 2. Tag Everything Spend 10 minutes tagging your expenses: * Makes spending analysis actually useful * Helps at tax time * Shows where your money really goes ### 3. Run Detection Monthly First of every month: * Click "Detect Recurring Expenses" * Review what was found * Add any missing ones manually ### 4. Review Quarterly Every 3 months, audit your expenses: * Cancel services you don't use * Look for cheaper alternatives * Update any changed amounts ### 5. Use It for Budgeting Set spending targets per category: * "We should keep hosting under €500" * "Marketing budget is €300/month" * Check your spending analysis to stay on track ## Next Steps > [card] [🔗 Connect Your Bank](/payment-processing/bank-sync-ponto) > > Set up Ponto to enable automatic expense detection. > [card] [🏷️ Set Up Tags](/organization-and-automation/tags-system) > > Learn how tags work for organizing all your data. > [card] [📊 Dashboard Overview](/analytics-and-reporting/insights-dashboard) > > See your complete business overview with revenue and expenses. > [card] [💳 Payment Processing](/payment-processing/payment-methods-overview) > > Understand how your income and expenses connect. *** *Keep your finger on the pulse of your business expenses. Know what you're paying for, and make smarter decisions about where your money goes!* 💳✨ # Export Functions Source: https://docs.payreque.st/analytics-and-reporting/export-functions CSV exports with filtering # Export Functions Export your data to CSV for accounting, backups, or analysis in a spreadsheet — filtered by tags so you only export exactly what you need. > [!NOTE] > > Exports are available for **Customers**, **Subscriptions**, **Products**, **Invoices**, and **Orders**. ## Exporting Data **1. Go to Bulk Actions** Navigate to **Bulk Actions** in your dashboard. **2. Choose Export** Select **Export** as the action type, then pick which entity you want to export (Customers, Subscriptions, Products, Invoices, or Orders). **3. Choose Export as CSV** Select the **Export as CSV** option. **4. Filter by tags (optional)** Select one or more tags to only export items with those tags. Leave empty to export everything. **5. Download** Confirm the export — your browser downloads a CSV file named `{entity}_export_{date}.csv`. ## What's Included Per Entity | Entity | Columns | | - | - | | **Customers** | ID, Name, Email, Phone, Company, Language, Tax Exempt, Created, Tags | | **Subscriptions** | ID, Name, Customer, Product, Amount (EUR), Interval, Status, Next Billing, Tags | | **Products** | ID, Name, SKU, Price (EUR), Tax Rate (%), Type, Status, Stock, Tags | | **Invoices** | Invoice details including status and amounts | | **Orders** | Order details including status and amounts | > [!NOTE] > > Exports are scoped to your account only — you can never export another business's data. ## FAQ > [accordion] Can I export to PDF instead of CSV? > > CSV is the supported export format today. Use the tag filter to narrow down exactly what you need, then open the CSV in Excel, Numbers, or Google Sheets if you need a formatted document. > [accordion] Can I schedule recurring exports? > > Not yet — exports are triggered manually from Bulk Actions. For ongoing reporting, consider the [API](/api/overview) to pull data programmatically on your own schedule. > [accordion] Does the export include archived items? > > This depends on the tag filter and entity selection — archived items are included unless you filter them out with tags. ## Next Steps > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > See all bulk actions available beyond exporting > [card] [Tags System](/organization-and-automation/tags-system) > > Organize records with tags so exports are easy to filter > [card] [API Reference](/api/overview) > > Pull data programmatically instead of exporting manually # Business Insights Dashboard Source: https://docs.payreque.st/analytics-and-reporting/insights-dashboard Monitor your business performance with comprehensive analytics and real-time metrics # Business Insights Dashboard 📊 The Business Insights dashboard is your command center for understanding your business performance. Get a comprehensive overview of your revenue trends, customer growth, subscription metrics, and recent activities - all in one beautifully designed interface. ## What You'll Find on Your Insights Dashboard ### 📈 Monthly Revenue Comparison Track your business growth with side-by-side revenue comparisons: ![Monthly revenue comparison showing current month vs last month with interactive chart](https://assets.payreque.st/docs/docs-insights-card-this-month.png) * **Current Month vs. Last Month**: See exactly how your revenue is trending * **Percentage Growth**: Quick visual indicators show if you're growing or need attention * **Interactive Charts**: Hover over any point to see detailed daily breakdowns * **Smart Date Ranges**: Automatically compares equivalent time periods for accurate insights > [!TIP] > > The monthly comparison chart uses your actual transaction data, so you'll see real-time updates as payments are processed throughout the month. ### 💰 Key Performance Metrics Get instant insights into your most important business metrics: #### Monthly Revenue (labeled "MRR") * **Current Month-to-Date**: Total paid Mollie transaction volume so far this month, compared to the same period last month * **Growth Trend**: See if this month's revenue is tracking ahead or behind last month * **Sparkline Chart**: Quick visual representation of your revenue trend over the past 12 months > [!NOTE] > > This metric is labeled "MRR" on the dashboard, but it's actually **gross month-to-date revenue from Mollie transactions** (all paid Mollie payments, one-time and recurring combined) — not a true Monthly Recurring Revenue figure limited to active subscriptions, and it doesn't include Stripe, PayPal, crypto, or bank transfer payments. #### Financial Health Indicators * **Mollie Balance**: See your available payment processor balance (when connected) * **Bank Balance**: Monitor your connected bank accounts through Ponto integration * **Transfer Schedule**: Know when to expect fund transfers #### Business Growth Metrics * **Active Subscriptions**: Track your growing subscriber base * **New Customers**: Monitor customer acquisition this month * **Payment Volume**: See how many payments you're processing > [card] 🔍 Real-Time Updates > > All metrics update automatically as new transactions are processed, giving you the most current view of your business. > [card] 📱 Mobile Optimized > > Check your insights on any device - the dashboard adapts perfectly to mobile and tablet screens. ### 🕒 Recent Activity Log Stay informed about what's happening in your business with the comprehensive activity log: #### What You'll See * **Recent Actions**: Create, update, delete operations on customers, products, subscriptions * **Payment Activities**: Successful payments, failed payments, refunds * **Email Communications**: Invoice emails sent, payment confirmations, reminders * **System Events**: Subscription renewals, trial expirations, mandate updates #### Activity Display Options * **10 or 25 entries**: Choose how many recent activities to display * **Smart Icons**: Color-coded icons instantly tell you what type of activity occurred * **Time Stamps**: See exactly when each activity happened (e.g., "2 uur geleden") * **Entity Details**: Click through to see the specific customer, invoice, or subscription involved #### Activity Types & Icons * 🟢 **Create Actions**: New customers, products, or subscriptions (green plus icon) * 🔵 **Updates**: Changes to existing records (blue pencil icon) * 🔴 **Deletions**: Removed items (red trash icon) * 💳 **Payments**: Successful payments and transactions (green credit card icon) * 📧 **Emails**: Communications sent to customers (purple envelope icon) ### 📋 Recent Business Activities Quick overviews of your latest business activities across different areas: #### Recent Invoices * **Latest 5 invoices**: See your most recent billing activity * **Payment Status**: Quickly identify paid, pending, and unpaid invoices * **Customer Names**: Know who you're billing and when * **Amount Tracking**: Monitor invoice values at a glance #### Recent Subscriptions * **New Subscriptions**: See customers who recently signed up * **Status Overview**: Active, trial, paused, or canceled subscriptions * **Product Information**: Which plans are customers choosing * **Growth Patterns**: Identify your most popular subscription offerings #### Recent Orders * **Shop Activity**: Track one-time purchases through your shop * **Order Values**: See the revenue from each order * **Customer Orders**: Monitor repeat purchase behavior * **Order Status**: Completed, processing, or pending orders ### 🔄 Upcoming Subscription Renewals Never miss a renewal with the upcoming renewals tracker: #### Renewal Overview * **Next 30 Days**: See all subscriptions renewing in the coming month * **Priority Indicators**: Color-coded badges show urgency (red for today/tomorrow, amber for this week) * **Revenue Forecast**: Understand upcoming cash flow from renewals * **Customer Details**: Know which customers are renewing when #### Renewal Management * **Days Until Renewal**: Clear countdown for each subscription * **Amount Information**: See the exact renewal amount for each subscription * **Customer Context**: Customer name and subscription details * **Quick Actions**: Jump directly to subscription management if needed > [!WARNING] > > Pay special attention to subscriptions showing in red (today/tomorrow) or amber (this week) - these may need your attention if there are payment issues. ## Making the Most of Your Insights ### Daily Business Check-ins Start each day by reviewing: 1. **Yesterday's Activity**: Check the activity log for any important overnight events 2. **Today's Renewals**: Look for any subscriptions renewing today 3. **Recent Payments**: Ensure payment processing is running smoothly 4. **New Customers**: Welcome any new sign-ups ### Weekly Business Reviews Once a week, dive deeper into: 1. **Monthly Trends**: Are you on track to meet your revenue goals? 2. **Customer Growth**: How many new customers did you acquire? 3. **Subscription Health**: Any concerning cancellation patterns? 4. **Payment Issues**: Any failed payments that need attention? ### Monthly Planning Use month-end insights for: 1. **Growth Analysis**: Compare this month to last month's performance 2. **Revenue Forecasting**: Use renewal data to predict next month's revenue 3. **Customer Retention**: Analyze subscription lifecycle patterns 4. **Business Optimization**: Identify areas for improvement ## Understanding Your Data ### Revenue Metrics All revenue data comes from your actual payment transactions, ensuring accuracy. We track: * **Paid Transactions**: Only completed payments count toward revenue * **Currency Handling**: All amounts displayed in your configured currency (typically EUR) * **Real-time Updates**: New payments appear within minutes ### Activity Tracking The activity log captures: * **User Actions**: Things you do in the dashboard * **System Events**: Automated processes and scheduled tasks * **Customer Activities**: Actions taken by your customers * **Integration Events**: Data from connected payment providers ### Data Privacy Your insights dashboard respects privacy: * **User-Scoped**: You only see data for your business * **Secure Access**: All data is encrypted and access-controlled * **GDPR Compliant**: Customer data handling follows European privacy standards ## Troubleshooting Common Questions > [accordion] Why don't I see any revenue data? > > Revenue data comes from completed payments through your connected payment providers. If you're not seeing data: > > * Ensure your payment provider (Mollie/Stripe) is connected and active > * Check that you've processed actual payments (test payments may not appear) > * Allow up to 15 minutes for new payments to appear in insights > [accordion] My MRR seems incorrect > > The dashboard's "MRR" figure is actually month-to-date gross revenue from **Mollie transactions only** — it includes one-time payments, not just subscriptions, and excludes Stripe, PayPal, crypto, and bank transfer payments. If it seems off: > > * Remember it resets and recalculates from the 1st of each month > * Check whether the payments you expected to see went through Mollie specifically > * For a true recurring-revenue view limited to active subscriptions, check the [Monthly Subscription Report](/analytics-and-reporting/monthly-subscription-report) instead > [accordion] The activity log is empty > > If you're not seeing activities: > > * Activities are only recorded for actions within PayRequest > * External payment provider activities may not appear immediately > * Try refreshing the page or adjusting the display limit (10 vs 25 entries) > [accordion] Upcoming renewals show wrong dates > > Renewal dates are based on your subscription billing cycles: > > * Check individual subscription "next billing date" settings > * Paused subscriptions won't show renewal dates > * Failed payment subscriptions may have delayed renewal dates ## Next Steps > [card] [📈 Revenue Tracking](/analytics-and-reporting/revenue-tracking) > > Dive deeper into your revenue analytics with detailed tracking and forecasting tools. > [card] [📊 Transaction Reports](/analytics-and-reporting/transaction-reports) > > Generate detailed reports for accounting, tax purposes, and business analysis. > [card] [👥 Customer Analytics](/analytics-and-reporting/customer-analytics) > > Understand your customer behavior, lifetime value, and retention patterns. > [card] [📤 Export Functions](/analytics-and-reporting/export-functions) > > Learn how to export your data for external analysis and record keeping. *** *Your insights dashboard is designed to give you confidence in your business decisions. The more you use PayRequest, the richer your insights become!* 📊✨ # Monthly Subscription Report Source: https://docs.payreque.st/analytics-and-reporting/monthly-subscription-report Receive automated monthly email reports with comprehensive subscription analytics and actionable insights # Monthly Subscription Report 📊 Stay on top of your subscription business with automated monthly email reports delivered straight to your inbox. Get a comprehensive overview of your subscription performance, revenue trends, customer behavior, and actionable insights - all without lifting a finger. ## What Is the Monthly Subscription Report? The Monthly Subscription Report is an automated email summary that provides a complete retrospective analysis of your subscription business performance. Every month, you'll receive a beautifully designed email showcasing your key metrics, growth patterns, and areas that need attention. > [!TIP] > > The report is sent on **the 1st of each month at 8:00 AM**, covering the previous month's data. For example, on November 1st, you'll receive insights for October. ## What's Included in Your Report ### 🎯 Business Overview Get instant visibility into your subscription health with key metrics: * **Active Subscriptions**: Total number of paying subscribers at month-end * **New Subscriptions**: Customers who started subscriptions during the month * **Reactivated Subscriptions**: Customers who resumed paused or canceled subscriptions * **Cancelled Subscriptions**: Customers who ended their subscriptions * **Total Revenue**: Your Monthly Recurring Revenue (MRR) for the period * **Average Revenue Per User (ARPU)**: The average value of each subscription > [card] 📈 Growth Tracking > > See at a glance whether you gained or lost subscribers, with clear percentage indicators showing business momentum. > [card] 💰 Revenue Insights > > Understand exactly how much recurring revenue your subscriptions generated and what each customer is worth on average. ### 🔄 Renewals & Billing Performance Monitor the health of your billing system with detailed renewal statistics: * **Renewal Attempts**: Total number of subscription renewals processed * **Successful Renewals**: How many renewals completed successfully * **Success Rate**: Percentage of successful renewals (with performance rating) * **Failed Payments**: Number of renewal failures that need attention > [!TIP] > > A renewal success rate above 95% is excellent! If you're seeing lower rates, the report will provide specific recommendations to improve payment success. ### 💳 Chargebacks & Refunds Keep track of payment disputes and customer refunds: * **Chargebacks**: Number and total value of payment disputes from customers * **Refunds**: Number and total value of refunds processed * **Total Impact**: Combined financial impact on your business * **Smart Insights**: Automatic warnings when chargeback rates exceed healthy levels The report provides intelligent recommendations based on your chargeback volume: * ✅ **No issues**: Congratulations when you have zero chargebacks * 👍 **Under control**: When impact is minimal (\< €100) * ⚠️ **Monitor closely**: When you should review patterns (€100-500) * 🚨 **Action required**: When high volumes need immediate attention (> €500) ### 🏆 Top 5 Most Popular Subscriptions Discover which subscription products are driving your business: * **Product Rankings**: Your five best-performing subscription offerings * **Active Subscriber Count**: How many customers have each subscription * **Monthly Revenue**: The recurring revenue generated by each product Use this insight to: * Focus marketing efforts on popular products * Identify underperforming offerings * Make informed pricing decisions * Plan product development priorities ### 📈 Strategic Insights Automatically calculated key performance indicators help you understand your business trajectory: #### Growth Metrics * **Growth Rate**: How fast your subscriber base is expanding * **Churn Rate**: Percentage of customers canceling subscriptions * **Payment Success Rate**: Overall billing reliability #### Performance Benchmarks * **Chargeback Rate**: Percentage of renewals resulting in disputes * **Industry Comparisons**: See how your metrics compare to healthy benchmarks > [!WARNING] > > The report includes intelligent recommendations when metrics fall outside healthy ranges, helping you identify and address issues before they impact revenue. ## Enabling Monthly Reports Monthly Subscription Reports are controlled through your notification settings: 1. Navigate to **Settings** in your dashboard 2. Click on the **Notifications** tab 3. Scroll to the **Subscriptions** section 4. Toggle **"Monthly Subscription Report"** to ON > [!TIP] > > You can enable or disable these reports at any time. Your setting will take effect for the next scheduled report. ## Report Delivery Schedule ### When You'll Receive Reports * **Delivery Date**: 1st of every month * **Delivery Time**: 8:00 AM (local time) * **Reporting Period**: Previous full calendar month ### Example Timeline | Report Date | Covers | Sent To | | - | - | - | | November 1, 8:00 AM | October 1-31 | Your registered email | | December 1, 8:00 AM | November 1-30 | Your registered email | | January 1, 8:00 AM | December 1-31 | Your registered email | > [!TIP] > > Reports are sent to your PayRequest account email address. Make sure to keep your email address up to date in your profile settings. ## Making the Most of Your Reports ### Monthly Review Ritual Set aside 15 minutes at the start of each month to: 1. **Review Growth Trends**: Are you gaining or losing subscribers? 2. **Check Renewal Health**: Is your billing system performing well? 3. **Address Failed Payments**: Take action on subscriptions that need attention 4. **Analyze Product Performance**: Double down on what's working 5. **Monitor Financial Impact**: Keep chargebacks and refunds in check ### Strategic Planning Use monthly reports for: **🎯 Goal Setting** * Set subscriber growth targets based on trends * Establish churn reduction goals * Plan revenue milestones **📊 Performance Tracking** * Compare month-over-month growth * Track improvement in payment success rates * Monitor the impact of business changes **💡 Business Optimization** * Identify which products to promote * Spot patterns in customer cancellations * Improve payment recovery strategies **📈 Forecasting** * Predict future revenue based on active subscriptions * Plan for seasonal subscription patterns * Anticipate cash flow needs ### Sharing with Your Team Forward reports to stakeholders who need subscription insights: * Financial team for revenue forecasting * Marketing team for campaign effectiveness * Customer success team for retention focus * Leadership for strategic decision-making ## Understanding Your Data ### What Counts in the Report The monthly report includes: * **Active Subscriptions**: All subscriptions in "active" status on the last day of the month * **New Subscriptions**: Subscriptions created during the reporting period * **Completed Renewals**: Successful recurring payments processed * **Revenue**: Only from successfully completed payments ### Data Accuracy * **Real-Time Collection**: Data is gathered throughout the month as events occur * **Final Snapshot**: Reports reflect the complete month with no partial data * **Transaction-Based**: All metrics calculated from actual payment transactions * **Multi-Currency Support**: Amounts displayed in your configured currency ## Frequently Asked Questions > [accordion] What if I don't have any subscriptions? > > You'll still receive the report, but it will show zeros for subscription metrics. This is useful for tracking when you launch your subscription business and seeing your first metrics appear. > [accordion] Can I receive reports for multiple businesses? > > Each PayRequest account receives its own monthly report. If you manage multiple businesses, you'll receive a separate report for each one. > [accordion] Will I receive a report if I just signed up? > > Yes! You'll receive your first report on the 1st of the month following your signup. The report will cover whatever data you have from the partial month. > [accordion] Can I change the email address that receives reports? > > Reports are sent to your primary account email. Update your email address in **Settings → Personal** to change where reports are delivered. > [accordion] What if I miss a report? > > Reports are sent once per month. If you miss one, you can view your subscription data in your dashboard at any time by visiting **Subscriptions** and using the date filters. > [accordion] Can I get reports more frequently? > > Yes! Enable the **Daily Business Summary** for a morning overview of the last 24 hours, including overnight billing results, payments, and new customers. Go to **Settings → Notifications → Reports & Digests** to enable it. See the [Daily Business Summary](/analytics-and-reporting/daily-business-summary) documentation for details. > [accordion] Why did I receive a report about chargebacks? > > The report automatically includes chargeback data when relevant. This helps you stay informed about payment disputes so you can take action to reduce them and protect your revenue. ## What Makes These Reports Valuable ### Automated Business Intelligence Instead of manually compiling data from various sources, you get: * **Time Savings**: 15+ hours of manual reporting saved monthly * **Consistency**: Same metrics tracked the same way every month * **Completeness**: All relevant subscription data in one place * **Accessibility**: Delivered to your inbox, no login required ### Strategic Insights The report doesn't just show numbers - it provides context: * **Performance Ratings**: Know if your metrics are healthy or need attention * **Smart Recommendations**: Get actionable advice when issues are detected * **Trend Analysis**: Compare performance to identify patterns * **Benchmarking**: Understand how your business compares to healthy standards ### Proactive Problem Detection Catch issues before they become serious: * **Failed Payment Alerts**: See exactly which subscriptions need follow-up * **Chargeback Warnings**: Get notified when dispute rates are concerning * **Churn Monitoring**: Track subscription cancellations month-over-month * **Revenue Tracking**: Spot declining revenue trends early ## Next Steps > [card] [📊 Insights Dashboard](/analytics-and-reporting/insights-dashboard) > > View real-time subscription metrics in your dashboard for up-to-the-minute insights. > [card] [🔄 Managing Subscriptions](/subscriptions/subscription-lifecycle) > > Learn how to manage the full subscription lifecycle to improve retention and reduce churn. > [card] [💳 Failed Payment Handling](/subscriptions/failed-payment-handling) > > Discover strategies to recover failed subscription payments and reduce involuntary churn. > [card] [🔔 Email Automations](/organization-and-automation/email-automations) > > Set up automated emails to improve customer communication and reduce payment failures. *** *Your Monthly Subscription Report is designed to make subscription management effortless. Enable it today and start receiving strategic insights delivered to your inbox automatically!* 📊✨ # PayRequest Page Visitor Analytics Source: https://docs.payreque.st/analytics-and-reporting/payrequest-page-visitors See how many people visit your PayRequest Page every day — a Premium plan feature # PayRequest Page Visitor Analytics The **Analytics** tab on your PayRequest Page shows how many people visited your page each day, so you can see whether traffic from a social post, README badge, or QR code actually reached your page. > [!NOTE] > > Visitor analytics is a **Premium plan** feature (and included in Business too). Free plan accounts see the chart blurred with an **Upgrade to Premium** button — see [PayRequest Plans](/business-settings/payrequest-plans) for details. ## What It Shows * **Daily visitor chart** — a line chart of unique visitors for the last 16 days * **Total visitors** — the sum across that window, shown above the chart * **Per-day tooltip** — hover any point on the chart to see the exact date and visitor count ## How Visits Are Counted * Each visitor is counted **once per day** per PayRequest Page, even if they reload the page or come back multiple times that day * Visits are identified using a hashed combination of IP address and browser — PayRequest never stores your visitors' raw IP addresses * **You don't count as a visitor** when you view your own PayRequest Page while logged into your dashboard, so your own testing/previewing doesn't inflate the numbers * Automated bots and crawlers are filtered out of the count > [!TIP] > > Because counting is per-day, refreshing your own page 10 times in a browser where you're signed in won't add 10 visitors — and a real visitor who checks your page twice in one day still only counts once. ## Accessing Visitor Analytics **1. Open your PayRequest Page** Go to **PayRequest Page** from the main menu. **2. Click the Analytics tab** It sits between **Overview** and **Styling**. **3. Review your visitor trend** The chart shows the last 16 days. Hover any point for the exact count on that day. ## Free Plan Accounts If you're on the Free plan, the Analytics tab is still visible — the chart is shown blurred behind an **Upgrade to Premium** button so you know the feature exists and what upgrading unlocks. Visitor data is still being collected in the background, so once you upgrade your existing history is already there. ## Frequently Asked Questions > [accordion] Why did the chart show 0 visitors for a day I know had traffic? > > Only visits to your actual public PayRequest Page count. Visits to a Smart Link, a direct invoice link, or your dashboard don't count toward PayRequest Page visitor numbers. > [accordion] Does this track individual visitor identities? > > No. PayRequest only stores a one-way hash used to deduplicate the same visitor within the same day — never raw IP addresses or any personally identifying information. > [accordion] Can I see more than 16 days of history? > > Not currently — the chart is fixed to the most recent 16 days. > [accordion] Do Business plan customers get this too? > > Yes. Visitor analytics is available on Premium and Business — Free is the only tier without access. ## Next Steps > [card] [PayRequest Plans](/business-settings/payrequest-plans) > > Compare Free, Premium, and Business plans > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize your page's look and feel > [card] [README Badge](/shop-and-checkout/readme-badge) > > Drive traffic to your PayRequest Page from GitHub and beyond > [card] [Business Insights Dashboard](/analytics-and-reporting/insights-dashboard) > > Revenue, subscriptions, and activity in one place # Product sales and recurring revenue Source: https://docs.payreque.st/analytics-and-reporting/product-sales-and-recurring-revenue Understand paid product sales, pending orders and the monthly recurring revenue estimate for a product. Product sales summaries help you understand two different kinds of activity: purchases already recorded for a product, and estimated monthly revenue from its active subscriptions. In the [PayRequest iOS app](/getting-started/ios-app), open **Sell** and select a product to review its available sales information. The figures displayed depend on the app version and the data available to your account. > [!NOTE] > > Product sales and recurring revenue describe different things. Sales describe qualifying paid orders. Recurring revenue estimates the monthly value of current subscriptions; it does not confirm that those future payments have been collected. ## Understand the product sales figures | Figure | Meaning | | - | - | | Paid orders | Distinct qualifying paid orders containing the product. Buying several units in one order still counts as one order. | | Units sold | The quantities of the product on those qualifying paid orders. | | Pending orders | Orders containing the product that are awaiting payment and remain pending or processing. | | Product line sales | Saved product line prices multiplied by their quantities, grouped by currency. | | Last sale | The latest qualifying recorded payment time, when available. | Product line sales include this product's lines, rather than the full value of a basket containing other products. They are calculated before order-level adjustments and are not a net revenue, profit or payout figure. Orders with recorded reversals are conservatively excluded from paid product sales. This can include an order with a partial refund: the summary does not guess which product received the refund. Failed or canceled orders and free product lines do not count as paid sales. ## Understand recurring revenue per product For subscriptions linked to the product, PayRequest calculates a monthly recurring revenue estimate from the recurring amount, quantity and billing interval. A subscription must be active, outside its trial and not paused. It is excluded once its effective cancellation date has arrived. A future cancellation date does not by itself exclude an otherwise qualifying active subscription before that date. The calculation multiplies the recurring amount by the quantity, then converts the billing interval to months. For example: | Example subscription | Estimated monthly value | | - | - | | EUR 10 each month, quantity 1 | EUR 10 | | EUR 120 each year, quantity 1 | EUR 10 | | EUR 15 each month, quantity 2 | EUR 30 | These examples explain the calculation; they are not PayRequest plan prices. Daily and weekly intervals use average month lengths: 365/12 days or 52/12 weeks. A quarter represents three months and a year represents twelve months. Unsupported intervals, missing or invalid recurring amounts, and quantities below one are excluded. ## Keep currencies separate The summary groups sales and recurring revenue by their recorded currency. It does not convert different currencies into one total. For example, EUR 30 and USD 20 in estimated monthly revenue remain separate figures. If a recorded currency is unknown, it must not be assumed to be EUR or converted using an invented exchange rate. ## Know what the figures cannot tell you * The recurring estimate is not a provider balance or payout forecast. * It is not a history of the recurring payments already collected. Use [Transaction Reports](/analytics-and-reporting/transaction-reports) to inspect payments. * Recorded product views do not establish a reliable purchase funnel. The product summary does not provide a conversion rate from those views. * Missing statistics are different from measured zero sales. If data cannot be loaded, treat the figure as unavailable rather than assuming no sales or subscriptions exist. For business-wide subscription reporting, see the [Monthly Subscription Report](/analytics-and-reporting/monthly-subscription-report). The [Revenue Tracking guide](/analytics-and-reporting/revenue-tracking) explains how other dashboard revenue figures differ from subscription-based estimates. # Revenue Tracking Source: https://docs.payreque.st/analytics-and-reporting/revenue-tracking MRR and growth metrics # Revenue Tracking Track how your revenue is trending — on demand from your dashboard, or delivered automatically to your inbox. ## On-Demand: Insights Dashboard The [Business Insights Dashboard](/analytics-and-reporting/insights-dashboard) is where you check revenue in real time: * **Month-to-date revenue** compared to the same period last month (labeled "MRR" on the dashboard, though it's actually gross Mollie transaction revenue — see the note on that page for the exact definition) * **12-month sparkline** showing the trend at a glance * **Upcoming renewals** for the next 30 days, so you can forecast near-term cash flow > [!NOTE] > > For a true recurring-revenue view scoped to active subscriptions only (not one-time payments), use the [Monthly Subscription Report](/analytics-and-reporting/monthly-subscription-report) instead of the dashboard's "MRR" figure. ## Automated: Scheduled Email Reports PayRequest can email you revenue summaries automatically, so you don't have to check the dashboard every day: > [card] [Daily Business Summary](/analytics-and-reporting/daily-business-summary) > > Every morning at 8:00 — overnight payments, renewals, and key metrics from the last 24 hours > [card] [Monthly Subscription Report](/analytics-and-reporting/monthly-subscription-report) > > On the 1st of each month — a full retrospective on subscription revenue, ARPU, and growth Both are opt-in — enable them in **Settings → Notifications** under **Reports & Digests**. ## Where the Numbers Come From All revenue figures are built from your actual paid transactions — never estimates: | Source | Feeds Into | | - | - | | Paid Mollie transactions | Dashboard "MRR" widget, Daily Business Summary | | Active/new/cancelled subscriptions | Monthly Subscription Report, ARPU | | Paid invoices + completed orders | Per-customer lifetime value on [Customer Analytics](/analytics-and-reporting/customer-analytics) | > [!TIP] > > If a number looks off, check [Transaction Reports](/analytics-and-reporting/transaction-reports) first — every revenue metric traces back to real transaction records you can inspect individually. ## FAQ > [accordion] Does revenue tracking include Stripe, PayPal, or crypto payments? > > The dashboard's "MRR" widget currently only counts Mollie transactions. Subscription-based reports (Monthly Subscription Report) count subscriptions regardless of payment provider. For a complete cross-provider view, check [Transaction Reports](/analytics-and-reporting/transaction-reports), which covers Mollie, PayPal, and bank transactions. > [accordion] Can I see revenue by product or by customer? > > By customer: yes, see [Customer Analytics](/analytics-and-reporting/customer-analytics) for per-customer lifetime revenue. By product, use [Export Functions](/analytics-and-reporting/export-functions) to export orders/invoices and analyze in a spreadsheet. > [accordion] Can I set revenue goals or targets? > > Not as a built-in feature today. Use the monthly comparison on the Insights Dashboard to track progress against your own targets manually. ## Next Steps > [card] [Business Insights Dashboard](/analytics-and-reporting/insights-dashboard) > > See all real-time metrics in one place > [card] [Transaction Reports](/analytics-and-reporting/transaction-reports) > > Browse the underlying payment history > [card] [Customer Analytics](/analytics-and-reporting/customer-analytics) > > Lifetime value per customer # Transaction Reports Source: https://docs.payreque.st/analytics-and-reporting/transaction-reports Payment history and analysis # Transaction Reports Browse, search, and filter your complete payment history — synced directly from your connected payment providers. > [!NOTE] > > Your **Transactions** page (Mollie-synced) is the single source of truth for paid amounts and `paid_at` timestamps across PayRequest. If a payment shows here, it's real and confirmed by the provider — not just an internal PayRequest record. ## Where to Find Transaction History > [card] Transactions > > Your main transaction list, synced from Mollie. Search by customer, description, or reference and filter by status. > [card] PayPal Transactions > > Transaction detail view for payments processed through a connected PayPal account. > [card] Bank Transactions > > Transactions synced from your connected bank account via [Ponto](/payment-processing/bank-sync-ponto). > [card] Ponto Transactions > > Raw bank feed transactions from Ponto, useful for reconciling incoming bank transfers against invoices. ## Searching and Filtering On the main Transactions page you can: * **Search** by customer name, description, or transaction reference * **Filter by status** using the status dropdown (populated from the statuses actually present in your data — e.g. paid, open, failed, canceled, expired) * **Select multiple transactions** for bulk actions ## What Counts as "Paid" PayRequest treats a transaction as paid based on confirmation from the payment provider itself (Mollie, Stripe, PayPal, or on-chain confirmation for crypto) — never based on invoice or order status alone. This is why the Transactions page, not the Invoices or Orders page, is the definitive record for accounting and reconciliation. > [!TIP] > > If an invoice shows as unpaid but you believe it was paid, check the Transactions page first — payment provider webhooks are the source of truth, and [webhook delivery issues](/troubleshooting/payment-failures) are the most common cause of a mismatch. ## FAQ > [accordion] Why do I see transactions with no matching invoice? > > Not every transaction is tied to an invoice — payment page payments without a selected product, crypto tips, or manually recorded payments can create a transaction without a formal invoice. > [accordion] Can I export transactions to CSV? > > Invoices and Orders can be exported via [Export Functions](/analytics-and-reporting/export-functions). For raw transaction-level exports, use the [API](/api/overview) to pull transaction data directly. > [accordion] How often does the Mollie sync run? > > PayRequest syncs continuously via webhooks as payments happen, with a periodic sync job as a backup in case a webhook is ever missed. ## Next Steps > [card] [Revenue Tracking](/analytics-and-reporting/revenue-tracking) > > See revenue trends built from this same transaction data > [card] [Export Functions](/analytics-and-reporting/export-functions) > > Export invoices, orders, and other records to CSV > [card] [Payment Failures](/troubleshooting/payment-failures) > > Troubleshoot missing or mismatched payments # Authentication Source: https://docs.payreque.st/api/authentication Secure your API requests with OAuth2 tokens # API Authentication The PayRequest API uses **OAuth2** with Personal Access Tokens for authentication. All API requests must include a valid access token in the `Authorization` header. ## Creating an Access Token **1. Navigate to API Settings** Go to **Settings** → **API Tokens** in your PayRequest dashboard. **2. Create New Token** Click the **Create New Token** button. **3. Configure Token** * Enter a descriptive name (e.g., "MCP Billing Agent") * Select the scopes (permissions) your token needs * Click **Create** **4. Copy Your Token** > [!WARNING] > > Your token is only shown once. Copy it immediately and store it securely. > If you lose it, you'll need to create a new token. ## Using Your Token Include the token in the `Authorization` header of every API request: ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" \ -H "Content-Type: application/json" ``` ## OAuth Scopes Scopes define what actions your token can perform. Request only the scopes you need for better security. ### Available Scopes | Scope | Description | Use Case | | - | - | - | | `billing.read` | Read invoices, subscriptions, transactions | Dashboards, reporting, monitoring | | `billing.write` | Create and modify invoices and subscriptions | Invoice automation, billing workflows | | `billing.agent` | Full AI billing agent access | MCP integrations, AI assistants | | `customers.read` | Read customer information | CRM integrations, customer lookup | | `customers.write` | Create and modify customers | Customer sync, onboarding automation | | `products.read` | Read product catalog | Catalog sync, price checks | | `products.write` | Create and modify products | Product management automation | ### Default Scope If you don't specify scopes when creating a token, it will receive the default `billing.read` scope. ### Scope Inheritance The `billing.agent` scope includes all capabilities of `billing.read` and `billing.write`, making it ideal for AI-powered billing assistants. ## Token Expiration | Token Type | Expiration | | - | - | | Personal Access Token | 6 months | | Access Token | 15 days | | Refresh Token | 30 days | > [!NOTE] > > Tokens expire automatically for security. Plan to refresh or regenerate tokens before they expire. ## Security Best Practices > [accordion] Store tokens securely > > * Never commit tokens to version control > * Use environment variables or secret management services > * Encrypt tokens at rest > [accordion] Use minimal scopes > > * Only request the scopes your application needs > * Review and audit token permissions regularly > * Create separate tokens for different integrations > [accordion] Rotate tokens regularly > > * Regenerate tokens periodically (every 3-6 months) > * Revoke tokens that are no longer needed > * Monitor for unauthorized usage > [accordion] Protect in transit > > * Always use HTTPS (enforced by our API) > * Don't log or display full tokens > * Use secure headers in requests ## Revoking Tokens To revoke a token: 1. Go to **Settings** → **API Tokens** 2. Find the token you want to revoke 3. Click the **Delete** button 4. Confirm the deletion > [!WARNING] > > Revoking a token is immediate and cannot be undone. Any applications using that token will lose access. ## Error Responses ### Invalid or Missing Token ```json theme={null} { "message": "Unauthenticated." } ``` **HTTP Status**: `401 Unauthorized` **Solution**: Ensure you're including a valid token in the `Authorization` header. ### Insufficient Scope ```json theme={null} { "success": false, "error": "Invalid scope(s) provided." } ``` **HTTP Status**: `403 Forbidden` **Solution**: Create a new token with the required scopes or update your existing token's permissions. ### Expired Token ```json theme={null} { "message": "Unauthenticated." } ``` **HTTP Status**: `401 Unauthorized` **Solution**: Generate a new access token from the dashboard. ## Example: Complete Authentication Flow ```javascript theme={null} // Node.js example using fetch const API_TOKEN = process.env.PAYREQUEST_API_TOKEN; async function getInvoices() { const response = await fetch('https://payrequest.app/api/v1/invoices', { method: 'GET', headers: { 'Authorization': `Bearer ${API_TOKEN}`, 'Accept': 'application/json', 'Content-Type': 'application/json' } }); if (!response.ok) { if (response.status === 401) { throw new Error('Invalid or expired API token'); } if (response.status === 403) { throw new Error('Insufficient permissions'); } throw new Error(`API error: ${response.status}`); } return response.json(); } ``` ```python theme={null} # Python example using requests import os import requests API_TOKEN = os.environ.get('PAYREQUEST_API_TOKEN') def get_invoices(): response = requests.get( 'https://payrequest.app/api/v1/invoices', headers={ 'Authorization': f'Bearer {API_TOKEN}', 'Accept': 'application/json', 'Content-Type': 'application/json' } ) if response.status_code == 401: raise Exception('Invalid or expired API token') if response.status_code == 403: raise Exception('Insufficient permissions') response.raise_for_status() return response.json() ``` # Error Handling Source: https://docs.payreque.st/api/errors Understanding and handling API errors # Error Handling The PayRequest API uses conventional HTTP response codes and returns detailed error messages to help you diagnose issues quickly. ## HTTP Status Codes | Code | Meaning | Description | | - | - | - | | `200` | OK | Request succeeded | | `201` | Created | Resource created successfully | | `400` | Bad Request | Invalid request parameters or body | | `401` | Unauthorized | Missing or invalid authentication | | `403` | Forbidden | Valid auth but insufficient permissions | | `404` | Not Found | Resource doesn't exist or doesn't belong to you | | `422` | Unprocessable Entity | Validation errors | | `429` | Too Many Requests | Rate limit exceeded | | `500` | Internal Server Error | Something went wrong on our end | ## Error Response Format All error responses follow this structure: ```json theme={null} { "success": false, "error": "Human-readable error message", "errors": { "field_name": [ "Specific validation error" ] } } ``` | Field | Type | Description | | - | - | - | | `success` | boolean | Always `false` for errors | | `error` | string | General error description | | `errors` | object | Field-specific validation errors (optional) | ## Common Errors ### Authentication Errors > [accordion] 401 - Unauthenticated > > **Cause**: Missing, invalid, or expired access token. > > ```json theme={null} > { > "message": "Unauthenticated." > } > ``` > > **Solutions**: > > * Ensure you're including the `Authorization` header > * Check that your token starts with `Bearer ` > * Generate a new token if expired > [accordion] 403 - Insufficient Scope > > **Cause**: Your token doesn't have the required scope. > > ```json theme={null} > { > "success": false, > "error": "Invalid scope(s) provided." > } > ``` > > **Solutions**: > > * Check which scope the endpoint requires > * Create a new token with the required scopes > * Use the [Authentication guide](/api/authentication) for scope details ### Validation Errors > [accordion] 422 - Validation Failed > > **Cause**: Request body failed validation rules. > > ```json theme={null} > { > "success": false, > "error": "The given data was invalid.", > "errors": { > "customer_id": ["The customer id field is required."], > "items": ["The items field is required."], > "due_date": ["The due date must be a date after or equal to date."] > } > } > ``` > > **Solutions**: > > * Check each field in the `errors` object > * Ensure required fields are provided > * Verify data types and formats match the documentation ### Resource Errors > [accordion] 404 - Not Found > > **Cause**: Resource doesn't exist or doesn't belong to your account. > > ```json theme={null} > { > "success": false, > "error": "Invoice not found" > } > ``` > > **Solutions**: > > * Verify the resource ID is correct > * Ensure the resource belongs to your account > * Check if the resource was deleted > [accordion] 400 - Bad Request > > **Cause**: Business logic prevented the action. > > ```json theme={null} > { > "success": false, > "error": "Invoice is already paid" > } > ``` > > **Solutions**: > > * Check the current state of the resource > * Review the error message for specific guidance ### Rate Limiting > [accordion] 429 - Rate Limited > > **Cause**: Too many requests in a short period. > > ```json theme={null} > { > "success": false, > "error": "Too many requests. Please try again later." > } > ``` > > **Headers included**: > > ``` > X-RateLimit-Limit: 60 > X-RateLimit-Remaining: 0 > X-RateLimit-Reset: 1706540400 > Retry-After: 45 > ``` > > **Solutions**: > > * Implement exponential backoff > * Cache responses where possible > * Wait until `X-RateLimit-Reset` timestamp ## Best Practices ### Implement Proper Error Handling ```javascript theme={null} async function apiRequest(endpoint, options = {}) { const response = await fetch(`https://payrequest.app/api/v1${endpoint}`, { ...options, headers: { 'Authorization': `Bearer ${process.env.PAYREQUEST_TOKEN}`, 'Accept': 'application/json', 'Content-Type': 'application/json', ...options.headers } }); const data = await response.json(); if (!response.ok) { // Handle specific error types switch (response.status) { case 401: throw new AuthenticationError('Invalid or expired token'); case 403: throw new PermissionError('Insufficient permissions'); case 404: throw new NotFoundError(data.error || 'Resource not found'); case 422: throw new ValidationError(data.errors); case 429: const retryAfter = response.headers.get('Retry-After'); throw new RateLimitError(`Rate limited. Retry after ${retryAfter}s`); default: throw new ApiError(data.error || 'Unknown error'); } } return data; } ``` ### Retry Strategy For transient errors (5xx, network issues), implement exponential backoff: ```javascript theme={null} async function apiRequestWithRetry(endpoint, options, maxRetries = 3) { for (let attempt = 0; attempt < maxRetries; attempt++) { try { return await apiRequest(endpoint, options); } catch (error) { // Don't retry client errors (4xx) if (error.status >= 400 && error.status < 500) { throw error; } // Don't retry on last attempt if (attempt === maxRetries - 1) { throw error; } // Exponential backoff: 1s, 2s, 4s const delay = Math.pow(2, attempt) * 1000; await new Promise(resolve => setTimeout(resolve, delay)); } } } ``` ### Validate Before Sending Catch validation issues early: ```javascript theme={null} function validateInvoiceData(data) { const errors = {}; if (!data.customer_id) { errors.customer_id = ['Customer ID is required']; } if (!data.items || data.items.length === 0) { errors.items = ['At least one line item is required']; } if (data.due_date && data.date && new Date(data.due_date) < new Date(data.date)) { errors.due_date = ['Due date must be on or after invoice date']; } if (Object.keys(errors).length > 0) { throw new ValidationError(errors); } } ``` ## Getting Help If you encounter persistent errors: 1. Check this documentation for the endpoint requirements 2. Verify your token has the correct scopes 3. Test with a minimal request body 4. Contact [support@payrequest.io](mailto:support@payrequest.io) with: * The endpoint you're calling * Your request (without the token) * The error response * Your account email # Invoices Source: https://docs.payreque.st/api/invoices Create, retrieve, and manage invoices via the API # Invoice Endpoints Manage your invoices programmatically with these endpoints. All endpoints require authentication and the appropriate OAuth scope. ## List All Invoices Retrieve a paginated list of all your invoices. **Authorization** `string` *required* Bearer token with `billing.read` scope **per_page** `integer` (default: 25) Number of invoices per page (max 100) **page** `integer` (default: 1) Page number for pagination ```bash theme={null} GET /api/v1/invoices ``` ### Request Example ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices?per_page=10&page=1" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### Response ```json theme={null} { "success": true, "data": { "current_page": 1, "data": [ { "id": 1234, "invoice_number": "INV-000042", "reference": "Project Alpha", "amount": 1250.00, "currency": "EUR", "status": "pending", "date": "2025-01-15", "due_date": "2025-01-30", "customer": { "id": 567, "name": "Acme Corp", "email": "billing@acme.com", "company": "Acme Corporation" }, "invoice_items": [ { "description": "Web Development Services", "quantity": 40, "unit_price": 25.00, "tax_rate": 21, "total": 1000.00 } ] } ], "per_page": 10, "total": 150, "last_page": 15 } } ``` *** ## Get Invoice Details Retrieve detailed information about a specific invoice. **invoice** `integer` *required* The invoice ID ```bash theme={null} GET /api/v1/invoices/{invoice} ``` ### Request Example ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices/1234" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### Response ```json theme={null} { "success": true, "data": { "id": 1234, "invoice_number": "INV-000042", "reference": "Project Alpha", "amount": 1250.00, "currency": "EUR", "status": "pending", "date": "2025-01-15", "due_date": "2025-01-30", "notes": "Payment terms: Net 15", "customer": { "id": 567, "name": "Acme Corp", "email": "billing@acme.com", "company": "Acme Corporation", "phone": "+31 20 123 4567", "address": "123 Business Street", "city": "Amsterdam", "postal_code": "1012 AB", "country": "Netherlands" }, "invoice_items": [...], "transactions": [...], "subscription": null } } ``` *** ## Get Invoice Statistics Get aggregated statistics about your invoices. ```bash theme={null} GET /api/v1/invoices/stats ``` ### Request Example ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices/stats" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### Response ```json theme={null} { "success": true, "data": { "total_invoices": 150, "pending_invoices": 23, "paid_invoices": 120, "overdue_invoices": 7, "total_outstanding": 15750.00, "total_overdue": 4200.00, "currency": "EUR" } } ``` ### Response Fields | Field | Type | Description | | - | - | - | | `total_invoices` | integer | Total number of invoices | | `pending_invoices` | integer | Invoices awaiting payment | | `paid_invoices` | integer | Fully paid invoices | | `overdue_invoices` | integer | Invoices past due date | | `total_outstanding` | decimal | Sum of all unpaid invoices | | `total_overdue` | decimal | Sum of overdue invoices | *** ## Get Overdue Invoices Retrieve all invoices that are past their due date. Ideal for payment follow-up automation and AI billing agents. ```bash theme={null} GET /api/v1/invoices/overdue ``` ### Request Example ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices/overdue" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### Response ```json theme={null} { "success": true, "count": 7, "total_outstanding": 4200.00, "currency": "EUR", "data": [ { "id": 1230, "invoice_number": "INV-000038", "reference": "Maintenance Q4", "amount": 600.00, "currency": "EUR", "status": "sent", "date": "2024-12-01", "due_date": "2024-12-15", "days_overdue": 45, "customer": { "id": 890, "name": "TechStart BV", "email": "finance@techstart.nl", "phone": "+31 20 987 6543" }, "payment_link": "https://payrequest.me/yourshop/invoice/1230" } ] } ``` > [!TIP] > > The `payment_link` field contains a direct link you can share with the customer. It's `null` if a payment has already been initiated. *** ## Create Invoice Create a new invoice with line items. **Authorization** `string` *required* Bearer token with `billing.write` scope ```bash theme={null} POST /api/v1/invoices ``` ### Request Body **customer_id** `integer` *required* The ID of an existing customer **invoice_number** `string` Custom invoice number (auto-generated if not provided) **reference** `string` Your internal reference (e.g., project name, PO number) **date** `string` *required* Invoice date in `YYYY-MM-DD` format **due_date** `string` *required* Due date in `YYYY-MM-DD` format (must be on or after invoice date) **notes** `string` Additional notes to include on the invoice **items** `array` *required* Array of invoice line items (minimum 1 item) ### Request Example ```bash theme={null} curl -X POST "https://payrequest.app/api/v1/invoices" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" \ -H "Content-Type: application/json" \ -d '{ "customer_id": 567, "reference": "Project Beta", "date": "2025-01-29", "due_date": "2025-02-13", "notes": "Thank you for your business!", "items": [ { "description": "Consulting Services", "quantity": 8, "unit_price": 150.00, "tax_rate": 21 }, { "description": "Software License", "quantity": 1, "unit_price": 500.00, "tax_rate": 21 } ] }' ``` ### Response ```json theme={null} { "success": true, "message": "Invoice created successfully", "data": { "id": 1235, "invoice_number": "INV-000043", "reference": "Project Beta", "amount": 1700.00, "currency": "EUR", "status": "pending", "date": "2025-01-29", "due_date": "2025-02-13", "customer": {...}, "invoice_items": [...] } } ``` **HTTP Status**: `201 Created` ### Item Structure Each item in the `items` array should have: | Field | Type | Required | Description | | - | - | - | - | | `description` | string | Yes | Line item description | | `quantity` | decimal | Yes | Quantity (min: 0.01) | | `unit_price` | decimal | Yes | Price per unit | | `tax_rate` | decimal | No | Tax percentage (default: 0) | *** ## Send Payment Reminder Send a payment reminder email for an unpaid invoice. **Authorization** `string` *required* Bearer token with `billing.write` scope **invoice** `integer` *required* The invoice ID ```bash theme={null} POST /api/v1/invoices/{invoice}/reminder ``` ### Request Example ```bash theme={null} curl -X POST "https://payrequest.app/api/v1/invoices/1230/reminder" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### Response ```json theme={null} { "success": true, "message": "Invoice reminder sent successfully" } ``` ### Error Responses **Invoice already paid:** ```json theme={null} { "success": false, "error": "Invoice is already paid" } ``` **HTTP Status**: `400 Bad Request` **Invoice not found:** ```json theme={null} { "success": false, "error": "Invoice not found" } ``` **HTTP Status**: `404 Not Found` *** ## Invoice Statuses | Status | Description | | - | - | | `draft` | Invoice created but not finalized | | `pending` | Invoice created, awaiting payment | | `sent` | Invoice emailed to customer | | `viewed` | Customer has viewed the invoice | | `paid` | Invoice fully paid | | `partial` | Invoice partially paid | | `overdue` | Payment past due date | | `cancelled` | Invoice cancelled | *** ## MCP Integration Example Here's how to use the invoice API with an MCP billing agent: ```typescript theme={null} // MCP Server Tool Definition { name: "get_overdue_invoices", description: "Get all overdue invoices that need follow-up", inputSchema: { type: "object", properties: {} } } // Tool Implementation async function getOverdueInvoices() { const response = await fetch( 'https://payrequest.app/api/v1/invoices/overdue', { headers: { 'Authorization': `Bearer ${process.env.PAYREQUEST_TOKEN}`, 'Accept': 'application/json' } } ); const data = await response.json(); return { content: [{ type: 'text', text: `Found ${data.count} overdue invoices totaling €${data.total_outstanding}` }], invoices: data.data }; } ``` # API Overview Source: https://docs.payreque.st/api/overview Connect your applications to PayRequest using our REST API # PayRequest API The PayRequest API allows you to programmatically access your billing data, create invoices, and automate your billing workflows. It's designed for integrations with external tools, MCP servers, and custom applications. ## Base URL All API requests should be made to: ``` https://payrequest.app/api/v1 ``` ## API Versioning The API uses URL-based versioning. The current version is `v1`. We recommend always specifying the version in your requests to ensure compatibility. ## Features > [card] [Invoice Management](/api/invoices) > > List, create, and manage invoices programmatically > [card] [OAuth2 Authentication](/api/authentication) > > Secure token-based authentication using OAuth2 > [card] [Payment Links](/api/payment-links) > > Create fixed-amount payment links with a custom description for reconciliation > [card] [Webhooks](/api/webhooks) > > Receive signed HMAC-SHA256 notifications on payment.succeeded events > [card] [Payments](/api/payment-links#list-payments) > > Query and reconcile payments by description or status > [card] [Payment Reminders](/api/invoices#send-payment-reminder) > > Automate follow-ups for overdue invoices ## Quick Start ### 1. Create an API Token 1. Go to **Settings** → **API Tokens** in your PayRequest dashboard 2. Click **Create New Token** 3. Give your token a name (e.g., "MCP Integration") 4. Select the required scopes (permissions) 5. Copy and securely store your access token ### 2. Make Your First Request ```bash theme={null} curl -X GET "https://payrequest.app/api/v1/invoices" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Accept: application/json" ``` ### 3. Handle the Response ```json theme={null} { "success": true, "data": { "data": [...], "current_page": 1, "per_page": 25, "total": 150 } } ``` ## Available Endpoints | Method | Endpoint | Description | Scope Required | | - | - | - | - | | GET | `/v1/invoices` | List all invoices | `billing.read` | | GET | `/v1/invoices/{id}` | Get invoice details | `billing.read` | | GET | `/v1/invoices/stats` | Get invoice statistics | `billing.read` | | GET | `/v1/invoices/overdue` | List overdue invoices | `billing.read` | | POST | `/v1/invoices` | Create a new invoice | `billing.write` | | POST | `/v1/invoices/{id}/reminder` | Send payment reminder | `billing.write` | | POST | `/v1/payment-links` | Create a payment link | `billing.write` | | GET | `/v1/payment-links` | List payment links | `billing.read` | | GET | `/v1/payments` | List & filter payments | `billing.read` | | POST | `/v1/deposits` | Create a security deposit link | `billing.write` | | GET | `/v1/deposits` | List and filter security deposits | `billing.read` | | GET | `/v1/deposits/{id}` | Get security deposit status | `billing.read` | | POST | `/v1/deposits/{id}/capture` | Capture an authorized deposit | `billing.write` | | POST | `/v1/deposits/{id}/release` | Release an authorized deposit | `billing.write` | ## Rate Limiting API requests are rate limited to ensure fair usage: * **Standard limit**: 60 requests per minute * **Burst limit**: 100 requests per minute (temporary) Rate limit headers are included in all responses: ``` X-RateLimit-Limit: 60 X-RateLimit-Remaining: 45 X-RateLimit-Reset: 1706540400 ``` ## Response Format All API responses follow a consistent JSON format: ### Success Response ```json theme={null} { "success": true, "data": { ... }, "message": "Optional success message" } ``` ### Error Response ```json theme={null} { "success": false, "error": "Error description", "errors": { "field_name": ["Validation error message"] } } ``` ## SDKs and Libraries While we don't currently offer official SDKs, the API works seamlessly with: * **MCP (Model Context Protocol)** servers for AI assistants * Standard HTTP libraries in any programming language * Tools like Postman, Insomnia, or cURL ## Support Need help with the API? Contact us at [support@payrequest.io](mailto:support@payrequest.io) or check our [troubleshooting guide](/troubleshooting/common-issues). # Payment Links & Payments Source: https://docs.payreque.st/api/payment-links Programmatically create payment links and reconcile payments via the API # Payment Links & Payments Use these endpoints to generate fixed-amount payment links on the fly and query incoming payments for reconciliation — for example, per-user or per-reference billing flows. ## Create a Payment Link Generates a shareable payment link (Smart Link) with a fixed amount and a custom description you can use as a reference when reconciling. **Authorization** `string` *required* Bearer token with `billing.write` scope ```bash theme={null} POST /api/v1/payment-links ``` ### Request Body **description** `string` *required* Your internal reference, shown on the payment page and included in all webhook payloads and payment records. Example: `JMIT-githubuser` **amount** `number` *required* Fixed payment amount in euros (decimal). Example: `49.00` **currency** `string` (default: EUR) 3-letter ISO currency code. Defaults to `EUR`. ### Request Example ```bash theme={null} curl -X POST "https://payrequest.app/api/v1/payment-links" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "description": "JMIT-githubuser", "amount": 49.00 }' ``` ### Response ```json theme={null} { "success": true, "data": { "id": 42, "url": "https://payrequest.me/jmit/jmit-githubuser", "description": "JMIT-githubuser", "amount": 49.00, "currency": "EUR", "created_at": "2026-05-30T12:00:00+02:00" } } ``` > [!NOTE] > > The URL slug is automatically derived from your `description` (e.g. `JMIT-githubuser` → `jmit-githubuser`). If a link with that slug already exists, a numeric suffix is appended (`jmit-githubuser-2`). *** ## List Payment Links Returns a paginated list of all your payment links. **Authorization** `string` *required* Bearer token with `billing.read` scope **per_page** `integer` (default: 25) Number of results per page (max 100) ```bash theme={null} GET /api/v1/payment-links ``` ### Request Example ```bash theme={null} curl "https://payrequest.app/api/v1/payment-links?per_page=10" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" ``` ### Response ```json theme={null} { "success": true, "data": { "current_page": 1, "data": [ { "id": 42, "url": "https://payrequest.me/jmit/jmit-githubuser", "description": "JMIT-githubuser", "amount": 49.00, "currency": "EUR", "payments_count": 1, "revenue": 49.00, "is_active": true, "created_at": "2026-05-30T12:00:00+02:00" } ], "per_page": 25, "total": 1 } } ``` *** ## List Payments Query incoming payments for reconciliation. Filter by `description` to find all payments tied to a specific reference. **Authorization** `string` *required* Bearer token with `billing.read` scope **description** `string` Filter payments by description (case-insensitive partial match). Example: `JMIT-githubuser` **status** `string` Filter by status: `paid`, `open`, `pending`, or `failed` **from** `date` Start date filter (YYYY-MM-DD) **to** `date` End date filter (YYYY-MM-DD) **per_page** `integer` (default: 25) Number of results per page (max 100) ```bash theme={null} GET /api/v1/payments ``` ### Request Example ```bash theme={null} curl "https://payrequest.app/api/v1/payments?description=JMIT-githubuser&status=paid" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" ``` ### Response ```json theme={null} { "success": true, "data": { "current_page": 1, "data": [ { "id": 1234, "description": "JMIT-githubuser", "amount": 49.00, "currency": "EUR", "status": "paid", "payment_method": "ideal", "payment_link_id": 42, "payment_link_url": "https://payrequest.me/jmit/jmit-githubuser", "reference": "tr_abc123", "paid_at": "2026-05-30T11:59:45+02:00", "created_at": "2026-05-30T11:58:00+02:00", "customer": { "id": 99, "name": "Jane Doe", "email": "jane@example.com" } } ], "per_page": 25, "total": 1 } } ``` *** ## Reconciliation workflow A typical programmatic billing flow using these endpoints: 1. **Create a payment link** with the user's identifier as `description` (e.g. `JMIT-githubuser`) 2. **Send the `url`** to your customer via email or embed it in your app 3. **Receive a webhook** (`payment.succeeded`) with the `description` and `payment_link_id` when payment arrives — see [Webhooks](/api/webhooks) 4. **Or poll** `GET /v1/payments?description=JMIT-githubuser&status=paid` to reconcile on demand # Security Deposits API Source: https://docs.payreque.st/api/security-deposits Create deposit links and synchronize authorization status with your own software # Security Deposits API Create a card authorization link for a booking, send it through your own guest communication system, and synchronize its status using signed webhooks. All endpoints require an OAuth bearer token. Use `billing.write` to create, capture, or release deposits and `billing.read` to retrieve them. ## Create a deposit link ```http theme={null} POST /api/v1/deposits Authorization: Bearer YOUR_TOKEN Idempotency-Key: booking-12345-deposit Content-Type: application/json ``` ```json theme={null} { "booking_reference": "BOOKING-12345", "amount": 300.00, "currency": "EUR", "customer": { "name": "John Doe", "email": "john@example.com" }, "check_in_date": "2026-09-10", "check_out_date": "2026-09-17", "metadata": { "apartment_id": "APT-42" } } ``` The response contains an `authorization_url`. Send this URL to the guest. Repeating the request with the same `Idempotency-Key` returns the original deposit instead of creating a duplicate. ## Retrieve deposits ```http theme={null} GET /api/v1/deposits?booking_reference=BOOKING-12345 GET /api/v1/deposits/{id} ``` The list endpoint also accepts `status` and `per_page`. Available statuses are `pending`, `authorized`, `partially_captured`, `captured`, `released`, `expired`, and `failed`. ### Dashboard labels and authorization attempts The dashboard uses more descriptive labels without changing these API status values: | API status | Dashboard label | Interpretation | | - | - | - | | `pending` | Waiting for customer | No confirmed hold; the customer may still need to complete authorization. | | `pending` with `metadata.authorization_state=processing` | Processing authorization | The provider is processing the attempt. Wait before requesting another payment. | | `pending` with `metadata.authorization_state=expired` | Authorization attempt expired | The checkout attempt expired without a confirmed hold. Verify existing provider references before arranging a new attempt. | | `authorized` | Funds reserved | A confirmed hold is available until `capture_before`. | | `captured` | Captured | Capture is final. For Stripe this includes a partial amount with the remainder released. | | `expired` | Expired | A previously confirmed hold expired. | Authorization-attempt metadata is provider-confirmed where available. Its absence does not prove that a customer has never opened a link. The new dashboard labels are not accepted as `status` query parameters; use the API values above. ## Capture or release Capture the full remaining amount by omitting `amount`, or capture part of it: ```http theme={null} POST /api/v1/deposits/{id}/capture Content-Type: application/json { "amount": 75.00, "description": "Damage to kitchen table" } ``` Release the remaining card authorization: ```http theme={null} POST /api/v1/deposits/{id}/release ``` > [!WARNING] > > Stripe deposits currently support **one final capture**. Capturing €150 from a €350 authorization charges €150, releases €200, and returns status `captured` with `captured_amount` equal to `150.00`. The difference between `amount` and `captured_amount` is not available for a second capture. Do not infer a remaining authorization by subtracting these fields. Attempts to capture a locally finalized deposit return HTTP 409. Stripe deposit captures have a **0% PayRequest platform fee**. Stripe processing fees apply separately. See [Security Deposits](/payment-processing/security-deposits) for dashboard steps, status explanations, and examples. ## Stripe deposit renewal New Stripe deposits can use saved-card renewal on Business after the customer explicitly opts in on the hosted authorization page. Send the returned `authorization_url` to the customer; creating a deposit through the API is not customer consent. Renewal is initiated from the deposit detail screen in the dashboard. There is **no public renewal API endpoint**. Consent and renewal history cannot be supplied through create-request metadata. Keys reserved for the renewal workflow are controlled by PayRequest. Read the current `capture_before` and provider status after a renewal. The existing API status values remain unchanged: a deposit may still be `authorized` while a replacement is awaiting bank confirmation. Capture and release are temporarily unavailable while that replacement is unresolved. Do not create a second deposit to bypass this protection. A replacement is recorded only after Stripe confirms the new hold and cancellation of the original. Renewal does not introduce a `deposit.renewed` webhook event, so do not rely on a new `deposit.authorized` event for every replacement; retrieve the current deposit to check the deadline. See [Stripe renewal steps and limits](/payment-processing/security-deposits#renew-a-stripe-deposit-on-business). ## Webhook events PayRequest sends `deposit.created`, `deposit.authorized`, `deposit.partially_captured`, `deposit.captured`, `deposit.released`, `deposit.expired`, and `deposit.failed` to the webhook URL configured under **Settings → API & MCP**. A final partial Stripe capture emits `deposit.captured`, not a promise that another capture remains available. Updates to pending authorization-attempt metadata do not introduce new deposit webhook event names. Retrieve the deposit to read the latest metadata. Verify the `X-PayRequest-Signature` header using the configured webhook secret. The signature format is `sha256=` followed by the HMAC-SHA256 digest of the raw request body. The `X-PayRequest-Event` header contains the event name. > [!NOTE] > > Card authorizations expire. Create the link close enough to check-in for the selected payment provider's authorization window. # Webhooks Source: https://docs.payreque.st/api/webhooks Receive signed real-time notifications for payments and security deposits # Webhooks PayRequest can send signed HTTP POST requests when a payment succeeds or a security deposit changes status. Use these events to automate fulfillment, synchronize bookings, or trigger downstream workflows without polling. ## Setup 1. Go to **Settings → API & MCP** in your PayRequest dashboard 2. Scroll down to the **Webhooks** section 3. Enter your endpoint URL (must be publicly reachable over HTTPS) 4. Click **Save** — a signing secret is generated automatically 5. Copy the **Signing Secret** and store it securely in your environment *** ## Verifying signatures Every request includes an `X-PayRequest-Signature` header containing an HMAC-SHA256 signature of the raw request body. **Always verify this before processing the event.** ``` X-PayRequest-Signature: sha256=a1b2c3d4... ``` ```php PHP theme={null} $secret = $_ENV['PAYREQUEST_WEBHOOK_SECRET']; $body = file_get_contents('php://input'); $received = $_SERVER['HTTP_X_PAYREQUEST_SIGNATURE'] ?? ''; $expected = 'sha256=' . hash_hmac('sha256', $body, $secret); if (!hash_equals($expected, $received)) { http_response_code(401); exit; } $event = json_decode($body, true); ``` ```python Python theme={null} import hashlib, hmac, os from flask import request, abort secret = os.environ['PAYREQUEST_WEBHOOK_SECRET'].encode() body = request.get_data() sig = request.headers.get('X-PayRequest-Signature', '') expected = 'sha256=' + hmac.new(secret, body, hashlib.sha256).hexdigest() if not hmac.compare_digest(expected, sig): abort(401) event = request.get_json() ``` ```javascript Node.js theme={null} const crypto = require('crypto'); const secret = process.env.PAYREQUEST_WEBHOOK_SECRET; const body = req.rawBody; // use raw body, not parsed JSON const sig = req.headers['x-payrequest-signature'] ?? ''; const expected = 'sha256=' + crypto .createHmac('sha256', secret) .update(body) .digest('hex'); if (!crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(sig))) { return res.status(401).send('Invalid signature'); } const event = JSON.parse(body); ``` > [!WARNING] > > Always use a timing-safe comparison (`hash_equals`, `hmac.compare_digest`, `timingSafeEqual`) to prevent timing attacks. *** ## Event: `payment.succeeded` Fired when a transaction status changes to `paid`. Delivered asynchronously via the queue (typically within seconds). ### Payload ```json theme={null} { "event": "payment.succeeded", "timestamp": "2026-05-30T12:00:00+02:00", "data": { "id": 1234, "amount": 49.00, "currency": "EUR", "description": "JMIT-githubuser", "payment_link_id": 42, "payment_method": "ideal", "reference": "tr_abc123", "paid_at": "2026-05-30T11:59:45+02:00", "customer": { "id": 99, "name": "Jane Doe", "email": "jane@example.com" } } } ``` ### Fields | Field | Type | Description | | - | - | - | | `event` | string | Always `payment.succeeded` | | `timestamp` | ISO 8601 | When the event was dispatched | | `data.id` | integer | Transaction ID | | `data.amount` | decimal | Amount paid (e.g. `49.00`) | | `data.currency` | string | 3-letter ISO currency code | | `data.description` | string | Your custom reference (e.g. `JMIT-githubuser`) | | `data.payment_link_id` | integer\|null | ID of the Smart Link used, if any | | `data.payment_method` | string | Payment method used (e.g. `ideal`, `creditcard`) | | `data.reference` | string | Payment provider transaction reference | | `data.paid_at` | ISO 8601 | Exact time the payment was confirmed | | `data.customer` | object\|null | Customer name, email, and ID | ## Security deposit events Security deposit integrations can receive: * `deposit.created` * `deposit.authorized` * `deposit.partially_captured` * `deposit.captured` * `deposit.released` * `deposit.expired` * `deposit.failed` The request also includes `X-PayRequest-Event` with the event name. See the [Security Deposits API](/api/security-deposits) for the payload and integration flow. *** ## Retries Security deposit webhook delivery uses **5 attempts** with increasing backoff intervals. Payment webhook delivery uses the existing payment queue policy. Return any `2xx` status code to acknowledge receipt. *** ## Rotating the secret If your secret is compromised, go to **Settings → API & MCP → Webhooks** and click **Regenerate**. Your old secret stops working immediately — update your environment variable before rotating. *** ## Testing locally Use a tunnel tool to expose your local server during development: ```bash theme={null} # Using ngrok ngrok http 8000 # Then set your webhook URL to: # https://abc123.ngrok.io/webhooks/payrequest ``` # Services & integrations Source: https://docs.payreque.st/business-settings/app-store Connect payment, domain and VPN providers for your business # Services & integrations The PayRequest App Store is your central hub for connecting, configuring, and managing all third-party integrations. From payment processors to domain provisioning services, the App Store provides a unified interface to manage all your business connections. > [!NOTE] > > **Location**: Open **Sell** → **Services & integrations** in your dashboard sidebar or visit `/apps`. ## Overview The App Store organizes integrations into categories, making it easy to find and configure the services you need: * **💳 Payments**: Payment processors like Mollie and Stripe * **🌐 Provisioning**: Domain registration and management services like OpenProvider * **📱 All Apps**: View all available integrations in one place ## Available Categories ### Payments Connect payment processors to accept payments from your customers. > [card] Mollie > > **European payment processing powerhouse** > > * iDEAL (Netherlands) > * SEPA Direct Debit > * Credit & Debit Cards > * Bancontact (Belgium) > * And 15+ other methods > > Perfect for EU-based businesses with automatic SEPA mandate management for subscriptions. > [!TIP] > > More payment providers coming soon! We're actively working on expanding our payment processor integrations. ### Provisioning Automate domain registration and management directly from PayRequest. > [card] OpenProvider > > **Domain registration and management** > > * Automatic domain provisioning > * TLD pricing configuration > * DNS management > * SSL certificate support > > Ideal for hosting companies, web agencies, and SaaS platforms offering domain services. ## Connecting Your First App Let's walk through connecting an integration from the App Store. **1. Navigate to App Store** Go to **Sell** → **Services & integrations** in your dashboard sidebar, or visit `/apps`. **2. Browse Available Apps** Use the category tabs to filter apps: * **All integrations**: View everything at once * **Payments**: Filter to payment processors only * **Hosting & domains**: Show domain provisioning * **Other integrations**: Find VPNresellers and other service integrations **3. Click on Your Desired App** Click on any app card to view its detail page with: * Current connection status * Configuration options * Management tools * Setup instructions **4. Connect the App** Follow the app-specific connection process: * For **Mollie**: OAuth connection via "Connect with Mollie" * For **OpenProvider**: Enter API credentials manually * For **VPNresellers**: The business owner enters their reseller API token ## Managing Connected Apps Once an app is connected, you can manage it directly from the App Store. ### Connection Status Apps display clear status badges: * 🟢 **Connected**: App is active and configured * ⚪ **Not Connected**: App needs to be set up * 🟡 **Test Mode**: App is in testing/sandbox mode * 🔴 **Inactive**: App is configured but disabled ### App Management Actions Each connected app provides specific management options: > [accordion] > > **Mollie Management** > > **Available Actions:** > > * View connection status and account details > * Switch between Mollie profiles > * Enable/disable payment methods > * Configure customer sync > * Manage subscription sync > * Test connection > * Disconnect and reconnect > > **Quick Access:** Click the Mollie card → Manage settings > > **OpenProvider Management** > > **Available Actions:** > > * View provider statistics > * Test API connection > * Configure TLD pricing > * Manage default nameservers > * Toggle test/production mode > * Enable/disable provider > * Update credentials > > **Quick Access:** Click OpenProvider card → Configure settings ## App-Specific Guides ### VPNresellers Integration Connect your own API 4.1 token to sell paid monthly or annual VPN subscriptions. Each business uses its own reseller balance. VPN accounts are delivered after confirmed payment, and authorized customers manage passwords and download configurations from **My services → VPN** in the customer portal. Only the business owner can configure the connection and use delivery recovery actions. Open the VPNresellers card or visit `/apps/vpnresellers` to connect, check your balance, create a VPN product and review service delivery. See [VPNresellers](/integrations/vpnresellers) for the complete setup, access rules and troubleshooting guide. ### Mollie Integration Mollie is the recommended payment processor for European businesses. **1. Prerequisites** * Active Mollie account (sign up at [mollie.com](https://www.mollie.com)) * Verified website profile in Mollie dashboard * Approved payment methods **2. Connect via OAuth** 1. Click **Connect with Mollie** in the Mollie app page 2. Log into your Mollie account 3. Authorize PayRequest to access your account 4. Select your default profile **3. Configure Settings** After connection: * **Profile Management**: Switch between multiple Mollie profiles * **Payment Methods**: Enable/disable specific payment methods * **Customer Sync**: Optionally sync customers to Mollie * **Subscription Sync**: Keep PayRequest and Mollie subscriptions in sync **4. Test Your Connection** Use the **Test Connection** button to verify everything works correctly before processing real payments. > [!WARNING] > > **Important**: Always start with test mode enabled. Switch to live mode only after thoroughly testing your payment flow. ### OpenProvider Integration OpenProvider enables automated domain provisioning for your products. **1. Get OpenProvider Credentials** 1. Sign up for an OpenProvider account 2. Navigate to your OpenProvider dashboard 3. Generate API credentials (username & password) **2. Add Provider in PayRequest** 1. Click **Add OpenProvider Credentials** on the OpenProvider app page 2. Enter your provider name (e.g., "My OpenProvider Account") 3. Paste your API username and password 4. Configure default nameservers (optional) 5. Toggle test mode if using sandbox **3. Configure TLD Pricing** After connecting: 1. Click **TLD Management** from the OpenProvider page 2. Sync available TLDs from OpenProvider 3. Set your profit margins per TLD 4. Configure sell prices for each extension **4. Test Connection** Use the **Test Connection** button to verify your credentials work correctly. > [!NOTE] > > OpenProvider automatically provisions domains when customers purchase domain products through your shop. No manual registration needed! ## Connection Status Indicators Understanding what each status means: | Status | Badge | Meaning | | - | - | - | | **Connected** | 🟢 Green | Fully configured and active | | **Not Connected** | ⚪ Gray | Needs configuration | | **Test Mode** | 🟡 Amber | Using sandbox/test credentials | | **Production** | 🔵 Blue | Live mode active | | **Inactive** | ⚪ Gray | Configured but disabled | ## Troubleshooting Common issues and solutions when working with App Store integrations. > [accordion] > > **App shows 'Not Connected' but I configured it** > > **Solution:** > > * Verify your credentials are correct > * Check that the app is set to "Active" status > * For Mollie: Ensure OAuth connection was completed > * Test your connection using the "Test Connection" button > > **Mollie OAuth connection fails** > > **Possible causes:** > > * Incorrect Mollie account permissions > * Browser blocking cookies/redirects > * Mollie account not fully verified > > **Solution:** > > * Use a different browser > * Ensure Mollie account is verified > * Check that website profile is approved in Mollie > > **OpenProvider test connection fails** > > **Possible causes:** > > * Wrong API credentials > * Account not activated > * IP whitelist restrictions > > **Solution:** > > * Double-check username and password > * Verify OpenProvider account is active > * Contact OpenProvider support for IP whitelist issues > > **Can't see my app in the list** > > **Solution:** > > * Check you're looking in the correct category tab > * Use the **All integrations** tab to see everything > * Some apps may require specific plan levels ## Best Practices > [card] Always Test First > > Enable test/sandbox mode before processing real transactions. Verify the entire flow works as expected. > [card] Monitor Connection Status > > Regularly check your app connections in the App Store to ensure everything remains properly configured. > [card] Keep Credentials Secure > > Never share your API credentials. Use environment-specific credentials for testing vs production. > [card] Enable Notifications > > Set up webhook notifications to stay informed about transaction events and sync issues. ## Security Considerations PayRequest takes the security of your integrations seriously: * ✅ **Encrypted Storage**: All credentials are encrypted at rest using AES-256 * ✅ **OAuth Preferred**: We use OAuth 2.0 for Mollie to avoid storing passwords * ✅ **Token Refresh**: Access tokens are automatically refreshed before expiration * ✅ **Audit Logs**: All connection changes are tracked in your activity log * ✅ **Secure Transit**: All API calls use TLS 1.3 encryption > [!WARNING] > > **Never share** your PayRequest API keys or provider credentials with third parties. PayRequest support will never ask for your passwords or access tokens. ## Coming Soon We're actively working on expanding the App Store with new integrations: * 🔜 **Stripe**: Alternative payment processor with global reach * 🔜 **TransIP**: Domain provisioning for Dutch market * 🔜 **Exact Online**: Accounting software integration * 🔜 **Mailchimp**: Email marketing automation > [!TIP] > > Have a specific integration request? [Email us](mailto:support@payrequest.io) with your suggestion! ## Related Documentation > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > Learn about available payment methods > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > Set up custom domains for your shop > [card] [API Reference](/api/overview) > > Integrate with PayRequest API *** > [!NOTE] > > **Quick Navigation**: Open `/apps` or **Sell → Services & integrations** in your dashboard sidebar. ## Hetzner Cloud Connect your own Hetzner Cloud project to view servers, keep private server notes and link existing servers to subscriptions. You can also create VPS products with automatic delivery after confirmed payment. Customer reboot and console access are separate permissions. See [Hetzner Cloud](/integrations/hetzner-cloud) for connection setup, manual linking, paid access, server actions and deletion rules. # Business Details Source: https://docs.payreque.st/business-settings/business-details Set your company identity, tax numbers, bank details, and logo used across invoices and payment pages. # Business Details Your business details identify your company on every invoice, payment page, and customer-facing document PayRequest generates — company name, address, registration numbers, bank details, and logo. > [!NOTE] > > Manage these under **Settings > Business** (`/settings?tab=business`). This tab is only shown for business accounts, not personal accounts. ## Fields You Can Set > [card] Company Info > > Company name, address, country, and preferred language > [card] Registration Numbers > > Company (Chamber of Commerce) number, VAT number, tax number > [card] Bank Details > > IBAN/BIC or local bank account details, depending on your bank's country > [card] Logo > > Upload a logo shown on invoices and your payment pages ## Updating Your Details **1. Go to Settings > Business** Navigate to **Settings** in your dashboard, then select the **Business** tab. **2. Fill in company information** **Company Name** and **Company Address** are required. As you type the address, PayRequest suggests matching addresses to reduce typos. **3. Select your country and language** Choosing a country from the list automatically sets the correct country code. **Language** controls the default language for documents (English, Nederlands, Deutsch, Français, or Español). **4. Add registration and tax numbers (optional)** **Company Number**, **VAT Number**, and **Tax Number** are all optional free-text fields shown on invoices where applicable. **5. Add bank details (optional)** Set your **Bank Country** first — PayRequest shows an IBAN/BIC form for IBAN-zone countries, a routing-number-style form for the US, or a generic account number field for everywhere else. **6. Upload a logo (optional)** Upload an image (max 1MB). It's used on invoices and your payment pages. You can remove it at any time. **7. Save** Click save to persist your changes immediately. ## Bank Detail Format by Country | Bank Country | Fields Shown | | - | - | | **IBAN-zone countries** (NL, DE, BE, FR, etc.) | IBAN, BIC | | **United States** | Bank account holder, account number, routing number | | **Other countries** | Generic account holder and account number fields | > [!NOTE] > > Bank details entered here are for display/reference (e.g. on invoices for manual bank transfer). They are separate from your connected payment providers (Mollie, Ponto, etc.), which handle actual payment processing. ## What's Configured Elsewhere Business Details covers company identity only. Related settings live on their own tabs: * **Invoice numbering, footer text, and IBAN display on invoices** — Settings > Invoice Design, see [Invoice Settings](/business-settings/invoice-settings) * **VAT registration, default tax rate, tax region, and currency** — Settings > Tax & Currency, see [Tax & VAT Guide](/business-settings/tax-vat-guide) ## FAQ > [accordion] Is the logo required? > > No. If you don't upload one, invoices and payment pages display without a logo. > [accordion] What's the maximum logo file size? > > 1MB. If your file is larger, compress or resize it before uploading. > [accordion] Can I have different business details per shop? > > No — Business Details are set once per account and apply across your business. > [accordion] Does changing my address update past invoices? > > No. Already-generated invoices keep the business details that were active when they were created. Only new invoices use the updated details. ## Next Steps > [card] [Invoice Settings](/business-settings/invoice-settings) > > Configure invoice numbering, footer, and display defaults > [card] [Tax & VAT Guide](/business-settings/tax-vat-guide) > > Set up VAT registration and tax defaults > [card] [Team Management](/business-settings/team-management) > > Invite team members to help manage your account > [card] [Email Configuration](/business-settings/email-configuration) > > Control which business notifications you receive by email # Data Import & Export Source: https://docs.payreque.st/business-settings/data-import-export Export your customers, products, subscriptions, invoices, and orders to CSV for backups, accounting, or analysis. # Data Import & Export PayRequest lets you export your core business data — customers, products, subscriptions, invoices, and orders — to CSV files. This is useful for backups, accounting, spreadsheet analysis, or moving data into another tool. > [!NOTE] > > CSV export is available from the **Bulk Actions** page. See [Export Functions](/analytics-and-reporting/export-functions) for the full step-by-step guide, entity-by-entity column reference, and FAQ. ## What You Can Export > [card] Customers > > Name, email, phone, company, language, tax exempt status, tags > [card] Products > > Name, SKU, price, tax rate, type, status, stock, tags > [card] Subscriptions > > Customer, product, amount, interval, status, next billing date, tags > [card] Invoices & Orders > > Amounts, status, dates, and tags Exports can be filtered by tags, so you can pull exactly the subset you need instead of your entire dataset. Full details are in [Export Functions](/analytics-and-reporting/export-functions). ## Other Places You Can Export Data A few other pages in PayRequest offer their own scoped CSV exports: * **Mollie Customers** — export your synced Mollie customer list directly from the Mollie Customers page. See [Customer Sync](/customer-management/customer-sync). * **Tags** — exporting subscriptions, Mollie subscriptions, or products for a specific tag from the tag detail page. ## Importing Data > [!NOTE] > > PayRequest does not currently offer a bulk CSV importer for customers or products. Customers and products are created individually (through the dashboard, a customer's first checkout, or automatically via [Mollie Customer Sync](/customer-management/customer-sync)). If you're migrating from another platform, the practical paths today are: * **Customers**: create them manually, or let them populate automatically as they check out on your payment page or shop * **Products**: recreate them individually using the product wizard — see [Creating Products](/products-and-pricing/creating-products) ## FAQ > [accordion] Can I export everything in one file? > > No. Exports are per entity type (customers, products, subscriptions, invoices, or orders) — you export one type of record at a time as a CSV. > [accordion] What format are exports in? > > CSV, with a UTF-8 byte-order mark so the file opens correctly with accented characters in Excel, Numbers, or Google Sheets. > [accordion] Is there a way to pull data programmatically instead of exporting manually? > > Yes — see the [API Reference](/api/overview) to fetch invoices, payments, and payment links programmatically rather than downloading CSVs. ## Next Steps > [card] [Export Functions](/analytics-and-reporting/export-functions) > > Full step-by-step guide to CSV exports > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > See everything else the Bulk Actions page can do > [card] [Customer Sync](/customer-management/customer-sync) > > Pull your existing Mollie customers into PayRequest > [card] [API Reference](/api/overview) > > Access your billing data programmatically # Email Configuration Source: https://docs.payreque.st/business-settings/email-configuration Control which business notifications you receive by email, and how customer email replies reach you. # Email Configuration PayRequest sends two kinds of email: automated notifications to **you** about events in your business, and transactional emails to your **customers** (invoices, receipts, reminders, etc.). This page covers how to control what you receive and how customer replies reach you — see the linked pages below for customer-facing email content and delivery troubleshooting. > [!NOTE] > > Manage your own notification preferences under **Settings > Notifications** (`/settings?tab=notifications`). ## Notification Settings Choose which business events send you an email, grouped by category: | Category | Example Notifications | | - | - | | **Payments** | Payment received, payment failed, refund processed, chargeback received, manual payment awaiting confirmation | | **Customers** | New customer, customer profile updated | | **Orders** | New order, order completed, order cancelled | | **Subscriptions** | New subscription, subscription renewed, subscription cancelled, subscription payment failed, trial ending soon, monthly subscription report | | **Reports & Digests** | Daily business summary (off by default) | **1. Go to Settings > Notifications** Open **Settings** and select the **Notifications** tab. **2. Toggle notifications on or off** Each notification type has its own switch. Most are enabled by default; the daily business summary is off by default. **3. Changes save instantly** Each toggle saves immediately — there's no separate save button. > [!NOTE] > > Notifications are sent to your account's login email address. Event-based notifications (payment received, new order, new subscription, etc.) are sent as soon as the event happens. The **Daily Business Summary** is sent at 08:00 (Europe/Amsterdam), and the **Monthly Subscription Report** is sent at 08:00 on the 1st of each month. ## Receiving Customer Replies (Email-to-Ticket) Every email PayRequest sends to your customers — invoices, reminders, order confirmations, and more — includes a Reply-To address unique to your business. When a customer replies, it's automatically converted into a support ticket in your dashboard. > [!NOTE] > > This requires no setup — your Reply-To address is generated automatically from your shop name or PayRequest Page handle (e.g. `yourshop@payreque.st`). Full details, including how ticket matching and two-way email conversations work, are covered in [Support Requests](/customer-management/support-requests). ## Customizing Customer-Facing Emails The content and subject line of transactional emails (invoices, reminders, subscription notices, etc.) are customized separately from notification preferences. See [Email Templates](/invoices/email-templates) to edit the wording customers see. > [!NOTE] > > There's currently no setting to change the sending domain or use your own SMTP relay — all business emails are sent through PayRequest's own email infrastructure. ## FAQ > [accordion] Can I send notifications to a different email address than my login email? > > Not currently — notifications go to your account's login email address. > [accordion] Can each team member choose their own notification preferences? > > Notification settings are configured at the account level, not per team member. > [accordion] Why didn't I get a notification for an event I enabled? > > Check [Email Delivery Issues](/troubleshooting/email-delivery-issues) for common causes — spam filtering is the most frequent one. > [accordion] Can I turn off all business notifications at once? > > There's no single master switch — toggle off each notification type individually under Settings > Notifications. ## Next Steps > [card] [Support Requests](/customer-management/support-requests) > > See how customer email replies become support tickets > [card] [Email Templates](/invoices/email-templates) > > Customize the content of customer-facing emails > [card] [Email Automations](/organization-and-automation/email-automations) > > Learn what triggers automated customer emails > [card] [Email Delivery Issues](/troubleshooting/email-delivery-issues) > > Troubleshoot missing or delayed emails # Invoice Settings Source: https://docs.payreque.st/business-settings/invoice-settings Configure your invoice numbering format, sequence, and related defaults # Invoice Settings Invoice numbering is configured per business, so every invoice you create follows a consistent, predictable sequence. > [!NOTE] > > Invoice numbering lives at **Settings → Business → Invoice Design → Numbering**. The same screen also has Logo and Footer tabs for visual branding — see [Invoice Templates](/invoices/invoice-templates). ## Numbering Format **1. Set your invoice number format** Enter a format string using placeholders: * `{NUMBER}` — the sequential number * `{YEAR}` — the current year * `{MONTH}` — the current month For example, `INV-{YEAR}{MONTH}-{NUMBER}` produces numbers like `INV-202607-0001`. **2. Set the next invoice number** This is the sequential number your **next** invoice will use. **3. Set the number padding** Choose how many digits the sequential number is padded to with leading zeros (1–10). A padding of 4 turns `1` into `0001`. **4. Check the live preview** The settings page shows exactly how your next invoice number will look, based on your current format, next number, and padding. ### How the Sequence Resets Your numbering scope is determined automatically by which placeholders you use in the format: | Format includes | Numbering resets | | - | - | | `{MONTH}` | Every month (numbering restarts within each new month) | | `{YEAR}` (no `{MONTH}`) | Every year | | Neither | Never — one continuous global sequence | When generating the next number, PayRequest checks your existing invoices matching the current period's prefix and uses whichever is higher: your stored "next number" setting, or one past the highest number already used. This avoids duplicate invoice numbers even if you've manually edited a number before. > [!NOTE] > > Credit notes draw from the same numbering sequence as regular invoices — creating a credit note also advances your next invoice number. ## Related Invoice Defaults A few other settings affect how new invoices behave, though they live on separate settings screens: | Setting | Location | Effect | | - | - | - | | **Auto-enable payment reminders** | Settings → Business → Payment Reminders | When on, every new invoice you create has payment reminders enabled by default (still adjustable per invoice) | | **Show IBAN on Invoice** | Settings → Business → Invoice Design → Footer | Whether your bank IBAN is printed on invoices, under your VAT number | | **Default tax rate** | Settings → Business → Tax & Currency | The tax rate applied to manually-added invoice items and new products | ## FAQ > [accordion] Can I use letters or symbols other than the placeholders in my format? > > Yes, anything outside of `{NUMBER}`, `{YEAR}`, and `{MONTH}` is treated as literal text — useful for prefixes like `INV-` or separators. > [accordion] What happens if I lower the 'next invoice number' below invoices I already have? > > PayRequest always uses the higher of your stored next number and one past the highest existing invoice number in the current numbering scope, so you won't get a collision with an existing invoice number. > [accordion] Does changing the format retroactively change past invoice numbers? > > No. Existing invoices keep the number they were created with. Only invoices created after the change use the new format. ## Next Steps > [card] [Invoice Templates](/invoices/invoice-templates) > > Customize your invoice's logo and footer > [card] [Creating Invoices](/invoices/creating-invoices) > > Learn the invoice creation flow > [card] [Payment Reminders](/invoices/payment-reminders) > > Configure your automatic reminder schedule > [card] [Tax & VAT Guide](/business-settings/tax-vat-guide) > > Set your default tax rate and VAT registration # Linked Accounts Source: https://docs.payreque.st/business-settings/linked-accounts Link separate PayRequest accounts and switch between businesses or personal pages without signing in again. # Linked Accounts Linked accounts let you move between separate PayRequest accounts without signing out. This is useful when you manage more than one business, or when you have both a business account and a personal PayRequest Page. For example, one login session can give you access to: * Your company account * A second business with its own email address * A personal account with its own `payrequest.me` handle > [!NOTE] > > Linking accounts does not merge them. Each account keeps its own customers, products, invoices, payment providers, subscription, settings, and PayRequest Page. ## Link an Existing Account Both accounts must already exist before you can link them. **1. Open Linked accounts** Click your account name in the top-right corner of the PayRequest dashboard, then select **Linked accounts**. **2. Enter the other account's email address** Under **Link an existing account**, enter the email address used by the other PayRequest account and click **Send confirmation**. **3. Confirm by email** Open the confirmation email sent to the other account and click **Confirm account link**. The confirmation link expires after one hour. **4. Return to PayRequest** Sign in to any linked account. The account menu now includes **Switch account**. > [!WARNING] > > Only link accounts you personally own and trust. Access to one account in a linked group allows switching to the other accounts in that group. ## Switch Accounts 1. Click the current account name in the top-right corner. 2. Open **Switch account**. 3. Select the business or personal account you want to use. PayRequest opens the selected account's dashboard. The account name and email shown in the menu help you confirm which account is currently active. > [!TIP] > > Always check the active account before creating invoices, connecting a payment provider, changing settings, or publishing products. ## What Remains Separate | Account data | Shared after linking? | | - | - | | Customers and contacts | No | | Products and orders | No | | Invoices and transactions | No | | Mollie, Stripe, PayPal, and bank connections | No | | PayRequest plan and billing | No | | Business details and tax settings | No | | PayRequest Page and handle | No | | Login session for switching | Yes | This means switching from a company account to a personal account also switches to that personal account's own products, payment connections, and `payrequest.me` page. ## Unlink an Account 1. Switch to an account that should remain in the linked group. 2. Open **Linked accounts** from the account menu. 3. Find the other account and click **Unlink**. 4. Confirm the action. After unlinking, you must sign in separately to access that account again. No account data is deleted. ## Security * The other account must confirm the initial link through its registered email address. * Confirmation links expire after one hour. * Both accounts receive a security notification after linking. * Account switches are recorded in PayRequest's activity logs. * Team members cannot link accounts or switch into a business owner's other accounts. * PayRequest never links accounts automatically based on a matching name, company domain, customer record, or payment provider. ## Troubleshooting > [accordion] I did not receive the confirmation email > > Check the spam folder and confirm that you entered the email address of an existing PayRequest account. You can submit the request again to receive a new link; the previous link will stop working. > [accordion] The confirmation link expired > > Open **Linked accounts** and send a new confirmation. Each link remains valid for one hour. > [accordion] The account is already part of another linked group > > PayRequest does not automatically combine two existing account groups because that could grant unintended access. Unlink the account from its current group before linking it to a different group. > [accordion] Can a team member use the account switcher? > > No. Linked accounts are intended for an owner managing their own separate PayRequest accounts. Use [Team Management](/business-settings/team-management) to give colleagues controlled access to one business. ## Related Guides > [card] [Business Details](/business-settings/business-details) > > Configure the identity and tax information for each business account > [card] [Team Management](/business-settings/team-management) > > Invite colleagues without linking your owner accounts # PayRequest Plans: Free, Premium & Business Source: https://docs.payreque.st/business-settings/payrequest-plans Compare the Free, Premium, and Business plans and see exactly what each tier unlocks # PayRequest Plans PayRequest offers three tiers: **Free**, **Premium**, and **Business**. Every account starts on the Free plan — you can invoice, take payments, and run a PayRequest Page from day one. Upgrading to Premium removes the per-transaction fee and unlocks features like quotes, digital products, and PayRequest Page visitor analytics. > [!NOTE] > > The Business plan includes Premium features, including AI product websites, plus subscriptions, an online shop and order management. You can order Business from **Settings → PayRequest Plan**. See [Upgrading to Business](#upgrading-to-business) below. ## Plan Comparison | | **Free** | **Premium** | **Business** | | - | - | - | - | | Price | €0/month | €5/month | €20/month | | Transaction fee | 2% per payment | 0% | 0% | | PayRequest Page & payment links | ✅ | ✅ | ✅ | | Basic invoicing | ✅ | ✅ | ✅ | | New security deposit requests per calendar month | 3 | 15 | Unlimited | | Open security deposit requests at a time | 1 | 5 | Unlimited | | Customer management | – | ✅ | ✅ | | Digital products | – | ✅ | ✅ | | AI product websites with hosting | – | ✅ | ✅ | | Activity log | – | ✅ | ✅ | | Quotes | – | ✅ | ✅ | | Bulk actions & exports | – | ✅ | ✅ | | Debt collection | – | ✅ | ✅ | | PayRequest Page visitor analytics | – | ✅ | ✅ | | Manual payment methods (bank transfer instructions, etc.) | – | ✅ | ✅ | | Subscriptions & recurring billing | – | – | ✅ | | Online shop | – | – | ✅ | | Order management | – | – | ✅ | ## Free Plan Every new account starts here. You can create a PayRequest Page, send invoices, and accept payments right away. The trade-off is a **2% fee** on every successful transaction — this is how PayRequest covers its costs for accounts that aren't on a paid plan. There's no monthly charge either way. > [!NOTE] > > Free accounts don't have access to quotes, digital products, bulk actions, debt collection, the activity log, or PayRequest Page visitor analytics. Where these appear in the dashboard, you'll see an **Upgrade to Premium** prompt instead. ## Premium Plan — €5/month Premium removes the 2% transaction fee entirely and unlocks the tools most freelancers and solo businesses need day-to-day: * **Customer management** — full customer profiles instead of just invoice recipients * **Security deposits** — 15 new requests per calendar month, with up to 5 open at a time * **Digital products** — sell downloads and Pay to Unlock images, audio, or video * **Memberships & Community** — sell one recurring membership and create a private welcome page with organized members-only posts * **AI product websites** — generate, edit and publish hosted sales websites from existing products; Business and Growth also qualify. Requires a current paid, non-trial subscription. [View the guide](https://docs.payreque.st/products-and-pricing/ai-product-websites). * **Activity log** — a full audit trail of what happened on your account and when * **Quotes** — send quotes that convert into invoices once accepted * **Bulk actions & exports** — act on many invoices/customers at once, export data * **Debt collection** — automated payment plans and collection workflows for overdue invoices * **PayRequest Page visitor analytics** — see how many people visit your page each day (see below) * **Manual payment methods** — configure your own bank transfer instructions (or other manual instructions) as a payment option on your payment page > [!NOTE] > > The 0% transaction fee and manual payment methods both require an **active or trial subscription** to Premium/Business specifically — not just having `plan_type` set on your account. If your subscription lapses (e.g. a failed renewal payment), these features are gated again until it's active. ### Upgrading to Premium 1. Go to **Settings → PayRequest Plan** 2. Find the **Premium** card and click **Subscribe to Premium** 3. Complete the payment — your account unlocks immediately > [!TIP] > > If you're on Free and click a Premium-gated feature (like Quotes or Bulk Actions), PayRequest redirects you to an upgrade page explaining exactly what you're missing — you don't need to hunt for the billing page yourself. ## Business Plan — €20/month Business adds everything needed to run recurring billing and a full online shop on top of Premium: * **Everything in Premium** * **Unlimited security deposit requests** — no monthly request limit or limit on open requests * **Subscriptions & recurring billing** — Mollie/iDEAL mandates, dunning, pausing, and lifecycle management * **Online shop** — a full storefront beyond the single PayRequest Page * **Order management** — track and fulfill shop orders ### Upgrading to Business 1. Go to **Settings → PayRequest Plan**. 2. Choose **Business** and open its checkout. 3. Complete the subscription purchase. Opening checkout alone does not grant plan access. If you already have Premium, review your current subscription before ordering Business. Ordering another plan does not automatically cancel an existing subscription. Existing Business subscribers keep their current-plan control. ## Security Deposit Allowances Free includes **3 new requests per calendar month and 1 open request at a time**. Premium includes **15 new requests per calendar month and 5 open requests at a time**. Business and Growth include unlimited requests. Pending requests, authorized holds, and partially captured deposits count as open. The monthly allowance resets on the first day of each month. Closing an eligible unused request frees an open slot, but the request still counts toward that month's allowance. View your usage under **Security Deposits** or **Settings → PayRequest Plan**. If you only need a few open requests, Premium provides more room without requiring Business. For unlimited requests, [upgrade to Business](#upgrading-to-business). Existing eligible Premium subscriptions retain unlimited access while that same subscription remains active or in trial and stays on Premium. A plan change does not prevent you from managing, capturing, or releasing existing deposits. Payment-provider fees remain separate from your plan's request allowance. **Saved-card Stripe renewal requires Business.** An allowance for creating deposits, including a grandfathered unlimited allowance, does not enable renewal. For new deposits with prior customer permission, Business can request replacement holds near expiry within a maximum of 30 days from the first authorization. Bank approval and the confirmed provider deadline still apply. See [renew a Stripe deposit](/payment-processing/security-deposits#renew-a-stripe-deposit-on-business). See [Security Deposits](/payment-processing/security-deposits) for request creation, status explanations, and safe closure of unused requests. ## Managing Your Plan Go to **Settings → PayRequest Plan** to see your current plan, payment method, next billing date, and billing history. From there you can also: * **Pause** your subscription (with an optional auto-resume date) * **Resume** a paused subscription * **Cancel** your subscription (you keep access until the end of your current billing period) > [!WARNING] > > Canceling removes access to Premium-only features (quotes, digital products, bulk actions, debt collection, activity log, PayRequest Page analytics) at the end of your billing period, and your account reverts to the Free plan's 2% transaction fee. ## Frequently Asked Questions > [accordion] Can I downgrade from Business to Premium? > > Downgrading from Business isn't available directly in the billing page. Contact [support@payrequest.io](mailto:support@payrequest.io) if you need to change tiers. > [accordion] Does the 2% Free plan fee apply to Premium and Business too? > > No. The 2% per-transaction fee only applies to the Free plan. Premium and Business both have a flat 0% platform fee — your subscription cost is the only fee PayRequest charges. > [accordion] What happens to my data if I cancel? > > Nothing is deleted. Your invoices, customers, and products remain in your account — you simply lose access to Premium-only features and pages until you resubscribe. > [accordion] Can I subscribe to Business from the dashboard? > > Yes. Open Settings → PayRequest Plan and choose Business to open checkout. If you already have another paid subscription, review it before ordering: the existing subscription is not automatically canceled. ## Next Steps > [card] [PayRequest Page Visitor Analytics](/analytics-and-reporting/payrequest-page-visitors) > > See daily visitor counts for your PayRequest Page — a Premium feature > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize the page your visitors and customers see > [card] [Debt Collection](/debt-collection/payment-plans) > > Automated payment plans for overdue invoices — a Premium feature > [card] [Business Details](/business-settings/business-details) > > Configure your business information > [card] [Lock \$PAYR for Free Premium](/integrations/lock-payr-for-premium) > > Get Premium for free by locking \$PAYR tokens on Solana instead of paying by card # Tax & VAT Guide Source: https://docs.payreque.st/business-settings/tax-vat-guide Complete guide to setting up and managing tax collection, VAT compliance, and tax exemptions in PayRequest # Tax & VAT Guide PayRequest provides comprehensive tax handling for businesses of all sizes. Whether you're collecting Dutch BTW, EU VAT, or dealing with international tax exemptions, this guide covers everything you need to know. ## Overview > [card] Automatic Calculations > > PayRequest automatically calculates taxes based on your product settings, customer location, and tax exemption status. > [card] EU VAT Compliant > > Built-in support for EU VAT rules including reverse charge mechanisms for B2B transactions. > [card] Flexible Display > > Choose how prices are displayed to customers - with tax included or shown separately. > [card] Customer Exemptions > > Easy-to-manage tax exemption status for B2B customers and qualifying organizations. ## Setting Up Your Tax Configuration ### Step 1: Configure Business Tax Settings Navigate to **Settings > Tax & Currency** to configure your business-wide tax defaults. **1. Enable VAT Registration** Toggle **VAT Registered** if your business is registered for VAT/BTW. This enables tax collection features across your account. **2. Set Default Tax Rate** Enter your default tax rate (e.g., **21%** for Dutch BTW high rate). This rate will be applied to new products automatically. **3. Specify Tax Region** Select your business location (**NL** for Netherlands, or your EU country code). This affects how taxes are calculated for international customers. **4. Enter Your VAT Number** Add your official VAT/BTW registration number. This appears on invoices and enables VAT validation features. > [!NOTE] > > Your default tax settings serve as templates for new products. You can always override these on individual products. ### Step 2: Configure Product Tax Settings Each product can have its own tax configuration. Go to **Products > Edit Product** to adjust: | Setting | Description | Example | | - | - | - | | **Tax Rate** | The percentage of tax to apply | 21%, 9%, 0% | | **Tax Included** | Whether the displayed price includes tax | Yes (recommended) | > [accordion] Understanding Tax Included vs Excluded > > **Tax Included (Recommended for B2C)** > > When enabled, the price you set is the final price customers see. Tax is calculated backwards from this price. > > * Price set: €121.00 > * Tax rate: 21% > * Net amount: €100.00 > * Tax amount: €21.00 > > **Tax Excluded (Common for B2B)** > > When disabled, the price you set is the net price. Tax is added on top. > > * Price set: €100.00 > * Tax rate: 21% > * Tax amount: €21.00 > * Total: €121.00 ### Step 3: Configure Shop Tax Display Control how prices appear in your shop. Go to **Settings > Shop** and find the **Tax Display** setting: > [tab] Inclusive (Default) > > Prices show the final amount including tax. > > **Customer sees:** > > ``` > Product Name > €121.00 incl. BTW > ``` > > Best for: B2C businesses, consumer-facing shops > [tab] Exclusive > > Prices show the base amount, with tax added at checkout. > > **Customer sees:** > > ``` > Subtotal: €100.00 > BTW (21%): €21.00 > Total: €121.00 > ``` > > Best for: B2B businesses, wholesale pricing ## Dutch BTW (VAT) Rates PayRequest supports all Dutch BTW rates: | Rate | Name | Common Use Cases | | - | - | - | | **21%** | High Rate (Algemeen tarief) | Most goods and services | | **9%** | Low Rate (Verlaagd tarief) | Food, books, medications, hotels | | **0%** | Zero Rate (Nultarief) | Exports, intra-EU B2B supplies | > [!WARNING] > > Always consult with your accountant to determine the correct tax rate for your products or services. ## Tax Exemptions for Customers Some customers may qualify for tax exemption, such as: * B2B customers with valid EU VAT numbers * Non-profit organizations * Government entities * Export customers outside the EU ### Marking a Customer as Tax Exempt **1. Open Customer Profile** Navigate to **Customers** and select the customer you want to mark as exempt. **2. Enable Tax Exemption** In the customer details, toggle **Tax Exempt** to enabled. **3. Document the Reason** Add a note explaining why this customer is tax exempt (e.g., "Valid EU VAT number verified" or "Non-profit organization"). ### What Happens When a Customer is Tax Exempt? When you create invoices or process orders for tax-exempt customers: * All tax rates are automatically set to **0%** * Invoice line items show **"BTW VERLEGD"** (Tax Reversed) * The invoice total excludes tax * Cart and checkout calculations reflect zero tax > [!NOTE] > > Tax exemption status is checked automatically at checkout. Exempt customers always see tax-free prices. ### Bulk Tax Exemption Updates Need to update multiple customers at once? Use the **Bulk Actions** feature: 1. Go to **Customers** 2. Select multiple customers using checkboxes 3. Click **Bulk Actions** 4. Choose **Toggle Tax Exempt** ## EU VAT Rules PayRequest implements standard EU VAT rules for cross-border transactions: ### B2C Sales (Business to Consumer) | Your Location | Customer Location | Tax Applied | | - | - | - | | Netherlands | Netherlands | Dutch BTW (21%) | | Netherlands | Other EU Country | Dutch BTW (21%)\* | | Netherlands | Outside EU | 0% (Export) | \*Note: For high-volume sellers, One-Stop-Shop (OSS) rules may apply. ### B2B Sales (Business to Business) | Your Location | Customer Location | Tax Applied | | - | - | - | | Netherlands | Netherlands | Dutch BTW (21%) | | Netherlands | Other EU Country with VAT | 0% (Reverse Charge) | | Netherlands | Outside EU | 0% (Export) | > [accordion] About Reverse Charge (BTW Verlegd) > > When selling B2B to customers in other EU countries who have a valid VAT number, the reverse charge mechanism applies: > > * You charge **0% VAT** on the invoice > * The invoice shows **"BTW VERLEGD"** or "VAT Reverse Charge" > * The customer accounts for VAT in their own country > * You must verify the customer's VAT number is valid > > **To apply reverse charge in PayRequest:** > > 1. Mark the customer as **Tax Exempt** > 2. Store their EU VAT number in the customer profile > 3. Add a note confirming VAT number validation ### Supported EU Countries PayRequest recognizes all 27 EU member states: > [accordion] View Full Country List > > | Code | Country | > | - | - | > | AT | Austria | > | BE | Belgium | > | BG | Bulgaria | > | HR | Croatia | > | CY | Cyprus | > | CZ | Czech Republic | > | DK | Denmark | > | EE | Estonia | > | FI | Finland | > | FR | France | > | DE | Germany | > | GR | Greece | > | HU | Hungary | > | IE | Ireland | > | IT | Italy | > | LV | Latvia | > | LT | Lithuania | > | LU | Luxembourg | > | MT | Malta | > | NL | Netherlands | > | PL | Poland | > | PT | Portugal | > | RO | Romania | > | SK | Slovakia | > | SI | Slovenia | > | ES | Spain | > | SE | Sweden | ## Tax on Invoices ### How Tax Appears on Invoices Your customers see a clear tax breakdown on every invoice: ``` ┌─────────────────────────────────────────┐ │ INVOICE #2025-001 │ ├─────────────────────────────────────────┤ │ Product/Service Qty Amount │ │ Web Hosting (Monthly) 1 €100.00 │ │ Domain Registration 1 €15.00 │ ├─────────────────────────────────────────┤ │ Subtotal €115.00 │ │ BTW 21% €24.15 │ │ Total €139.15 │ └─────────────────────────────────────────┘ ``` For tax-exempt customers: ``` ┌─────────────────────────────────────────┐ │ INVOICE #2025-002 │ │ BTW VERLEGD │ ├─────────────────────────────────────────┤ │ Product/Service Qty Amount │ │ Consulting Services 5 €500.00 │ ├─────────────────────────────────────────┤ │ Subtotal €500.00 │ │ BTW (0% - Verlegd) €0.00 │ │ Total €500.00 │ └─────────────────────────────────────────┘ ``` ### Per-Line Tax Rates Different products on the same invoice can have different tax rates: ``` ┌─────────────────────────────────────────────────┐ │ Product Tax Rate Amount │ ├─────────────────────────────────────────────────┤ │ Software License 21% €100.00 │ │ Training Manual (Book) 9% €25.00 │ │ Export Shipping 0% €15.00 │ ├─────────────────────────────────────────────────┤ │ BTW Breakdown: │ │ 21% over €100.00 €21.00 │ │ 9% over €25.00 €2.25 │ │ 0% over €15.00 €0.00 │ │ Total BTW €23.25 │ │ Total €163.25 │ └─────────────────────────────────────────────────┘ ``` ## Setup Fees and Tax [Setup fees](/products-and-pricing/setup-fees) are taxed at the same rate as their parent product. If a product has: * Price: €50.00/month at 21% BTW * Setup fee: €100.00 (named "Borg" or "Installation Fee") The setup fee will also be taxed at 21%. > [!NOTE] > > Setup fees with custom names (like "Borg" or "Onboarding Fee") appear with their custom name on invoices, making it clear what the customer is paying for. ## Tax in the Shopping Cart During checkout, customers see a complete tax breakdown. The cart displays: * Individual product prices * Setup fees (if applicable) * Custom field markups * Tax amount calculated * Total including tax ## Common Tax Scenarios > [accordion] Selling to Dutch Consumers (B2C) > > **Setup:** > > * Tax Rate: 21% > * Tax Included: Yes > * Customer: Not tax exempt > > **Result:** Customer pays the displayed price, which includes 21% BTW. > [accordion] Selling to Dutch Businesses (B2B) > > **Setup:** > > * Tax Rate: 21% > * Customer: Regular Dutch business (not exempt) > > **Result:** Customer pays 21% BTW. They can reclaim this on their own VAT return. > [accordion] Selling to EU Business with VAT Number > > **Setup:** > > * Customer: Marked as Tax Exempt > * Customer's EU VAT number recorded > > **Result:** 0% VAT applied (reverse charge). Invoice shows "BTW VERLEGD". > [accordion] Selling Outside the EU > > **Setup:** > > * Customer country: Outside EU (e.g., USA, UK) > * Customer: Should be marked as Tax Exempt > > **Result:** 0% VAT applied (export). No Dutch BTW on exports. > [accordion] Selling Reduced-Rate Products > > **Setup:** > > * Product Tax Rate: 9% > * Examples: Books, food, medications > > **Result:** 9% BTW applied instead of standard 21%. ## Best Practices > [card] Verify VAT Numbers > > Always validate EU VAT numbers before applying tax exemption. Use the [VIES VAT validation service](https://ec.europa.eu/taxation_customs/vies/). > [card] Document Exemptions > > Keep records of why each customer is tax exempt. Add notes to customer profiles with validation dates. > [card] Review Periodically > > VAT numbers can become invalid. Review tax-exempt customers periodically to ensure continued compliance. > [card] Consult Professionals > > Tax laws are complex and change frequently. Work with an accountant familiar with Dutch and EU VAT regulations. ## Troubleshooting > [accordion] Tax not being calculated > > **Check these settings:** > > 1. Is your business marked as VAT Registered in Settings? > 2. Does the product have a tax rate set? > 3. Is the customer accidentally marked as Tax Exempt? > [accordion] Wrong tax rate appearing > > **Possible causes:** > > 1. Product has a different tax rate than your default > 2. Customer has specific tax settings > 3. Country-based tax rules are being applied > > **Solution:** Check the product's individual tax settings and the customer's tax exemption status. > [accordion] Tax Exempt customer still seeing tax > > **Check:** > > 1. Is the Tax Exempt toggle actually enabled on the customer profile? > 2. Was the invoice/order created before the exemption was set? > 3. Clear any cached cart data and try again > [accordion] Invoice shows wrong tax amount > > **Verify:** > > 1. Check if Tax Included is set correctly on the product > 2. Ensure the tax rate matches what you expect > 3. For existing invoices, you may need to edit and recalculate ## Related Documentation > [card] [Tax Exemptions](/customer-management/tax-exemptions) > > Detailed guide on managing customer tax exemptions > [card] [Invoice Tax Configuration](/invoices/tax-configuration) > > How tax is configured and displayed on invoices > [card] [Setup Fees](/products-and-pricing/setup-fees) > > Configure one-time setup fees with custom names > [card] [Business Details](/business-settings/business-details) > > Configure your business information including VAT number *** > [!NOTE] > > Tax regulations vary by country and situation. This documentation provides general guidance on PayRequest's tax features. Always consult with a qualified tax professional for advice specific to your business. # Team Management Source: https://docs.payreque.st/business-settings/team-management Invite team members and manage permissions for your business # Team Management Add team members to help manage your PayRequest business. Assign roles and control exactly what each team member can access and modify. ## Overview Team management allows you to: * Invite colleagues to your dashboard * Assign predefined roles or custom permissions * Control access to specific features * Suspend or remove team members * Track pending invitations ## Inviting Team Members ### Send an Invitation 1. Navigate to **Settings** → **Team** 2. Click **Invite Team Member** 3. Enter the team member's email address 4. Select a role (or customize permissions) 5. Click **Send Invitation** The invited person receives an email with a link to join your team. ### Invitation Status | Status | Description | | - | - | | **Pending** | Invitation sent, awaiting acceptance | | **Accepted** | Team member has joined | | **Expired** | Invitation link has expired | ### Resend or Cancel For pending invitations: * **Resend**: Send the invitation email again * **Cancel**: Remove the invitation entirely ## Roles and Permissions ### Predefined Roles Choose from these standard roles: | Role | Description | | - | - | | **Admin** | Full access to everything | | **Manager** | View and edit most features, limited settings | | **Sales** | Focus on products, customers, and orders | | **Support** | View-only access for customer support | | **Custom** | Build your own permission set | ### Admin Role Full access including: * All product operations (create, edit, delete) * All customer management * All invoice operations * All order operations * Subscription management * Settings access * Reports and analytics ### Manager Role Standard management access: * Products: View, create, edit * Customers: View, create, edit * Invoices: View, create, edit * Orders: View, edit * Subscriptions: View, edit * Settings: View only * Reports: Full access ### Sales Role Sales-focused permissions: * Products: View, create * Customers: View, create, edit * Invoices: View, create * Orders: View, create * Subscriptions: View * Reports: View ### Support Role Read-only for customer assistance: * Products: View * Customers: View * Invoices: View * Orders: View * Subscriptions: View ### Custom Permissions Build a custom permission set by toggling individual permissions: **Products** * View products * Create products * Edit products * Delete products **Customers** * View customers * Create customers * Edit customers * Delete customers **Invoices** * View invoices * Create invoices * Edit invoices * Delete invoices **Orders** * View orders * Create orders * Edit orders **Subscriptions** * View subscriptions * Edit subscriptions * Cancel subscriptions **Settings** * View settings * Edit settings **Reports** * View reports and analytics ## Managing Team Members ### View Team Navigate to **Settings** → **Team** to see: * Active team members * Their assigned roles * Current status * Pending invitations ### Suspend a Member Temporarily disable access without removing: 1. Find the team member 2. Click the status toggle 3. Member is suspended (can be reactivated) Suspended members cannot log in until reactivated. ### Remove a Member Permanently remove access: 1. Find the team member 2. Click **Remove** 3. Confirm removal > [!WARNING] > > **Permanent Action**: Removing a team member deletes their access permanently. You'll need to send a new invitation if you want to add them back. ### Edit Permissions To change a team member's role or permissions: 1. Click on the team member 2. Update their role or toggle individual permissions 3. Save changes Changes take effect immediately on their next page load. ## Team Member Experience ### Accepting an Invitation When someone receives a team invitation: 1. They click the link in the email 2. Create a password (if new to PayRequest) 3. Accept the invitation 4. Gain access to your dashboard ### Dashboard Access Team members see a version of the dashboard filtered by their permissions: * Hidden features they can't access * Read-only views for view-only permissions * Full edit capabilities where permitted ### Switching Businesses If a team member is invited to multiple businesses: * They can switch between them * Each business has separate permissions * Data is completely isolated ## Best Practices > [card] Principle of Least Privilege > > Give team members only the permissions they need > [card] Use Predefined Roles > > Start with predefined roles before customizing > [card] Regular Review > > Periodically review team member access > [card] Suspend Before Remove > > Suspend first if unsure about removing access ## Common Use Cases ### Virtual Assistant * **Role**: Support or Custom * **Permissions**: View customers, view invoices, view orders * **Purpose**: Answer customer questions without making changes ### Accountant * **Role**: Custom * **Permissions**: View invoices, view reports, view settings * **Purpose**: Financial oversight and reporting ### Sales Team * **Role**: Sales * **Permissions**: Full product and customer access * **Purpose**: Create products and manage customer relationships ### Operations Manager * **Role**: Manager * **Permissions**: Most features except settings * **Purpose**: Day-to-day business operations ## Security Considerations ### Email Verification Team members must verify their email to accept invitations. ### Invitation Expiry Invitations expire after a set period for security. Resend if needed. ### Activity Logging All team member actions are logged in the activity feed for audit purposes. ### Password Requirements Team members must create secure passwords meeting minimum requirements. ## Troubleshooting ### Invitation Not Received * Check spam/junk folder * Verify email address is correct * Resend the invitation * Ask team member to whitelist PayRequest emails ### Cannot Access Features * Verify assigned role includes needed permissions * Check if account is suspended * Confirm invitation was accepted (not just clicked) ### Forgot Password Team members can use the password reset flow on the login page. ## Related Topics > [card] [Business Details](/business-settings/business-details) > > Configure your business information > [card] [Activity Tracking](/organization-and-automation/activity-tracking) > > Monitor team member actions > [card] [Two-Factor Authentication](/security-and-compliance/two-factor-authentication) > > Secure team member accounts > [card] [Audit Logs](/security-and-compliance/audit-logs) > > Review all account activity # Category Display Types Source: https://docs.payreque.st/categories/display-types Learn how to customize how your products are displayed in different categories using Cards, List, or Price Table layouts # Category Display Types PayRequest offers three different ways to display your products within categories, allowing you to choose the best layout for each type of product you sell. ## Available Display Types ### Cards Layout (Default) The Cards layout displays your products in a grid format with product images, names, and prices in individual cards. This is the most visually appealing option and works well for most product types. **Best for:** * Physical products with images * Digital products and services * General merchandise * When you want a modern, visual shopping experience ### List Layout The List layout shows your products in a horizontal format with the image on the left and product details on the right. This compact view allows customers to quickly scan through multiple products. **Best for:** * Services and consultations * Digital downloads * Products where detailed descriptions are important * When you have many products in a category ### Price Table Layout The Price Table layout displays your products in a structured comparison table with feature-by-feature comparison, pricing, and action buttons. Each feature is shown as a row with checkmarks or values for each product, making it easy for customers to understand what's included in each plan. **Best for:** * Subscription plans and pricing tiers * Service packages with different features * Software licenses with various capabilities * Membership options with different benefits * When customers need to compare features side-by-side * SaaS products with multiple plan tiers ## How to Set Category Display Types 1. **Navigate to Categories** * Go to your dashboard * Click on "Categories" in the sidebar 2. **Create or Edit a Category** * Click "Create Category" for a new category, or * Click "Edit" next to an existing category 3. **Choose Display Type** * In the category form, find the "Display Type" field * Select from the dropdown: * **Cards** - Grid layout with product cards * **List** - Horizontal list layout * **Price Table** - Structured table layout 4. **Configure Features (Price Table Only)** * If you selected "Price Table", you'll see a "Features" section * Add the features you want to compare across products * Each feature will become a row in your pricing table * Examples: "Storage", "Users", "Support", "API Access" 5. **Save Your Changes** * Click "Create Category" or "Update Category" * Your category will now display products using the selected layout ## Examples in Action ### Cards Layout Example Perfect for an "Accessories" category where customers browse visually: * Product images are prominently displayed * Clean grid layout * Easy to browse and discover products ### List Layout Example Ideal for a "Services" category where details matter: * Detailed descriptions visible at a glance * Compact view showing more products per page * Professional appearance for service-based businesses ### Price Table Example Perfect for a "Plans" or "Memberships" category: * **Product columns** show plan names, descriptions, and pricing * **Feature rows** display each feature with checkmarks (✓) or values * **Visual comparison** makes it easy to see what's included * **Setup fees** automatically displayed if configured * **Clear action buttons** for subscribing or purchasing * **Professional SaaS-style** presentation that customers expect ## Setting Up Price Table Features When using the Price Table layout, you can define features that will be compared across all products in the category. This creates a professional comparison table that helps customers understand the differences between your plans or products. ### Adding Features to a Category 1. **Edit Your Category** * Go to Categories in your dashboard * Click "Edit" on a category with "Price Table" display type 2. **Configure Features** * Scroll to the "Features" section * Click "Add Feature" to add a new feature * Enter feature names like: * "Storage Space" * "Number of Users" * "Email Support" * "API Access" * "Custom Branding" 3. **Save Category** * Click "Update Category" to save your features ### Setting Feature Values for Products After defining features in your category, you need to set the values for each product: 1. **Edit a Product** * Go to Products in your dashboard * Click "Edit" on a product in your price table category 2. **Configure Feature Values** * Scroll to the "Features" section * You'll see all features defined in the category * Set values for each feature: * **Text values**: "100GB", "Unlimited", "24/7" * **Yes/No features**: Leave blank for ✗ (no), add any text for ✓ (yes) * **Numeric values**: "5 users", "\$50/hour" 3. **Save Product** * Click "Update Product" to save feature values ### How Features Display In your shop's price table: * **Feature names** appear as row headers on the left * **Feature values** show in each product column * **Checkmarks (✓)** appear for features with values * **X marks (✗)** appear for empty/missing features * **Setup fees** automatically display if configured on products ### Feature Management Tips **Naming Features** * Use clear, descriptive names * Keep names concise for mobile display * Use consistent terminology across features **Setting Values** * Leave features blank if not included in a plan * Use consistent units (GB, users, hours, etc.) * Add qualifiers when helpful ("Email support", "Priority support") **Feature Order** * List most important features first * Group related features together * Put pricing-related features (like usage limits) early ### Updating Features **Adding New Features** * Edit the category and add new features * Existing products will show ✗ for new features until you set values * Edit each product to add values for new features **Renaming Features** * Edit the category and change feature names * The system automatically updates product features to use new names * Existing feature values are preserved during renames **Removing Features** * Remove features from the category * Feature data is automatically removed from all products in the category ## Tips for Choosing the Right Display Type ### Consider Your Products * **Visual products** (clothing, electronics, etc.) → Use **Cards** * **Services or consultations** → Use **List** * **Plans or tiers** → Use **Price Table** ### Think About Your Customers * **Browsing behavior** → Cards work well for discovery * **Comparison shopping** → Price tables help with decisions * **Quick scanning** → Lists provide efficient overview ### Match Your Brand * **Modern, visual brand** → Cards layout * **Professional services** → List or Price Table * **SaaS or subscription business** → Price Table ## Advanced Tips ### Category Descriptions When using different display types, make sure your category descriptions help guide customers: * For Cards: Focus on the product category benefits * For Lists: Explain what makes your services unique * For Price Tables: Highlight what customers can compare ### Product Information Ensure your products have the right information for each display type: * **Cards**: Good images and clear names * **Lists**: Detailed descriptions * **Price Tables**: Clear feature lists and pricing ### Customer Experience You can use different display types for different categories in the same shop to create the best experience for each type of product you offer. ## Troubleshooting **Q: Can I change the display type after creating a category?** A: Yes! You can edit any category and change its display type at any time. When switching to Price Table, you'll need to add features. **Q: Do all products show the same information in each layout?** A: The layouts show different amounts of detail. Cards show basic info, Lists show more description, and Price Tables show features and structured information. **Q: What happens when I rename a feature in a category?** A: The system automatically updates all products in that category to use the new feature name while preserving the existing values. **Q: Can I reorder features in the price table?** A: Yes, edit the category and drag features to reorder them. The new order will appear in your price table. **Q: What if I delete a feature from a category?** A: The feature and all its values will be removed from all products in that category. This action cannot be undone. **Q: Why don't some products show checkmarks for features?** A: Products show checkmarks (✓) only for features that have values set. Edit the product and add values for features you want to show as included. **Q: Can I preview how a category will look before saving?** A: After saving your category settings, visit your shop to see how the category appears to customers. **Q: What happens if I have products with missing information?** A: Each layout gracefully handles missing information. For Price Tables, missing feature values show as ✗ marks. For best results, ensure your products have complete feature information. ## Price Table Best Practices ### Feature Examples by Industry **SaaS/Software Products** * Storage: "10GB", "100GB", "Unlimited" * Users: "1 user", "10 users", "Unlimited" * API Calls: "1,000/month", "10,000/month", "Unlimited" * Support: "Email", "Priority", "24/7 Phone" **Service Businesses** * Response Time: "48 hours", "24 hours", "Same day" * Revisions: "2 revisions", "5 revisions", "Unlimited" * Meeting Time: "30 min", "1 hour", "2 hours" * Deliverables: "Basic report", "Detailed analysis", "Full strategy" **Membership/Subscription** * Access Level: "Basic", "Premium", "VIP" * Content: "Weekly", "Daily", "Real-time" * Downloads: "5/month", "25/month", "Unlimited" * Community: "Forum access", "Priority support", "1-on-1 calls" ### Visual Design Tips **Feature Naming** * Keep feature names under 20 characters when possible * Use title case: "Email Support" not "email support" * Be specific: "24/7 Phone Support" not just "Support" **Value Formatting** * Use consistent units across similar features * Include qualifiers: "Priority email support" vs just "Email" * Use "Unlimited" instead of very large numbers * Keep values concise for mobile readability **Category Organization** * Put your most popular plan in the middle for emphasis * Order plans from basic to premium (left to right) * Highlight differences between adjacent plans * Consider setup fees and trial periods in your planning ### Common Patterns **Free Trial Indicators** * Add "Free Trial" as a feature if applicable * Set values like "14 days", "30 days", or "No trial" **Setup Fees** * Setup fees automatically display in the table * No need to add "Setup Fee" as a manual feature **Popular Plan Highlighting** * Use clear naming: "Starter", "Professional", "Enterprise" * Consider badges or special styling for recommended plans This comprehensive comparison table approach helps customers make informed decisions and can significantly improve conversion rates for subscription and service-based businesses. # Changelog Source: https://docs.payreque.st/changelog Track PayRequest platform updates, new features, and improvements # Changelog 📝 Stay up-to-date with the latest PayRequest improvements and new features. We're constantly enhancing your billing experience. **2026-11-13** Page setup, server care and request inbox ## Clearer setup and daily operations * **One onboarding flow** asks new accounts to explicitly save their Page title and handle after payment setup, with an optional avatar. * **Server care & SLA** brings Hetzner and DigitalOcean inventory together, with provider filters, manually recorded backup and update checks, and configurable intervals that default to weekly. * **Request inbox categories** separate support and cancellations, with category-specific folder counts and a To reply view. * **Invoice-paid email preferences** are respected before queueing and again at delivery. Customers can keep new-invoice emails while disabling payment confirmations. [Onboarding](/getting-started/onboarding) · [Server care](/integrations/server-care) · [Support requests](/customer-management/support-requests) **2026-11-11** PDF reading and video seasons ## More ways to deliver paid content * **PDF covers** can be generated from the first page while preserving manual covers. Buyers can use **Read edition** to open a purchased single PDF in their browser under the existing access limits. * **Video series** group existing videos into an ordered season, with free opening episodes and one-time paid season access on the product page. [Sell PDFs](/products-and-pricing/selling-pdfs) · [Video series](/products-and-pricing/video-series) **2026-10-02** Repeat customer payments ## Request Another Payment From an Existing Customer * **Request payment again** opens a draft using the customer's latest eligible payment, with the customer, amount, currency, and description filled in. Choose a different payment from the five recent entries on their profile. * **No product setup required** — the draft is a one-time Amount Link. Review and edit it before creating the link; opening the draft does not save or send anything. * **Clearer Payment Links overview** — see the customer, requested amount, payment status, last activity, and revenue. Search by customer and filter paid requests or links without a linked payment. * **Direct actions** — copy a checkout link, request another payment, or open reminder settings for eligible unpaid links. * **Recorded payment status** — overview figures use linked paid transactions. Historical payments without a link connection remain in the customer's payment history. [Customer profile guide](/customer-management/customer-profiles#request-payment-again) · [Payment Links overview](/payment-processing/smart-links#payment-links-overview) **2026-08-13** v3.31.0 ## Community — A Private Home for Paying Members Turn one recurring membership into a simple private mini-site that lives inside your existing PayRequest Page. ### What's New * **Private Community tab** — visitors see the membership offer; active members see the protected content area * **Welcome page** — add formatted welcome content and an optional YouTube or Vimeo video * **Organized sections** — group members-only posts into topics such as Breakfast, Lunch, Dinner, or Tips & tricks * **One central setup screen** — manage the membership name, description, image, price, interval, benefits, welcome page, and sections under **Community** * **Shared Page design** — Community automatically uses the same banner, avatar, theme, profile, and navigation as your PayRequest Page * **Automatic access control** — successful membership payment unlocks content; access ends when the subscription is no longer active * **Always-available login** — customer login stays visible while Community is published * **Download library** — logged-in customers can return to digital products they purchased under **My downloads** * **Included with Premium** — Community and membership publishing are available on Premium and higher plans [Full Community documentation](/shop-and-checkout/community) **2026-07-16** v3.30.0 ## Pay to Unlock (Video) — Sell Videos Behind a Teaser Upload a full video, let customers watch a short teaser for free, and deliver the private original automatically after payment. ### What's New * **New product type: Pay to Unlock (Video)** — available from **Products → New Product** alongside the image and audio variants * **Automatic video teaser** — choose a free preview length up to 60 seconds; PayRequest detects the full video's duration and never offers a teaser longer than the source * **Private original** — the public player never receives the full video URL; the MP4, MOV, WebM, or M4V original stays private until payment * **Optional cover art** — add a separate image for product cards and listings * **Instant delivery** — buyers receive the full original through the existing secure download-token flow * **Clearer names** — the original photo option is now called **Pay to Unlock (Image)**, next to **Audio** and **Video** [Full documentation](/products-and-pricing/pay-to-unlock#pay-to-unlock-video) **2026-07-13** v3.29.0 ## Product Photo Gallery — Add Multiple Photos Per Product Products can now show more than one photo. Upload up to 8 photos per product instead of just one — the first photo is always the cover shown in your shop, and customers browsing your checkout page can click through the rest in a simple carousel. ### What's New * **Multiple photos per product** — upload up to 8 photos instead of one, for every product type except Pay to Unlock Image, Audio, Video, and AI Prompts (which each have their own single-image behavior) * **First photo is the cover** — no separate "featured image" step; whichever photo is first in the gallery is automatically used in shop listings, product cards, and the Marketplace * **Reorder and remove** — when editing a product, use the arrow buttons to reorder photos or the × button to remove one * **AI-generated photos join the gallery** — clicking **Generate with AI** adds the generated image as your new cover photo instead of replacing a single image field * **Checkout carousel** — products with more than one photo show a carousel with arrows and dot indicators on your checkout page; single-photo products look exactly as before ### How It Works 1. Create or edit a product and upload one or more photos in the **Product Images** field 2. Drag to reorder, or click **×** to remove a photo you don't want anymore 3. The first photo in the list is automatically your product's cover image everywhere it's shown 4. Customers see a swipeable carousel on checkout for any product with more than one photo [Full documentation](/products-and-pricing/creating-products#product-photo-gallery) **2026-07-12** v3.28.0 ## AI Prompts — Sell Your ChatGPT, Midjourney, and Claude Prompts A new product type for selling the prompts you've engineered for AI tools. Customers see a teaser you write yourself, then pay to instantly unlock the full prompt with a one-click copy button — plus a dedicated Marketplace category so people who don't already know you can discover it. ### What's New * **New product type: AI Prompts** — sell a prompt written for ChatGPT, Claude, Gemini, Midjourney, Stable Diffusion, DALL·E, Suno, Runway, and more, grouped by whether the AI produces text, images, audio, or video * **Teaser, not a leak** — you write the pre-payment preview yourself; PayRequest never shows a snippet of the real prompt text, so the wording stays yours until it's paid for * **Instant unlock** — after payment, the full prompt appears on the confirmation page with a **Copy Prompt** button, and is also emailed as a text file * **Customer portal access** — customers can return to their order history any time to re-copy a purchased prompt * **AI Prompts Marketplace category** — list your prompt on [payrequest.me/marketplace](https://payrequest.me/marketplace) under one of 10 categories: Marketing & Sales, Content & Social Media, Business & Productivity, Ecommerce, Coding & Automation, Image & Design, Video & Animation, Writing & Research, Education & Career, or Audio & Music ### How It Works 1. Create a new product and select **AI Prompt** as the type 2. Choose the target AI model, pick a category, and write a short teaser 3. Paste the full prompt text — it's stored privately and only revealed after payment 4. Optionally turn on **List on Marketplace** and pick an AI Prompts category to reach new buyers [Full documentation](/products-and-pricing/ai-prompts) **2026-07-07** v3.27.0 ## PayRequest Page Visitor Analytics, Plan Rename, and Business Plan by Request See how many people visit your PayRequest Page every day with a new **Analytics** tab. Alongside it, the self-billing plan is now clearly named **Premium**, and the **Business** plan moves to a request-only model instead of self-serve checkout. ### What's New * **Visitor analytics** — a new **Analytics** tab on your PayRequest Page shows a daily chart of unique visitors over the last 16 days, plus a total for the period * **Privacy-friendly counting** — visits are deduplicated per day using a hashed IP + browser combination; raw IP addresses are never stored, and your own visits while logged in don't count * **Premium plan feature** — visitor analytics is included with Premium and Business; Free plan accounts see the chart blurred with an **Upgrade to Premium** button * **Premium plan naming finalized** — the €5/month self-billing plan (previously internally referred to as "Freelancer") is now consistently labeled **Premium** everywhere, including a clearer Free-vs-Premium-vs-Business comparison on the billing page * **Business plan is now request-only** — the €20/month Business plan (subscriptions, online shop, order management) is no longer a self-serve checkout; existing subscribers are unaffected, and new customers request access via [support@payrequest.io](mailto:support@payrequest.io) ### How It Works 1. Go to **PayRequest Page → Analytics** to see your visitor chart 2. Go to **Settings → PayRequest Plan** to compare Free, Premium, and Business and manage your subscription 3. Need Business features? Email [support@payrequest.io](mailto:support@payrequest.io) to request access [Full documentation](/analytics-and-reporting/payrequest-page-visitors) · [Plan comparison](/business-settings/payrequest-plans) **2026-07-07** v3.26.0 ## README Badge — Link Back to Your PayRequest Page from Anywhere A copy-paste badge for your GitHub README, website, or bio that links straight to your PayRequest Page — plus a faster way to switch between Products, Amounts, and Donation mode. ### What's New * **README badge** — a new card on the **PayRequest Page → Overview** tab gives you a ready-made Markdown snippet, already filled in with your handle and link * **Live on Donation Mode** — if your page is running a donation goal, the badge automatically shows the current amount raised, no manual updates needed * **Works anywhere Markdown or images do** — GitHub, GitLab, npm package READMEs, blogs, or plain websites * **Page Mode quick-toggle** — switch your page between **Products & services**, **Amount buttons**, and **Donation mode** with one click from the Overview tab sidebar, without opening Settings * **Cleaner Overview tab** — the products list section now only shows when your page is actually in Products mode ### How It Works 1. Go to **PayRequest Page → Overview** 2. Find the **README badge** card in the sidebar and copy the snippet 3. Paste it into your GitHub README (or anywhere else that renders Markdown or images) 4. Optionally switch to **Donation mode** first from the **Page Mode** card so the badge shows your live fundraising total [Full documentation](/shop-and-checkout/readme-badge) **2026-07-06** v3.25.0 ## PayRequest Upload — Drop a File, Get a Payment Link A new, WeTransfer-style way to sell a single file: drop it in, set a price, and share the link — no product wizard, no shop setup. Open to everyone at [payrequest.me/upload](https://payrequest.me/upload); you only need a PayRequest account at the very last step. ### What's New * **One-page upload flow** — drag and drop almost any file type (documents, audio, video, images, archives, fonts, 3D models) up to 250MB * **Auto-filled details** — the title is pre-filled from your filename and the file's category is detected automatically, both editable before you publish * **Pay to Unlock, built in** — for photos and audio tracks, a one-click toggle sells the file behind a free preview instead of an instant download * **Sign in without losing your upload** — clicking Generate Payment Link while signed out prompts you to sign in or register on the main app; once done, you're brought straight back to finish publishing * **Zero setup** — creates a normal product and a Smart Link automatically, and provisions a PayRequest Page handle if your account doesn't have one yet, so the link works immediately ### How It Works 1. Go to **payrequest.me/upload** and drop your file 2. Confirm the auto-filled title and set a price 3. Optionally turn on Pay to Unlock for photos or audio 4. Click **Generate Payment Link** — sign in first if prompted 5. Share your new link: `payrequest.me/[handle]/[filename]` [Full documentation](/products-and-pricing/quick-upload) **2026-07-05** v3.24.0 ## Pay to Unlock (Audio) — Sell Tracks Behind a Free Preview The **Pay to Unlock** product type now supports audio, not just photos. Upload a full track and PayRequest automatically generates a short, free preview clip — customers listen before they buy, then unlock the full track after payment. ### What's New * **New product type: Pay to Unlock (Audio)** — create it from **Products → New Product** alongside the existing photo Pay to Unlock type * **Automatic preview clips** — upload the full MP3, WAV, or FLAC track; a short public preview (5–60 seconds, default 25s, with a fade-out) is generated on our servers and never contains more than that clip * **Configurable preview length** — adjust the **Free preview length** slider any time; the preview regenerates automatically, even without re-uploading the track * **Full track and preview length shown to customers** — product and checkout pages display both, e.g. "0:15 free preview of the 0:27 track" * **Separate cover art** — upload album/cover artwork independently of the track itself * **Same secure delivery as Digital Products** — the full track is delivered via a download token immediately after payment, with the same download limit and link expiry settings ### How It Works 1. Go to **Products → New Product** and select **Pay to Unlock (Audio)** 2. Upload the full track and set the free preview length 3. Optionally add cover art and a description 4. Publish — customers can listen to the free preview and pay to unlock the full track [Full documentation](/products-and-pricing/pay-to-unlock) **2026-07-03** v3.23.0 ## Commissions — Sell Custom-Scoped Creative & Freelance Work A new **Commission** product type for work where the final price depends on scope — illustrations, tattoo designs, custom development, and other bespoke work. List it with a starting price, and PayRequest handles the rest: a distinct storefront badge, a capped platform fee, and an optional turnaround note. ### What's New * **New product type: Commission** — create it from **Products → New Product** just like any other product * **"From €X" pricing** — the price you set is shown to customers as a starting price, not a fixed one, since final cost can vary once you scope the request * **Pink "Commission" badge** — automatically shown on your PayRequest Page storefront so commissions stand out from regular products * **Typical turnaround field** — optional note (e.g. "5-7 business days") shown under the price * **Capped platform fee** — commission purchases use a flat 2% fee capped at €25, regardless of your plan, instead of the normal plan-based fee ### How It Works 1. Go to **Products → New Product** and select **Commission** as the type 2. Set your **Starting Price**, add a description and sample image 3. Optionally add a **Typical turnaround** on the Commission Details step 4. Publish — it appears on your PayRequest Page with the Commission badge and "From €X" pricing 5. Once purchased, follow up with the customer to scope the work; invoice separately for anything beyond the starting price [Full documentation](/products-and-pricing/commissions) **2026-06-27** v3.22.0 ## Product Carousel — New Layout for Your Services & Products Your PayRequest Page's product showcase now has two display modes. Switch between a horizontal **Carousel** (always open, swipeable cards with a storefront feel) and the classic collapsible **Grid** — all from a single toggle in the Settings tab. ### What's New * **Carousel layout** — horizontal scrollable row with external prev/next controls, fade edges, and large product image cards; always visible without an accordion * **Grid layout** — unchanged classic 3-column collapsible grid; remains the default for all existing pages * **Product layout picker** — Grid / Carousel segment control in **PayRequest Page → Settings → Products** ### How It Works 1. Go to **PayRequest Page → Settings** 2. Scroll to **Products** and find the **Product layout** picker 3. Select **Carousel** or **Grid** 4. Click **Save Settings** — your public page updates immediately [Full documentation](/shop-and-checkout/product-display) **2026-06-26** v3.21.0 ## Invoice Bundle — Pay All Open Invoices with One Link Send a customer a single payment link that covers all their outstanding invoices. Instead of chasing each invoice separately, bundle them all into one Smart Link and let the customer settle everything in a single Mollie checkout. ### What's New * **New Smart Link type: Invoice Bundle** — select a customer and tick the invoices to include; the total is calculated automatically * **Branded payment page** — lists all invoices with numbers, amounts, due dates, and an "Overdue" badge where applicable, then a single **Pay** button for the combined total * **Auto-mark paid** — when the Mollie payment succeeds, all bundled invoices are instantly marked paid and linked to the payment ID * **Email & SMS delivery** — send the link to the customer on creation, with a rich email showing the full invoice breakdown and total * **Re-send from edit** — update the invoice selection and re-send the link at any time from the smart link edit page ### How It Works 1. Go to **Payment Page → Smart Links** and click **Create Smart Link** 2. Choose **Invoice Bundle** as the link type 3. Select the customer — all their open, sent, and overdue invoices appear as checkboxes 4. Tick the invoices to include; the total updates in real time 5. Add an optional description (e.g., "Your hosting has been suspended — please pay below") 6. Choose **Email** and/or **SMS** delivery and click **Create** 7. The customer receives the link, pays once, and all invoices are marked paid automatically [Full documentation](/payment-processing/smart-links#creating-a-smart-link) **2026-06-22** v3.20.0 ## Apple Wallet Card for Your PayRequest Page Carry your PayRequest Page as a card in Apple Wallet. Show it to a customer, they scan the QR code, and they land straight on your page to pay — no need to pull up your QR code separately. ### What's New * **Add to Apple Wallet** button on your PayRequest Page settings, next to your QR code * The card shows your business name, handle, and tagline in PayRequest's signature blue * Built-in QR code scans to the same link as your existing PayRequest Page QR code ### How It Works 1. Go to **PayRequest Page** in the main menu 2. Click **Add to Apple Wallet** next to your QR code 3. Confirm on the Apple Wallet add screen 4. Show the card to customers any time — they scan to pay [Full documentation](/shop-and-checkout/apple-wallet-card) **2026-06-21** v3.19.0 ## Payment Pages Now Speak 21 Languages Every Payment Page (`payrequest.me/yourhandle`) now automatically shows in your customer's own language — no translation work required on your end. ### What's New * **21 languages**: English 🇬🇧, Dutch 🇳🇱, German 🇩🇪, French 🇫🇷, Spanish 🇪🇸, Italian 🇮🇹, Portuguese 🇵🇹, Polish 🇵🇱, Swedish 🇸🇪, Danish 🇩🇰, Norwegian 🇳🇴, Finnish 🇫🇮, Greek 🇬🇷, Czech 🇨🇿, Romanian 🇷🇴, Hungarian 🇭🇺, Turkish 🇹🇷, Russian 🇷🇺, Chinese 🇨🇳, Japanese 🇯🇵, and Ukrainian 🇺🇦 * **Automatic detection** — based on the customer's browser language, falling back to their country (via IP) when needed * **Manual language switcher** — a flag-icon dropdown in the corner of every Payment Page, with the active language shown first and checked * **Shareable language links** — e.g. `payrequest.me/yourhandle?lang=it` always opens in Italian ### How It Works Nothing to configure — it just works on every existing Payment Page. Core checkout fields (name, email, address, totals, payment method, and more) are translated for all 21 languages. [Full documentation](/payment-processing/payment-forms#multi-language-support) **2026-06-16** v3.18.1 ## 26 Manual Payment Platforms — Asia & LatAm Coverage The **Other Ways to Pay** feature now covers 26 platforms, adding Mercado Pago, GCash, PayNow, PromptPay, KakaoPay, MoMo, WeChat Pay, and Alipay — plus smarter handle input that auto-corrects common mistakes. ### What's New * **Mercado Pago** 🌎 — Argentina, Brazil, Mexico, Colombia, and more (alias, phone, or CVU) * **GCash** 🇵🇭 — Philippines' most popular mobile wallet * **PayNow** 🇸🇬 — Singapore instant transfers via phone, NRIC, or UEN * **PromptPay** 🇹🇭 — Thailand's national payment system * **KakaoPay** 🇰🇷 — South Korea's chat-native payment app * **MoMo** 🇻🇳 — Vietnam's leading mobile wallet * **WeChat Pay** 🇨🇳 — China's ubiquitous payment platform * **Alipay** 🇨🇳 — Accepted by hundreds of millions worldwide * **Auto-correct on save** — Pasting a full profile URL or adding a stray `@` is fixed automatically for Wise, Revolut, Venmo, bunq.me, and Cash App * **Binance Pay numeric-only** — The Binance Pay ID field now accepts only digits, preventing entry errors ### How It Works 1. Go to **Settings → Payment Providers → Other Ways to Pay** 2. Find the platform, enter your handle or phone number, and click **Save** 3. Toggle visibility on or off — active platforms appear as buttons on your payment page [Full documentation](/payment-processing/other-ways-to-pay) **2026-06-16** v3.18.0 ## Payoneer — Global Payments for Creators Accept payments from customers in 150+ countries by connecting your Payoneer account. Ideal for creators and businesses with audiences in Asia, LatAm, Africa, and the Middle East — markets where Mollie and Stripe have limited reach. ### What's New * **Payoneer Checkout integration** — A **Pay with Payoneer** button now appears on your payment links when Payoneer is connected * **API-key onboarding** — Connect in seconds using your Client ID and Client Secret from the Payoneer Developer Portal — no OAuth redirect required * **150+ currencies** — USD, EUR, GBP, INR, PHP, IDR, NGN, KES, BRL, and many more * **Sandbox / test mode** — Toggle `PAYONEER_SANDBOX=true` to test without real charges * **Runs alongside Mollie, Stripe, and PayPal** — All four providers can be active simultaneously; buyers choose at checkout ### How It Works 1. Go to **Settings → Providers** and find the Payoneer card under **Add more payment options** 2. Click **Connect**, enter your Payoneer API credentials, and save 3. The **Pay with Payoneer** button appears on your payment links immediately [Full documentation](/payment-processing/connect-payoneer) **2026-06-15** v3.17.1 ## Automatic Currency Conversion for PayPal Fixed a bug where PayPal could charge the wrong amount when your payment page currency differed from your PayPal account's settlement currency. ### What's New * **Live exchange-rate conversion** — When your PayPal account settles in a different currency than your payment page displays, PayRequest now converts the amount automatically before sending it to PayPal * **Accurate buyer preview** — The PayPal button shows the converted amount (e.g. "≈ ₱607.50") before checkout, so buyers know exactly what PayPal will charge * **Conversion audit trail** — Every converted payment records the exchange rate and original/converted amounts on the transaction [Learn more](/payment-processing/connect-paypal#currency-conversion) **2026-06-11** v3.17.0 ## 25 Social Platforms on Your PayRequest Page Your PayRequest Page now supports the platforms creators actually use — from Instagram and TikTok to OnlyFans, Twitch, and Discord — each displayed with its official brand icon. ### What's New * **25 supported platforms** — Instagram, TikTok, Twitter/X, YouTube, Twitch, Discord, Telegram, Snapchat, Spotify, Kick, WhatsApp, Facebook, Reddit, SoundCloud, Substack, Pinterest, LinkedIn, GitHub, Calendly, Patreon, Signal, OnlyFans, plus Email, Phone, and Website * **Official brand icons everywhere** — Every link on your public page shows the platform's real logo (YouTube now shows the YouTube icon, not a generic play button) * **Searchable platform picker** — Click **Add More** in the Styling tab and type to filter the list instantly * **Direct contact links** — Email and phone entries automatically become click-to-email and click-to-call links for your visitors * **Smart URL handling** — Paste a full URL or just the address; PayRequest formats the link correctly ### How It Works 1. Open **PayRequest Page → Styling** and scroll to the **Social Links** card 2. Fill in the always-visible favorites (Instagram, TikTok, Twitter/X, YouTube, Website) 3. Click **Add More** and search for any other platform 4. Watch the live preview update with each brand icon as you type [Full documentation](/shop-and-checkout/sales-page-styling#social-links) **2026-06-10** v3.16.0 ## SMS Payment Links for Everyone Send payment links straight to your customer's phone — now available on every PayRequest account with a fair credit system. ### What's New * **SMS delivery for all accounts** — Sending smart payment links via SMS no longer requires a paid plan * **1 free SMS credit** — Every account starts with one credit on the house * **Earn credits by getting paid** — Every payment you receive adds 1 SMS credit to your balance, automatically * **Automatic refunds** — If an SMS fails to send, your credit comes right back * **Clear balance display** — The smart link form shows your remaining credits, and explains how to earn more when you run out * **Better SMS messages** — Texts now always link to your own branded payment URL and show your business name as sender ### How It Works 1. Create a smart link and select a customer with a phone number 2. Tick **SMS** as the delivery method — the form shows your credit balance 3. Save the link and the SMS is sent instantly 4. Receive any payment and earn a fresh credit [Full documentation](/payment-processing/sms-payment-links) **2026-06-02** v3.15.0 ## Telegram Payment Bot Create payment links and receive payment notifications directly in Telegram — no app switching required. ### What's New * **@payrequestme_bot** — Connect your PayRequest account with one tap and start creating payment links straight from Telegram * **Instant payment alerts** — Get a Telegram message the moment a payment lands, with amount, customer name, and invoice number * **`/pay` command** — Type `/pay 50 for design work` and the bot returns a ready-to-share payment link in seconds * **`/links` and `/status`** — View your recent payment links and transactions without opening the dashboard * **Permanent connection** — Link your Telegram account once; notifications and commands work forever until you disconnect ### How to Connect 1. Open **@payrequestme_bot** in Telegram and tap **Start** 2. Tap the connect link the bot sends you 3. Log in to PayRequest — your account is linked instantly [Full setup guide](/integrations/telegram-bot) **2026-05-28** v3.14.0 ## Crypto Recurring Payments for Subscriptions Subscriptions can now be paid with **USDC on Base**. Crypto works as an invoice-based payment method — each billing cycle generates an invoice that the customer pays from their wallet, with 98% going directly to your wallet via the on-chain FeeSplitting contract. ### What's New * **Crypto as a subscription payment method** — Select **Crypto (USDC)** when creating or editing a subscription, just like you would choose automatic or manual payment * **Invoice-based recurring billing** — Each billing cycle generates an invoice; customers pay with USDC from their wallet via WalletConnect. No mandate or bank details needed * **Instant settlement** — Once the customer confirms the transaction, Base settles it in under a second. The invoice is marked paid, and your wallet receives 98% automatically * **No chargebacks** — USDC payments are irreversible on-chain, even for recurring billing * **Switch anytime** — Toggle between crypto, automatic (SEPA/card), and manual bank transfer on any subscription, even mid-cycle * **Works with trials** — Free trials convert normally; the first invoice after trial end can be paid with crypto ### How It Works 1. Enable **Crypto (USDC)** in your Provider Settings (one-time setup) 2. Create or edit a subscription → set payment method to **Crypto (USDC)** 3. On each billing date, PayRequest generates an invoice with a **Pay with Crypto** option 4. Customer opens the invoice, scans the WalletConnect QR code, and confirms the USDC amount 5. 98% goes directly to your wallet; the invoice is marked paid automatically [Read the full guide](/subscriptions/crypto-recurring-payments) · [Crypto Payments overview](/payment-processing/crypto-payments) **2026-05-26** v3.13.1 ## P2P Payments: Multi-Wallet Support P2P wallet payments now work with every major Solana wallet — not just Phantom. ### What's New * **Solflare, Coinbase Wallet, Trust Wallet, Backpack** — all supported for sending P2P USDC * **MetaMask native Solana** — MetaMask's native Solana support (Wallet Standard) is now detected automatically; existing MetaMask users can send without installing a separate wallet * **MetaMask Snaps** — Install the Solflare Snap from inside MetaMask (Snaps → Search "Solflare") to add full Solana support in one click * **Wallet Standard auto-detection** — Any wallet implementing the [Solana Wallet Standard](https://github.com/wallet-standard/wallet-standard) is discovered and usable automatically * **Simplified UX** — P2P section no longer has its own amount/note fields; it reads from the main payment form so there's no duplication * **Separate wallet storage** — Your Solana P2P wallet and Base USDC wallet are now stored separately in Provider Settings so connecting one never affects the other [P2P Wallet Payments guide](/payment-processing/p2p-wallet-payments) **2026-05-26** v3.13.0 ## Crypto Page Themes + P2P Wallet Payments Two new Web3-native features for your `payrequest.me` page. ### What's New * **Crypto Page Themes** — Choose a visual theme in **PayRequest Page → Styling → Page Theme**. Two options: **Solana** (deep dark bg with purple-to-green radial glow and glowing card border) and **Crypto Native** (animated gradient mesh background with a glassmorphism frosted-glass card). Themes work alongside your existing accent color — they control the background and card style while your accent color still applies to buttons and highlights. * **P2P Wallet Payments** — Any Phantom user can now send USDC directly to your Solana wallet from your `payrequest.me` page. Connect your Solana wallet in Settings and a **"Send USDC directly"** panel appears on your page automatically. No invoice, no checkout form, no platform fee — 100% of the USDC goes to your wallet. Transfers are tracked in your Wallet Dashboard with Solscan links. ### How It Works — P2P Payments 1. Connect your Solana wallet in **Settings → Wallet** 2. A visitor opens your `payrequest.me/{handle}` page 3. They enter an amount and click **Connect Phantom to send** 4. They confirm the transfer in Phantom — USDC arrives in your wallet in under a second [Crypto Page Themes guide](/shop-and-checkout/crypto-page-themes) · [P2P Wallet Payments guide](/payment-processing/p2p-wallet-payments) **2026-05-22** v3.12.0 ## Crypto Wallet Balance + Atomic On-Chain Fee Split Two improvements to the USDC payment system on Base. ### What's New * **Wallet balance in settings** — Your USDC and ETH balances on Base are now shown directly in **Provider Settings → Crypto (USDC)**. No need to open your wallet app to check your balance. Cached for 5 minutes with a one-click Refresh button. * **ETH gas balance** — Alongside the USDC balance, your ETH balance is displayed so you always know you have enough gas for transactions. * **Atomic FeeSplitting contract** — Payments are now split on-chain in a single transaction: 98% goes directly to your wallet, 2% to PayRequest — atomically, with no intermediate escrow or treasury step. The contract is immutable with no admin keys. * **New supported wallets guide** — A dedicated [Supported Wallets](/payment-processing/crypto-supported-wallets) page covering MetaMask, Coinbase Wallet, Rabby, Rainbow, Trust Wallet, Kraken Wallet, and more — with setup instructions and troubleshooting tips. [Read the Crypto Payments guide](/payment-processing/crypto-payments) · [Supported Wallets](/payment-processing/crypto-supported-wallets) **2026-05-13** v3.11.1 ## One-Click Payment Method Toggles for Stripe Turning on a Stripe payment method like **MobilePay**, **Klarna**, or **iDEAL** now actually shows it to buyers — in one click. Previously, enabling a method inside PayRequest only told Stripe "my account wants this method", but a separate buyer-visibility switch inside Stripe stayed off, so customers never saw the new tile at checkout. We now flip both switches together. ### What's New * **One-click enable** — Click **Enable** on a method in **Provider Settings → Stripe → Payment Methods** and the tile shows up on your next checkout. No more hunting through Stripe Dashboard settings. * **"Hidden at checkout" badge** — If a method is enabled on your account but Stripe says it's not currently visible to buyers (wrong currency, wrong buyer country, or pending verification), an amber **Hidden at checkout** badge appears next to it. So you know exactly why a method isn't appearing on a test page. * **Bonus fix** — Smart Link donation pages and amount links now show Stripe (and PayPal) when those are the only providers connected. Previously they fell back to a "no payment provider connected" message even when Stripe was wired up. [Read the Stripe payment-method guide](/payment-processing/connect-stripe#choosing-which-payment-methods-show) **2026-05-13** v3.11.0 ## Donation Mode + Default Payment Gateway Two big additions to your PayRequest Page and payment setup. Run a **donation goal** with a live progress bar and a public donor feed — perfect for community servers, creator support, or recurring cost crowdfunding. And tidy up multi-provider setups by picking a **default payment gateway** for your account. ### What's New — Donation Mode * **Third display mode** on the PayRequest Page, alongside Products & services and Amount buttons — switch any time from **PayRequest Page → What to show on your page** * **Goal amount** with two reset cycles: **Monthly** (auto-resets on the 1st) or **One-time** (runs until you change it) * **Live progress bar** showing total raised vs. goal, with percentage funded and "€X to go" status * **Public donor feed** with name, amount, and relative time ("3 hours ago"); 1–50 donors visible, default 10 * **Goal-reached banner** kicks in at 100% — donations keep accepting so supporters can overshoot * **Pay any amount** — donors enter custom amounts or pick from optional preset buttons (€1, €5, €10…) * **Permanent URL** at `payrequest.me/` — share once, never expires, the goal resets on its own * **Refund-safe totals** — the progress bar reads from paid invoices, so refunds and chargebacks roll back automatically ### What's New — Default Payment Gateway * **New "Set as default" button** on each active provider card in **Provider Settings** * **Blue Default badge** on the active gateway so it's clear at a glance * Only one provider can be default at a time — assigning a new one demotes the previous default automatically * Inactive providers can't be marked as default — you must activate first * Doesn't disable other providers — customers can still pay through any active gateway ### How It Works (Donation Mode) 1. Open **PayRequest Page** from the dashboard 2. Under **What to show on your page**, click the **Donation goal** tab 3. Set your goal amount (e.g. `10.00`) and reset period 4. Toggle the donor feed on and pick a count 5. Optionally add suggested amount buttons 6. Click **Save Settings** — your live page is ready to share [Read the Donation Mode guide](/shop-and-checkout/donation-mode) · [Default gateway setup](/payment-processing/setting-up-payment-providers#setting-a-default-gateway) **2026-05-09** v3.10.0 ## Embed Smart Link Payment Buttons on Any Website Every Smart Link now ships with a ready-to-paste **payment button snippet**. Copy the HTML, paste it on your website, blog, WordPress page, or email signature, and customers can pay directly from there — your Smart Link analytics keep tracking views, payments, and conversion rate exactly as before. ### What's New * **Three button styles** — Blue (default), Dark, and Outline — each chosen to fit different site designs out of the box * **Live preview** — See exactly how each style looks with your Smart Link's label before copying * **One-click copy** — Click **Copy snippet** to put the full HTML on your clipboard, ready to paste * **Works everywhere** — WordPress Custom HTML blocks, Squarespace, Wix, Webflow, plain HTML, even email signatures — anywhere a hyperlink can be pasted * **Editable label** — The button text defaults to the Smart Link amount or name, but you can rewrite it freely after pasting (e.g. "Donate", "Buy now", or in any language) * **Optional secure-lock modifier** — Add `pr-btn--secure` to prefix the button with a small lock icon for an extra trust signal * **Centralised styling** — The button stylesheet is hosted by PayRequest, so design refreshes appear automatically across every embed ### How It Works 1. Open **Payment Page → Smart Links** and click the link you want to embed 2. Click **Share** at the top right 3. Scroll to **Embed button on your website** in the share dialog 4. Pick **Blue**, **Dark**, or **Outline** — the snippet preview updates instantly 5. Click **Copy snippet** and paste it into a Custom HTML block on your site [Read the full guide](/payment-processing/smart-links#embed-button-on-your-website) **2026-04-30** v3.9.1 ## Brand Your PayRequest Page with a Custom Accent Color The PayRequest Page Styling tab now has an **Accent Color** picker. Choose a brand color and it's applied to your "Pay" button, avatar border, and other primary highlights on your public PayRequest Page — so visitors see *your* color, not the default blue. ### What's New * **Three ways to pick a color** — A 10-color curated swatch palette, your OS-native color picker for any custom shade, or a hex input for exact brand matching * **Live preview** — The preview avatar border and sample Pay button update instantly as you change the color, before you save * **Applied across the live page** — The chosen color flows into the main Pay button, the avatar border, the selected-product ring, and other primary call-to-action elements * **Clear to default** — Reset back to the standard blue accent in one click * **Per-page setting** — Stored on your PayRequest Page, ready to extend per-business in the future ### How It Works 1. Open **PayRequest Page** from the dashboard and click the **Styling** tab 2. Find the **Accent Color** card under Tagline & Bio 3. Click a swatch, use the native color picker, or paste a hex value (e.g. `#f59e0b`) 4. Watch the preview avatar and sample Pay button update instantly 5. Click **Save Styling** — your live PayRequest Page picks up the new color on the next visit [Read the full guide](/shop-and-checkout/sales-page-styling#accent-color) **2026-04-29** v3.9.0 ## Stripe and PayPal — Now Available Alongside Mollie PayRequest now supports **Stripe** and **PayPal** as payment providers in addition to Mollie. Connect any combination of the three, and your customers will see whichever methods you've enabled. This release covers payment links — invoices and subscriptions still run through Mollie for now, with broader Stripe and PayPal support coming in upcoming releases. ### What's New * **Connect Stripe in one click** — A new Stripe card on Provider Settings runs the full Stripe Connect flow. Cards, Apple Pay, Google Pay, Klarna, iDEAL, Bancontact, and many more methods drop in automatically based on the buyer's location. * **Connect PayPal in one click** — A new PayPal card on Provider Settings runs PayPal's Partner onboarding. Adds the familiar PayPal button, plus Pay Later for higher-ticket orders and Venmo for US mobile buyers. * **Adaptive Pricing for Stripe** — Buyers see prices in their own local currency in 150+ countries. The 2–4% conversion fee is paid by the buyer, not you. Toggle on or off per merchant from Provider Settings. * **Embedded checkout** — Both providers render directly on your payment page. No redirect to a third-party site; buyers stay in your branded flow start to finish. * **Login with PayPal** — New merchants can sign up to PayRequest by authenticating with PayPal, which automatically chains a PayPal Connect step so their account is ready to take payments by the end of signup. * **Smart payment-method labels** — On Stripe checkouts, the pay button updates to show the chosen method ("Pay with iDEAL", "Pay with Apple Pay") so buyers always know what they're confirming. * **Multi-provider transaction view** — The transactions table now shows the source provider on each row, with deep-links to the right detail page for Mollie, Stripe, or PayPal. ### How It Works 1. Open `/provider-settings` from your dashboard 2. Click **Connect** on the Stripe or PayPal card (or both) 3. Authorize on the provider's onboarding page and return to PayRequest 4. Share a payment link — your customers see the new options automatically [Read the full guide](/payment-processing/setting-up-payment-providers) **2026-04-22** v3.8.4 ## File Attachments on Support Requests Replies on support tickets can now carry file attachments — screenshots, PDFs, signed documents, anything that helps resolve an issue. Attachments show up inline in the conversation on both sides, and are sent along as real attachments in the reply email so customers never have to open the portal to get them. ### What's New * **Drag-and-drop upload** — A new Attachments dropzone below the reply editor accepts files via drop or file picker * **Admin and customer uploads** — Both the dashboard reply form and the customer portal reply form support attachments * **Up to 10 files per reply, 20 MB each** — Any file type (images, PDFs, spreadsheets, ZIPs, etc.) * **Inline conversation display** — Images render as previews, other files appear as download cards with filename and size * **Real email attachments** — When you send a reply notification, the files are attached to the email itself, not just linked * **Ticket-scoped access** — Downloads are served through an authorized endpoint that checks ticket ownership, with unguessable file identifiers * **Automatic cleanup** — Attachments are tied to their reply; removing the reply removes the files ### How It Works 1. Open a support request and scroll to the reply form 2. Drop files onto the **Attachments** dropzone or click to browse 3. Remove any queued file before sending by clicking its remove icon 4. Send the reply — attachments appear in the conversation history and, if email notification is enabled, arrive in the customer's inbox as real attachments 5. Customers see the same dropzone in the portal when replying, and downloaded files from your replies through a secure link [Read the full documentation](/customer-management/support-requests#-file-attachments) **2026-03-15** v3.8.3 ## Email-to-Ticket: Inbound Email Support Customers can now create support tickets by **replying to any email** they receive from your business — invoices, payment reminders, order confirmations, and more. Business owners are notified instantly and can reply directly from email for a seamless two-way conversation. ### What's New * **Reply-To on all outgoing emails** — Every invoice, order, reminder, and notification email now includes a Reply-To address at your business's `payreque.st` address * **Automatic ticket creation** — Customer replies are parsed and converted into support tickets with full message body * **Smart customer matching** — Matches sender by exact email or company domain (e.g., `jan@acme.com` matches existing customer `support@acme.com`) * **Spam protection** — Emails from unknown senders (not matching any customer) are automatically rejected * **Two-way email conversations** — Business owners can reply to ticket notification emails, which appends to the conversation and notifies the customer * **New ticket notifications** — Business owners receive an email when a new ticket is created (both from portal and inbound email) * **Freelancer support** — Works for businesses with shops and freelancers with PayRequest Pages alike * **Attachment references** — Email attachments are tracked in ticket metadata for future retrieval ### How It Works 1. Customer receives an invoice, reminder, or any other email from your business 2. Customer replies to the email with their question or concern 3. A support ticket is automatically created and you receive a notification 4. Reply to the notification email or open the ticket in your dashboard 5. Your reply is sent to the customer — they can reply back to continue the conversation [Read the full documentation](/customer-management/support-requests#-email-to-ticket-inbound-email) **2026-03-13** v3.8.2 ## Archive Subscriptions A new **Archived** status lets you permanently shelve subscriptions you no longer need — customers who switched plans, former clients, completed projects, discontinued products — while keeping all invoices and transaction history intact. ### What's New * **Archive button on canceled subscriptions** — Open any canceled subscription and click **Archive Subscription** to move it out of your active list * **Confirmation modal** — Clear explanation of what archiving does before you confirm * **Dedicated Archived tab** — The subscription list includes an Archived tab with count badge * **Hidden from customer portal** — Archived subscriptions are invisible to customers * **Billing & MRR excluded** — No more accidental billing, not counted in revenue calculations * **Reactivation support** — Bring back any archived subscription if a customer returns * **Bulk action protection** — Archived subscriptions cannot be resumed or canceled via bulk actions * **All data preserved** — Invoices, transactions, tags, and notes remain accessible on the detail page ### How It Works 1. **Cancel** the subscription (if still active) 2. Click **Archive Subscription** on the canceled subscription's detail page 3. Confirm in the modal — the subscription moves to the **Archived** tab 4. Customer no longer sees it, billing stops, your list stays clean 5. Need it back? Click **Reactivate Subscription** any time [Read the full documentation](/subscriptions/archiving-subscriptions) **2026-03-11** v3.8.1 ## Chargeback Details on Invoice Page Invoice detail pages now show chargeback information and payment retry status directly in the sidebar, eliminating the need to navigate to the subscription page to understand a failed payment. ### What's New * **Chargeback status badge** — Invoices with chargebacks display a red "Chargeback" badge instead of "Paid" * **Chargeback details card** — Shows amount, date, SEPA reason code, and chargeback ID on the invoice sidebar * **Payment retry status** — Failed attempts, last failure date, next retry schedule, and full retry history visible on the invoice * **Status protection** — Chargeback status can no longer be accidentally overwritten back to "Paid" by webhooks or payment syncs * **Direct subscription link** — Quick navigation to the associated subscription from the chargeback card ### How It Works 1. When a chargeback is received, the invoice status automatically changes to **Chargeback** 2. Open the invoice to see the **Chargeback Details** card in the sidebar 3. If linked to a subscription, the card also shows **Payment Retry Status** with attempt history 4. Click **View Subscription** to manage retry settings or take further action [Read the full documentation](/payment-processing/handling-chargebacks) **2026-03-11** v3.8.0 ## Bulk Subscription Price Adjustments Apply inflation adjustments and price increases to multiple subscriptions at once. The enhanced bulk pricing wizard supports multiple increase methods, smart rounding, scheduling, MRR impact previews, and legally compliant customer notifications. ### What's New * **Three increase methods** — Choose between percentage-based increase (+X%), fixed amount (+EUR X), or setting a specific new price for all selected subscriptions. * **Smart rounding** — Round results to the nearest EUR 0.50, EUR 1.00, or EUR 5.00 with options for round up, round down, or nearest. * **Price cap** — Set a maximum price to prevent subscriptions from exceeding a limit after the increase. * **Flexible scheduling** — Apply immediately, on a specific future date, or at each subscription's individual next renewal date. * **MRR impact preview** — See the total revenue impact before executing, with current MRR, new MRR, increase amount, and percentage change. * **Per-subscription preview table** — Review each subscription's old price, new price, and difference in a scrollable table. * **Customer notification emails** — Automatically send price increase emails with old/new price, effective date, and cancellation link. * **Dutch law compliance** — Built-in 30-day notice validation, cancellation right inclusion, and ACM-compliant email templates. * **Enhanced audit trail** — Full price change details (old/new amounts per subscription) stored in bulk action history. ### How It Works 1. Go to **Bulk Actions > Subscriptions > Apply Inflation Adjustment** 2. Configure the increase method, rounding, scheduling, and notification preferences 3. Review the MRR impact preview and per-subscription price changes 4. Confirm and execute — scheduled changes are applied automatically before billing [Read the full documentation](/subscriptions/price-adjustments) **2026-03-06** v3.7.1 ## Support Request Improvements Enhanced the support request system with smarter subscription linking, admin approval actions for cancellation requests, and detailed subscription popovers. ### What's New * **Required subscription selection** — When creating a "Cancel Subscription" or "Pause Subscription" request, the subscription field is now required and auto-selected. The dropdown shows subscription names with amounts and status. * **Subscription hover popover** — On the admin request detail page, hovering over a linked subscription shows a detailed card with name, status, amount, billing interval, next billing date, and cancellation details. * **Approve & Reject actions** — Cancel subscription requests now show dedicated "Approve & Cancel" and "Reject & Keep Active" buttons for one-click decisions. * **Support page layout fix** — Fixed a layout issue on the customer portal support requests page where the heading and table were displayed side-by-side instead of stacked. * **Cancellation constraint fix** — Fixed a database constraint that prevented cancel subscription requests from being created. [Read the support requests documentation](/customer-management/support-requests) **2026-03-04** v3.7.0 ## Subscription Cancellation Requests Subscription cancellations now go through a structured request process with configurable notice periods, reason collection, and automatic domain management. Customers submit a cancellation request from the portal, and the subscription stays active until the notice period ends. ### What's New * **Cancellation request flow** — Customers select a reason and submit a request instead of instantly canceling. A support ticket is automatically created for admin review. * **Configurable notice period** — Set a notice period per product (default 30 days). The effective date is the later of the notice period end or the next billing date. * **Automatic domain management** — Linked domain auto-renewals are automatically disabled when a cancellation is requested. * **Admin controls** — Withdraw cancellation requests or cancel immediately from the subscription detail page. * **Separate pause and cancel toggles** — Per-product settings to independently enable or disable pause and cancel actions in the customer portal. * **Cancellation mode choice** — Choose between "Request" mode (notice period + support ticket) or "Immediate" mode (instant cancel) per product. * **Automatic processing** — A daily scheduled job cancels subscriptions that have passed their effective cancellation date. ### How It Works 1. Customer clicks **Cancel Subscription** in the portal and selects a reason 2. A support request is created and the notice period begins 3. The subscription stays active until the effective date 4. Admin can review, communicate, withdraw, or cancel immediately 5. After the notice period, the subscription is automatically canceled [Read the full documentation](/subscriptions/cancellation-requests) **2026-03-03** v3.6.0 ## Digital Product File Delivery Sell digital files like PDFs, ebooks, and guides with automatic secure delivery. Upload a file to any digital product and customers receive unique download links immediately after payment. ### What's New * **File upload on products** — Upload PDF, ZIP, or EPUB files (up to 50MB) when creating or editing a digital product * **Automatic delivery** — Customers receive secure, unique download links on the success page, in their order email, and in the customer portal * **Download limits** — Configure how many times a customer can download (1-100, default: 5) and how long the link stays active (1-365 days, default: 30) * **Download tracking** — See per-product and per-order download statistics including total downloads, active tokens, and exhausted tokens * **Payment page preview** — Digital products show an "Includes digital file" card on the payment page so customers know what they're getting * **Multi-domain support** — Download links work across all domains including payrequest.me, custom domains, and the dashboard * **Customer portal access** — Customers can re-download files from their order history with remaining download count and expiry info ### How It Works 1. Create a product with type **Digital** and upload your file 2. Configure **Max Downloads** and **Link Expiry** in the download settings 3. Customer purchases the product and pays via Mollie 4. A unique download token is created with your configured limits 5. Customer downloads from the success page, email link, or customer portal [Read the full documentation](/products-and-pricing/digital-products) **2026-03-02** v3.5.0 ## Consolidated Invoicing Customers with multiple subscriptions can now receive a single combined invoice instead of separate invoices for each subscription. This reduces email noise and saves on transaction costs (up to €0.29 per consolidated charge with Mollie SEPA Direct Debit). ### What's New * **Global toggle** — Enable consolidated invoicing in **Settings** > **Consolidated Invoicing** with configurable frequency (monthly, bi-weekly, weekly) and anchor day slider * **Per-customer opt-in** — Enable consolidation individually per customer with optional frequency and anchor day overrides * **Automatic bundling** — Subscription charges are collected as pending items, then bundled into a single invoice on the anchor day * **Consolidated badge** — Invoices created by consolidation show an indigo **Consolidated** badge and can be filtered in the invoice list * **Grouped line items** — Consolidated invoice detail view groups charges by subscription * **Smart cancellation** — Pending items are automatically voided when a subscription is canceled * **Multi-currency support** — Customers with subscriptions in different currencies receive separate consolidated invoices per currency * **Automatic scheduling** — Invoices are generated automatically on the configured anchor day ### How It Works 1. Enable **Consolidated Invoicing** in Settings and choose frequency + anchor day 2. Opt in customers via the **Invoice Consolidation** section in the customer edit form 3. Subscription billing creates pending items instead of individual invoices 4. On the anchor day, all pending items are bundled into one invoice per customer 5. Payment is collected automatically (mandate) or an invoice email is sent (bank transfer) [Read the full documentation](/invoices/consolidated-invoicing) **2026-03-02** v3.4.0 ## Pause/Resume, Partial Payments & Pre-Incasso Debt collection cases now support pausing, manual payment registration, balance waivers, and a new pre-collection stage — giving you full control over the recovery process. ### What's New * **Pause & Resume** — Temporarily suspend automated escalation while negotiating with customers. Paused cases show a purple badge and banner, and the customer portal shows "Case On Hold" * **Register Payments** — Record bank transfers, cash, or other payments received outside PayRequest. The amount breakdown updates in real-time and the case auto-closes when fully paid * **Waive Balance (Kwijtschelding)** — Write off the remaining balance after partial payments for settlements. Waived amounts are tracked separately in the payment history * **Pre-Incasso (Stage 0)** — New optional first stage with gentle, informal reminder language. Auto-escalates to Stage 1 after 14 days. Toggle when creating a case * **Unified Activity Timeline** — All actions (emails, letters, payments, stage changes, notes) shown in a single timeline on the case sidebar * **Payment History Table** — Full log of every payment registered, with date, amount, method, and notes * **Paused filter** — Filter the debt collection overview by paused status * **Customer portal updates** — Paused banner, stage 0 soft language, and partial payment breakdown visible to customers ### How It Works 1. Create a case with optional **Pre-Incasso** toggle for a soft start 2. **Pause** the case from the Actions sidebar when negotiating 3. **Register payments** as they come in via bank transfer or cash 4. **Waive remaining** balance when you've agreed on a settlement 5. Case auto-closes when the full balance is covered [Read the full documentation](/debt-collection/managing-cases) **2026-03-01** v3.3.0 ## Email Bounce Suppression & Delivery Tracking PayRequest now automatically detects email bounces and spam complaints, suppresses future emails to problematic addresses, and confirms delivery of invoice reminders. No more silently sending emails to dead addresses. ### What's New * **Automatic email suppression** — Bounced and complained emails are blocked until you clear the suppression or update the email address * **Bounce warning on customer profiles** — Red callout with bounce type, SMTP error, and a **Clear Suppression** button * **Email Issue History** — Full chronological log of bounces, complaints, and failures in the customer's Logs tab * **Customer list filter** — New **Email Issues** filter and red **Bounced** badge on affected customer cards * **Delivery confirmation** — Invoice reminders show a green **Email Delivered** event in the timeline when Resend confirms receipt * **Auto-resolve transient failures** — Temporary delivery failures clear automatically when the next email delivers * **Smart email change** — Updating a customer's email automatically clears suppressions and removes bounce tags * **16 email channels protected** — Every customer-facing email (reminders, confirmations, debt collection, smart links, deposits) checks suppression before sending * **MCP integration** — The `send-invoice-reminder` tool returns a clear error when the customer email is suppressed ### How It Works 1. Resend reports a bounce or complaint via webhook 2. PayRequest records the issue and blocks future emails to that address 3. A red warning appears on the customer profile with full details 4. Fix the email or click **Clear Suppression** to resume delivery [Read the full documentation](/customer-management/customer-health) **2026-02-28** v3.2.0 ## Contact Persons Customers and business owners can now add **Contact Persons** — additional people from the customer's organization who receive email notification copies (CC). Perfect for bookkeepers who need invoice copies, managers who want payment updates, or technical contacts for subscription changes. ### What's New * **Contact Persons page** in the customer portal sidebar with add, edit, and delete * **Role labels** — General, Billing, Bookkeeping, Technical, Management, or Support * **Two notification categories** — Billing emails (invoices, payments, reminders) and Account emails (subscriptions, orders) * **Admin management** — Add and manage contact persons from the customer detail page in the dashboard * **Automatic CC** — Contact persons are automatically CC'd on matching email types * **Up to 10 contacts** per customer with duplicate email prevention ### How It Works 1. Customer navigates to **Contact Persons** in the portal sidebar 2. Adds a contact person with name, email, role, and notification preferences 3. Future emails matching their selected categories are automatically CC'd to them [Read the full documentation](/customer-management/contact-persons) **2026-02-28** v3.1.0 ## Subscription Suspension A new **Suspended** status for subscriptions lets you halt service for non-paying customers while tracking the state in PayRequest and automatically reactivating when they pay. ### What's New * **Suspend button** on subscription detail page with optional reason field * **Orange "Suspended" badge** — distinct from blue "Paused" to differentiate admin-initiated holds from voluntary pauses * **Customer email notification** sent automatically when a subscription is suspended * **Auto-reactivation** when the overdue invoice is paid via Mollie webhook — no manual follow-up needed * **Manual unsuspend** button for admin to reactivate at any time * **Suspended tab** in the subscription table with count badge * **Insights dashboard** Action Required section now shows suspended subscription count * **Customizable email template** under Settings > Email Templates > Subscription Suspended * **Full activity log** tracking for suspend, unsuspend, and auto-reactivation events ### How It Works 1. Customer has overdue invoices and isn't paying 2. Admin clicks **Suspend Subscription** and enters an optional reason 3. Status changes to Suspended, customer receives email 4. When customer pays the overdue invoice, subscription auto-reactivates [Read the full documentation](/subscriptions/suspending-subscriptions) **2026-02-20** v3.0.0 ## Debt Collection & Payment Recovery A complete debt collection system to help you recover unpaid invoices professionally. From friendly reminders to formal notices and physical letters — manage the entire recovery process from your dashboard. ### 📋 Collection Cases Create and manage collection cases for overdue invoices: * **Case Management**: Track every collection case with unique case numbers * **From Invoices**: Open a case directly from any overdue invoice * **External Debts**: Create cases for debts outside your invoicing system (auto-creates invoice) * **Customer Portal**: Customers can view their case, see what they owe, and pay directly * **Activity Tracking**: Full audit trail of every action, reminder, and payment ### 🔄 4-Stage Escalation Pipeline Gradually increase urgency with a structured escalation process: | Stage | Name | What Happens | | - | - | - | | 1 | Friendly Reminder | Polite notice, assumes oversight | | 2 | Formal Notice | Professional letter with payment deadline | | 3 | Collection Fees | Fees added to the outstanding balance | | 4 | Final Warning | Last chance before further consequences | * **Automatic Escalation**: Cases progress through stages automatically based on days overdue * **Manual Control**: Escalate or send reminders at any time * **Per-Case Language**: Set Dutch or English per case for accurate communication ### 💶 Payment Plans (Installments) Let customers pay in monthly installments when they can't afford the full amount: * **Flexible Terms**: 2, 3, 6, or 12 monthly installments * **Automatic Billing**: Uses PayRequest's subscription system for automatic monthly charges * **Progress Tracking**: Visual progress bar showing installments completed * **Auto-Close**: Cases automatically close when all installments are paid * **Customer Requests**: Customers can request a payment plan from the portal (toggle per case) ### ✉️ Postal Letters via Pingen Send physical collection letters for formal notices: * **Professional Layout**: A4 business letters with your company details * **Stage-Appropriate Content**: Letter text matches the current collection stage * **QR Code Payment**: Each letter includes a QR code for quick mobile payment * **Automatic Sending**: Letters sent automatically during escalation (Stage 2+) * **Delivery Tracking**: Monitor letter status (pending, sent, delivered) ### 💰 Collection Fees Add collection fees at later stages to cover recovery costs: * **Visible Everywhere**: Fees shown on payment pages, portal, and postal letters * **Clear Breakdown**: Customers see original amount + fee = total * **Included in Plans**: Payment plans cover the total including fees ### 🏪 Customer Experience Customers see their collection case in the portal with: * Warning banner explaining the situation * Case details and amount breakdown * Stage progress indicator * Pay Now button for immediate settlement * Payment plan request option [Read the full Debt Collection guide →](/debt-collection/overview) **2026-01-29** v2.9.5 ## MCP Integration: Claude Desktop & ChatGPT Support Connect your favorite AI assistant to PayRequest and manage your billing with natural language conversations. The Model Context Protocol (MCP) integration is now fully working with both Claude Desktop and ChatGPT. ### 🤖 Supported AI Assistants * **Claude Desktop**: Anthropic's desktop application with full MCP support * **ChatGPT**: OpenAI's ChatGPT with MCP connector support (Plus subscription required) ### 💬 Natural Language Billing Ask questions in plain English: * *"What are my invoice statistics?"* * *"Show me all overdue invoices"* * *"List my recent invoices"* * *"Send a payment reminder for invoice #INV-2025-042"* ### 🔧 Available Tools | Tool | Description | | - | - | | Get Invoice Stats | Real-time overview of total, pending, paid, and overdue invoices | | List Invoices | Search and filter invoices by status | | Get Overdue Invoices | Find invoices that need attention | | Send Invoice Reminder | Automate payment reminder emails | ### 🔐 Secure OAuth Authentication * Industry-standard OAuth 2.0 with PKCE * No API keys to manage or rotate * Revoke access anytime from your dashboard * All actions logged for audit purposes ### ⚡ Quick Setup 1. Go to **Settings → API** in your PayRequest dashboard 2. Select the **Claude Desktop** or **ChatGPT** tab 3. Follow the on-screen instructions 4. Authenticate with your PayRequest account 5. Start chatting with your billing data! [Read the full MCP setup guide →](/mcp/setup) **2025-12-29** v2.9.4 ## Bank Transfer Payment Method Accept bank transfers with automatic payment matching. Customers pay via bank transfer, and PayRequest automatically marks invoices as paid when the payment arrives. ### 🏦 Zero-Fee Bank Payments Accept bank transfers without any PayRequest transaction fees: * **Automatic Matching**: Ponto integration matches incoming payments automatically * **Unique References**: Each payment gets a unique reference code (e.g., `PAY-12345`) * **Instant Recognition**: Payments matched within minutes of arriving in your bank * **Copy Buttons**: Easy one-click copying of IBAN and reference for customers ### 💰 How It Works 1. Customer selects "Bank Transfer" at checkout 2. Customer sees your IBAN and unique payment reference 3. Customer transfers the exact amount via their bank 4. Ponto syncs your bank transactions automatically 5. PayRequest matches the reference and marks invoice as paid ### 📍 Available Everywhere Bank Transfer is now available on all payment surfaces: * **Payment Pages**: Your public payment page (payrequest.me/yourbusiness) * **Invoice Payments**: Customer portal invoice payment * **Smart Links**: Shareable payment links ### ⚙️ Easy Setup 1. Connect your bank via **Settings → Ponto** 2. Toggle **Bank Transfer Payment Method** on 3. Optionally add custom instructions for customers 4. Start accepting bank transfers! ### 🎯 Perfect For * **B2B Payments**: Business customers who prefer bank transfers * **High-Value Transactions**: Large payments without card limits * **Cost-Conscious Customers**: No processing fees passed on * **European Markets**: Strong bank transfer culture in NL, BE, DE [Learn more about Bank Transfer Payments →](/payment-processing/bank-transfer) **2025-12-17** v2.9.3 ## Vacation Mode Take a break from your business without missing a beat. The new Vacation Mode lets you temporarily pause all new orders while keeping your shop and PayRequest Pages visible. ### 🏖️ Pause Orders Temporarily Enable Vacation Mode when you need a break: * Going on holiday * Restocking inventory * Seasonal closures * Maintenance periods ### ⏰ Automatic End Dates Set it and forget it: * Choose when vacation mode should automatically disable * Your shop resumes accepting orders at midnight on the selected date * Or leave it empty and manually re-enable when ready ### 💬 Custom Messages Tell customers what's happening: * Write a personalized vacation message * Display your return date * Keep customers informed and engaged ### 🛡️ What's Protected Vacation Mode only blocks **new** orders: * Existing subscriptions continue billing normally * Customers can still pay outstanding invoices * Your shop remains browsable ### 📍 Where to Find It **Shop** → **Shop Settings** tab → **Vacation Mode** card [Learn more about Vacation Mode →](/shop-and-checkout/vacation-mode) **2025-12-13** v2.9.2 ## Paid-Only Order Creation Reduce email noise and keep your order data clean with the new Order Creation Mode for products. ### 🛒 Order Creation Control New product setting to control when orders are created during checkout: **Orders at Checkout (Default)** * Current behavior - orders created immediately when checkout starts * Emails sent right away (customer registration, order confirmation) * Good for standard e-commerce where you want to track all attempts **Paid-Only Orders (New)** * Orders only created after successful payment * No emails until payment is confirmed * Perfect for high-traffic products with many abandoned checkouts ### 📧 Cleaner Email Flow With paid-only mode enabled: * No "Customer registered" emails for window shoppers * No "New order" notifications that get cancelled minutes later * No "Order cancelled" emails for abandoned checkouts * Customers only receive order confirmation when they actually pay ### 🎯 Where It Works The order creation mode setting works across all checkout channels: * Shop checkout (cart-based purchases) * Payment page (product links) * Smart links (shareable payment URLs) ### 💡 When to Use Enable paid-only orders for products that: * Generate many abandoned checkouts * Are used in marketing campaigns with high traffic * Don't require pre-payment order tracking * Create too much email noise for your team **How to Enable:** 1. Edit your product 2. Go to Custom Fields step 3. Find "Order Creation" setting 4. Select "Paid-only orders" **2025-12-08** v2.9.1 ## Smarter Pricing & Better Payment Recovery Make your pricing more flexible and ensure customers can easily complete their payments, even after interruptions. ### 💰 Price Per Unit for Numeric Fields Create dynamic pricing based on quantities your customers enter. Perfect for rental days, seats, licenses, or any quantity-based pricing. **Example Use Cases:** * Rental equipment: €16 per day × number of days * Event tickets: €25 per person × number of attendees * Software licenses: €10 per seat × number of users **How It Works:** 1. Add a number field to your product's custom fields 2. Set a "per unit markup" price (e.g., €16) 3. Customers enter their quantity and the total updates automatically **What Customers See:** * Clear input field with per-unit price displayed * Real-time calculation as they change the quantity * Example: "2 × €16.00 = +€32.00" ### 📊 Price Breakdown on PayRequest Page Customers now see exactly what they're paying for with a clear, itemized breakdown on your payment page. **Breakdown Shows:** * Base product price * Each custom field option with its price impact * Setup fees (with your custom name like "Deposit" or "Installation") * **Total price** - clearly visible **Benefits:** * Builds trust with transparent pricing * Reduces customer questions about charges * Professional checkout experience ### 🔄 Custom Fields Retained After Failed Payment When a customer's payment is interrupted (cancelled, failed, or closed), they no longer lose their selections. **Before:** Customer fills in rental days, size, options → payment fails → all data lost, start over. **Now:** Customer returns to payment page → all their custom field selections are still there, ready to complete. **Works With:** * Cancelled payments * Failed payments * Browser closed during payment * Session timeouts ### 🚫 Cancelled Invoice Protection Cancelled invoices can no longer be paid, preventing confusion and duplicate payments. **What Happens:** * Customer visits a cancelled invoice link * Clear message: "This invoice has been cancelled" * Invoice items shown with strikethrough (so they know what was ordered) * Payment form is completely hidden **Why This Matters:** * Prevents payments on orders you've already cancelled * Clear communication with customers * No manual refunds needed for cancelled orders > [!TIP] > > **Pro Tip:** Use the per-unit markup feature for rental businesses, event tickets, or any service where customers choose quantities. Combined with the price breakdown, customers see exactly what they're paying for. **2025-12-04** v2.9.0 ## Get Paid Faster with Automated Reminders & Invoice Read Receipts Stop chasing payments manually. PayRequest now automatically reminds your customers about unpaid invoices and shows you exactly when they've seen them. ### 🔔 Automated Payment Reminders Set it and forget it. Your invoices now remind customers automatically so you don't have to. **What You Get:** * Automatic reminder emails sent daily at 9:00 AM * Choose when to remind: before due date, after due date, or both * Control how often reminders are sent (e.g., once per week) * Professional reminder emails with your branding and invoice details **Easy Setup:** 1. Open any invoice 2. Go to the "Payment Reminders" tab 3. Toggle reminders on 4. Set your preferences (days before/after, frequency) 5. Done! Reminders will be sent automatically **Stay in Control:** * Send a reminder manually anytime with one click * Send reminders to multiple invoices at once with bulk actions * See complete history of all reminders sent ### 👁️ Invoice Read Receipts Know the moment your customer opens their invoice - just like email read receipts. **New "Viewed" Indicator:** * Sky blue "Viewed" badge appears on invoices your customer has opened * See the exact date and time they viewed it * Appears in invoice history timeline **Why This Matters:** * **Customer says "I never received it"?** Check if they viewed it * **Following up on unpaid invoice?** Know if they've seen it first * **Optimize your timing:** Follow up right after they've viewed ### 💡 Get Paid Faster **Before:** Manually tracking which invoices need reminders, guessing if customers received them, chasing payments one by one. **Now:** Reminders go out automatically, you see when customers view invoices, and you can focus on your actual business. > [!TIP] > > **Pro Tip:** Set reminders to start 3 days before the due date. This gives customers a gentle nudge while there's still time to pay on time. **2025-11-16** v2.8.1 ## Payment Page Enhancements: Duplicate Prevention & Language Switcher Prevent accidental double charges and serve international customers better with two important payment page improvements. ### 🛡️ Pending Payment Protection Customers can no longer accidentally pay twice while SEPA Direct Debit payments are processing. **How It Works:** * When a customer pays via SEPA Direct Debit, payment takes 1-3 business days to complete * During this time, the invoice status is "pending" instead of "paid" * If customer opens the payment link again, they see a clear warning * **Payment form is completely hidden** - prevents duplicate charges **What Customers See:** * ⏰ Yellow warning callout: "Payment Processing" * Message: "SEPA Direct Debit is pending. This typically takes 1-3 business days to complete." * Full invoice details (items, quantities, total amount) * No payment button or form visible **Benefits:** * ✅ Zero duplicate payments - impossible to pay twice * ✅ Clear communication - customers understand what's happening * ✅ No manual refunds - prevents the problem entirely * ✅ Professional experience - shows payment processing expertise **Technical Details:** * Applies to all payment pages: direct links, smart links, invoice links * Checks real-time payment status via Mollie transaction data * Works with `?invoice=` parameter in URLs * Automatic - no configuration needed ### 🌍 Language Switcher Dropdown All payment pages now include an interactive language switcher for seamless multilingual experiences. **Features:** * **Fixed Top-Right Position**: Always visible, never in the way * **Flag Emoji Indicators**: 🇬🇧 English and 🇳🇱 Dutch with country flags * **Smart URL Preservation**: Keeps all parameters (invoice numbers, product IDs, etc.) * **Instant Switching**: No page reload, immediate language change * **Clean Design**: Ghost button style matches payment page aesthetic **What Customers See:** * Current language flag in top-right corner (🇬🇧 or 🇳🇱) * Click to reveal dropdown with both language options * Select new language → page content updates immediately * All buttons, labels, and messages translate automatically **Use Cases:** * International businesses serving Dutch and English customers * Customers sharing payment links with others who prefer different languages * Invoices sent to companies with international teams * Payment pages accessed from global marketing campaigns **Technical Integration:** * Works with `?lang=en` and `?lang=nl` URL parameters * Preserves query parameters when switching languages * Example: `?invoice=1505&lang=nl` → `?invoice=1505&lang=en` * Uses FluxUI dropdown component for consistency > [!TIP] > > **Pro Tip**: The language switcher is especially useful when sending payment links via email campaigns. Recipients can choose their preferred language without you having to create separate links. **2025-11-06** v2.8.0 ## Quote Requests for Freelancer Pages Engage with potential customers before they buy. Enable quote requests on your freelancer page to receive custom project inquiries. ### 💬 Quote Request Button Let visitors request custom quotes directly from your freelancer page. * **One-Click Enable**: Toggle "Enable Request Quote" in Payment Page settings * **Beautiful Modal Form**: Professional quote form appears without leaving the page * **Clean UX**: No URL changes, smooth AJAX submission with success confirmation * **Instant Notifications**: Email sent to you immediately with customer details * **Auto-Creates Customers**: New customer profiles created automatically **Perfect for:** * Custom service inquiries * Project scope discussions * Pricing questions before commitment * Building customer relationships * Qualifying leads ### 📊 Support Requests Dashboard Manage all customer inquiries in one place. **New Features:** * **Support Requests Sidebar Item**: Access from Store Management section * **Available on Freelancer Plan**: No upgrade required - all users can receive quotes * **Quote Request Type**: Dedicated request type with "Quote" label * **Customer Linking**: Automatically finds or creates customer profiles * **Email Integration**: Reply-to set to customer email for easy responses **Request Management:** * View all quote requests in dashboard * Filter by type (Quote, Support, Refund, etc.) * Track request status (Open, In Review, Resolved) * Assign to team members * Add internal notes * Link to created invoices ### 🎨 Professional Customer Experience Built-in features for a polished experience. * **Success Callout**: Green checkmark confirmation when quote sent * **Error Handling**: Clear error messages if something goes wrong * **Form Validation**: Email format checking, required fields * **Loading States**: "Sending..." button during submission * **Mobile Optimized**: Works perfectly on all devices **How It Works:** 1. Customer clicks "Request Custom Quote" on your freelancer page 2. Fills form with name, email, and message 3. Clicks "Send Request" → Shows "Sending..." 4. Green success callout appears: "Quote request sent!" 5. You receive email + dashboard notification 6. Respond to customer and convert to invoice > [!TIP] > > **Pro Tip**: Respond within 4 hours for best conversion rates. Quick responses show professionalism and increase your chances of winning the project. **2025-11-02** v2.7.0 ## AI-Powered Products & Smart Subscription Management Save time with AI-generated product descriptions, offer profitable add-ons with markup pricing, and collect payments faster with one-click mandate charging. ### 🤖 AI Product Description Writer Never stare at a blank screen again. Generate professional product descriptions in seconds. * **Click the Sparkles Icon**: Located right in your product editor toolbar * **Instant Professional Copy**: AI writes 2-3 sentences highlighting your product's benefits * **Sales-Focused**: Emphasizes value and what customers get, not just features * **Edit & Personalize**: Use as a starting point and customize to match your brand * **Always Available**: Works for any product - just enter a product name and click **Perfect for:** * Quickly creating product catalogs * Maintaining consistent professional tone * Overcoming writer's block * Saving hours of copywriting time ### 💰 Flexible Add-On Pricing Offer extras and upgrades with automatic price calculations. Perfect for upselling services and options. **Toggle Add-Ons** * Simple on/off switches for extras (SSL certificate, priority support, etc.) * Price clearly shown: "+€25.00" * Customers see exactly what they're paying for **Dropdown Options** * Different pricing tiers in one product (Basic/Pro/Enterprise) * Each option can have its own markup price * Great for server resources, storage tiers, feature bundles **Works Everywhere** * Customer shop checkout * Subscription creation in dashboard * Automatic price calculation: (Base Price + Selected Add-ons) × Quantity **Smart Custom Pricing** * Set a fixed custom price when creating subscriptions * Add-ons automatically excluded (custom price is final amount) * Clear info message explains no add-ons will be charged * Perfect for special deals and negotiated contracts ### ⚡ Instant Mandate Charging Get paid faster. Charge existing SEPA mandates with one click instead of waiting for the billing cycle. **How It Works** 1. Open any unpaid invoice linked to a subscription with mandate 2. See the **"⚡ Charge Mandate Now"** button 3. Click to charge immediately 4. Payment processes via existing SEPA mandate 5. Invoice marked as processing **Safety Features** * Only appears for invoices with active mandates * Prevents duplicate charges (checks last 5 days) * Shows processing status after charging * Clear messaging about 1-3 day SEPA processing time **Perfect For** * Charging early renewals * Processing failed billing immediately * Getting cash flow faster * Reducing wait time for scheduled billing ### 🔄 Improved Manual Renewals Create invoices for subscriptions anytime, with automatic mandate detection. **Automatic Payment Method Selection** * **Has Mandate**: Charges SEPA mandate automatically * **No Mandate**: Sends invoice email with payment link to customer **Smart Redirect** * Takes you to the invoice page (not payment checkout) * You see the invoice, customer gets charged or emailed * Clear success messages explain what happened **Perfect For** * Billing early renewals * Processing extra charges mid-cycle * Offering discounts with manual invoicing ### 🎨 Better User Experience Small improvements that make your daily work smoother. **Clearer Payment Status** * Processing indicator replaces button after charging * Shows "Payment Processing - SEPA Direct Debit pending (1-3 business days)" * No confusion about whether charge went through **Transaction Visibility** * Fixed: All invoice transactions now appear correctly in Transactions tab * See all payment attempts (pending, paid, canceled, expired) * Payment IDs shown in success messages for easy tracking **Price Summaries** * Detailed breakdown: Base Price + Add-ons + Quantity = Total * Only shows add-ons when applicable * Clear indication when custom pricing is used ### 💡 What This Means For Your Business **Save Time** * AI writes product descriptions in seconds, not hours * Automatic price calculations eliminate manual math * One-click charging faster than manual bank transfers **Increase Revenue** * Easy to offer add-ons and upgrades * Clear pricing encourages upsells * Faster payments improve cash flow **Reduce Errors** * Smart custom pricing prevents double-charging * Duplicate charge prevention protects your reputation * Clear status indicators reduce support questions **Professional Experience** * Consistent product descriptions across catalog * Clean, modern interface throughout * Customer-friendly checkout with clear pricing ### 🐛 Fixes & Improvements * **Transaction Display**: Fixed issue where some invoice transactions weren't appearing in the Transactions tab * **Price Calculations**: Subscription summaries now correctly show totals including add-on markup * **Status Updates**: Payment processing status now updates immediately after charging mandates * **Error Messages**: Clearer explanations when operations can't be completed **2025-09-30** v2.6.0 ## Invoice Payment Links & Retry System Major improvements to how customers pay invoices, making failed or canceled payments easier to retry and giving you more control over payment links. ### 🔗 Invoice Payment Links * **Easy Sharing**: Share invoice payment links directly from your dashboard * **Invoice Status Badges**: Payment pages show invoice number with color-coded status (Paid, Pending, Overdue) * **QR Code Support**: Generate QR codes for mobile payments - perfect for in-person or printed invoices * **Permanent Links**: Payment links never expire and work until the invoice is paid ### 🔄 Payment Retry System * **Smart Retry**: Failed or canceled payments can be easily retried using the same invoice * **Auto-Fill Everything**: Retry links remember all customer details - no need to re-enter information * **No Duplicate Invoices**: System reuses the same invoice instead of creating duplicates * **Clear Status Display**: Customers see if an invoice is already paid before attempting payment ### 💳 Payment Page Enhancements * **More Pre-Fill Options**: Share links with customer info, amounts, payment methods, and addresses pre-filled * **Product Links**: Link directly to specific products with prices automatically filled in * **Custom Fields Support**: Collect additional information like domain names or custom requirements * **Mobile Friendly**: All payment pages work perfectly on phones and tablets ### 🎯 Customer Experience Improvements * **Paid Invoice Display**: Customers see a clear success message with payment details for already-paid invoices * **Item Breakdown**: Complete list of purchased items with quantities and prices * **Payment Protection**: Can't accidentally pay the same invoice twice * **Faster Checkout**: Pre-filled information speeds up the payment process ### 📚 New Documentation * **Invoice Payment Links Guide**: Learn how to share payment links effectively * **Payment Retry Instructions**: Help customers retry failed payments * **Payment Page Parameters**: Complete guide to pre-filling payment information * **QR Code Usage**: How to use QR codes for quick mobile payments ### 🐛 Reliability Improvements * **Order Status Updates**: Orders now correctly show as "completed" after successful payment * **Faster Processing**: Improved webhook handling for quicker payment confirmations * **Subscription Activation**: Subscriptions activate immediately after payment instead of staying "pending" * **Better Error Recovery**: Automatic retry of failed payment notifications ### 💡 What This Means For You * **Less Support Work**: Customers can retry failed payments themselves * **Professional Experience**: Consistent, branded payment flows everywhere * **Better Tracking**: Clear payment status throughout your dashboard * **More Flexibility**: Multiple ways to share payment links (email, SMS, QR codes) * **Happier Customers**: Smooth payment experience reduces abandonment ### 🎨 Quality of Life Updates * **Cleaner URLs**: Simplified payment link format for better sharing * **Unified System**: All invoice payments now use the same reliable payment page * **Automatic Updates**: Payment status syncs across invoices, orders, and subscriptions * **Better Navigation**: Easy access to payment links from invoice details and lists **2025-09-29** v2.5.2 ## Iframe Payment Integration Fix Enhanced checkout process to work seamlessly when embedded in iframes, resolving iDEAL payment issues. ### 🎯 Iframe Payment Support * **Embedded Checkout**: PayRequest checkout now works perfectly when embedded in third-party websites * **iDEAL Integration**: Fixed payment flow for iDEAL and other payment methods within iframes * **Parent Window Redirect**: Smart detection automatically redirects to payment pages in the parent window * **Universal Compatibility**: Works with all payment providers that have frame restrictions ### 💡 User Benefits * **Seamless Integration**: Businesses can embed PayRequest checkout forms anywhere * **No Payment Interruptions**: Customers complete payments without technical errors * **Better User Experience**: Smooth transition from embedded forms to secure payment pages * **Wide Compatibility**: Works across different websites and integration methods **2025-09-29** v2.5.1 ## Payment Reminder Race Condition Fix Critical bugfix preventing payment reminders from being sent for already paid invoices. ### 🐛 Race Condition Fix * **Database Synchronization**: Added fresh database checks to prevent stale component state * **Real-Time Validation**: Verify invoice status at the moment of reminder sending * **User Feedback**: Clear error messages when attempting to send reminders for paid invoices * **Webhook Reliability**: Prevents race conditions between webhook processing and user actions ### 🔧 Technical Details * **Problem**: Users could send reminders for invoices that were paid during their session * **Root Cause**: Livewire component state not updated when webhooks processed payments * **Solution**: Double-check invoice status with fresh database query before sending reminders * **Impact**: Eliminates customer confusion from receiving reminders for already paid invoices **2025-09-29** v2.5.0 ## Product Duplication & Category Display Types New powerful features for managing your product catalog with enhanced organization and efficiency. ### 🔄 Product Duplication System * **One-Click Duplication**: Copy any product with customizable name and price * **Modal Interface**: Clean popup for quick edits during duplication * **Complete Copy**: All settings, descriptions, and configurations preserved * **Time-Saving**: Perfect for creating product variations and seasonal items ### 📋 Category Display Types * **Cards Layout**: Visual grid display perfect for products with images * **List Layout**: Horizontal layout ideal for services and detailed descriptions * **Price Table Layout**: Professional comparison tables for plans and tiers * **Flexible Organization**: Each category can use a different display type ### 🎯 Enhanced Shop Experience * **Category-Specific Headers**: Categories show their name and description instead of generic text * **Clean Navigation**: Removed generic welcome text for focused product browsing * **Professional Appearance**: Better visual hierarchy and customer experience ### 🛠️ Technical Improvements * **PostgreSQL Compatibility**: Fixed boolean field handling for reliable product operations * **Better Performance**: Optimized database queries and field management * **Translation Support**: Full Dutch language support for all new features **2025-09-26** v2.4.0 ## Complete Documentation Redesign Brand new comprehensive documentation to help you get the most out of PayRequest. ### 📚 New Help Resources * **Getting Started Guide**: Interactive setup checklist for new users * **Payment Methods**: Complete guide to connecting Mollie, Stripe, and other providers * **Custom Domains**: Professional branded storefronts for your business * **Customer Portal**: Self-service tools for your customers ### 🎨 Enhanced Experience * **Interactive Components**: Expandable sections and tabbed content * **Visual Examples**: Real-world screenshots and use cases * **Mobile Optimized**: Perfect experience on all devices * **Fast Search**: Instantly find what you need **2025-09-26** v2.3.8 ## Improved Shopping Cart Enhanced cart functionality with better quantity management and custom field support. ### 🛒 Cart Improvements * **Quantity Management**: Easier product quantity adjustments * **Custom Fields**: Support for product-specific customer information * **Better Validation**: Improved error handling and user feedback * **Session Persistence**: Cart contents saved across browser sessions ### 🔧 Technical Fixes * **Mandate Sync**: Automatic synchronization for subscription orders * **Webhook Reliability**: Fixed 404 errors on custom domains * **API Access**: Resolved Mollie API mandate access issues **2025-09-25** v2.3.7 ## Enhanced Activity Tracking Improved history views with better organization and visual design. ### 📊 Better Organization * **Segmented Tabs**: Replace dropdowns with visual tab navigation * **Timeline Sorting**: Most recent activities shown first * **Activity Logging**: Comprehensive tracking of invoice and subscription changes * **Visual Callouts**: Important events highlighted with colored indicators ### 🎯 User Experience * **Cleaner Interface**: Modern tab-based navigation * **Better Context**: Clear visual hierarchy for different event types * **Faster Navigation**: Quick access to relevant information **2025-09-24** v2.3.5 ## Enhanced Platform Reliability Improved platform stability and automatic issue resolution for better uptime. ### 🛠️ Platform Improvements * **Automatic Monitoring**: Continuous health checks every 15 minutes * **Self-Healing**: Automatic resolution of common issues * **24/7 Reliability**: Proactive maintenance prevents downtime * **Better Performance**: Faster loading and smoother experience ### 📊 What This Means for You * **Less Downtime**: Issues fixed before you notice them * **Consistent Service**: Reliable access to your billing dashboard * **Peace of Mind**: Your billing operations run smoothly around the clock **2025-09-24** v2.3.5 ## Automated Maintenance & Custom Setup Fees Platform reliability improvements and enhanced setup fee customization. ### 🛠️ Automated Maintenance * **Self-Healing System**: Automatic issue detection and resolution * **24/7 Monitoring**: Continuous health checks prevent downtime * **Proactive Fixes**: Problems solved before they affect your business * **Better Uptime**: More reliable access to your billing dashboard ### 💰 Custom Setup Fee Names * **Personalized Terms**: Use "Borg", "Installation Fee", or any custom name * **Clear Descriptions**: Explain what setup fees cover to customers * **Multi-Language**: Dutch, English, and other language support * **Business Specific**: Terms that match your industry and customer expectations **2025-09-23** v2.3.0 ## Enhanced Payment Processing & Product Sharing Major improvements to payment handling and new product sharing capabilities. ### 💳 iDEAL Payment Improvements * **Instant Activation**: Subscriptions start immediately after iDEAL payments * **Better Reliability**: Enhanced payment processing for Dutch customers * **Faster Setup**: Quicker mandate creation and subscription activation * **Reduced Support**: Fewer customer questions about payment status ### 🔗 Product Sharing & QR Codes * **Professional Links**: Share products with your custom domain * **QR Code Generation**: Perfect for in-person sales and marketing materials * **Easy Sharing**: One-click link copying for emails and social media * **Mobile Optimized**: Works seamlessly on phones and tablets ### 🌍 Dutch Language Support * **Complete Translation**: Full Dutch interface for Dutch customers * **Localized Content**: Documentation and help content in Dutch * **Cultural Adaptation**: Payment terms and business language that fits the Dutch market **2025-09-22** v2.2.5 ## Order Management & Checkout Improvements Enhanced order handling with better deletion options and checkout flexibility. ### 🛍️ Order Management * **Order Deletion**: Delete orders with related items for cleaner records * **Status Filtering**: Better organization with status-based filtering * **Checkout Parameters**: Support for disabled checkout fields * **Address Handling**: Improved URL parameter processing for customer addresses ### 💳 Payment Processing * **Subscription Webhooks**: Instant subscription activation for one-time payments * **Amount Display**: Fixed monetary formatting issues across the platform * **Sync Improvements**: Better Mollie integration and balance visibility **2025-09-21** v2.2.0 ## Subscription System Overhaul Major improvements to subscription management and database performance. ### 🔄 Subscription Enhancements * **Better Performance**: Faster subscription processing and management * **PostgreSQL Fixes**: Resolved database compatibility issues * **Customer Management**: Enhanced tools for managing customer subscriptions * **Improved Reliability**: More stable subscription billing and processing ### 📊 Platform Improvements * **Database Optimization**: Significant performance improvements * **Error Handling**: Better error messages and user feedback * **Data Integrity**: Enhanced data validation and consistency **2025-09-20** v2.1.8 ## Enhanced Analytics & Banking Integration New insights dashboard features and improved bank connectivity. ### 📊 Analytics Improvements * **Bank Balance Cards**: Real-time account balance display from Ponto integration * **Subscription Renewals**: Upcoming renewal tracking and management * **Better Insights**: Enhanced dashboard with actionable business metrics * **Performance Tracking**: Improved monitoring of key business indicators ### 🏦 Banking Features * **Ponto Integration**: Enhanced bank account connectivity * **Balance Monitoring**: Real-time account balance tracking * **OAuth Improvements**: Better authentication flow for bank connections * **Sync Reliability**: More stable bank transaction synchronization **2025-09-17** v2.1.5 ## Modern Design & Checkout Enhancements Complete design refresh with improved checkout functionality. ### 🎨 Design Improvements * **Modern Cards**: Contemporary card styling throughout the platform * **Dark Theme**: Elegant dark mode options for better user experience * **Professional Layout**: Cleaner, more professional interface design * **Mobile Responsive**: Optimized experience across all devices ### 🛒 Checkout Enhancements * **Pre-filled URLs**: Support for pre-populated checkout forms * **Custom Fields**: Enhanced custom field handling in checkout process * **PayRequest.me Domain**: Cleaner, more professional payment URLs * **Better Validation**: Improved form validation and error handling **2025-09-13** v2.1.0 ## Customer Management & Email Automation Advanced customer relationship tools with automated email workflows. ### 👥 Customer Management * **Customer Tags**: Organize customers with customizable tags and filtering * **Modern Card Design**: Beautiful customer cards with improved information display * **Tag Filtering**: Quick customer searches using tag-based filters * **Health Tracking**: Monitor customer email health and engagement ### 📧 Email Automation * **Smart Workflows**: Automated email responses based on customer behavior * **Health Monitoring**: Track email bounces, complaints, and delivery issues * **Customer Segmentation**: Target specific customer groups with relevant messaging * **Automation Rules**: Set up custom triggers for email campaigns **2025-09-11** v2.0.8 ## Invoice Refunds & Improvements Complete refund system with better invoice management tools. ### 💰 Refund System * **Full Refund Support**: Process complete or partial refunds easily * **Duplicate Prevention**: Automatic protection against accidental double refunds * **Visual Indicators**: Clear refund status display for invoices * **Business & Customer Views**: Comprehensive refund information for all users ### 📄 Invoice Enhancements * **Improved Sidebar**: Better invoice detail navigation and information display * **Enhanced UX**: Cleaner interface with better user experience * **Translation Updates**: Improved Dutch language support throughout * **Amount Display**: Fixed critical monetary formatting issues **2025-09-09** v2.0.5 ## Team Management & Product Categories Enhanced collaboration tools and better product organization. ### 👥 Team Management * **Complete Team System**: Invite and manage team members with role-based access * **Invitation Cleanup**: Automatic cleanup of expired team invitations * **Better Permissions**: Granular control over team member access levels * **Improved Workflow**: Streamlined team collaboration features ### 📦 Product Categories * **Category System**: Organize products into logical categories * **Better Navigation**: Easier product discovery and management * **Pricing Fixes**: Resolved critical Mollie migration pricing issues * **Enhanced Organization**: Cleaner product management interface **2025-09-06** v2.0.0 ## PayRequest 2.0 Platform Launch Major platform redesign with modern technology and enhanced reliability. ### 🚀 Modern Platform * **New Technology Stack**: Updated to latest Laravel, Livewire, and FluxUI * **Modern Interface**: Complete redesign with contemporary card-based layouts * **Logo System**: Dynamic logo switching and improved branding * **Better Performance**: Faster loading times and smoother interactions ### 🔧 Reliability Improvements * **Webhook System**: Comprehensive webhook reliability and failure recovery * **Billing Improvements**: Enhanced subscription billing and payment processing * **CSV Export**: Complete export functionality with proper monetary formatting * **Security Enhancements**: Improved security across all platform features **2025-09-04** v2.4.0 ## Enhanced Data Management & Security Major improvements to data export capabilities and customer management security. ### 📊 Comprehensive CSV Export * **Monetary Value Fixes**: Accurate financial data in all exports * **Custom Field Support**: Export custom field data for detailed analysis * **Multi-format Options**: Choose the data format that works for your workflow * **Bulk Operations**: Export large datasets efficiently ### 🔒 Enhanced Security * **Customer-Specific Access**: Improved mandate sync with proper user isolation * **Bulk Action Security**: Fixed security issues in bulk operations * **Data Privacy**: Better protection of customer financial information * **Audit Trail**: Complete tracking of all data access and modifications **2025-09-02** v2.3.8 ## Advanced Organization & Subscription Analytics Powerful new tools for organizing customers and tracking subscription performance. ### 🏷️ Enhanced Tag Management * **Advanced Search**: Find tagged customers and subscriptions instantly * **Smart Pagination**: Navigate large tag lists efficiently * **CSV Export**: Export tagged data for external analysis * **Improved Layout**: Cleaner interface for better productivity ### 📊 Subscription Insights * **Duration Tracking**: Visual progress indicators for subscription lifecycles * **Internal Notes**: Add private notes to subscription records * **Performance Analytics**: Better understanding of subscription health * **Timeline Views**: Clear history of subscription changes **2025-08-30** v2.3.7 ## Trial System & Performance Optimization Complete trial functionality and major performance improvements for better user experience. ### 🎁 Free Trial System * **Product Trials**: Offer free trials on any subscription product * **Automatic Conversion**: Seamless transition from trial to paid subscription * **Customer Communication**: Clear trial status and billing information * **Business Control**: Configure trial length and terms per product ### ⚡ Performance Improvements * **99.9% Faster Sync**: Eliminated performance bottlenecks in payment processing * **Real-time Notifications**: Instant business notifications for important events * **Reduced Database Load**: Optimized queries prevent system slowdowns * **Better Monitoring**: Sentry integration for proactive issue resolution **2025-08-28** v2.3.5 ## Custom Domain Excellence & Payment Enhancements Professional branded storefronts with advanced payment capabilities. ### 🌐 Custom Domain Perfection * **Seamless Integration**: Your domain works flawlessly with all PayRequest features * **Cart Functionality**: Shopping cart works perfectly on custom domains * **Asset Loading**: Optimized performance on your branded storefront * **Route Management**: Smart routing prevents conflicts and errors ### 💳 Advanced Payment Options * **Saved Payment Methods**: Customers can reuse trusted payment methods * **SEPA Direct Debit**: Streamlined European bank payments * **Payment Button States**: Clear feedback during payment processing * **Mandate Management**: Automatic handling of payment authorizations **2025-08-27** v2.3.0 ## Payment Processing Excellence & Multi-Language Support Major improvements to payment reliability and complete Dutch language support. ### 💳 Enhanced Payment Processing * **Custom Domain CSRF**: Bulletproof security for custom domain payments * **Livewire Integration**: Seamless real-time payment processing * **Subscription Management**: Fixed mandate issues for reliable recurring billing * **Payment History**: Complete transaction tracking and customer payment portals ### 🌍 Complete Localization * **89.6% Dutch Coverage**: Nearly complete Dutch language interface * **Payment Translations**: Clear payment terms in customer's language * **Cultural Adaptation**: Payment flows optimized for Dutch market * **Multi-Language Ready**: Foundation for additional language support **2025-08-25** v2.2.5 ## Email System Overhaul & Enhanced Integrations Professional email communications and improved third-party integrations. ### 📧 Advanced Email System * **Email Template Management**: Custom templates for all communications * **Template Variables**: Dynamic content personalization * **Delivery Tracking**: Monitor email delivery success and failures * **Professional Design**: Branded email templates that match your business ### 🔗 Banking Integration * **Ponto Enhancement**: Improved bank account synchronization * **Transaction Matching**: Automatic reconciliation of bank transactions * **Real-time Updates**: Faster sync with your business bank accounts * **Error Recovery**: Robust handling of API connection issues ### 🖼️ Visual Improvements * **Product Images**: Upload and manage product photos * **Logo Management**: Easy logo upload and customization * **Dark Mode**: Enhanced dark mode support throughout the platform * **UI Polish**: Improved dropdowns, cards, and visual elements **2025-08-23** v2.2.0 ## Advanced Customization & Activity Monitoring Powerful tools for customizing products and tracking customer interactions. ### 🎛️ Advanced Custom Fields * **Select Fields**: Dropdown options with pricing markup * **Toggle Fields**: Boolean options for add-on services * **Required Validation**: Ensure important information is collected * **Cart Integration**: Custom field data flows seamlessly through checkout * **Quantity Selection**: Flexible quantity management per product ### 📊 Complete Activity Tracking * **Customer Logs**: Track all customer interactions and changes * **Email History**: Monitor invoice and payment email delivery * **Audit Trail**: Complete history of all system activities * **Performance Insights**: Understand customer behavior patterns ### 📧 Professional Email Templates * **Custom Templates**: Design emails that match your brand * **Template Variables**: Personalize emails with customer and business data * **Resend Functionality**: Easy re-sending of important communications * **Queue Management**: Reliable email delivery with retry capabilities **2025-08-21** v2.1.8 ## Enhanced Mollie Integration & Developer Tools Major improvements to payment provider connections and debugging capabilities. ### 🔗 Mollie OAuth Enhancement * **Bi-directional Sync**: Automatic customer synchronization between PayRequest and Mollie * **Token Management**: Automatic token refresh prevents connection interruptions * **Proxy Support**: Enhanced API reliability for all Mollie operations * **Debug Tools**: Comprehensive scripts for troubleshooting integration issues ### 🔧 Developer Experience * **PostgreSQL Optimization**: Fixed boolean field handling for better database performance * **Sequence Management**: Automatic fix for database sequence issues * **Error Logging**: Enhanced logging for faster issue resolution * **Configuration Scripts**: Automated setup tools for production deployment **2025-08-19** v2.1.5 ## Streamlined Onboarding & Invoice Automation Simplified user experience with powerful automation features. ### 🚀 Magic Link Authentication * **Passwordless Login**: Secure email-based authentication * **Onboarding Flow**: Guided setup for new users * **Reduced Friction**: Faster access to your billing dashboard * **Security First**: Enhanced security without password complexity ### 📄 Invoice Automation * **Smart Numbering**: Configurable invoice numbering systems * **Transaction Integration**: Seamless connection between payments and invoices * **Status Tracking**: Real-time invoice status updates * **FluxUI Modernization**: Updated interface with modern table components **2025-08-15** v2.1.0 ## Performance & Reliability Enhancements Major infrastructure improvements for better platform stability. ### ⚡ Performance Optimization * **Queue Management**: Laravel Horizon integration for reliable job processing * **Token Automation**: Automatic refresh of payment provider connections * **Timezone Handling**: UTC-based token management for global reliability * **Database Efficiency**: Optimized queries and proper boolean handling ### 🔄 Enhanced Automation * **Chargeback Monitoring**: Automatic detection and processing of chargebacks * **Sync Reliability**: Improved synchronization with payment providers * **Error Recovery**: Better handling of API failures and timeouts * **Deployment Scripts**: Streamlined production deployment process **2025-08-13** v2.0.8 ## Complete Multi-Language Foundation Comprehensive internationalization system for global businesses. ### 🌍 Translation System * **Laravel i18n Integration**: Professional translation management system * **Dutch Language Support**: Complete Dutch interface for local businesses * **Translation Tracking**: Automated scanning and coverage reporting * **Dynamic Content**: Multi-language support for all user-facing content ### 🎯 Localized Experience * **Shop Localization**: Customer-facing content in local languages * **Invoice Translation**: Localized invoice templates and terminology * **UI Components**: Translated interface elements throughout the platform * **Cultural Adaptation**: Payment terms adapted for different markets **2025-08-11** v2.0.5 ## Professional Payment Pages & Custom URLs Enhanced payment collection with branded, professional appearance. ### 💰 Payment Page System * **Custom Handles**: Professional URLs like payrequest.me/yourhandle * **Flexible Amounts**: Support for custom and fixed payment amounts * **Business Branding**: Professional appearance with your business identity * **Mobile Optimized**: Perfect experience across all devices ### 🎨 Enhanced Interface * **Modern Design**: Contemporary card styling and visual improvements * **Dashboard Optimization**: Faster loading with optimized queries * **Icon Standardization**: Consistent visual language throughout * **Empty State Improvements**: Better guidance when starting with the platform **2025-04-03** v1.5.0 ## Banking Integration & Wise Support Expanded banking capabilities with new financial institution support. ### 🏦 Wise Integration * **Profile Management**: Connect and manage Wise business accounts * **Transaction Sync**: Automatic synchronization of Wise transactions * **Multi-Currency**: Enhanced support for international transactions * **Balance Monitoring**: Real-time account balance tracking ### 🌐 Enhanced Localization * **Language Expansion**: Additional translation coverage for English and Dutch * **Settings Localization**: Multi-language support for all settings pages * **Helper Functions**: Enhanced internationalization tools for developers **2025-03-22** v1.4.0 ## Advanced Mandate & Transaction Management Comprehensive tools for managing payment mandates and transaction details. ### 📋 Mollie Mandate System * **Complete Management**: Full lifecycle management of SEPA Direct Debit mandates * **Enhanced Logging**: Detailed logging and pagination for mandate operations * **Customer Linking**: Automatic linking of mandates to customer records * **Status Tracking**: Real-time mandate status monitoring ### 📊 Transaction Insights * **Detail Views**: Comprehensive transaction information with formatted metadata * **Responsive Design**: Mobile-optimized transaction displays * **Enhanced Formatting**: Improved layout and visual presentation * **JSON Formatting**: Professional display of complex transaction data **2025-03-20** v1.3.0 ## Customer Management & Navigation Improvements Streamlined customer management with improved navigation and search. ### 👥 Customer Experience * **Detailed Views**: Comprehensive customer detail pages with subscription information * **Smart Navigation**: Direct links between related records (customers, subscriptions, payments) * **Search Integration**: Enhanced Algolia search with customer and subscription indexing * **Simplified Interface**: Cleaner navigation with better user experience ### 🔗 Relationship Management * **Connected Data**: Seamless navigation between customers, subscriptions, and payments * **Context Awareness**: Smart buttons and links based on available data * **Improved Organization**: Better grouping and presentation of related information *** ## 🔮 Coming Soon We're constantly working on new features and improvements. Here's what's on our roadmap: ### Q2 2026 * **Multi-Currency**: Full support for international currencies * **Advanced Reporting**: Custom dashboard builder and data visualization * **AI-Powered Insights**: Machine learning for churn prediction and revenue optimization * **Stripe Payment Provider**: Full Stripe integration alongside Mollie *** > [!TIP] > > **Stay Updated**: Follow our [GitHub repository](https://github.com/payrequestio/payrequest.me) for the latest updates and contribute to the PayRequest community. # Your Customer Account Source: https://docs.payreque.st/customer-guide/customer-account Sign in to a business’s PayRequest account area and find your invoices, orders, services, subscriptions and support. Your customer account belongs to the business you are buying from. Use that business's payment page, shop or login link. The PayRequest business dashboard is for the business itself. ## Sign in without a password **1. Open the business's page** Use the link in your order, invoice or message from the business. Choose the customer **Login** or account menu where available. **2. Enter your email address** Use the same address as your purchase or invoice, or the address the business has invited as a contact. **3. Open the email login link** Follow the login link sent to your inbox. You do not need to remember a customer password. Keep this link private because it grants access to your account. If no email arrives, check spelling and spam folders. If the link has expired, request a new one from the same business's login page. If you no longer have access to the original email address, contact the business to verify your identity and arrange access. ## Which account area do you have? | Area | What you may see | | - | - | | **Payment-page account** | Notification settings, contacts, saved payment methods, a subscription overview and support. | | **Shop customer portal** | Invoices, orders, **My services**, saved payment methods, profile details, support and notifications. | | **Deposit link** | The request or status for a specific deposit. Keep the original link even if you also use a customer portal. | A business may use only a payment page. That does not mean an invoice or purchase is missing because it has no full shop portal. Ask the business for the relevant invoice or order link. ## Invoices and orders In a shop portal, open **Invoices** to view available invoices, download PDFs and pay outstanding amounts. Check a pending payment before starting another one. Open **Orders** for purchase details and any eligible digital downloads. Download availability can depend on payment status, access limits and the product purchased. If a record is missing, confirm you are on the correct business's page and used the purchase email address. Contact the business with your order or invoice reference rather than creating a second purchase. If an invoice or payment link supports partial payments in multiple installments, your customer account will show the payment progress, including amounts already paid and the current due installment. If an invoice is still open after a payment, follow [I paid, but my invoice is still open](/customer-guide/invoice-still-open) before paying again. ## Services and subscriptions Open **My services** or the subscription section offered by the business. Review the service status, price, billing interval and next billing date. Pause, resume or cancellation controls appear only when the service, business settings and your permissions allow them. A payment-page subscription list may be read-only; use the shop portal or contact the business if you need an action that is not shown. When requesting cancellation, read the effective date and any notice period. Sending a request does not necessarily end the service immediately or cancel existing invoices. Check the confirmation and contact the business if the displayed date is unclear. ## Domains, DNS and website forwarding For a domain service, follow [Manage your domain, DNS and email](/customer-guide/manage-domain) to choose nameservers, switch to the business's DNS, configure Google Workspace or forward your website. Availability depends on the business's domain integrations and your contact role. ## Cancel, pause or review an offer Use [Cancel or pause your subscription](/customer-guide/manage-subscription) for a step-by-step guide to requests, effective dates, existing invoices and alternative proposals. A cancellation request and an immediately ended subscription are different outcomes. ## Details, contacts and payment methods Where the controls are available, you can update profile details, notification preferences or contacts, and review saved payment methods. Additional contacts may have restricted access according to their role. Removing or revoking a payment method does **not** cancel your subscription or erase an outstanding invoice. Arrange cancellation separately with the business. ## If you are an additional contact Use your own contact email at the business's customer login page. The business or customer administrator must enable **Portal access** for that contact. Email-copy preferences alone do not enable login. Portal roles control which sections you can use: Admin has account-management access, Billing focuses on invoices/payment methods, and Operations/Viewer have different viewing and support scopes. A job label such as “Technical” is separate from the portal permission role. Ask the account owner to check your role if an action is missing. Cancellation proposals require the primary customer or an enabled Admin contact to accept or decline. ## Support and security deposits Use **Support** to send a message to the business and follow its replies. For a deposit, use the original deposit link to check its status; do not expect every deposit to appear as an invoice or order. > [card] [Security deposits](/customer-guide/security-deposits) > > Understand a hold, release or deposit charge. > [card] [Getting help](/customer-guide/getting-help) > > Resolve login problems or ask the business about a transaction. ## Choose your invoice emails Open **Settings → Notifications** in the business’s customer portal. Switch **Payment confirmation** off if you do not want invoice-paid confirmation emails. **New invoice** and **Payment reminders** have separate switches, so you can keep them enabled. Payment confirmations are enabled by default. Your current preference is checked again before delivery, including for queued confirmations. Changing this setting does not change whether an invoice is paid. # Getting Help as a Customer Source: https://docs.payreque.st/customer-guide/getting-help Contact the business about payments, bookings, refunds or deposits, or get help with a PayRequest page. ## Contact the business first For an order, invoice, cancellation, deposit release, charge explanation or refund, contact the **business you paid or booked with**. It holds the purchase details and decides how to handle the request. Use the contact details in its message or website. Where available, sign in to its customer account area and open **Support**. Describe the issue, select the related record if offered and submit the request. Keep the ticket reference and check the thread for replies. If the portal offers a refund or cancellation request, read the confirmation carefully: submitting the request does not itself guarantee approval, an immediate refund or an immediate cancellation. Before contacting the business, you can follow [the open-invoice payment guide](/customer-guide/invoice-still-open) or [the subscription cancellation guide](/customer-guide/manage-subscription) for the relevant checks. ## Include the details needed to investigate * Business name and the email address used for the purchase. * Invoice, order, booking or deposit reference, if you have one. * Amount, currency and the date of the payment or authorization. * What the page says and what you expected to happen. * For a bank entry: whether it is pending or completed, its displayed description and your card's last four digits. If the bank appears to show two holds, include the date and amount of **each** entry. Ask the business to verify both references before making another payment or authorization. > [!WARNING] > > Never send your full card number, card security code, bank password or one-time login codes. Crop screenshots to the relevant entries and hide unrelated financial details. Keep customer login and deposit links private. ## A released deposit still appears at the bank Ask the business to confirm the provider release result, date and time, released amount and payment reference. Your bank or card issuer can investigate why the pending entry is still visible. A release of reserved funds is different from a refund of money already charged. See [Security deposits for customers](/customer-guide/security-deposits). ## Trouble with PayRequest itself If a payment page fails to load, a login link does not work or the business cannot resolve a platform problem, email [support@payrequest.io](mailto:support@payrequest.io). Include the business name, page address and error message. Share private access links only with the business or support, never in public. PayRequest can help investigate the software and payment status. The business remains your contact for its service, terms and approval of deposit charges, cancellations or refunds. > [card] [Your customer account](/customer-guide/customer-account) > > Sign in and find available support and account features. > [card] [Paying a business](/customer-guide/payments) > > Check a pending or unclear payment before trying again. # I Paid, but My Invoice Is Still Open Source: https://docs.payreque.st/customer-guide/invoice-still-open Check a pending payment, bank transfer or manual payment confirmation without accidentally paying twice. If your bank shows a payment but the invoice is still open, **check the existing payment before paying again**. A bank entry, your checkout result and the business's invoice status can update at different times. ## Start with the original invoice Open the invoice link sent by the business, or **Invoices** in its customer portal where available. Check the invoice reference, total, currency and current status. Also check the email address used for the payment, including its spam folder. If you paid from a different email address, tell the business rather than creating a second purchase or account to find it. ## Match your situation | What you see | What to do | | - | - | | **Pending / processing** | The payment is not confirmed yet. Check again later or ask the business to verify the existing provider reference. | | A **pending card entry** | Ask whether it is a reservation or a completed charge. Your bank's wording may not make the difference clear. | | A bank transfer sent from your banking app | Check the recipient, exact amount, currency and payment reference. Sending the transfer does not itself prove the business received and matched it. | | You selected **I have paid** | This tells the business you made an external transfer. It is not automatic verification that money arrived. | | A failure message, but money appears at your bank | Share both results with the business and ask it to check the exact payment before retrying. | | Two visible payments or reservations | Ask the business to investigate both entries; do not assume one is a duplicate or ordinary processing. | ## If you paid by bank transfer Compare the bank details against the original instructions. Include the payment reference exactly as supplied. Missing or different references, a different amount or currency, and bank processing can prevent or delay matching. Send the business your transfer date, amount, currency, invoice number and the reference you used. It can check incoming funds and any matching process. The presence and timing of automatic matching depend on the business's payment setup. Do not transfer again just to correct the reference. Ask the business to reconcile the original payment first. ## If you used an external payment app For methods that ask you to pay outside PayRequest and return to select **I have paid**, the business must verify receipt in its bank or payment app. That confirmation button does not collect the money itself or guarantee the invoice is paid. If you did not actually complete the external transfer, tell the business so it can check the request. Follow up in the same conversation rather than repeatedly submitting confirmations. ## If it was a security deposit A card authorization reserves funds rather than paying an ordinary invoice. Releasing that reservation may remove the pending bank entry without a separate incoming refund. Use the original deposit link and the [security-deposit guide](/customer-guide/security-deposits). An advance-payment invoice for a booking or quote is different: payment of that invoice collects the advance amount. ## What to send the business * Invoice or order number and the email address used. * Amount, currency and payment date, including the approximate time if relevant. * Payment method and displayed reference or description. * Whether your bank says **pending** or **completed**. * For a card, only its last four digits if needed to identify the entry. A cropped screenshot can help. Hide unrelated transactions, balances and full card or bank details. Never send card security codes, banking passwords or one-time login codes. The business can compare the invoice with its payment provider records and confirm whether it received payment, needs to match it, or is still waiting for a result. If the business confirms a completed payment but the page still disagrees, it can contact PayRequest Support with the references. [Contact the right support team](/customer-guide/getting-help) # Manage Your Domain, DNS and Email Source: https://docs.payreque.st/customer-guide/manage-domain Choose nameservers, switch to your provider’s DNS, forward a website and set up Google Workspace from your customer account. Sign in to the **business that manages your domain**, open **My services**, and select the domain. The **Domain** tab shows its registration information and nameservers. Depending on the business's setup, you can also use **DNS** and **Forwarding**. The primary customer, enabled customer administrators and operations contacts can change DNS settings. Billing and viewer contacts have read-only DNS access. If an action is missing, contact the business. ## Choose DNS when ordering a new domain | Option | Where you manage DNS | | - | - | | **Manage DNS through the business** | Your provider configures the domain's assigned nameservers after payment. Manage records in your customer account. | | **Use your own nameservers** | Enter two different nameserver hostnames, such as `ns1.example.net` and `ns2.example.net`. Continue managing DNS with that provider. | A new domain can start with an empty DNS zone. You can add website or mail records later. Registration and nameservers alone do not create a website or mailbox. ## Switch an existing domain to your provider's DNS **1. Prepare DNS and forwarding** Open the domain's **Domain** tab and select **Prepare DNS and forwarding**. This prepares DNS management without changing your current nameservers. **2. Copy the settings you need** Open **DNS** and copy required records from your current DNS provider. Include website addresses, mail records, verification TXT, DKIM and any subdomains you use. Preparation does not automatically import these records. For a redirect-only domain, you can configure **Forwarding** instead. An empty zone is also allowed if you do not need website or mail services yet. **3. Review the nameservers** Return to **Domain** and choose **Review nameserver switch**. Check the current nameservers, new nameservers and prepared record count. **4. Confirm the switch** Confirm that all required records have been copied and checked, or that they are not needed. Select **Switch nameservers now**. The button shows progress and the result appears in the Domain tab. > [!WARNING] > > If you currently use the domain for a website or email, copy the relevant records before switching. A switch to an empty or incomplete zone can interrupt those services. If the preview reports active **DNSSEC**, disable the existing registry DNSSEC using the available Domain controls or ask your provider for help. Create a fresh preview afterwards. You can enable DNSSEC again once managed DNS is active. A preview expires after ten minutes. If you edit records or nameservers, review the switch again before confirming. Nameserver changes and DNS caches take time to propagate; preparing a zone is different from activating it. ## Add or edit DNS records Open **DNS** to view the current records. Use **Add Record**, the edit button or the delete button as needed. **Refresh** reloads records from the DNS provider. | Record | Common use | | - | - | | A / AAAA | Connect a hostname to a website or server IP address. | | CNAME | Point a hostname to another hostname. | | MX | Route incoming email to a mail provider. | | TXT | Add domain verification or email authentication values, such as SPF and DKIM. | Use the exact values supplied by your hosting or email provider. Keep verification records and existing mail settings unless you know they are no longer required. Do not create multiple SPF records at the same hostname. You can prepare records while the zone awaits activation. They become public after the domain uses the assigned nameservers and DNS activates. ## Set up Google Workspace email 1. Open **DNS → Google Workspace → Preview mail settings**. 2. Review the proposed records. For new setups, the template uses `smtp.google.com` as the MX destination with priority `1` and TTL **Auto**. 3. If MX records from another mail provider exist, review the replacement list and confirm that you want incoming mail to go to Google Workspace. 4. Choose **Apply Google Workspace template** and check the result. The template adds Google's SPF record only if no SPF exists. Existing SPF remains unchanged: if it needs Google authorization, combine the required senders into one SPF record using your mail providers' instructions. Existing Google MX records, including legacy Google MX, are kept. Your website records, verification TXT, subdomain mail records, DKIM and DMARC are preserved. A root CNAME that conflicts with mail records must be reviewed before the template can be applied. > [!NOTE] > > You still need your own Google Workspace account. Get domain verification and DKIM values from **Google Admin**, add those TXT records separately with **Add Record**, then complete Gmail and DKIM activation in Google Admin. The template does not create mailboxes or verify your Google account for you. [Google's Gmail MX instructions](https://support.google.com/a/answer/174125) · [Google's SPF instructions](https://support.google.com/a/answer/33786) ## Forward your domain to another website Open **Forwarding**, enter the complete destination URL, and choose: * **301 Permanent** for a lasting move, or **302 Temporary** for a temporary redirect. * **Preserve Path** to keep paths such as `/contact` in the destination. * **Preserve Query String** to keep parameters such as `?ref=campaign`. Save the forwarding settings and check the confirmation. If an existing root A record must be replaced, check the warning first: a website using that record will stop being served from that address. If the domain still uses external nameservers, return to **Domain** to complete the switch. A prepared redirect only works publicly after nameserver activation. If your browser remembers an old redirect, test again in a private window after DNS has updated. ## If a change seems to do nothing Check the message in the **Domain** tab and refresh the page to see the saved nameservers. The new nameservers may already be saved while public DNS still uses cached information. If a confirmation expires or settings change, create a fresh preview. If the result cannot be confirmed, review the current nameservers before trying again. Contact the business with the domain name, action, time and exact message if the state is still unclear. [Get help from the business](/customer-guide/getting-help) # Cancel or Pause Your Subscription Source: https://docs.payreque.st/customer-guide/manage-subscription Find your subscription, understand its end date, review any alternative offer and check what happens to existing invoices. Use the customer account of the **business that supplies your subscription**. Start with its order, invoice or account link and sign in using the purchase email address. ## Find your subscription Open **My services** or the subscription section available in the business's portal, then select the subscription. Check its name, amount, billing interval and next billing date. A payment-page account area may only show a read-only subscription overview. If no management action is shown, ask the business for its portal link or contact it directly. Features also depend on the service and your account permissions. ## Choose the action you need | Action | What it means | | - | - | | **Pause** | Temporarily change the subscription to paused where supported. Confirm with the business what this means for service access and future billing. | | **Resume** | Continue an eligible paused subscription. Check its updated status and billing dates. | | **Cancel** | End the subscription immediately or submit a cancellation request, depending on the business's settings and agreed terms. | Removing a payment method does **not** cancel the subscription. Pausing or canceling also does not automatically erase existing invoices, reverse payments or issue a refund. ## Request cancellation **1. Open the subscription** Confirm you selected the correct service. Choose **Cancel Subscription** when the action is available. **2. Read the confirmation** Some subscriptions cancel immediately. Others ask for a reason and create a request with a notice period. Review the calculated end date before confirming. **3. Keep the result** Check the subscription's cancellation status, effective date and related support request. Save any confirmation email and follow up with the business if the result is unclear. A requested cancellation can leave your subscription active until its effective date. It does not necessarily stop billing on the date you submit the request. Ask the business to explain existing invoices and any amount due before the final end date. ## Understand the end date The business may configure notice in **days** or **calendar months**. One calendar month is not always 30 days: October 15 plus one month is November 15; a month-end date uses the last available day when necessary. The next billing date or an explicit minimum contract end can set a later lower bound. Use the actual date displayed for your subscription and ask the business if it differs from your agreement. Do not infer it only from a generic notice-period description. ## If the business offers an alternative An eligible cancellation request may contain a proposal to end earlier, apply a temporary discount or move to a compatible cheaper subscription. 1. Open the related support request in your portal. 2. Read the complete offer: dates, price, currency, VAT, duration and what happens afterwards. 3. Accept only if you agree to those terms. Acceptance requires the agreement confirmation; only the primary customer or an enabled customer administrator can accept or decline the proposal. For a temporary discount, check when the regular price returns. For a switch, check which product changes and when its new price begins. For an early end, agree on service access and any data export with the business. > [!NOTE] > > Ignoring, declining or letting an offer expire preserves the original cancellation. An offer is not accepted merely because the business publishes it. Accepting a discount or compatible product switch withdraws the pending cancellation according to the offer terms. These proposals do not automatically refund paid invoices or migrate external services. If you already agreed to stop sooner directly with the business, it can confirm an earlier end and send a confirmation; review that date and any separate invoice handling. ## Change your mind Where **Withdraw Cancellation** is offered, read its confirmation before using it. If the option is absent, contact the business. Resuming a paused subscription and withdrawing a cancellation are different actions; a canceled subscription cannot simply be resumed as though it were paused. ## Why a button might be missing The service may not support the action, the business may not enable it, or your contact role may have limited access. Provider-managed subscriptions and services with external provisioning can have additional restrictions. For example, VPNresellers subscriptions do not support customer pausing. Cancellation retains already-paid VPN access until its paid end; it does not grant access for an unpaid renewal. Contact the business through **Support** or its published contact details. Include the subscription reference, requested change and any date you need clarified. [Get help from the business](/customer-guide/getting-help) # Customer Guide Source: https://docs.payreque.st/customer-guide/overview Received a PayRequest link? Learn how to pay, access your account, check a security deposit and get help from the business. This guide is for **customers of businesses using PayRequest**. You might have received a payment link, an invoice, a shop order or a security-deposit request. PayRequest provides the payment and account tools. The business you are buying from manages your booking, order, subscription, deposit and any refund decision. ## Start with the link the business sent you | What you received | What to do | | - | - | | A payment page or payment link | Check the business, amount and currency, then follow [Paying a business](/customer-guide/payments). | | An invoice | Use its payment link, or open **Invoices** in the business's customer portal if available. | | A security-deposit request | Read [Security deposits](/customer-guide/security-deposits) before authorizing. A reservation is different from a payment. | | A customer login link | Follow [Your customer account](/customer-guide/customer-account) to view the features that business offers. | | A payment or deposit you do not understand | [Contact the business](/customer-guide/getting-help) before making another payment or authorization. | ## Common account questions * [I paid, but my invoice is still open](/customer-guide/invoice-still-open). * [Cancel or pause my subscription](/customer-guide/manage-subscription). * [Manage my domain, DNS, email or website forwarding](/customer-guide/manage-domain). ## Payment page, customer account or deposit page? A **payment page** lets you pay a business. Some pages also have a login menu with a small account area for preferences, payment methods, subscriptions and support. A **shop customer portal** has a broader account area, including orders, invoices and services where available. Use the business's own shop or login link to access it. A **deposit page** shows a particular security-deposit request or its status. Keep the original link: a deposit does not have to appear in the same list as your invoices or orders. > [!NOTE] > > The features and buttons you see depend on the business's setup and your account permissions. You do not need to open a PayRequest business account just to follow a payment or deposit link. > [card] [Paying a business](/customer-guide/payments) > > Check a payment link and understand pending payments. > [card] [Your customer account](/customer-guide/customer-account) > > Sign in and find invoices, orders, subscriptions and support. > [card] [Security deposits](/customer-guide/security-deposits) > > Understand card reservations, charges and releases. > [card] [Getting help](/customer-guide/getting-help) > > Find the right contact and share the details needed to investigate. # Paying a Business Source: https://docs.payreque.st/customer-guide/payments Use a PayRequest payment page, invoice link or shop checkout, and know what to do if the result is unclear. ## Before you pay Open the link supplied by the business. It may use `payrequest.me`, a PayRequest shop address or the business's own domain. Check the business name, what the request is for, the **amount and currency**, and any tax or other amounts shown in the final total. For split or partial payments, you may see a progress display showing how many payment stages have been confirmed and how many remain. > [!NOTE] > > A normal payment collects money. A **security-deposit authorization** reserves an amount that the business can charge or release later. If the page describes an authorization hold, see the [security-deposit guide](/customer-guide/security-deposits). > > For partial payment links, each scheduled installment appears with its due amount and status. You will be prompted to pay the current due amount. ## Complete the payment **1. Review the request** Check the product, invoice or description. Some payment pages let you enter an amount; an invoice or fixed-price request may already set it. **2. Enter your details** Use the email address you want the business to associate with this purchase. Complete any details the checkout requests. **3. Choose an available payment method** The methods shown depend on the business, currency and payment type. You may be redirected to a payment provider, wallet or banking app for approval. **4. Return and check the result** Follow the return link after approval. Keep the confirmation or reference. Some methods need additional processing before the business receives a confirmed result. ## If the result is pending or unclear A bank approval screen, a pending card entry or a closed browser window is not enough to determine whether the business received a completed payment. 1. Open the original invoice, order or confirmation link to check its status. 2. Check the email address used at checkout, including its spam folder. Available confirmation emails depend on the payment flow and the business's configuration. 3. If the page says **pending** or **processing**, or your bank already shows an entry, ask the business to check the existing payment before trying again. If the page reports a clear failure, follow its instructions. If your bank shows a transaction despite that message, ask the business to verify it first. > [!WARNING] > > Do not make another payment just because a receipt has not arrived. Share the existing reference with the business so it can check the result. For a bank entry that does not match an invoice's status, follow [I paid, but my invoice is still open](/customer-guide/invoice-still-open). It covers bank transfers and **I have paid** confirmations as well as provider processing. ## Find your invoice, purchase or subscription Where the business offers a shop portal, sign in with the email address used for the purchase. **Invoices**, **Orders** and **My services** show the records available to your account. A payment-page account area has fewer features; use the invoice link if no invoice list is shown. See [Your customer account](/customer-guide/customer-account) for sign-in help. ## Refunds or an incorrect amount Contact the business that collected the payment. If **Request a refund** is available on a paid invoice, it submits a request for the business to review; it does not issue an immediate refund. For an unused card reservation, ask about **releasing the deposit** instead. A release and a refund are different actions. [Get help with a payment](/customer-guide/getting-help) # Security Deposits for Customers Source: https://docs.payreque.st/customer-guide/security-deposits Understand a pending card hold, check whether a deposit was released, and know who to contact if the bank still shows it. A security deposit is a temporary **reservation** on your card. It reduces the amount you can spend or your available credit while it is active. The business can release it or charge an amount under the terms you agreed to. A **£250 reservation** is different from a **£250 completed charge**. Your banking app may show both with similar wording. Stripe also notes that some bank interfaces do not clearly distinguish an authorization from a settled payment. See [Stripe's explanation](https://docs.stripe.com/payments/place-a-hold-on-a-payment-method#capture-the-funds). ## Authorize a deposit 1. Open the deposit link sent by the business. 2. Check the business, deposit amount, currency, booking reference and instructions. 3. Follow the authorization button and complete any card or bank verification. 4. Return to the deposit page and keep its link and any confirmation email. Opening a link alone does not reserve funds. If the page is still processing or the result is unclear, check the existing attempt with the business before authorizing again. > [!WARNING] > > Do not use another link, card or repeated authorization to resolve an uncertain result. Ask the business to verify whether a reservation already exists first. ## What the status means The wording may vary between deposit pages and payment providers. | Status | Meaning and next step | | - | - | | **Waiting / awaiting authorization** | No successful reservation has been confirmed on this request. If you already completed verification or see a bank entry, ask the business to check before trying again. | | **Processing** | The provider has not finished confirming the result. Wait or contact the business; do not start a second authorization. | | **Hold active / authorized / funds reserved** | Funds are reserved. The business must release them or charge an agreed amount before the authorization ends. | | **Captured / charged** | An amount has been collected from the deposit. Check the actual charged amount; it can be less than the original reservation. | | **Released** | The remaining reservation has been released at the provider. Your bank may still need time to update its display and available balance. | | **Expired** | Check whether this refers to an unused checkout attempt or an actual card hold. An expired checkout does not prove that no other reservation exists. Ask the business if your bank still shows one. | Use your **original deposit link** to check the request. Some links open a dedicated status page; others show status on the original authorization page. You do not need to find the deposit in a shop invoice list. ## If the business needs to renew the deposit For a new Stripe deposit, you may see **Allow renewal of this deposit on my saved card** before authorizing. This is optional. Checking it allows the business to save your card with Stripe and request replacement reservations for the **same amount and booking**, up to **30 days after the first authorization**. Leaving it unchecked still lets you authorize the original deposit. A renewal creates a new reservation; it does not charge your card. The original reservation keeps its existing deadline until Stripe confirms the replacement and cancellation of the previous reservation. Your bank may briefly display both. A renewal can be declined and does not guarantee another seven days. If your bank needs verification: 1. Follow the deposit confirmation link from the business or the renewal notice. 2. If shown, choose **Open secure bank confirmation** to continue to the secure PayRequest payment page. 3. Choose **Confirm deposit renewal** and complete your bank's verification. You do not need to enter your card again. 4. Check the confirmed status and deadline afterward. If it is unclear, contact the business before trying another card or link. Confirmation is available for up to 23 hours after the renewal request and only while enough time remains within the agreed limit. Without a successful confirmation, the original reservation is not extended. If the link no longer works, contact the business. To withdraw permission for future renewals, contact the business before the next request. Withdrawing permission does not itself refund a charge or release an already completed reservation. Existing deposits without prior permission cannot use this saved-card renewal feature. ## After the business releases the hold A release tells the payment provider to cancel the remaining reservation. The bank controls when the pending entry disappears and your available balance or credit updates. This may take several days; there is no single guaranteed timeframe for every bank or card. Because the money was reserved rather than collected, you may **not** see a separate incoming refund. The original pending entry may simply disappear or change status. For tracked deposits with your email address, PayRequest sends confirmations after a confirmed reservation, charge or release. Check your spam folder if one is missing. A missing email alone does not tell you whether funds are held: ask the business to verify the provider result. > [!TIP] > > If the business confirms release but your bank still shows the hold, ask for the release date and time and the payment reference. Your card issuer can use these details to investigate the pending entry. ## If part of the deposit is charged For the current Stripe deposit flow, the business makes one final full or partial capture. For example: | Original reservation | Amount charged | Remaining reservation released | | - | - | - | | £250 | £40 | £210 | The bank may take time to update the original pending amount. Releasing the unused part does **not** refund the £40 already charged. If you dispute a charge or want a refund, ask the business to review it separately. Other payment providers may handle partial capture differently. ## If you see two reservations A confirmed renewal can briefly show both the previous and replacement reservations. If the timing or amounts do not match what you agreed, ask the business to verify both references. Do not assume that two entries are normal bank processing, or that one must be a duplicate. Ask the business to check the exact authorizations and compare their amounts, currencies, dates, references and card last four digits. Share a cropped screenshot showing the relevant entries and whether each says **pending** or **completed**. Hide unrelated transactions, your balance and full card or account details. Never send your card security code or login verification codes. ## Who can release my deposit? The **business that requested the deposit** controls its release or charge. Use its contact details, reply to its deposit confirmation or open **Support** in its customer account area where available. If you cannot reach the business or a PayRequest page is not working, contact [support@payrequest.io](mailto:support@payrequest.io) with the business name, booking reference and a description. Support can help investigate the platform issue; a support message itself does not release funds or approve a refund. [What to include when asking for help](/customer-guide/getting-help) # Contact Persons and Portal Access Source: https://docs.payreque.st/customer-management/contact-persons Give additional contacts the right notifications and optional customer-portal access without creating duplicate customer accounts. Contact persons belong to an existing customer account. Use them for a bookkeeper, manager or operational colleague who needs selected emails, access to the customer portal, or both. **Email notifications and portal access are separate settings.** Adding a contact or selecting a descriptive job role does not by itself enable login. ## Add or update a contact Business users can open **Customers**, select the customer and find **Contact Persons**. In the shop portal, the primary customer or an enabled customer administrator can use **Contact Persons** where available. 1. Enter the person's name, email and optional phone. 2. Choose a descriptive role such as **General**, **Billing**, **Bookkeeping**, **Technical**, **Management** or **Support**. 3. Select **Billing emails** and/or **Account emails** according to the notifications they need. 4. If they also need login, enable **Portal access** and choose its separate permission role. 5. Save, then check the contact's enabled state and role in the list. There is a maximum of **10 contacts per customer**. A contact email must be unique within that customer and cannot be the primary customer's email. You do not need to create another customer record to give a colleague access. ## Notification preferences | Setting | Intended use | | - | - | | **Billing emails** | Applicable invoice, payment, reminder and mandate notifications. | | **Account emails** | Applicable subscription, order and account-related notifications. | Contacts receive copies of supported notifications according to these choices. Delivery still depends on the event, business configuration and email delivery result. Enabling portal access does not subscribe the contact to every notification. ## Choose a portal permission role These permissions apply only when **Portal access** is enabled. They are different from the descriptive **Billing**, **Technical** or other job labels above. | Portal role | Access scope | | - | - | | **Admin** | Customer account management and supported account actions, subject to the business's enabled features. | | **Billing** | Invoice and subscription viewing, billing information, and viewing/managing available payment methods. | | **Operations** | Orders, subscription viewing and support access. | | **Viewer** | Invoice, order and subscription viewing, plus support access. No account-management or payment-method-management scope. | Additional controls can restrict sensitive services. For example, active VPN credentials and configurations are available to the primary customer and authorized Admin/Operations contacts; Billing/Viewer contacts cannot access them. Only the primary customer or an enabled Admin contact can accept or decline a cancellation proposal. > [!NOTE] > > A contact's job label describes their role in the organization. The **portal permission role** determines access. Giving a contact the job label “Technical” does not automatically grant Operations permissions. ## How a contact signs in Give the contact the business's customer login page. They enter **their own enabled contact email address** and follow the emailed magic link. They do not need the primary customer's password or login link. They access the linked customer account with their assigned permissions. If a section or action is missing, check the enabled portal role and whether the business offers that feature. A contact cannot use this account to view a different business's customer data. If their email is also the primary email of another customer under the same business, login prioritizes the primary customer record. Ask the business or PayRequest Support to review the identity before creating another duplicate account. ## Change or remove access Edit the contact to change notification choices, enable/disable portal access or select a different portal role. Save and check the resulting settings. Removing a contact stops their future contact notifications and removes that contact's enabled login identity; existing emails are not recalled. Do not treat a disabled notification checkbox as disabled portal access: change the **Portal access** setting explicitly when a colleague no longer needs access. ## Common questions > [accordion] Can a contact receive invoices without being able to log in? > > Yes. Select the relevant billing notifications and leave portal access disabled. > [accordion] Can a contact log in without receiving every email? > > Yes. Enable portal access, choose the appropriate permission role and configure email preferences separately. > [accordion] Why does a contact see fewer actions than the primary customer? > > Their portal role may limit access. Product settings, service type and other feature requirements can also restrict actions. > [accordion] Do contacts count as separate customers? > > No. They remain contacts of the existing customer account. > [card] [Customer sign-in guide](/customer-guide/customer-account) > > Share instructions for signing in with the correct email. > [card] [Customer portal](/customer-management/customer-portal) > > See the account features your business can offer. # Email Health & Bounce Suppression Source: https://docs.payreque.st/customer-management/customer-health Monitor email deliverability per customer and automatically prevent sending to bounced or invalid addresses # Email Health & Bounce Suppression PayRequest automatically tracks email delivery issues — bounces, spam complaints, and failures — and suppresses future emails to problematic addresses. This protects your sender reputation and prevents wasted delivery attempts. > [!NOTE] > > Email health tracking works automatically via Resend webhooks. No setup is required beyond having your Resend integration connected. > [card] Automatic Suppression > > Emails to bounced or complained addresses are blocked until you clear the suppression > [card] Customer Visibility > > Bounce warnings appear on customer profiles with full issue history > [card] Delivery Confirmation > > Invoice reminders show delivery status when Resend confirms receipt > [card] Self-Healing > > Transient failures auto-resolve when a subsequent email delivers successfully *** ## How It Works **1. Email is sent** PayRequest sends an invoice reminder, order confirmation, or other customer email via Resend. **2. Resend reports back** Resend sends a webhook when the email bounces, gets a spam complaint, fails, or is successfully delivered. **3. PayRequest records the event** The bounce or complaint is recorded as an **email issue** linked to the customer's email address. Delivery confirmations update the reminder history. **4. Future emails are suppressed** Any attempt to send email to that address is blocked. The sender (command, UI, or MCP tool) is notified that the email was suppressed. **5. You review and clear** A red warning on the customer profile shows the bounce details. You can update the email address or clear the suppression to resume sending. *** ## Email Health Statuses Each customer has an email health status based on their unresolved email issues: | Status | Badge Color | Meaning | | - | - | - | | **Healthy** | Green | No active issues — emails deliver normally | | **Bounced** | Red | Email address rejected by the recipient server (e.g., address doesn't exist) | | **Complained** | Orange | Recipient marked your email as spam | | **Failed** | Yellow | Transient delivery failure (auto-resolves on next successful delivery) | *** ## Customer Profile: Bounce Warning When a customer has an active bounce or complaint, a prominent red callout appears at the top of their **Details** tab: * **Bounce type** — Permanent or Transient * **Date** — When the bounce occurred * **Reason** — The SMTP error message from the recipient's mail server * **Clear Suppression** button — Resolves all active issues and re-enables email delivery ### Email Issue History The **Logs** tab on the customer profile shows a chronological table of all email issues, including: * Date and time of each event * Issue type (Bounced, Complained, Failed) * Reason and SMTP message * Status — **Active** (red) or **Resolved** (green) *** ## Customer List: Email Issues Filter The customer list shows email delivery problems at a glance: * **Email Issues count** in the stats bar (only visible when issues exist) * **Email Issues filter** in the status dropdown to show only affected customers * **Red "Bounced" badge** on customer cards with active suppression *** ## What Gets Suppressed When an email is suppressed, every customer-facing email channel is blocked: | Email Type | Behavior When Suppressed | | - | - | | Invoice reminders (automatic) | Skipped with "suppressed" status in command output | | Invoice reminders (manual/bulk) | Toast warning in the dashboard | | Invoice paid confirmations | Silently skipped with log entry | | Smart link emails | Smart link still created, email skipped | | Debt collection notices | Email skipped, escalation continues normally | | Checkout recovery emails | Silently skipped | | Deposit authorized emails | Silently skipped | | MCP send-invoice-reminder | Returns error message explaining the suppression | > [!TIP] > > Business owner emails (like daily summaries) are **never** suppressed — only customer-facing emails are affected. *** ## Clearing Suppression There are two ways to clear a suppression and resume email delivery: ### Manual Clear Click the **Clear Suppression** button on the customer profile's bounce warning callout. This resolves all active email issues for that customer. ### Automatic Clear on Email Change When you edit a customer and change their email address to a different one, PayRequest automatically: 1. Resolves all active email issues on the old address 2. Removes any tags that were added by email bounce automations (e.g., the "Invalid Email" tag) > [!WARNING] > > Only clear a suppression if you're confident the email address is now valid — for example, after the customer confirms a typo fix. Clearing suppression for a permanently invalid address will just result in another bounce. *** ## Delivery Confirmation When Resend confirms that an invoice reminder was delivered, PayRequest records a `delivered_at` timestamp on the reminder history. This appears as a green **Email Delivered** event in the invoice timeline, giving you confirmation that the customer received the reminder. Delivery confirmations also automatically resolve any previous transient **Failed** issues for that email address. *** ## FAQ > [accordion] What's the difference between Bounced and Failed? > > **Bounced** means the recipient server permanently rejected the email (e.g., the address doesn't exist). This creates a suppression that blocks future emails. **Failed** is a transient issue (e.g., temporary server problem) that auto-resolves when a later email delivers successfully. > [accordion] Will clearing suppression cause another bounce? > > If the underlying problem hasn't been fixed (e.g., the email address is still invalid), yes — the next email will bounce and the suppression will be re-applied. Only clear suppression when you're confident the issue is resolved. > [accordion] Does suppression affect emails to contact persons (CC)? > > No. Suppression only checks the primary recipient (the customer's email). CC recipients on contact persons are not checked against the suppression list. > [accordion] Can I see which emails were blocked? > > Every suppressed email attempt is logged in the application log with the email address, context (which job or command tried to send), and the reason for suppression. *** ## Next Steps > [card] [Payment Reminders](/invoices/payment-reminders) > > Configure automatic invoice reminder schedules > [card] [Email Automations](/organization-and-automation/email-automations) > > Set up automatic tagging for bounced emails > [card] [Contact Persons](/customer-management/contact-persons) > > Add CC recipients who receive email copies > [card] [Email Delivery Troubleshooting](/troubleshooting/email-delivery-issues) > > Diagnose and fix common email delivery problems # Customer Portal Source: https://docs.payreque.st/customer-management/customer-portal Give your customers a self-service portal to manage subscriptions, view invoices, pay bills, and update their preferences # Customer Portal The PayRequest Customer Portal is a full self-service experience for your customers. When customers log into your shop, they get a personal dashboard with everything they need: subscriptions, invoices, orders, payment methods, support tickets, and account settings. > [!NOTE] > > The Customer Portal is automatically available for every shop. Customers register or log in via your shop URL (or custom domain) and get immediate access to their personal dashboard. > [!NOTE] > > There's also a lighter-weight account area built directly into your **payment page** (magic-link login, settings/contacts/payment methods/subscriptions/support tabs) that doesn't require a full shop. See [Customer Login & Account Area](/payment-processing/payment-forms#customer-login-account-area) for that flow. ## Share the customer guide Send customers [Your customer account](/customer-guide/customer-account) for sign-in and self-service instructions. It explains the difference between the shop portal and the lighter payment-page account area. For a reservation, also share [Security deposits for customers](/customer-guide/security-deposits); a deposit may use its own status link rather than appearing as a portal invoice or order. ## Portal Navigation When logged in, customers see a persistent sidebar with quick access to all portal sections: | Section | Description | | - | - | | **Shop** | Return to the shop homepage / product catalog | | **Payment Methods** | Manage SEPA mandates and saved payment methods | | **Edit Details** | Update name, email, address, and company information | | **Invoices** | View all invoices, pay outstanding ones, download PDFs | | **Orders** | Browse order history with details | | **My services** | View services, domain management and linked subscriptions; available actions depend on the service and merchant settings | | **Support** | Create and track support tickets | | **Contact Persons** | Add people from the organization to receive email notifications | | **Notifications** | View announcements, alerts, and updates from the business | | **Settings** | Appearance, language, and notification preferences | The sidebar also shows **open invoices** with amounts and **open support tickets** with status badges, giving customers a quick overview of items that need attention. ## My services **My services** brings the existing subscription overview and supported service management together. Customers can see status, renewal or next-payment dates and linked billing. Opening a domain uses the existing domain-management page; supported actions depend on the provider configuration and customer permissions. For businesses, **Services & integrations** in the dashboard explains how the provider, automatic delivery and customer portal connect. Openprovider supports the existing domain flow. DirectAdmin, Enhance and VirtFusion are labelled **Planned** and cannot be connected yet; no release date has been announced. The existing subscription URLs and billing rules remain in place. The payment-page account area's subscription tab is separate from the shop portal described here. ## Customer Homepage The homepage is the customer's personal dashboard. It shows at-a-glance statistics and recent activity. ### Statistics Cards Three clickable stat cards at the top show: * **Orders** — Total order count, links to order history * **Invoices** — Total invoice count, links to invoice list * **Subscriptions** — Active subscription count, links to subscription management ### Active Subscriptions A prominent section showing all active subscriptions with: * Product name and status badge (Active, Paused, Trial) * Billing interval and amount (e.g., "monthly" at "15.00/month") * Next billing date * Trial end date (if on trial, with countdown) * Direct link to subscription details ### Recent Orders The most recent orders displayed with: * Order number and date * Total amount * Link to order details ### Open Invoices & Tickets (Mobile) On mobile devices, open invoices and support tickets are displayed as alert cards. On desktop, these appear in the sidebar instead. ## Portal Pages ### Invoices Customers can browse all their invoices with status indicators: * **Pay outstanding invoices** directly via iDEAL, credit card, or saved payment methods * **Download PDF** invoices for their records * **Request a refund** for paid invoices — submits a support ticket linked to the invoice (see [Refund Requests](/invoices/refund-requests)) * View payment history and transaction details per invoice * Filter by status (paid, unpaid, pending) ### Subscriptions Full subscription self-management: * View subscription details (product, amount, interval, next billing) * **Pause** a subscription temporarily * **Resume** a paused subscription * **Cancel** a subscription * View custom fields associated with the subscription * See trial status and end dates > [!NOTE] > > Subscription self-management can be enabled or disabled per product via the **Allow Self-Management** toggle in product settings. ### VPN services For [VPNresellers subscriptions](/integrations/vpnresellers), customers open **My services**, select their subscription and use the **VPN** tab. It shows delivery status, the VPN username and **Access paid until**. While access is active, the primary customer and contacts with **Admin** or **Operations** access can reveal or change the VPN password and download WireGuard, OpenVPN or VLESS configurations. **Billing** and **Viewer** contacts cannot access credentials. Configuration files contain private access keys and should be kept private. VPN subscriptions do not support customer pausing or free trials. Cancellation retains access until the end of the paid period; an unpaid renewal does not extend access. If delivery is delayed, customers can check again shortly or contact the business through the portal. ### Orders Complete order history with: * Order number, date, and status * Line items with quantities and amounts * Order total with tax breakdown * **Digital downloads** — For orders containing digital products, customers see download buttons with remaining download count and expiry date (see [Digital Products](/products-and-pricing/digital-products)) * **AI Prompts** — For orders containing an AI Prompt, customers see the full prompt text with a **Copy Prompt** button, so they can re-copy it any time without digging through email (see [AI Prompts](/products-and-pricing/ai-prompts)) Customers who log in from a PayRequest Page can also open **My downloads**. PayRequest uses their customer email to show eligible digital purchases across creators in one download library. Buying a digital product does not by itself grant access to a creator's private Community; that requires an active membership for the connected membership product. ### Payment Methods (Mandates) Customers can manage their saved payment methods: * View active SEPA Direct Debit mandates * See mandate status (valid, pending, invalid) * Add new payment methods * Use saved methods to pay invoices ### Profile Customers can update their personal and business details: * Name, email, phone number * Address (street, city, postal code, country) * Company details (for business customers) ### Debt Collection Cases When a business opens a collection case for an overdue invoice, the customer sees it in their portal: * View case details (case number, linked invoice, days overdue) * See amount breakdown (original amount + any collection fees) * Visual progress indicator showing the current collection stage * **Pay Now** button to settle the full amount immediately * **Request a payment plan** to pay in monthly installments (when enabled by the business) > [!NOTE] > > Customers can only see collection cases linked to their own invoices. The portal shows clear, professional communication without unnecessary legal jargon. ### Support Integrated support ticket system: * Create new support tickets * Track ticket status (Open, In Review, Resolved) * Add replies to existing tickets * View ticket history * Receive email notifications when the business replies See [Support Requests](/customer-management/support-requests) for full documentation on managing support tickets from the admin side. ### Contact Persons Customers can add additional people from their organization to receive email notifications: * Add up to 10 contact persons with name, email, phone, and role * Choose notification preferences per contact: **Billing emails** (invoices, payments) or **Account emails** (subscriptions, orders) * Edit or remove contact persons at any time See [Contact Persons](/customer-management/contact-persons) for full documentation. ### Settings A dedicated settings page where customers control their portal experience. See [Customer Portal Settings](/customer-management/customer-portal-settings) for full details. * **Appearance** — Choose between System, Light, or Dark mode * **Language** — Select Auto (browser default), English, or Dutch * **Notifications** — Toggle email notifications per category ## Custom Domain Support The Customer Portal works seamlessly on custom domains. If you've configured a custom domain for your shop (e.g., `shop.yourbusiness.com`), the entire portal including all customer pages, settings, and payment flows operates under your domain. Everything works automatically under your domain — a fully white-label experience for your customers. ## Customer Authentication Customers create an account on your shop and log in with their email and password. They stay logged in during their session and can log out from the portal header. > [!WARNING] > > Customer login is completely separate from your PayRequest dashboard. Customers cannot access your business dashboard. ## Mobile Experience The portal is fully responsive: * **Desktop** — Sidebar navigation with all sections visible * **Mobile** — Optimized layout with collapsible sections, open invoices and tickets shown inline instead of sidebar ## Next Steps > [card] [Portal Settings](/customer-management/customer-portal-settings) > > Learn about appearance, language, and notification preferences > [card] [Customer Profiles](/customer-management/customer-profiles) > > Managing customer profiles and data > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > Set up a custom domain for your shop and portal > [card] [Subscription Self-Service](/subscriptions/customer-self-service) > > Configure what customers can manage themselves > [card] [Debt Collection](/debt-collection/overview) > > How collection cases appear in the customer portal > [card] [Refund Requests](/invoices/refund-requests) > > How customers can request refunds for paid invoices > [card] [Portal Notifications](/customer-management/portal-notifications) > > Send announcements and alerts to customers in the portal ## Hetzner server access Customers open **My services**, select their subscription and choose **Server** to see linked Hetzner server details. The available controls depend on the service and permissions enabled by the business. **Refresh server details**, **Restart** and **Open console** appear together when available. The console opens in a full-screen window on the same page. Select **Connect**, then sign in with your own Linux username and server password. Closing the window disconnects the browser; log out of Linux first. Primary customers and enabled admin/operations contacts can use permitted server actions. Billing/viewer contacts cannot operate the server or connect to its console. See [Hetzner Cloud](/integrations/hetzner-cloud#open-a-server-console) for access requirements and troubleshooting. # Customer Portal Settings Source: https://docs.payreque.st/customer-management/customer-portal-settings Customers can personalize their portal experience with appearance, language, and notification preferences # Customer Portal Settings The Settings page gives your customers control over their portal experience. Customers can choose their preferred theme, language, and which email notifications they receive. All changes are saved automatically. > [!NOTE] > > The Settings page is available at `/customer/settings` on your shop (or custom domain). It's accessible from the sidebar navigation in the customer portal. ## Appearance Customers can choose how the portal looks with three theme options: | Option | Behavior | | - | - | | **System** (default) | Follows the customer's browser/OS dark mode preference | | **Light** | Always uses light mode | | **Dark** | Always uses dark mode | The theme applies instantly when selected — no page reload needed. The preference is saved to the customer's account and persists across sessions and devices. > [!TIP] > > **Default behavior**: When no preference is set, the portal follows the customer's system preference. This means customers who have dark mode enabled in their OS will automatically see the portal in dark mode. ## Language Customers can choose their preferred language for the portal: | Option | Behavior | | - | - | | **Auto** (default) | Uses the browser's language setting | | **English** | Portal displays in English | | **Nederlands** | Portal displays in Dutch | When a language is selected, the page refreshes to apply the new language immediately. The preference is stored in the customer's account. ## Notification Preferences Customers can toggle individual email notification categories on or off. This gives them control over which emails they receive from your business. ### Invoice Notifications | Notification | Description | Default | | - | - | - | | **New invoice** | When a new invoice is created for the customer | On | | **Payment confirmation** | When a payment has been received | On | | **Payment reminders** | Reminders for unpaid invoices | On | ### Subscription Notifications | Notification | Description | Default | | - | - | - | | **Renewal notices** | Before a subscription renews | On | | **Status changes** | When a subscription is paused, resumed, or canceled | On | ### Order Notifications | Notification | Description | Default | | - | - | - | | **Order confirmation** | When an order has been placed successfully | On | All notification toggles are saved automatically when changed. A note at the bottom of the section confirms: "Changes are saved automatically." > [!NOTE] > > **Good to know**: When your customer opts out of a notification category (e.g. payment reminders), PayRequest automatically respects that preference when sending emails. You don't need to configure anything extra. ## Next Steps > [card] [Customer Portal](/customer-management/customer-portal) > > Overview of all customer portal features > [card] [Email Configuration](/business-settings/email-configuration) > > Configure your email templates and delivery settings # Customer Profile Source: https://docs.payreque.st/customer-management/customer-profiles Complete guide to viewing and managing individual customer profiles in PayRequest # Customer Profile The customer profile page provides a comprehensive view of all information and activity related to a single customer. Access it by clicking on any customer from your customer list. ## Page Layout The customer profile is divided into two main sections: * **Left Sidebar**: Quick overview, actions, and contact information * **Main Content Area**: Tabbed interface with detailed information *** ## Header Section At the top of the page, you'll see: * **Customer Avatar**: Displays the company logo (for business customers with a website) or generated initials * **Customer Name**: Company name for business customers, full name for individuals * **Status Badge**: Shows Active, Archived, or Suspended status * **Email Address**: Primary contact email * **Tags**: Up to 3 tags displayed with a "+X more" indicator if there are additional tags * **Archive Information**: If archived, shows the reason and date *** ## Left Sidebar ### Customer Overview Card The top card displays: * **Avatar & Name**: Large avatar with customer name and email * **Tags Section**: All assigned tags with quick add (+) button * Hover over a tag to reveal the remove (×) button * **Quick Stats**: Three-column grid showing: * Total Invoices count * Total Orders count * Total Subscriptions count ### Customer Details Accordion Expandable section showing: | Field | Description | | - | - | | Member Since | Month and year the customer was created | | Customer Type | VIP (>€1000 revenue), Regular (≥3 orders), or New | | Unpaid Invoices | Count of outstanding invoices (if any) | | Total Revenue | Lifetime revenue from paid invoices | | Last Login | Date, time, and location of last portal login | ### Quick Actions Card Action buttons for common tasks: > [accordion] Primary Actions > > * **Request payment again**: Opens an editable payment request using the customer's most recent paid transaction > * **View unpaid payment requests**: Opens the Payment Links overview filtered to this customer and links without a recorded linked payment > * **Create Invoice**: Opens invoice creation with customer pre-selected > * **Create Subscription**: Opens subscription creation modal > * **Create Order**: Opens order creation with customer pre-selected > * **Add Note**: Opens the note creation modal > * **Manage Tags**: Opens tag management modal > [accordion] Communication Actions > > * **Create Support Ticket**: Initiates a support conversation > [accordion] Management Actions > > * **Login as Customer**: Access the customer portal as this customer > * **Archive Customer**: Move to archived status (for active customers) > * **Reactivate Customer**: Restore from archived status ### Request Payment Again Use this action when an existing customer needs to pay for another service, a new billing period, or a similar purchase. You do not need to create a product first. **1. Choose a previous payment** Open the customer profile and select **Request payment again** in **Quick Actions** to use the most recent payment. To choose a different payment, use **Request again** on one of the five entries under **Request a previous payment again**. These entries show the description, amount, currency, and payment date. Only positive paid transactions are offered; security deposit transactions are excluded. If the customer has no eligible previous payment, the action opens a new Amount Link with the customer selected and the amount left empty. **2. Review the new request** The form has the customer selected and copies the previous payment's amount, currency, and description. For example, a previous £65 GBP payment opens a new £65 GBP request. Edit these details for the new service or period. The new request is an **Amount Link** with a **One-Time Payment** limit. It does not carry over access settings, reminders, or delivery choices from an earlier link. **3. Create and share** Click **Create Payment Link** after reviewing the draft. Leave delivery methods unselected to create a link you can copy and share yourself, or choose email or SMS before saving to send it through the selected method. SMS requires available credits. > [!NOTE] > > Opening or reviewing the draft does not create a payment link or send a message. The previous payment remains unchanged. This action requests a new payment; it does not automatically charge the customer or renew their service access. See [Managing payment requests](/payment-processing/smart-links#payment-links-overview) for status filters, copying links, and reminder settings. ### Contact Info Card with Map When a country is set, displays: * **Interactive Map**: Mapbox map centered on the customer's country with flag overlay * **Phone Number**: Clickable to initiate a call * **Full Address**: Street, postal code, city, and country * **Website**: Clickable link to company website (if set) > [!NOTE] > > The map shows the country location. For privacy reasons, it does not pinpoint the exact address. ### SEPA Mandate Card If the customer has an active SEPA Direct Debit mandate via Mollie, a credit card-style display shows: * Payment method type (SEPA Direct Debit) * Mandate status (Valid/Invalid) * Account holder name * IBAN (formatted with spaces) * BIC code * Signature date * Mandate reference ID *** ## Main Content Tabs ### Customer/Business Tab For **Individual Customers**, shows the "Klant" (Customer) tab with: > [card] Personal Information > > * Full name > * Email address with [health status badge](/customer-management/customer-health) (Healthy/Bounced/Complained/Failed) > * Phone number > [card] Address > > * Street address > * City and postal code > * Country > [card] Preferences > > * Preferred language (EN/NL/ES) > * Default payment method > [card] Customer Notes > > * Private notes visible only to your team > * Add, edit, and delete notes > * Shows author and timestamps For **Business Customers**, shows the "Business" tab with additional fields: > [card] KVK Sync > > For Dutch businesses with a KVK number: > > * KVK registration number > * Last sync timestamp > * Re-sync button to update from KVK.nl > [card] Business Information > > * Company name > * VAT number > * Legal form (B.V., N.V., etc.) > * Industry code and description > * Established date > * Trade names > [card] Tax & Location Settings > > * Country with flag > * VAT number with validation status > * Validate VAT button (checks via VIES) > * Tax exempt status ### Orders Tab View and filter all orders placed by this customer: **Status Filters** (pill tabs): * All, Pending, Processing, Completed, Cancelled, Refunded, Failed **Order Table Columns**: | Column | Description | | - | - | | Order # | Order number or ID | | Date | Creation date | | Status | Order status with colored badge | | Payment | Payment status (Paid/Pending/Failed/Refunded) | | Total | Order total amount | | Actions | View button to open order details | All columns are sortable by clicking the header. ### Invoices Tab Complete invoice management for the customer: **Invoice Summary Callout**: * Total invoice count with paid/unpaid breakdown * Total amount and unpaid amount * Send Payment Reminder button (when unpaid invoices exist) **Status Filters** (pill tabs): * All, Draft, Concept, Open, Pending, Unpaid, Paid, Cancelled, Chargeback **Invoice Table Columns**: | Column | Description | | - | - | | Invoice # | Invoice number | | Date | Creation date | | Due Date | Payment due date | | Amount | Invoice amount | | Status | Status with colored badge | | Actions | View and Edit buttons | **Quick Actions**: * Create Invoice button in the header * Create First Invoice prompt for new customers ### Subscriptions Tab Manage recurring billing for the customer: **Subscription Summary Callout**: * Total subscription count with active/paused/canceled breakdown * Monthly Recurring Revenue (MRR) from active subscriptions **Status Filters** (pill tabs): * All, Active, Paused, Pending, Canceled, Failed, Completed **Subscription Table Columns**: | Column | Description | | - | - | | Product | Product name with subscription name | | Status | Status with colored badge | | Amount | Recurring amount and interval | | Next Billing | Next billing date | | Actions | View button | **Quick Actions**: * Create Subscription button in the header ### Smart Links Tab View all Smart Links created for this customer: * Link name and type (Product/Amount) * Status (Active/Inactive) * Views and payments statistics * Revenue generated * Quick actions to view/edit ### Transactions Tab Complete payment history: * All transactions related to invoices, orders, and subscriptions * Mollie payment IDs and status * Amount and currency * Payment method used * Created timestamp ### Activity Log Tab Chronological activity feed showing: * Invoice creation, sending, and payment events * Order placements and status changes * Subscription lifecycle events (created, paused, resumed, canceled) * Customer data changes * Note additions Each entry shows: * Activity type and description * Timestamp (relative, e.g., "2 hours ago") * User who performed the action (when applicable) *** ## Editing Customer Information Click the **Edit Customer** button (pencil icon) to open the edit modal. ### Individual Customer Fields * Customer type (Individual/Business) * Full name * Email address * Phone number * Street address (with Google Maps autocomplete) * City * Postal code * Language preference (English, Dutch, Spanish) * Payment method preference * Country * Tax exempt toggle ### Business Customer Fields All individual fields plus: * Company name * VAT number * Company registration number (with country selector) * Legal form * Industry code * Industry description * Established date * Website URL ### Avatar Selection (Business Customers) When a website URL is entered for a business customer: 1. An "Customer Avatar" section appears 2. Shows a preview of the company logo from the website 3. Click to select the logo as the customer avatar 4. The avatar appears on the customer profile page 5. Click "Remove" to clear the avatar > [!TIP] > > The avatar uses unavatar.io to fetch the website's favicon/logo automatically. No manual upload required! *** ## Tag Management ### Adding Tags 1. Click the **+** button next to "Tags" or the **Manage Tags** quick action 2. Search existing tags or create new ones 3. Select multiple tags to assign 4. Click Save to apply ### Removing Tags * Hover over any tag to reveal the **×** button * Click to instantly remove the tag * Or use the Manage Tags modal to remove multiple at once ### Creating New Tags 1. In the tag management modal, type a new tag name 2. If no match is found, click "Create new tag" 3. Choose a color for the tag 4. The tag is created and automatically assigned *** ## Customer Notes Private notes visible only to your team members. ### Adding a Note 1. Click **Add Note** from Quick Actions or the Notes section 2. Enter a title (required) 3. Enter the note content (supports multi-line text) 4. Click Save ### Editing a Note 1. Click the pencil icon on any note 2. Modify the title or content 3. Click Save ### Deleting a Note 1. Click the trash icon on any note 2. Confirm deletion in the modal Notes display: * Title and content * Creation timestamp ("2 days ago") * Update timestamp (if edited) * Author name *** ## KVK Integration (Dutch Businesses) For customers with a Dutch company (country = NL) and KVK number: ### Automatic Data Sync When a KVK number is entered: * Company name, address, and details are fetched from KVK.nl * Legal form, industry information, and trade names are populated ### Manual Re-sync 1. Navigate to the Business tab 2. Check the "Last Synced" timestamp 3. If outdated (>1 year), click **Re-sync with KVK** 4. Customer data is updated from the KVK registry > [!WARNING] > > KVK sync is only available for Netherlands-based businesses with valid KVK numbers. *** ## VAT Validation Validate European VAT numbers via the VIES system: 1. Ensure the customer has a VAT number entered 2. Click **Validate VAT** button 3. Results show: * Valid/Invalid status badge * Company name from VIES * Registered address from VIES * Validation timestamp > [!NOTE] > > If the VAT number is valid, the customer is automatically marked as tax exempt. *** ## Archiving Customers ### Archive a Customer 1. Click **Archive Customer** from Quick Actions 2. Select an archive reason: * No longer needed * Duplicate entry * Customer request * Payment issues * Other 3. Add an optional note 4. Confirm archival ### Effects of Archiving * Customer is hidden from default customer list * Status badge shows "Archived" * Archive reason and date displayed in header * Existing invoices, orders, and subscriptions remain accessible * Customer cannot log into the portal ### Reactivate a Customer 1. Navigate to the archived customer's profile 2. Click **Reactivate Customer** 3. Confirm reactivation 4. Customer returns to Active status *** ## Login as Customer Test the customer portal experience: 1. Click **Login as Customer** from Quick Actions 2. A new tab opens with the customer portal 3. You're logged in as the customer 4. View their invoices, subscriptions, and orders 5. Test payment flows and portal features > [!WARNING] > > This creates an actual session as the customer. Be careful not to modify their data unintentionally. *** ## Related Documentation > [card] [Private Notes](/customer-management/private-notes) > > Learn more about customer notes and best practices > [card] [Tax Exemptions](/customer-management/tax-exemptions) > > Managing tax-exempt customers > [card] [Customer Portal](/customer-management/customer-portal) > > What your customers see in their portal > [card] [Tags System](/organization-and-automation/tags-system) > > Organizing customers with tags # Customer Sync Source: https://docs.payreque.st/customer-management/customer-sync Pull your existing Mollie customers into PayRequest automatically, matched and merged by email. # Customer Sync If you've been using Mollie before connecting it to PayRequest, Customer Sync pulls your existing Mollie customer records into PayRequest and links them to your PayRequest customers — matched by email address. > [!NOTE] > > Customer Sync lives on the **Mollie Customers** page in your dashboard, and requires a connected Mollie account. ## How Matching Works **1. Mollie customers are fetched** PayRequest pulls your Mollie customer list in pages of 50, storing each one (name, email, locale, metadata) as a Mollie Customer record. **2. PayRequest checks for an existing match** For each Mollie customer with an email address, PayRequest looks for a PayRequest customer with the same email under your account. **3. No match: a new PayRequest customer is created** A new customer is created using the Mollie customer's name, email, and locale. Its internal notes field is set to record the Mollie customer ID it was synced from, for traceability. **4. Match found: missing fields are filled in** If a PayRequest customer with that email already exists, Customer Sync only fills in fields that are currently empty (name, language) — it never overwrites data you've already entered. > [!WARNING] > > Sync is one-way: Mollie → PayRequest. Changes you make to a customer in PayRequest are not pushed back to Mollie. ## Running a Sync * **First visit**: if you land on the Mollie Customers page with zero customers and Mollie already connected, a sync starts automatically. * **Manual sync**: click **Sync** on the Mollie Customers page at any time to pull the latest data. This also enables ongoing sync on your Mollie connection if it wasn't already on. * Sync runs as a background job — the page shows a toast confirming it started, and the last sync time is displayed once it completes. > [!NOTE] > > Syncing large customer lists is paginated automatically — if there are more pages of customers, PayRequest queues the next page a couple of seconds later to avoid hitting Mollie's rate limits. ## Fixing Mismatched Customers If Mollie customer records end up with no owner or the wrong owner (for example after reconnecting Mollie under a different account), the Mollie Customers page detects this and shows a fix option to correct the ownership. ## Exporting Synced Customers The Mollie Customers page has its own **CSV export** of the customers Mollie has returned (name, email, metadata) — separate from the account-wide export covered in [Data Import & Export](/business-settings/data-import-export). ## FAQ > [accordion] Does Customer Sync overwrite my existing customer data? > > No. If a PayRequest customer already exists with a matching email, sync only fills in blank fields (name, language) — it never overwrites data that's already there. > [accordion] Does this sync customers created in PayRequest back to Mollie? > > No, sync is one-directional: from Mollie into PayRequest. > [accordion] How do I know a customer was created by sync? > > Synced customers have their internal notes field populated with the source Mollie customer ID, stored on the record for traceability. > [accordion] Does sync run automatically on a schedule? > > No — it runs once automatically the first time you visit the Mollie Customers page with no customers yet, and otherwise only when you click Sync manually. ## Next Steps > [card] [Data Import & Export](/business-settings/data-import-export) > > Export your customer data to CSV > [card] [Private Notes](/customer-management/private-notes) > > Keep your own staff-only notes on any customer > [card] [Customer Health](/customer-management/customer-health) > > Understand customer activity after they're synced # Last Login Tracking Source: https://docs.payreque.st/customer-management/last-login-tracking Monitor customer activity with automatic last login tracking including location data ## Overview PayRequest automatically tracks when customers log into your shop, recording the date, time, and geographic location based on their IP address. This information helps you understand customer engagement and identify active users. ## How It Works ### Automatic Tracking When customers log in to your shop using the magic link system, PayRequest automatically: * Records the exact login timestamp * Captures the customer's IP address * Determines their geographic location (country and city) * Updates their customer profile with this information ### Location Detection The system uses IP geolocation services to determine: * **Country**: The customer's country (e.g., "The Netherlands", "Germany") * **City**: The customer's city when available (e.g., "Amsterdam", "Berlin") * **Fallback Handling**: Shows "Local Network" for private/local IP addresses ## Viewing Last Login Information ### Customer Detail Page In your dashboard, navigate to any customer's profile to see their last login information: 1. Go to **Customers** in your dashboard 2. Click on any customer to view their profile 3. In the sidebar, look for the **Customer Details** section 4. The last login appears as: `"27 Sep 2025, 11:29 (Amsterdam, The Netherlands)"` ### Information Display Format The last login information shows: * **Date and Time**: In a readable format (27 Sep 2025, 11:29) * **Location**: City and country when available * **Only When Available**: Only displays if the customer has logged in at least once ## Privacy and Security ### Data Handling * **IP Addresses**: Stored for location detection purposes * **No Personal Data**: Only geographic location is derived and stored * **GDPR Compliant**: Data handling follows privacy regulations * **Automatic Cleanup**: Old login data can be managed according to your data retention policies ### Location Accuracy * **Country Level**: Usually very accurate (99%+ correct) * **City Level**: Generally accurate but may vary by provider * **ISP Dependent**: Location depends on the customer's internet service provider * **VPN Consideration**: May show VPN server location if customer uses VPN ## Use Cases ### Customer Support When customers contact support: * Verify recent account activity * Confirm login attempts * Identify account access patterns ### Business Intelligence Track customer engagement: * Monitor active vs. inactive customers * Understand geographic customer distribution * Identify login patterns and trends ### Security Monitoring Basic security insights: * Unusual login locations * Recent account activity * Customer engagement levels ## Technical Details ### Automatic Implementation Last login tracking is automatically enabled for all shops and requires no setup. The system: * Tracks all magic link logins * Updates customer records in real-time * Handles failures gracefully (login won't fail if tracking fails) * Provides fallback for local/development environments ### Data Storage * **Database Field**: `last_login_at`, `last_login_ip`, `last_login_country`, `last_login_city` * **Privacy Focused**: Only stores necessary location data * **Efficient Queries**: Optimized for fast customer profile loading ## Frequently Asked Questions ### Will this slow down customer logins? No, the location detection happens asynchronously and won't impact login speed. If the location service fails, the login still completes successfully. ### How accurate is the location data? Country-level data is typically 99%+ accurate. City-level data is generally accurate but can vary depending on the customer's ISP and network configuration. ### Can customers opt out of tracking? This is basic login tracking for business purposes. The data helps you provide better customer service and is handled according to standard privacy practices. ### What about customers using VPNs? If customers use VPN services, the location will show the VPN server's location rather than their actual location. ### Is this GDPR compliant? Yes, this tracking is for legitimate business purposes (customer service and account security) and follows GDPR guidelines for data minimization and purpose limitation. *** *Last updated: September 2025* # Portal Notifications Source: https://docs.payreque.st/customer-management/portal-notifications Send announcements, alerts, and updates directly to your customers through the Customer Portal ## Overview Portal Notifications let you communicate directly with your customers through the Customer Portal. Whether you're announcing a price change, going on vacation, or flagging a service issue, notifications appear as prominent banners and in a notification bell — so your customers never miss important updates. > [!TIP] > > Think of Portal Notifications as your private communication channel with customers. Unlike emails that can end up in spam, portal notifications are always visible the moment a customer logs in. ## Key Features * **Four notification types**: Announcements, Price Changes, Vacation notices, and Problem alerts * **Targeted delivery**: Send to all customers, specific customers, or customers with certain tags * **Two display locations**: Callout banners at the top of the portal and a notification bell in the header * **Optional email delivery**: Also send the notification via email when you create it * **Scheduling**: Set a start date for future notifications * **Expiry dates**: Automatically hide notifications after a certain date * **Permanent or dismissible**: Choose whether customers can dismiss the notification or not * **Active/inactive toggle**: Quickly enable or disable notifications without deleting them ## How Customers See Notifications ### Callout Banners When a customer logs into the portal, active notifications appear as colored banners at the top of every page. Each notification type has its own color and icon: | Type | Color | Icon | Best For | | - | - | - | - | | **Announcement** | Blue | Megaphone | General updates, new features, company news | | **Price Change** | Yellow | Currency symbol | Upcoming price adjustments, plan changes | | **Vacation** | Yellow | Calendar | Holiday closures, reduced availability | | **Problem** | Red | Warning triangle | Service issues, outages, known bugs | Customers can dismiss banners (unless you've marked them as permanent), and dismissed notifications won't reappear. ### Notification Bell A bell icon appears in the portal header with a badge showing the number of unread notifications. Clicking the bell opens a panel listing all active notifications with: * Notification title and message * Color-coded icon matching the notification type * How long ago the notification was posted * A dismiss button (for non-permanent notifications) > [!NOTE] > > The notification count on the bell icon updates automatically. When a customer dismisses a notification, it disappears from both the banner area and the bell panel. ## Creating a Notification ### Step 1: Open the Notification Manager Navigate to **Portal Notifications** in your dashboard sidebar (under Portal & Products). Click the **Create Notification** button. ### Step 2: Write Your Message * **Title**: A short, clear heading (e.g., "Holiday Closure December 24-31") * **Message**: The full notification text. Keep it concise — customers see the first few lines in the bell panel. ### Step 3: Choose Notification Type Select the type that best matches your message: * **Announcement** — General updates and news (blue banner) * **Price Change** — Pricing-related notices (yellow banner) * **Vacation** — Availability or closure notices (yellow banner) * **Problem** — Issues or alerts that need attention (red banner) > [!TIP] > > The notification type automatically sets the banner color and icon. You can also choose a custom color variant (Info, Success, Warning, Danger) if you want a different look. ### Step 4: Select Your Audience Choose who should see this notification: **All Customers** * Every customer who logs into your portal will see the notification. * Best for: General announcements, holiday closures, system updates. **Specific Customers** * Pick individual customers from a searchable list. * Best for: Targeted price change notices, account-specific updates. **Customers with Tags** * Select one or more tags. Any customer with at least one of the selected tags will see the notification. * Best for: Segment-based communication (e.g., all "Enterprise" customers, all "Trial" customers). > [!NOTE] > > Tags are a powerful way to organize your customers into groups. If you haven't set up tags yet, check out the [Tags System](/organization-and-automation/tags-system) documentation. ### Step 5: Configure Options **Permanent notification** Turn this on if the notification should always stay visible. Customers won't be able to dismiss it. Use this sparingly — only for critical, ongoing information. **Send email notification** Turn this on to also send the notification content via email to the targeted customers. The email includes your business name and the notification message. Emails are sent immediately when you create the notification. > [!WARNING] > > Emails are only sent when creating a new notification — not when editing an existing one. Make sure your message is ready before enabling this option. ### Step 6: Set Timing (Optional) **Start date** Leave empty to show the notification immediately, or pick a future date to schedule it. **Expiry date** Leave empty for no expiration, or set a date after which the notification automatically hides. Great for time-limited announcements like holiday closures or promotional periods. ### Step 7: Preview and Save A live preview at the bottom of the form shows exactly how your notification will look as a banner in the portal. Review it, then click **Save**. ## Managing Notifications ### The Notification List The Portal Notifications page shows all your notifications in a table with: * **Title** and **type badge** * **Target audience** (All, Specific, or Tagged) * **Status** (Active, Inactive, Scheduled, or Expired) * **Active toggle** — Quickly enable or disable a notification * **Actions menu** — Edit or delete ### Filtering Notifications Use the filter dropdowns at the top to narrow down your list: * **Search** — Find notifications by title or message text * **Type** — Filter by Announcement, Price Change, Vacation, or Problem * **Status** — Filter by Active, Inactive, Scheduled, or Expired ### Editing a Notification Click **Edit** from the actions menu to update any notification. All fields can be changed except the email setting — emails that were already sent cannot be unsent. ### Activating and Deactivating Use the toggle switch in the notification list to quickly turn notifications on or off. Deactivated notifications are hidden from customers but not deleted, so you can reactivate them later. ### Deleting a Notification Click **Delete** from the actions menu to permanently remove a notification. This also removes any dismissal records associated with it. ## Use Cases ### Holiday Closure > **Type**: Vacation > > **Title**: "Holiday Closure: December 24 - January 2" > > **Message**: "Our office will be closed for the holidays. We'll respond to support tickets when we return on January 2nd. Happy holidays!" > > **Target**: All Customers > > **Expiry**: January 2nd > > **Email**: Yes ### Upcoming Price Increase > **Type**: Price Change > > **Title**: "Price Update Effective March 1st" > > **Message**: "Starting March 1st, our Business plan will increase from €15 to €18 per month. Your current billing continues unchanged until your next renewal. Contact us with questions." > > **Target**: Customers tagged "Business Plan" > > **Permanent**: Yes (until the change takes effect) > > **Email**: Yes ### Service Issue > **Type**: Problem > > **Title**: "Payment Processing Delay" > > **Message**: "We're experiencing a brief delay in processing payments. Your payments are safe — they will complete within 1-2 hours. We apologize for the inconvenience." > > **Target**: All Customers > > **Permanent**: Yes (remove manually when resolved) ### New Feature Announcement > **Type**: Announcement > > **Title**: "New: Pay with Saved Payment Methods" > > **Message**: "You can now pay invoices using your saved SEPA Direct Debit mandate. Look for the 'Use Saved Method' option on your next invoice payment." > > **Target**: All Customers > > **Expiry**: 2 weeks from now ## Best Practices * **Keep messages short** — Customers scan rather than read. Use clear, direct language. * **Use the right type** — It sets the right color and tone automatically. * **Set expiry dates** — Old notifications clutter the portal. Always add an expiry unless the notice is truly permanent. * **Use permanent sparingly** — If customers can't dismiss a notification, it stays visible forever. Reserve this for critical, ongoing information. * **Combine with email** — For important notices (price changes, outages), enable email delivery so customers are notified even if they don't log in. * **Target wisely** — Use tags to segment your audience. A price change for one plan doesn't need to go to all customers. ## Frequently Asked Questions > [accordion] Can customers reply to notifications? > > No, portal notifications are one-way communication. For two-way communication, customers can use the Support section to create a ticket. > [accordion] What happens when I delete a notification? > > The notification is permanently removed and all customer dismissal records are deleted too. Customers will no longer see it anywhere. > [accordion] Can I edit a notification after sending the email? > > Yes, you can edit the title, message, and all other settings. However, the email that was already sent will still show the original content. > [accordion] How many notifications can I have active at once? > > There's no limit. However, we recommend keeping it to 2-3 active banners at most — too many banners can overwhelm customers. > [accordion] Do notifications show on mobile devices? > > Yes. Both callout banners and the notification bell are fully responsive and work on all screen sizes. > [accordion] Can I schedule a notification for a specific time? > > You can set a start date. The notification will become visible on that date. Time is based on your account timezone. > [accordion] What if a customer isn't logged in when I send a notification? > > The notification will be waiting for them the next time they log in, as long as it hasn't expired. If you also enabled email, they'll receive the email regardless of login status. ## Next Steps > [card] [Customer Portal](/customer-management/customer-portal) > > Learn about the full Customer Portal experience > [card] [Tags System](/organization-and-automation/tags-system) > > Organize customers into groups for targeted notifications > [card] [Email Configuration](/business-settings/email-configuration) > > Set up your email settings for notification delivery > [card] [Customer Portal Settings](/customer-management/customer-portal-settings) > > Configure portal appearance and preferences # Private Notes Source: https://docs.payreque.st/customer-management/private-notes Keep internal, staff-only notes on a customer's profile that are never visible to the customer. # Private Notes Add internal notes to any customer's profile to track important context — special arrangements, past issues, reminders, or anything your team needs to know. Notes are only ever visible to you and your team; customers never see them, including in the customer portal. > [!NOTE] > > Notes are managed from the **Customer Notes** section on a customer's detail page. ## Adding a Note **1. Open a customer** Go to **Customers** and open the customer you want to add a note to. **2. Find the Customer Notes section** Scroll to **Customer Notes**. A compact preview of your most recent notes appears near the top of the profile; the full list with add/edit/delete controls is further down. **3. Add a note** Give the note a **title** and write the **content**. Both are required. **4. Save** The note appears immediately, newest first, along with a timestamp and your name. ## Editing and Deleting Notes Each note shows its title, content, creation date, and — if it's been edited — a separate "Updated" timestamp. Use the edit icon to update a note's title or content, or the delete option to remove it. Only notes belonging to customers in your own account are accessible — you can't view or edit notes on another business's customers. > [!NOTE] > > Deleted notes are soft-deleted rather than permanently erased immediately, but they no longer appear anywhere in the interface once removed. ## Who Can See Notes > [card] You and your team > > Any team member with access to the customer can view, add, edit, and delete notes. > [card] Never the customer > > Notes are excluded entirely from the customer portal — there is no code path that exposes them to customers. ## FAQ > [accordion] Can customers see private notes in the customer portal? > > No. Private notes are staff-only and never rendered anywhere a customer can access. > [accordion] Can I add more than one note to a customer? > > Yes — there's no limit. Notes are listed newest first, with the three most recent shown as a compact preview at the top of the profile. > [accordion] Do notes show who wrote them? > > Yes, each note displays the name of the team member who created it. > [accordion] Can I attach files to a note? > > Not on customer notes. If you need to share files internally on a specific case, use an internal note on a [Support Request](/customer-management/support-requests) instead, which supports attachments. ## Next Steps > [card] [Support Requests](/customer-management/support-requests) > > Use internal notes on tickets for case-specific, attachment-friendly documentation > [card] [Customer Health](/customer-management/customer-health) > > See other ways PayRequest surfaces context about a customer > [card] [Tax Exemptions](/customer-management/tax-exemptions) > > Manage customer-specific billing settings # Support Requests Source: https://docs.payreque.st/customer-management/support-requests Manage customer support tickets with email-to-ticket, rich text replies, file attachments, email notifications, and two-way email conversations # Support Requests 🎫 A built-in ticketing system that lets you manage customer inquiries, complaints, billing questions, and more — all from your PayRequest dashboard. Customers can submit requests from the customer portal, and you can respond with rich text replies that optionally notify them via email. > [!NOTE] > > **All Plans**: Support Requests are available on all plans. Customers submit requests through the customer portal, and you manage them from the **Support Requests** page in your dashboard sidebar. ## 🎯 Overview > [card] 📥 Receive > > Customers submit tickets from the portal or by replying to any email > [card] 📧 Email-to-Ticket > > Customer replies to invoices, orders, or reminders automatically create support tickets > [card] 💬 Respond > > Reply with a rich text editor, insert customer variables, and optionally email the customer > [card] 👁️ Track > > See when customers view their tickets, track conversation history, and monitor resolution ## 📋 Request Types Support requests are categorized by type to help you triage and filter: | Type | Use Case | | - | - | | **General Support** | General questions and help requests | | **Billing Question** | Questions about charges, invoices, or payments | | **Technical Issue** | Problems with portal access, payments, or functionality | | **Refund Request** | Customer requesting a refund | | **Complaint** | Formal complaints requiring attention | | **Pause Subscription** | Request to pause an active subscription | | **Cancel Subscription** | Request to cancel a subscription with notice period (see [Cancellation Requests](/subscriptions/cancellation-requests)) | | **Invoice/Order Correction** | Corrections needed on invoices or orders | | **Feature Request** | Suggestions for improvements | | **Quote Request** | Custom quote inquiries (legacy category — for new custom-scoped work, sell a [Commission product](/products-and-pricing/commissions) or send a [Quote](/invoices/creating-invoices) instead) | | **Provider Request** | Requests related to service providers | ## 🚀 Managing Requests ### Request List Open the **Inbox** and select **All requests**, **Support** or **Cancellations**. Support includes every request type except subscription cancellation. Category cards show active requests and how many need a reply across the inbox. Within a category, use **Open**, **To reply**, **In Review**, **Done** or **All**. Open includes open and in-review requests; Done includes resolved, closed and rejected requests. Folder counts follow the selected category and can differ from the visible list when additional search or priority filters apply. **To reply** highlights active requests with no public business reply yet, or where the latest public reply came from the customer. Internal notes do not count as a customer-facing response. Search and filter by request type, priority or assigned person to work through the queue. The list shows each request’s subject, customer, message preview, status, priority where relevant and reply indicator. Open a row to read the conversation and respond. ### Filtering & Search Use the filter bar to narrow down requests: * **Search** — Find by subject, message content, or customer name/email * **Status** — Open, In Review, Resolved, Rejected, Closed * **Type** — Filter by any request type * **Priority** — Low, Medium, High, Urgent ## 💬 Responding to Requests ### Rich Text Editor The response form includes a full rich text editor with: * **Formatting** — Bold, italic, underline, strikethrough * **Lists** — Bullet and numbered lists * **Blockquote** — For quoting customer messages * **Links** — Insert clickable links * **Undo/Redo** — Full history support > [!TIP] > > **Keyboard Shortcuts**: Use standard shortcuts like `Ctrl+B` for bold, `Ctrl+I` for italic, and `Ctrl+Z` for undo. The editor also supports Markdown notation — type `**text**` for bold, `- ` for bullet lists, etc. ### Insert Variables Click the **code bracket icon** (`{ }`) in the editor toolbar to quickly insert contextual data at your cursor position: > [card] 👤 Customer Variables > > * **Name** — Customer's display name > * **Email** — Customer's email address > * **Company** — Company name (if business customer) > [card] 🎫 Request Variables > > * **Request ID** — e.g. `#32` > * **Subject** — The request subject line > [card] 🔄 Subscription Variables > > Inserts the customer's subscription names (up to 3 shown), with amounts displayed for reference > [card] 📄 Invoice Variables > > Inserts invoice numbers (up to 3 shown), with amounts displayed for reference The dropdown also includes a **Business Name** option that inserts your company name. > [!NOTE] > > **Real Values**: Variables insert the actual values (e.g. "Francesco Trovato"), not template placeholders. This makes your replies read naturally. ### Internal Notes Check **"Internal Note (only visible to admin)"** to add notes that customers cannot see. Internal notes appear with an amber highlight in the conversation and are excluded from the customer portal view. ## 📎 File Attachments You and your customers can add files to any reply — screenshots, PDFs, invoices, signed documents, anything that helps resolve the ticket. Attachments appear inline in the conversation and are automatically included as real attachments on the reply email. > [!NOTE] > > **Both sides can attach**: Admins upload from the dashboard reply form; customers can attach files when replying from the customer portal. ### Uploading Files Below the reply editor is a drag-and-drop **Attachments** area. Drop files onto it, or click to browse. * **Up to 10 files** per reply * **Maximum 20 MB** per file * Any file type is accepted — images, PDFs, spreadsheets, ZIPs, etc. * Remove a queued file by clicking the remove icon on its preview card before sending ### How Attachments Are Shown In the conversation history: * **Images** (JPG, PNG, GIF, etc.) are rendered as inline previews — click to open full-size * **Other files** appear as download cards with filename and size * Each attachment belongs to a specific reply and shows alongside that message ### Attachments in Emails When you send a reply with **"Send reply notification to customer via email"** enabled, any files you attached are included as **real email attachments** — the customer receives them directly in their inbox, no portal login needed. > [!WARNING] > > **Email size limits**: Most email providers reject messages over 25–40 MB total. The 20 MB per-file limit gives room for one large attachment plus the email body, but combining many large files in a single reply may cause delivery issues. ### Privacy & Storage * Files are stored on PayRequest's private object storage with unguessable unique identifiers * Downloads from the portal or dashboard are routed through an authorized download endpoint that verifies ticket ownership on every request * Internal notes and their attachments are never visible to customers * Attachments inherit the ticket's lifecycle — deleting a reply removes its files automatically ## 📧 Email Notifications ### Sending Reply Notifications When replying to a request (non-internal), you can check **"Send reply notification to customer via email"** to email the customer about your response. The email includes: * **Your business logo** at the top * **Customer greeting** by name * **Request subject** for context * **Reply preview** (first 200 characters) * **"View Full Reply" button** linking to the customer portal * **Any attachments** you added to the reply, sent as real email attachments * **Business branding** in the footer > [!TIP] > > **Enabled by Default**: The email notification checkbox is checked by default for convenience. Uncheck it if you only want to add a reply without notifying the customer. ### Button States The submit button changes based on your selection: * **"Add Reply"** — When email notification is unchecked or reply is internal * **"Send Reply & Email"** — When email notification will be sent After sending, a confirmation message shows the recipient's email address. ## 📨 Email-to-Ticket (Inbound Email) Customers can create support tickets simply by **replying to any email** they receive from your business — invoices, payment reminders, order confirmations, subscription notices, and more. No portal login needed. > [!NOTE] > > **How it works**: Every outgoing email includes a Reply-To address at your business's `payreque.st` address (e.g., `yourshop@payreque.st`). When a customer replies, the email is automatically converted into a support ticket. ### Supported Emails All customer-facing emails include the Reply-To header: | Email Type | Example | | - | - | | New Invoice | Invoice created notification | | Invoice Paid | Payment confirmation | | Invoice Reminder | Overdue payment reminders | | Order Confirmation | New order acknowledgment | | Order Completed | Order fulfillment notice | | Payment Link | Smart link sent to customer | | Payment Reminder | Smart link follow-up | | Subscription Suspended | Pause/suspension notice | | Price Increase | Subscription price change | | Mandate Request | iDEAL mandate setup | | Mandate Activation | Mandate confirmed | | Security Deposit | Deposit authorization | | Debt Collection | Payment collection notices | | Checkout Recovery | Abandoned cart reminders | | Portal Notification | Custom portal alerts | | Support Reply | Your reply to an existing ticket | ### How Tickets Are Created **1. Customer Replies to Email** The customer hits "Reply" on any email from your business and writes their message. **2. Email Received** The reply is received at your `payreque.st` address and processed automatically. **3. Customer Matched** The sender's email is matched to an existing customer in your account. If no exact match is found, the system checks for customers with the same email domain (e.g., `jan@company.com` matches `support@company.com`). **4. Ticket Created** A new support ticket is created with the email subject and full message body, set to type **Support** and priority **Medium**. **5. You're Notified** You receive an email notification about the new ticket with a direct link to your dashboard. > [!TIP] > > **Domain Matching**: If a customer emails from a different address at the same company domain, the system still matches them. For example, if `support@acme.com` is your customer, an email from `jan@acme.com` will also be matched. Common email providers like Gmail, Outlook, etc. are excluded from domain matching to prevent false matches. ### Reply via Email (Two-Way Conversations) When you receive a notification about a new ticket, you can **reply directly to the notification email** instead of opening the dashboard. Your reply is automatically added to the ticket conversation and forwarded to the customer. Similarly, when a customer receives your reply notification, they can reply back by email — their response is appended to the same ticket thread. > [!WARNING] > > **Unknown Senders**: Emails from addresses that don't match any customer in your account are automatically ignored. This prevents spam from creating unwanted tickets. ### Reply-To Address Your business's Reply-To address is determined automatically: | Business Type | Reply-To Address | | - | - | | **Shop owners** | `{shopname}@payreque.st` | | **Freelancers** (PayRequest Page) | `{handle}@payreque.st` | | **Fallback** | `u{userid}@payreque.st` | > [!NOTE] > > **No Setup Required**: The Reply-To address is generated automatically based on your shop name or PayRequest Page handle. No DNS or email configuration needed on your end. ## 👁️ Customer Activity Tracking ### Ticket Views The timeline automatically tracks when a customer views their support ticket in the portal. This helps you understand engagement: * **Teal eye icon** in the timeline when the customer opens the ticket * **Throttled to once per hour** — repeated page refreshes don't create duplicate entries * Shows the exact timestamp of each view ### Timeline The sidebar timeline shows a chronological feed of all activity on a request: | Event | Icon | Color | | - | - | - | | Request created | Dot | Green | | Customer reply | Dot | Gray | | Admin response | Dot | Blue | | Internal note | Dot | Amber | | Email sent to customer | Envelope | Indigo | | Customer viewed request | Eye | Teal | Up to 15 events are shown, with a summary if there are more. ## 🔄 Request Lifecycle **1. Customer Submits Request** Customer creates a ticket from the portal, or by replying to any business email. Status: **Open**. You receive an email notification. **2. You Review the Request** View the request details, customer info, and any related records. Change status to **In Review** **3. Respond to Customer** Write a reply using the rich text editor, insert relevant variables, and optionally send an email notification **4. Customer Views & Replies** Customer sees your reply in the portal (tracked in timeline). They can add follow-up replies which reopen closed tickets **5. Resolve or Close** Mark the request as **Resolved** when the issue is addressed, or **Closed** when no further action is needed ### Status Flow ``` Open → In Review → Resolved → Rejected → Closed ``` > [!NOTE] > > **Auto-Reopen**: If a customer replies to a resolved or closed ticket, it automatically reopens with status **Open** so you don't miss follow-ups. ## 📊 Request Detail Page ### Main Content Area The detail page has a two-column layout: **Left Column (2/3 width):** * Original request message (rendered with full HTML formatting) * Related record link (if linked to an invoice, order, or subscription) * Full conversation history with color-coded messages * Reply form with rich text editor **Right Column (1/3 width):** * Customer card with avatar, name, email, phone, company * Status and priority management dropdowns * Activity timeline ### Related Record Popover When a request is linked to a subscription, hovering over the related record badge shows a detailed popover with: * **Subscription name** and ID * **Status badge** (active, cancelled, etc.) * **Amount and billing interval** (e.g. €9.25 / month) * **Next billing date** and creation date * **Cancellation details** if a cancellation is pending (requested date, effective date, reason) * **Quick link** to the full subscription detail page For invoices and orders, the link shows the invoice number or order number alongside the ID. ### Cancellation Decision Actions For a cancellation request, review the linked subscription and its effective date before choosing an action: * **Confirm scheduled cancellation** confirms the agreed date; a future-dated subscription continues until that date. * The business cannot withdraw the customer's cancellation through the former reject action. Use an eligible **proposal** if you want to offer an alternative. * **Preview proposal** lets the account owner review an earlier end, temporary discount or compatible cheaper product before publishing. The customer must explicitly accept the offer. * If an earlier end has already been agreed with the customer, the owner can review **End immediately** and its separate confirmation. Review access, export and existing invoices first. Ignoring, declining or letting a proposal expire preserves the original cancellation. Closing a ticket alone does not prove its subscription has ended. Check the subscription status, effective date and confirmation-email status separately. See [Cancellation Requests](/subscriptions/cancellation-requests) for eligibility and processing, and share [the customer cancellation guide](/customer-guide/manage-subscription) with the customer. ### Quick Actions Action buttons at the top of the page let you quickly: * **Mark In Review** — Acknowledge you're looking into it * **Mark as Resolved** — Issue has been addressed * **Close Request** — No further action needed ## 🎨 Customer Portal Experience Customers interact with support through the portal at `/shop/{storename}/support`: * **View all their tickets** with status badges and filtering * **Create new tickets** with subject, message, type, and priority * **Reply to existing tickets** (automatically reopens closed tickets) * **Attach files** to replies — same 10 files / 20 MB limits as the admin side * **See admin responses** (internal notes are hidden) * **Download attachments** sent by your team through a secure, ticket-scoped link When creating a request with type **Cancel Subscription** or **Pause Subscription**, the form automatically selects "Subscription" as the related record type and requires the customer to choose which subscription the request is about. The dropdown shows subscription names with amounts and status for easy identification. > [!NOTE] > > **Custom Domains**: Support works on custom domains too. If your shop uses `shop.yourbusiness.com`, support is available at `shop.yourbusiness.com/support`. ## 💡 Best Practices > [card] ⚡ Response Time > > * Acknowledge requests within 4 hours > * Use "In Review" status to signal you're on it > * Use internal notes to document your investigation > * Send email notifications for important updates > [card] 📝 Reply Quality > > * Use the variable inserter for consistent, personalized replies > * Reference specific subscription or invoice details > * Include next steps or expected timelines > * Use formatting to highlight key information ## 🎓 Next Steps > [card] [Commissions](/products-and-pricing/commissions) > > Sell custom-scoped creative and freelance work with a starting price > [card] [Customer Portal](/customer-management/customer-portal) > > See the full customer portal experience including support integration > [card] [Portal Notifications](/customer-management/portal-notifications) > > Set up in-portal notifications for your customers > [card] [Email Configuration](/business-settings/email-configuration) > > Configure your email settings for support notifications # Tax Exemptions Source: https://docs.payreque.st/customer-management/tax-exemptions Manage tax-exempt status for B2B customers, non-profits, and international clients # Tax Exemptions Tax exemptions allow you to process orders and invoices without charging VAT/BTW for qualifying customers. This is essential for B2B transactions within the EU, exports, and dealings with non-profit organizations. ## Who Qualifies for Tax Exemption? > [card] EU B2B Customers > > Businesses in other EU countries with valid VAT numbers qualify for reverse charge (BTW Verlegd). > [card] Export Customers > > Customers outside the EU are exempt from Dutch/EU VAT on exports. > [card] Non-Profit Organizations > > Certain registered non-profits and charities may qualify for tax exemption. > [card] Government Entities > > Government organizations and public institutions may be exempt from VAT. ## Enabling Tax Exemption ### For Individual Customers **1. Open Customer Profile** Navigate to **Customers** in your dashboard and click on the customer you want to update. **2. Find Tax Settings** In the customer details panel, look for the **Tax Exempt** toggle in the business information section. **3. Enable Tax Exemption** Toggle the switch to enable tax exemption. The customer will now receive 0% tax on all future invoices and orders. **4. Add Documentation** Add a **Private Note** explaining why this customer is exempt (e.g., "EU VAT number verified: DE123456789"). > [!NOTE] > > Tax exemption applies immediately. Any new invoices or orders for this customer will automatically have 0% tax. ### Using Bulk Actions To update multiple customers at once: 1. Go to **Customers** 2. Check the boxes next to customers you want to update 3. Click **Bulk Actions** button 4. Select **Toggle Tax Exempt** 5. Confirm the action All selected customers will have their tax exemption status toggled. ## Visual Indicators PayRequest makes it easy to identify tax-exempt customers: ### In Customer Lists Tax-exempt customers display a badge: * **Tax Exempt**: Green badge indicating exemption is active * **Standard Tax**: Gray badge (or no badge) for regular customers ### On Customer Detail Pages The customer profile shows: * Tax exemption toggle status * Country information (relevant for EU VAT rules) * VAT number if stored ### On Invoices When creating invoices for tax-exempt customers: * All line items show **0%** tax rate * Invoice displays **"BTW VERLEGD"** (Tax Reversed) * Total excludes tax automatically ## How Tax Exemption Affects Different Areas ### Shopping Cart & Checkout When a tax-exempt customer shops in your store: | Without Exemption | With Exemption | | - | - | | Product: €100.00 | Product: €100.00 | | BTW (21%): €21.00 | BTW (0%): €0.00 | | **Total: €121.00** | **Total: €100.00** | The cart automatically detects the customer's exemption status and adjusts calculations. ### Invoice Creation When creating an invoice for a tax-exempt customer: 1. System automatically sets tax rate to 0% for all items 2. Invoice header/footer can show "BTW Verlegd" note 3. No manual intervention needed ### Subscriptions Existing subscriptions for a customer who becomes tax-exempt: * Future billing cycles will use 0% tax * Past invoices remain unchanged (for audit purposes) * Recurring amount stays the same (customer saves the tax portion) ### Orders New orders placed by tax-exempt customers: * Order total calculated without tax * Order confirmation shows 0% tax breakdown * OrderItems stored with 0% tax rate ## VAT Number Storage For EU B2B customers, store their VAT number for compliance: ### Adding VAT Information 1. Open the customer profile 2. Navigate to **Business Information** section 3. Enter: * **VAT Number**: The customer's EU VAT number (e.g., DE123456789) * **Country**: The customer's country * **Company Name**: Legal business name > [!WARNING] > > Always verify VAT numbers before applying tax exemption. Use the EU's [VIES VAT validation service](https://ec.europa.eu/taxation_customs/vies/) to check validity. ### VAT Number Validation PayRequest stores validation information: * `vat_number_valid`: Whether the number passed validation * `vat_number_validated_at`: When validation was performed * `vat_company_name`: Company name returned by validation * `vat_company_address`: Address returned by validation > [!TIP] > > Keep records of your VAT validations. Tax authorities may request proof that you verified customer VAT numbers before applying reverse charge. ## Reverse Charge (BTW Verlegd) When selling to EU businesses with valid VAT numbers, the reverse charge mechanism applies: ### How It Works 1. **You sell** to an EU business (not in your country) 2. **You verify** their VAT number is valid 3. **You mark them** as tax exempt in PayRequest 4. **You invoice** them at 0% VAT 5. **Invoice shows** "BTW Verlegd" or "Reverse Charge VAT" 6. **Customer accounts** for VAT in their own country ### Requirements for Reverse Charge To legally apply reverse charge, you must: **1. Verify VAT Number** Validate the customer's EU VAT number through VIES or similar service. **2. Confirm Different Country** The customer must be in a different EU country than your business. **3. Document the B2B Nature** The transaction must be business-to-business, not B2C. **4. Include Required Invoice Text** Invoice must mention "Reverse Charge" or "BTW Verlegd" and show 0% VAT. ### Invoice Requirements For reverse charge invoices, ensure your invoice shows: * Your VAT number * Customer's VAT number * Text: "BTW verlegd" or "VAT reverse charge applies" * 0% VAT rate on all items ## Export Sales (Outside EU) For customers outside the European Union: ### Automatic Detection PayRequest recognizes non-EU countries and can apply 0% tax for exports. ### Manual Setup 1. Set customer's **Country** to their non-EU location 2. Mark customer as **Tax Exempt** 3. Add note: "Export - customer outside EU" ### Export Invoice Requirements Your export invoices should include: * Clear indication this is an export sale * Customer's full address (outside EU) * 0% VAT rate with explanation ## Best Practices > [accordion] Document Everything > > For each tax-exempt customer, record: > > * Why they qualify for exemption > * Date exemption was verified > * VAT number validation results (for EU businesses) > * Any supporting documentation received > > Use Private Notes on customer profiles to store this information. > [accordion] Regular Reviews > > VAT numbers can become invalid. Schedule periodic reviews: > > * Revalidate EU VAT numbers annually > * Check if business customers are still operating > * Verify non-profits maintain their exempt status > [accordion] Train Your Team > > Ensure anyone creating invoices understands: > > * How to verify VAT numbers > * When to apply tax exemption > * What documentation to collect > * How to handle edge cases > [accordion] Audit Trail > > PayRequest maintains an activity log of changes. Keep your records up to date: > > * Note when exemption was enabled/disabled > * Record reasons for changes > * Store validation screenshots or exports from VIES ## Frequently Asked Questions > [accordion] Can I apply tax exemption retroactively? > > Tax exemption only applies to new invoices and orders. Past invoices are not automatically updated (this is correct for accounting purposes). If you need to correct a past invoice, you may need to issue a credit note and new invoice. > [accordion] What if a customer's VAT number becomes invalid? > > If you're notified that a customer's VAT number is no longer valid: > > 1. Disable their tax exemption > 2. Contact the customer to verify their VAT status > 3. Re-enable only after confirming a valid number > 4. Document the change in their profile > [accordion] Can different products have different exemption rules? > > Tax exemption is applied at the customer level, not product level. When a customer is tax exempt, all products they purchase are at 0% tax. If you need per-product rules, consider creating separate customer records or using different product variants. > [accordion] How do subscriptions handle exemption changes? > > If you toggle tax exemption for a customer with active subscriptions: > > * **Enabling**: Future billing cycles will be at 0% tax > * **Disabling**: Future billing cycles will include tax at the product's rate > > The change takes effect on the next billing cycle. > [accordion] Do I need proof of export for non-EU sales? > > While PayRequest handles the tax calculation, you should maintain proof of export (shipping documentation, delivery confirmations) for your records. Tax authorities may request this during audits. ## Compliance Checklist Before applying tax exemption, verify: **1. Customer Qualification** Does the customer legally qualify for tax exemption? **2. Documentation** Do you have the required documentation (VAT number, export proof, etc.)? **3. Validation** Have you validated any VAT numbers through official channels? **4. Record Keeping** Have you recorded the exemption reason in the customer profile? ## Related Documentation > [card] [Tax & VAT Guide](/business-settings/tax-vat-guide) > > Complete guide to tax configuration in PayRequest > [card] [Customer Profiles](/customer-management/customer-profiles) > > Managing customer information and settings > [card] [Creating Invoices](/invoices/creating-invoices) > > How to create invoices with proper tax handling > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > Update multiple customers at once *** > [!NOTE] > > Tax exemption rules are complex and vary by jurisdiction. This documentation covers PayRequest's features. Consult with a tax professional for advice specific to your business situation. # Creating Collection Cases Source: https://docs.payreque.st/debt-collection/creating-cases How to create debt collection cases from overdue invoices or external debts # Creating Collection Cases You can create collection cases in two ways: from an existing overdue invoice, or as an external debt for amounts not tied to an invoice in PayRequest. ## Creating a Case from an Invoice This is the most common way to start a collection. When an invoice is overdue and regular payment reminders haven't worked, you can escalate it to a formal collection case. ### Navigate to Debt Collection Go to **Debt Collection** in your dashboard sidebar, then click **Create Case**. ### Select "From Invoice" The default tab lets you create a case from an existing invoice. ### Choose the Invoice Use the dropdown to select the overdue invoice. Only unpaid invoices are shown. You'll see the invoice number, customer name, and amount. ### Add Internal Notes (Optional) Add any context about the case — previous communication attempts, customer responses, or special circumstances. These notes are only visible to you, never to the customer. ### Enable Pre-Incasso (Optional) Toggle **Pre-Incasso** on if you want to start with a soft, informal reminder (Stage 0) before beginning formal collection. This gives the customer one more chance to pay without the pressure of formal notices. ### Create the Case Click **Create Case**. The system will: * Create a new collection case with a unique case number (e.g., `DC-2026-001`) * Link it to the invoice and customer * Set the stage to **Stage 0: Pre-Collection** (if pre-incasso is enabled) or **Stage 1: Friendly Reminder** * Record the original invoice amount as the case amount > [!NOTE] > > Each invoice can only have one active collection case. If you try to create a case for an invoice that already has one, you'll see a warning. ## Creating a Case for an External Debt Sometimes you need to collect on debts that aren't tracked as invoices in PayRequest — for example, an outstanding balance from another system, a verbal agreement, or a service provided outside your normal invoicing flow. ### Navigate to Debt Collection Go to **Debt Collection** in your dashboard sidebar, then click **Create Case**. ### Select "External Debt" Switch to the **External Debt** tab. ### Fill in the Details | Field | Description | | - | - | | **Customer** | Select an existing customer from the dropdown | | **Description** | What the debt is for (becomes the invoice line item) | | **Amount** | The total amount owed | | **Due Date** | The original due date (must be in the past) | | **Currency** | EUR by default | | **Notes** | Optional internal notes about the case | ### Enable Pre-Incasso (Optional) Toggle **Pre-Incasso** on to start with a gentle reminder before formal collection. ### Create the Case Click **Create Case**. The system will: * Automatically create an invoice with the amount and description * Create a collection case linked to this new invoice * Set the stage to **Stage 0: Pre-Collection** (if pre-incasso) or **Stage 1: Friendly Reminder** > [!TIP] > > The automatically created invoice works just like any other invoice in PayRequest. Customers can pay it through the payment page, customer portal, or via a payment link you share. ## After Creating a Case Once a case is created, you can: * **Send a reminder email** — Notify the customer about the outstanding amount * **Send a postal letter** — Mail a physical collection letter via Pingen * **Pause the case** — Temporarily suspend escalation while negotiating * **Register payments** — Record bank transfers, cash, or other payments received * **View the case** — See all details, payment history, and activity timeline * **Configure settings** — Set the language, enable payment plan requests, and manage case-specific options ### Case Settings On the case detail page, you'll find a **Case Settings** card where you can configure: * **Language** — Set the language for all communication with this customer (Dutch or English) * **Allow installment requests** — Let the customer request a payment plan from the portal ## What Happens Next After creating the case, your next step depends on your recovery strategy: 1. **Immediate action**: Send a reminder email right away to notify the customer 2. **Wait for automation**: Let the automated escalation handle it based on your schedule 3. **Personal approach**: Contact the customer directly, then use the case to track the outcome > [card] [Escalation Pipeline](/debt-collection/escalation-pipeline) > > Learn about the 4 stages and automated progression > [card] [Payment Plans](/debt-collection/payment-plans) > > Set up installment plans for customers # Escalation Pipeline Source: https://docs.payreque.st/debt-collection/escalation-pipeline How the 5-stage collection pipeline works and how cases are escalated automatically # Escalation Pipeline Every collection case follows up to 5 stages. Each stage increases the urgency of communication and can add collection fees to the outstanding balance. You can escalate cases manually or let PayRequest handle it automatically. ## The Stages ### Stage 0: Pre-Collection (Optional) A soft, informal reminder before formal collection begins. Enable this by toggling **Pre-Incasso** when creating the case. **Tone:** Gentle and friendly **Message:** "We would like to kindly remind you that the following invoice is still open." * No collection fees * Ideal for first-time late payers * Automatically escalates to Stage 1 the next time daily automatic escalation runs after the invoice is overdue — there is no fixed grace period, so keep a case in Pre-Collection only as long as you're actively working it manually * Gray/neutral presentation in the customer portal > [!TIP] > > Pre-incasso is free and non-threatening. Use it to give customers one final chance before starting formal collection. ### Stage 1: Friendly Reminder The first contact assumes the customer simply forgot or overlooked the invoice. **Tone:** Polite and helpful **Message:** "You have an outstanding invoice that requires your attention. Please arrange payment to avoid further action." * No collection fees added * Email reminder sent * Customer sees a gentle warning in the portal ### Stage 2: Formal Notice A more formal communication setting a clear deadline for payment. **Tone:** Professional and firm **Message:** "This is a formal notice regarding your outstanding payment. Please settle this amount within 7 days." * No collection fees added (optional at your discretion) * Postal letter recommended at this stage * Customer portal shows formal notice banner ### Stage 3: Collection Fees At this stage, collection fees can be added to cover your recovery costs. **Tone:** Firm and direct **Message:** "Collection fees have been added to your outstanding balance. Please pay the total amount immediately." * **Collection fees added** to the balance * The customer sees the original amount + collection fee in the portal * Payment pages show the total including fees * Postal letter sent automatically (if Pingen is configured) ### Stage 4: Final Warning The last stage before further consequences (legal action, external collection agency, etc.). **Tone:** Urgent **Message:** "This is your final warning. Immediate payment is required to avoid further consequences." * Maximum urgency in all communication * Customer portal shows a red warning banner * All payment links reflect the full amount including fees ## Visual Progress Customers see a progress bar in the Customer Portal showing how far along the collection process they are: | Stage | Color | Label | | - | - | - | | 0 | Gray | Pre-Collection | | 1 | Blue | Reminder | | 2 | Amber | Formal Notice | | 3 | Orange | Collection Fees | | 4 | Red | Final Warning | This helps customers understand the seriousness of the situation and motivates earlier payment. ## Adding Collection Fees You can add a collection fee at any stage, though it's most common at Stage 3. 1. Open the case detail page 2. Find the **Amount Breakdown** section 3. Enter the collection fee amount 4. Click **Update Fee** The fee is immediately reflected: * In the case total * On the customer portal * On the payment page * In postal letters and email reminders > [!TIP] > > In the Netherlands, collection fee guidelines (WIK/BIK) suggest fees proportional to the original amount. For example, up to 15% on the first EUR 2,500. Check your local regulations. ## Manual Escalation To manually move a case to the next stage: 1. Open the case detail page 2. Click the **Escalate** button in the case header 3. The case moves to the next stage immediately 4. You can then send a reminder with the new stage's messaging > [!WARNING] > > Escalation cannot be reversed. Once a case moves to the next stage, it stays there. Make sure you're ready before escalating. ## Automatic Escalation PayRequest can automatically escalate cases based on how many days they've been overdue. This runs daily and processes all active cases. **Stage thresholds (by total days overdue):** | Days Overdue | Target Stage | | - | - | | 0–7 days | Stage 1 (Friendly Reminder) | | 8–21 days | Stage 2 (Formal Notice) | | 22–30 days | Stage 3 (Collection Fees) | | 31+ days | Stage 4 (Final Warning) | > [!WARNING] > > Each daily run recalculates the correct stage directly from the case's total days overdue — it does not step through stages one at a time. If a case is missed for a while (for example, it was paused) and comes back with 35 days overdue, it can jump straight from Stage 1 all the way to Stage 4 in a single run, skipping Stages 2 and 3. When a case is automatically escalated: * The stage is updated * A reminder email is sent to the customer * A postal letter is sent (if Pingen is configured, at Stage 2+) * The escalation is logged in the activity timeline > [!NOTE] > > Automatic escalation only runs for **active** cases. Paused cases, cases with payment plans, paid cases, and closed cases are all skipped. When you resume a paused case, it catches up automatically if enough time has passed. ## Sending Reminders At any stage, you can send a reminder to the customer: ### Email Reminders Click **Send Reminder** on the case detail page to send an email. The email content automatically matches the current stage — no need to write the message yourself. ### Postal Letters Click **Send Postal Letter** to mail a physical letter via Pingen. The letter includes your business details, the customer's address, the amount breakdown, and a QR code for quick payment. See [Postal Letters](/debt-collection/postal-letters) for details. ## Resolving Cases A case can be resolved in several ways: | Resolution | How It Happens | | - | - | | **Paid** | Customer pays the full amount (auto-detected via payment webhook) | | **Manual Payments** | You register partial payments until the balance is covered | | **Remission** | You register partial payment(s) then waive the remaining balance | | **Payment Plan Completed** | All installments paid (auto-closed) | | **Manually Closed** | You close the case from the dashboard | | **Cancelled** | You cancel the case with a reason | ## Best Practices > [accordion] Give customers enough time between stages > > Don't escalate too quickly. Allow at least 14 days between stages so customers have a realistic chance to arrange payment. > [accordion] Send a reminder at each new stage > > Customers need to know their case has been escalated. Always send a reminder (email or postal) when moving to a new stage. > [accordion] Use postal letters for Stage 2+ > > Physical letters carry more weight than emails. Starting postal communication at Stage 2 (Formal Notice) shows you're serious about recovery. > [accordion] Consider payment plans before Stage 4 > > Before reaching the Final Warning, consider offering a payment plan. Collecting in installments is usually better than not collecting at all. > [accordion] Keep internal notes updated > > Document any phone calls, customer responses, or agreements in the case's internal notes. This creates a clear record if you need to involve a legal advisor later. ## Related Documentation > [card] [Creating Cases](/debt-collection/creating-cases) > > How to open a new collection case > [card] [Payment Plans](/debt-collection/payment-plans) > > Set up installment plans for customers > [card] [Postal Letters](/debt-collection/postal-letters) > > Send physical letters via Pingen > [card] [Debt Collection Overview](/debt-collection/overview) > > Back to the overview # Managing Cases Source: https://docs.payreque.st/debt-collection/managing-cases Pause and resume collection cases, register manual payments, and waive remaining balances # Managing Cases Once a collection case is open, you have full control over how it progresses. Pause cases when a customer is negotiating, register payments received outside PayRequest, or waive remaining balances when you've agreed on a settlement. > [!NOTE] > > These features work for both invoice-based cases and external debt cases. You can manage any active or paused case from the case detail page. ## Key Capabilities > [card] Pause & Resume > > Temporarily suspend automated escalation while you negotiate with the customer > [card] Partial Payments > > Register payments received via bank transfer, cash, or other channels > [card] Waive Balance > > Write off the remaining balance when you've agreed on a settlement (kwijtschelding) > [card] Activity Timeline > > Every action is logged in a unified timeline — emails, letters, payments, stage changes ## Pause & Resume Sometimes you need to put a case on hold — for example, while negotiating a payment arrangement, waiting for a customer response, or during a dispute review. ### Pausing a Case ### Open the Case Navigate to **Debt Collection** and click on the case you want to pause. ### Click Pause In the **Actions** card on the right sidebar, click **Pause**. Confirm the action. ### Case is Paused The case status changes to **Paused** (purple badge). A purple banner appears at the top of the case. **What happens when a case is paused:** * Automated escalation is suspended — the case won't progress to the next stage * Daily processing skips the case entirely * The customer portal shows a "Case On Hold" message * You can still send reminders, register payments, and add notes * The payment link remains active — the customer can still pay at any time ### Resuming a Case Click **Resume** on the purple banner (or from the paused case list). The case returns to **Active** status and: * Days overdue are recalculated based on the current date * If enough time has passed, the case may automatically escalate to the next stage * Automated processing resumes from the next daily run > [!TIP] > > Use pause strategically. If a customer promises to pay within a week, pause the case to show good faith. If they don't follow through, resume and escalate. ### Filtering Paused Cases On the Debt Collection overview, use the **Status** filter and select **Paused** to see all cases currently on hold. ## Registering Payments When a customer pays outside of PayRequest — via direct bank transfer, cash, or another channel — you can register the payment manually to keep the case up to date. ### Register a Payment ### Open the Case Navigate to the collection case detail page. ### Find the Register Payment Section Below the amount breakdown, you'll see the **Register Payment** form (only visible for active or paused cases with a remaining balance). ### Fill in the Details | Field | Description | | - | - | | **Amount** | How much was paid (cannot exceed remaining balance) | | **Date** | When the payment was received | | **Method** | Bank Transfer, Cash, or Other | | **Note** | Optional note about the payment (e.g., reference number) | ### Click Register Payment The payment is recorded and the amount breakdown updates immediately. ### Amount Breakdown When partial payments are registered, the case detail page shows a clear breakdown: | Line | Example | | - | - | | Original Amount | EUR 1,000.00 | | Collection Fee | EUR 40.00 | | **Total Due** | **EUR 1,040.00** | | Amount Paid | - EUR 500.00 | | **Remaining** | **EUR 540.00** | This breakdown is also visible to the customer in the portal and on payment pages. ### Automatic Case Closure When the total amount paid reaches or exceeds the total due, the case is **automatically marked as paid**. No manual action needed. ### Payment History All registered payments appear in the **Payment History** table on the case detail page, showing the date, amount, method, and any notes for each payment. ## Waiving the Remaining Balance Sometimes you agree to accept less than the full amount — a settlement, goodwill gesture, or recognition that the full debt won't be recovered. In Dutch collection practice, this is called **kwijtschelding** (remission). ### Register Partial Payment(s) First Register any actual payments you've received. The remaining balance will be calculated automatically. ### Click Waive Remaining Below the Register Payment button, click **Waive Remaining**. You'll see a confirmation dialog showing the exact amount that will be waived. ### Confirm the Waiver The remaining balance is recorded as a "remission" entry in the payment history, and the case is marked as **Paid**. > [!WARNING] > > Waiving a balance is permanent. The case will be closed as paid and cannot be reopened. Make sure you've received all expected payments before waiving. The waived amount appears in the payment history with a purple **waived** label, so you always have a clear record of what was actually paid versus what was written off. ## Pre-Collection Stage (Pre-Incasso) Before starting formal debt collection, you can send a free, informal reminder — the **Pre-Collection** stage. This is a soft first step that often resolves the payment without any formal collection process. ### How It Works When creating a new collection case, toggle **Pre-Incasso** on. The case starts at **Stage 0: Pre-Collection** instead of Stage 1. **Stage 0 characteristics:** * Softer, more friendly communication tone * No collection fees added * Gray/neutral color in the portal (less alarming for customers) * Emails and letters use gentle reminder language * After 14 days without payment, the case automatically escalates to Stage 1 > [!TIP] > > Pre-incasso is ideal when you want to give customers one final chance before starting formal collection. It's free, non-threatening, and often resolves the issue without needing the full pipeline. ### Stage Overview (Including Pre-Collection) | Stage | Name | Tone | Fees | | - | - | - | - | | 0 | Pre-Collection | Gentle, assumes oversight | None | | 1 | Friendly Reminder | Polite, clear request | None | | 2 | Formal Notice | Professional, sets deadline | None | | 3 | Collection Fees | Firm, fees applied | Yes | | 4 | Final Warning | Urgent, final chance | Yes | ## Activity Timeline Every action on a case is recorded in a unified timeline on the right sidebar of the case detail page. The timeline combines: * **Stage changes** — When the case moves to a new stage (with colored badges) * **Emails sent** — Each reminder email, with timestamp * **Letters sent** — Postal letters uploaded to Pingen * **Payments registered** — Manual payment registrations * **Balance waived** — Remission entries * **Case created, paused, resumed, cancelled, closed** — All status changes * **Notes added** — Internal notes you add to the case Events are sorted newest-first, with color-coded dots for quick scanning. ## Best Practices > [accordion] Use pre-incasso for first-time late payers > > If a customer has a good payment history and is late for the first time, start with pre-incasso. A gentle nudge is usually enough. > [accordion] Pause before escalating to Stage 3 > > Before adding collection fees, pause the case and reach out to the customer directly. Many disputes and arrangements happen at this stage. > [accordion] Register all payments, even small ones > > Tracking every payment builds a clear record. If you ever need to involve a legal advisor, a complete payment history is invaluable. > [accordion] Use notes to document agreements > > When you agree to a payment arrangement or partial settlement, document it in the case notes. This protects both you and the customer. > [accordion] Consider remission for uncollectable amounts > > If recovery costs would exceed the remaining balance, it's often more practical to waive the amount and close the case. Focus your energy on cases with better recovery potential. ## FAQs > [accordion] Can I register a payment on a paused case? > > Yes. You can register payments on both active and paused cases. If the registered amount covers the full balance, the case is automatically marked as paid regardless of its current status. > [accordion] What happens to the payment plan when I pause a case? > > The payment plan continues independently — pausing the case only stops automated escalation. If you need to pause the plan too, cancel it separately. > [accordion] Can customers still pay when a case is paused? > > Yes. The payment link remains active and the **Pay Now** button is visible in the customer portal. Pausing only affects automated processing, not the customer's ability to pay. > [accordion] Is the waived amount shown to the customer? > > The customer sees the case as paid. The internal payment history (visible only to you) shows the breakdown of actual payments versus waived amounts. > [accordion] Can I skip pre-incasso and start at Stage 1? > > Yes. Pre-incasso is optional. When creating a case, simply leave the **Pre-Incasso** toggle off. The case will start at Stage 1 (Friendly Reminder) as before. ## Related Documentation > [card] [Creating Cases](/debt-collection/creating-cases) > > How to open a new collection case with or without pre-incasso > [card] [Escalation Pipeline](/debt-collection/escalation-pipeline) > > Understand the full 5-stage escalation process > [card] [Payment Plans](/debt-collection/payment-plans) > > Set up installment plans for structured repayment > [card] [Debt Collection Overview](/debt-collection/overview) > > Back to the overview # Debt Collection Source: https://docs.payreque.st/debt-collection/overview Recover unpaid invoices with automated collection workflows, escalation stages, and payment plans # Debt Collection Stop chasing unpaid invoices manually. PayRequest's Debt Collection feature gives you a professional, structured approach to recovering overdue payments — from friendly reminders all the way to formal notices and postal letters. > [!NOTE] > > Debt Collection works alongside your existing invoicing system. When an invoice goes unpaid past its due date, you can open a collection case to start the recovery process. ## Key Features * **5-Stage Escalation Pipeline** — Start with a soft pre-collection reminder, then progress through four formal stages * **Pre-Incasso (Stage 0)** — Free, informal reminder before starting formal collection * **Automated Escalation** — Cases automatically progress through stages based on your schedule * **Pause & Resume** — Temporarily suspend a case while negotiating, then pick up where you left off * **Partial Payments** — Register payments received via bank transfer, cash, or other channels * **Waive Balance (Kwijtschelding)** — Write off the remaining balance when you've agreed on a settlement * **Collection Fees** — Add collection fees at later stages to cover recovery costs * **Payment Plans** — Let customers pay in installments when they can't pay the full amount at once * **Postal Letters** — Send physical collection letters via Pingen for formal notices * **Customer Portal** — Customers can view their case, pay directly, or request a payment plan * **External Debts** — Create collection cases for debts not tied to existing invoices * **Activity Timeline** — Unified audit trail of every action, email, letter, payment, and status change ## When to Use Debt Collection Debt Collection is designed for invoices that remain unpaid after your regular payment reminders haven't worked. **Typical workflow:** 1. Invoice is sent to customer 2. Payment reminders are sent automatically (3 days before, 7 days after due date) 3. Customer still hasn't paid after 14+ days 4. **Open a collection case** to start formal recovery > [!TIP] > > Don't start collection too early. Give customers at least 14 days past the due date before opening a case. Most late payments are resolved with regular reminders. ## How It Works ### 1. Create a Case Open a collection case from an overdue invoice or create one for an external debt. The case tracks everything: the original amount, any collection fees, payment attempts, and communication history. ### 2. Escalate Through Stages Each case can progress through up to five stages, each with increasingly urgent communication: | Stage | Name | Tone | | - | - | - | | 0 | Pre-Collection (optional) | Gentle, informal reminder | | 1 | Friendly Reminder | Polite, assumes oversight | | 2 | Formal Notice | Professional, sets deadline | | 3 | Collection Fees | Firm, fees added to balance | | 4 | Final Warning | Urgent, last chance before further action | ### 3. Communicate with Customers At each stage, you can send email reminders or physical postal letters. Customers also see their case in the Customer Portal where they can pay directly or request a payment plan. ### 4. Track Payments Register partial payments received via bank transfer or cash. The amount breakdown updates in real-time, and when the full balance is covered, the case closes automatically. You can also waive the remaining balance for settlements. ### 5. Resolve the Case Cases are resolved when the customer pays the full amount (including any collection fees), when you waive the remaining balance, or when all payment plan installments are completed. ## Dashboard Overview Your Debt Collection dashboard shows all active cases at a glance: * **Case number** and linked invoice * **Customer name** and contact details * **Current stage** with visual progress indicator * **Total amount due** (original + collection fees) and remaining balance * **Days overdue** count * **Quick actions** — send reminder, escalate, pause, view details ## What Customers See When you open a collection case, your customer can view it in the Customer Portal: * A clear warning banner explaining the situation * Case details (case number, invoice, due date, days overdue) * Amount breakdown (original amount + any collection fees) * Stage progress indicator * **Pay Now** button to settle immediately * Option to **request a payment plan** (if you've enabled this) > [!WARNING] > > Collection cases are visible to customers in their portal. Make sure you're ready to proceed before creating a case. ## Getting Started > [card] [Creating Cases](/debt-collection/creating-cases) > > Learn how to create collection cases from invoices or external debts > [card] [Escalation Pipeline](/debt-collection/escalation-pipeline) > > Understand the 5-stage escalation process and automation > [card] [Payment Plans](/debt-collection/payment-plans) > > Set up installment plans for customers who can't pay at once > [card] [Managing Cases](/debt-collection/managing-cases) > > Pause, resume, register payments, and waive balances > [card] [Postal Letters](/debt-collection/postal-letters) > > Send physical collection letters via Pingen ## FAQs > [accordion] Can I use Debt Collection without Pingen (postal letters)? > > Yes. Postal letters are optional. You can run the full collection pipeline using only email communication and the customer portal. > [accordion] Does the customer get notified when I create a case? > > Creating a case does not automatically notify the customer. You choose when to send the first reminder — either by email or postal letter. > [accordion] Can I add collection fees? > > Yes. At Stage 3 (Collection Fees) and Stage 4 (Final Warning), you can add a fee to the outstanding balance. The fee is shown separately in the customer portal and on payment pages. > [accordion] What happens when the customer pays? > > When the linked invoice is paid (including any collection fees), the case is automatically marked as paid and closed. You can also register manual payments for bank transfers or cash received outside PayRequest. > [accordion] Can I close a case without full payment? > > Yes. You can close a case manually, waive the remaining balance (kwijtschelding), or cancel the case from the detail page. > [accordion] Can I pause a case? > > Yes. Pausing suspends automated escalation while keeping the payment link active. This is useful when negotiating with the customer. Resume the case at any time to continue the collection process. ## Related Documentation * [Payment Reminders](/invoices/payment-reminders) — Automated invoice reminders (before collection) * [Failed Payment Handling](/subscriptions/failed-payment-handling) — Automatic retry for failed subscription payments * [Handling Chargebacks](/payment-processing/handling-chargebacks) — Managing SEPA chargebacks * [Customer Portal](/customer-management/customer-portal) — What your customers see # Payment Plans Source: https://docs.payreque.st/debt-collection/payment-plans Let customers pay outstanding debts in monthly installments with structured payment plans # Payment Plans Sometimes customers want to pay but can't afford the full amount at once. Payment plans let you split the outstanding debt into monthly installments, making it easier for customers to settle their balance while ensuring you get paid. > [!NOTE] > > Payment plans use PayRequest's built-in subscription system. Each installment is billed automatically — no manual follow-up needed. ## How Payment Plans Work 1. A collection case exists with an outstanding amount 2. You create a payment plan (or the customer requests one) 3. The total amount is divided into equal monthly installments 4. PayRequest creates a subscription that bills the customer each month 5. When all installments are paid, the collection case is automatically closed ## Creating a Payment Plan ### From the Dashboard ### Open the Collection Case Navigate to **Debt Collection** and click on the case you want to set up a plan for. ### Find the Payment Plan Section In the case detail view, scroll to the **Payment Plan** section. ### Choose the Number of Installments Select how many monthly installments the customer should pay. Available options: | Installments | Example (EUR 600 debt) | | - | - | | **2 months** | EUR 300.00/month | | **3 months** | EUR 200.00/month | | **6 months** | EUR 100.00/month | | **12 months** | EUR 50.00/month | The monthly amount is calculated automatically based on the total amount due (including any collection fees). ### Create the Plan Click **Create Plan**. PayRequest will: * Create a monthly subscription for the installment amount * Link it to the collection case * Set the status to **Pending Mandate** (waiting for the customer to authorize payments) > [!NOTE] > > The customer needs to set up a payment mandate (SEPA Direct Debit authorization) before installments can begin. They'll receive instructions to do this. ### Customer-Initiated Requests You can also let customers request a payment plan themselves from the Customer Portal. #### Enabling Customer Requests 1. Open the collection case detail page 2. Go to **Case Settings** 3. Toggle **Allow installment requests** on When enabled, the customer sees a **Request Installments** button on their collection case page. #### What Customers See Customers can: 1. Click **Request Installments** 2. Choose their preferred number of installments (2, 3, 6, or 12) 3. See the monthly payment amount for each option 4. Review a summary (total amount, monthly payment, duration) 5. Submit the request > [!TIP] > > Customer requests don't create the plan automatically. You receive a notification and can review the request before setting up the actual plan. This gives you full control over the terms. #### Reviewing Customer Requests When a customer submits a payment plan request: * A note is added to the case's internal notes with the requested terms * An activity log entry is created * You can then create the plan from the dashboard (or contact the customer to discuss) ## Tracking Payment Progress Once a payment plan is active, you can track its progress: ### Dashboard View On the case detail page, the Payment Plan section shows: * **Progress bar** — Visual indicator of completion (e.g., 2 of 6 installments paid) * **Amount per installment** — How much is charged each month * **Interval** — Monthly billing cycle * **Next payment date** — When the next installment will be charged * **Subscription status** — Active, Pending Mandate, or Completed ### Customer Portal View Customers see the same information in their portal: * Progress bar with installment count * Monthly payment amount * Next payment date * Overall plan status ## Payment Plan Lifecycle ``` Plan Created → Pending Mandate → Active → Completed → Case Closed ``` | Status | What It Means | | - | - | | **Pending Mandate** | Waiting for customer to authorize SEPA payments | | **Active** | Installments are being charged automatically | | **Completed** | All installments paid — case automatically closed | | **Cancelled** | Plan was cancelled before completion | ## Automatic Case Closure When the final installment is paid: 1. The subscription is marked as **Completed** 2. The collection case is automatically marked as **Paid** 3. No manual action needed — everything happens automatically > [!NOTE] > > This only works when the payment plan covers the full outstanding amount. If there's a remaining balance (due to rounding), you may need to manually close the case. ## Cancelling a Payment Plan If you need to cancel an active payment plan: 1. Open the collection case 2. Find the Payment Plan section 3. Click **Cancel Plan** This cancels the subscription but keeps the collection case open. You can then: * Create a new plan with different terms * Continue with regular collection stages * Negotiate a different arrangement with the customer ## Best Practices > [accordion] Offer payment plans proactively > > Don't wait for the customer to ask. At Stage 2 or 3, consider proactively suggesting a payment plan. This shows flexibility and often leads to faster recovery. > [accordion] Keep installments manageable > > Choose a number of installments that balances your cash flow needs with the customer's ability to pay. A plan the customer can't afford will just lead to more failed payments. > [accordion] Enable customer requests for large debts > > For larger amounts, enabling the "Allow installment requests" toggle lets customers take the initiative. This reduces back-and-forth communication. > [accordion] Monitor payment plan progress weekly > > Check the status of active payment plans regularly. If an installment fails, you'll want to follow up quickly before the customer falls further behind. ## FAQs > [accordion] Can I change the number of installments after creating a plan? > > Not directly. Cancel the current plan and create a new one with different terms. > [accordion] What happens if an installment payment fails? > > The standard subscription retry logic applies. PayRequest will automatically retry the payment after 3 days, then again after 10 days. > [accordion] Do collection fees get included in the payment plan? > > Yes. The payment plan covers the total amount due, which includes the original invoice amount plus any collection fees. > [accordion] Can I create a payment plan for an external debt? > > Yes. External debts work exactly the same as invoice-based cases. An invoice is automatically created for the external debt, and the payment plan is linked to that invoice. > [accordion] What if the customer wants to pay off the remaining balance early? > > The customer can always pay the full remaining amount through the payment page or customer portal. The case will close automatically when the invoice is fully paid. ## Related Documentation > [card] [Escalation Pipeline](/debt-collection/escalation-pipeline) > > Understand the 4 stages of collection > [card] [Customer Portal](/customer-management/customer-portal) > > What customers see in their self-service portal > [card] [Managing Mandates](/subscriptions/managing-mandates) > > How SEPA mandates work for recurring payments > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > How failed installment payments are retried # Postal Letters Source: https://docs.payreque.st/debt-collection/postal-letters Send physical collection letters to customers via Pingen postal service # Postal Letters For formal collection notices, a physical letter carries more weight than an email. PayRequest integrates with [Pingen](https://www.pingen.com) to send professional postal letters directly from your dashboard — printed, enveloped, and mailed automatically. > [!NOTE] > > Postal letters are optional. You can use the full debt collection pipeline with email-only communication. Pingen integration adds the ability to send physical letters when needed. ## Why Send Postal Letters? * **Higher impact** — Physical letters are taken more seriously than emails * **Proof of delivery** — Track when letters are delivered * **Legal standing** — Physical notices may carry more legal weight in some jurisdictions * **Unreachable customers** — Reach customers who don't respond to emails * **Professional appearance** — Formal business letterhead with your company details ## Setting Up Pingen Before you can send postal letters, you need to connect your Pingen account. ### Create a Pingen Account Sign up at [pingen.com](https://www.pingen.com) and create an organisation. ### Get Your API Credentials In your Pingen dashboard: 1. Go to **Settings** → **API** 2. Note your **Client ID** and **Client Secret** 3. Note your **Organisation ID** from the account settings ### Configure PayRequest Contact PayRequest support or add the Pingen credentials in your environment configuration. You'll need: | Setting | Description | | - | - | | **Client ID** | Your Pingen API client ID | | **Client Secret** | Your Pingen API client secret | | **Organisation ID** | Your Pingen organisation ID | ### Top Up Your Pingen Balance Pingen charges per letter sent (typically EUR 1-2 per letter within the Netherlands). Make sure your Pingen account has sufficient balance. ## Sending a Postal Letter Once Pingen is configured, you can send letters from any collection case. ### Open the Collection Case Navigate to **Debt Collection** and click on the case. ### Click "Send Postal Letter" Find the **Send Postal Letter** button in the case header (next to "Send Reminder"). ### Review and Confirm The system generates a professional A4 letter including: * Your business details (company name, address, VAT number, IBAN) * Customer's name and address * Stage-appropriate content matching the current collection stage * Amount breakdown (original amount + collection fees = total) * Payment link and case reference number * QR code for quick mobile payment ### Letter Is Sent PayRequest uploads the letter to Pingen, which handles printing, enveloping, and mailing. The letter is typically delivered within 1-3 business days (within the Netherlands). ## Letter Content Each letter is automatically tailored to the current collection stage: ### Stage 1: Friendly Reminder * Polite tone, assumes the customer may have overlooked the invoice * Mentions the invoice number and original due date * Requests payment at the customer's earliest convenience ### Stage 2: Formal Notice * More formal tone with a clear payment deadline * States that this is a formal notice * Requests payment within 7 days ### Stage 3: Collection Fees Added * Direct tone informing the customer that collection fees have been applied * Shows the breakdown: original amount + collection fee * Requests immediate payment of the total amount ### Stage 4: Final Warning * Urgent tone making clear this is the last notice * Warns of potential further consequences * Demands immediate payment ## Letter Format Every letter follows a professional Dutch business letter format: * **A4 paper** with proper margins * **Sender block** — Your company name, address, VAT number, and IBAN * **Recipient address** — Positioned for standard window envelopes * **Date and reference** — Case number and current date * **Body** — Stage-appropriate content in the case's configured language * **Amount table** — Clear breakdown of what's owed * **QR code** — Scannable payment link for quick mobile payment * **Signature** — "With kind regards" followed by your company name > [!TIP] > > The letter language follows the language you've set for each individual case. Set this in the Case Settings on the case detail page. ## Tracking Letters After sending a letter, you can track its status: * **Pending** — Letter is being processed by Pingen * **Sent** — Letter has been printed and mailed * **Delivered** — Letter has been delivered (when tracking is available) Letter history is shown in the case's overview section, including: * Date sent * Current status * Delivery confirmation (when available) ## Automatic Postal Letters When Pingen is configured, the automatic escalation process can send postal letters automatically: | Stage | Email | Postal Letter | | - | - | - | | Stage 1 (Friendly Reminder) | Sent automatically | Not sent (email only) | | Stage 2 (Formal Notice) | Sent automatically | **Sent automatically** | | Stage 3 (Collection Fees) | Sent automatically | **Sent automatically** | | Stage 4 (Final Warning) | Sent automatically | **Sent automatically** | > [!NOTE] > > Automatic postal letters only happen during automated escalation. If you manually escalate a case, you choose whether to send a letter. ## Costs Pingen charges per letter. Typical costs (Netherlands): * **Standard letter** — approximately EUR 1.00 - 2.00 * **Registered letter** — higher cost, includes delivery confirmation * **International** — varies by destination country Costs are charged to your Pingen account, not through PayRequest. Check [pingen.com](https://www.pingen.com/pricing) for current pricing. ## FAQs > [accordion] Do I need Pingen to use Debt Collection? > > No. Pingen is optional. You can use the full collection pipeline with email-only communication. > [accordion] Can I preview the letter before sending? > > The letter is generated as a PDF using your business details and the case information. You can download a preview from the case detail page before confirming the send. > [accordion] What if the customer's address is wrong? > > Make sure your customer records have accurate addresses before sending postal letters. Letters sent to incorrect addresses will still be charged by Pingen. > [accordion] Can I send letters internationally? > > Yes. Pingen supports international mail. The cost varies by destination country. > [accordion] How long does delivery take? > > Within the Netherlands, letters are typically delivered within 1-3 business days. International delivery may take longer depending on the destination. ## Related Documentation > [card] [Escalation Pipeline](/debt-collection/escalation-pipeline) > > How automatic escalation triggers postal letters > [card] [Creating Cases](/debt-collection/creating-cases) > > How to create collection cases > [card] [Debt Collection Overview](/debt-collection/overview) > > Back to the overview > [card] [Business Details](/business-settings/business-details) > > Make sure your company details are up to date for letters # Freelancer Page Source: https://docs.payreque.st/freelancers/freelancer-page Create a public freelancer profile, get discovered, accept quote requests, and sell prepaid hours without creating a product yourself # Freelancer Page Turn your PayRequest Page into a simple freelancer profile where clients can understand what you do, request a quote, or hire you for a prepaid block of time. Your public URL stays short and easy to share: ```text theme={null} https://payrequest.me/your-handle ``` > [card] Show Your Expertise > > Add your profession, location, skills, languages, hourly rate, and availability. > [card] Request a Quote > > Let a potential client describe custom work without leaving your profile. > [card] Hire Me > > Let clients select a number of hours and pay immediately. ## Set Up Your Freelancer Profile **1. Open your PayRequest Page** In the PayRequest dashboard, go to **PayRequest Page** and open the **Settings** tab. **2. Enable the Showcase** Find the **Showcase** section and turn on **List me on the Showcase**. **3. Choose a category** Select the category that best represents your work. This helps visitors find relevant profiles and services. **4. Complete your professional details** Add your profession, location, skills, languages, hourly rate, and current availability. **5. Choose how clients can contact or hire you** Enable **Accept quote requests**, **Hire me**, or both, then click **Save Settings**. ## Profile Details The freelancer fields make your page easier to understand and easier to find on the public directory at [payrequest.me/discover](https://payrequest.me/discover). | Field | What to enter | Example | | - | - | - | | **Profession** | A clear role or specialty | Portrait artist | | **Location** | City, region, or remote | Amsterdam, Netherlands | | **Skills** | Comma-separated services and techniques | Illustration, pencil drawing, portraits | | **Languages** | Languages you can work in | English, Dutch | | **Hourly rate** | Your public price for one hour | €45.00 | | **Availability** | Available, limited, or unavailable | Available for work | Your availability is also shown as a colored status badge on your avatar. Visitors can hover over the avatar to quickly see your professional details. > [!TIP] > > Use specific skills that clients would search for. “A4 pencil portrait from a photo” is more useful than “art.” ## Get Discovered When **List me on the Showcase** is enabled, your page can appear in the public PayRequest directory. Visitors can search and filter freelancers by details such as category, skills, hourly rate, and availability. Keep these details current: * Set your availability to **Available for work** when you can accept new projects * Use a recognizable profile photo or logo * Add a banner that shows your style, portfolio, or best work * Write a short tagline that says what you deliver and for whom * Add focused skills instead of a long list of unrelated terms See [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) to customize your avatar, profile banner, tagline, description, colors, and social links. ## Accept Quote Requests Enable **Accept quote requests** when the price depends on the client's requirements. The **Request a quote** button opens a form directly on your public profile. The visitor enters their name, email address, request, and project details without being sent to a separate directory page. After submission, they return to your profile and see a confirmation. PayRequest creates a customer and an open quote request for your business, then sends you a notification. You can review the request, discuss the scope, and prepare the final quote. Use quote requests for work such as: * A custom website or software integration * An illustration with several people or complex usage rights * Consulting where the required research is not yet clear * A photo-based portrait with custom size, materials, framing, or delivery > [!NOTE] > > A quote request does not charge the client. It starts a conversation so you can agree on scope and price first. ## Enable Hire Me Use **Hire me** when you are comfortable selling your time at a clear hourly rate. 1. Enter your **Hourly rate** 2. Turn on **Enable Hire me** 3. Set the minimum and maximum number of hours a client can buy 4. Save your settings On your public profile, the client clicks **Hire me**, chooses the number of hours, describes the work, and continues directly to payment. The total is calculated from your hourly rate and the selected number of hours. > [!TIP] > > You do not need to create or choose a product. PayRequest automatically manages the internal checkout product behind the Hire me button and keeps it out of your normal product list. The purchase is a prepaid block of time. Contact the client after payment to confirm the scope, schedule, and expected outcome. If the work requires more time, the client can purchase another block or request a quote. ## Quote, Hire Me, or Commission? Choose the simplest option that fits the work: | Option | Best when | When the client pays | | - | - | - | | **Request a quote** | Scope and final price are unknown | After you agree and send a quote | | **Hire me** | You sell time at a known hourly rate | Immediately for selected prepaid hours | | **Commission product** | You sell a repeatable creative offer with a starting price | At checkout for the starting price | For example, an **A4 pencil drawing based on one supplied photo** can be a [Commission](/products-and-pricing/commissions) if the offer is repeatable and has a predictable starting price. Use a quote request when the number of people, background, dimensions, rights, materials, or delivery requirements can change the price substantially. ## Recommended Simple Setup For most freelancers, start with: 1. A complete profile with a clear profession, skills, and availability 2. **Accept quote requests** enabled for custom work 3. **Hire me** enabled only if you have a confident hourly rate 4. One or two commission products only for services you can describe and price consistently This gives clients a fast next step without requiring you to build a large product catalog first. ## Related Topics > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize your profile photo, banner, bio, colors, and social links. > [card] [Commissions](/products-and-pricing/commissions) > > Sell repeatable custom creative work with a starting price. > [card] [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) > > Connect a provider before accepting prepaid work. > [card] [Creating Invoices](/invoices/creating-invoices) > > Invoice additional work or an agreed custom amount. # Spotify Now Playing Source: https://docs.payreque.st/freelancers/spotify-now-playing Show the song you are currently listening to in your freelancer profile popover # Spotify Now Playing Add a little personality to your Freelancer Page by showing the track you are currently playing on Spotify. Visitors can see the song and artist in your profile popover and open the track directly in Spotify. > [!NOTE] > > Spotify Now Playing is currently available as a limited beta. The connection option only appears for PayRequest accounts that have been enabled for the beta. ## What Visitors See When you are actively playing music, your profile popover shows: * The Spotify icon * **Now listening on Spotify** * The track title * The artist name * A link that opens the track on Spotify The music itself is not embedded or played through PayRequest. PayRequest only displays the current track information and links visitors back to Spotify. When playback is paused or Spotify cannot provide a current track, the entire Spotify section is hidden. Your profile therefore never shows an empty player or an outdated “now playing” status. ## Connect Spotify **1. Open your PayRequest Page settings** In the PayRequest dashboard, go to **PayRequest Page**, open **Settings**, and scroll to **Showcase**. **2. Open your Freelancer profile settings** Enable **List me on the Showcase** if needed. The Spotify option appears with your other freelancer profile settings when your account has beta access. **3. Connect your account** Click **Connect Spotify**. Spotify opens its authorization screen so you can sign in and approve read-only access to your currently playing track. **4. Start listening** Play a track in Spotify, then open your public PayRequest Page and click or hover over your profile photo to see the result. > [!TIP] > > Spotify information is cached briefly. After changing tracks, allow up to 30 seconds for your public profile to update. ## Privacy and Permissions PayRequest requests only the Spotify permission needed to read what is currently playing. The connection does not let PayRequest: * Start, pause, or skip your music * Change your playlists or saved songs * Post anything to Spotify * Play Spotify audio on your PayRequest Page Your Spotify tokens are stored encrypted. Visitors only receive the public track title, artist, and Spotify link while playback is active. ## Disconnect Spotify To remove the integration: 1. Go to **PayRequest Page → Settings → Showcase** 2. Find **Spotify — Listen now** 3. Click **Disconnect** The Spotify section disappears from your public profile immediately. You can reconnect later by completing the Spotify authorization flow again. ## Troubleshooting > [accordion] The Spotify section is not visible > > Make sure a track is actively playing and is not paused. The section is intentionally hidden when no current playback is available. > [accordion] I changed tracks but still see the previous song > > Wait up to 30 seconds and reopen the profile popover. PayRequest briefly caches Spotify responses to keep public pages fast and respect API limits. > [accordion] The Connect Spotify button is missing > > Spotify Now Playing is in limited beta. Contact [PayRequest support](mailto:support@payrequest.io) to ask whether your account can be enabled. > [accordion] Spotify asks me to authorize again > > Spotify connections can expire or be revoked. Return to your Freelancer Page settings and reconnect your Spotify account. ## Related Topics > [card] [Freelancer Page](/freelancers/freelancer-page) > > Create your public profile, show your expertise, and let clients hire you. > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize your profile photo, banner, colors, and social links. # Initial setup checklist Source: https://docs.payreque.st/getting-started/initial-setup-checklist Check what you need for a first payment and leave optional branding and automation for later. Start with the essentials for the payment flow you want to use. You do not need to complete every optional feature to receive your first payment. ## Essential account setup * [ ] Verify your account email and save the onboarding intake. * [ ] Describe what customers are paying for and choose your first goal. * [ ] Confirm the actual legal country of your payment account when connecting a provider. * [ ] Connect a provider offered for your account and complete its receiving approval or verification. Check that PayRequest shows a payment-ready setup. * [ ] Complete business details when requested. Review the name, address, currency and applicable tax settings before issuing documents. * [ ] Create your Page when prompted and choose an available handle. * [ ] Complete checkout if you selected a paid plan and need its features. A provider request or plan selection alone does not activate payments. Missing a provider or stuck during authorization? Follow the [onboarding help](https://docs.payreque.st/getting-started/onboarding#payment-connection-not-complete). Do not collect API keys or identity documents just to follow this checklist; provider verification takes place through the provider's own process. ## Choose one first payment flow | Flow | Check before sharing | | - | - | | Amount-based link | Agreed amount, currency, description and available payment methods. No product or API integration is required. | | Digital product | Correct file and price, relevant tax settings, and delivery configuration. For a PDF, use the [quick PDF flow](https://docs.payreque.st/products-and-pricing/digital-products#quick-route-for-a-workbook-or-pdf). | | Invoice | Correct customer, invoice details, dates, items and payment instructions. | | Subscription | Recurring product, billing terms and a compatible payment method; automatic collection may require a customer mandate or additional provider approval. | * [ ] Review the customer-facing link or document before sharing it. * [ ] Confirm the recorded payment status when the customer pays. Opening a link or returning from checkout does not alone establish settlement. You do not have to make a real payment to tick off account setup. For testing, first confirm that the relevant flow genuinely supports a sandbox; do not treat a live checkout as test mode. ## Optional improvements for later * [ ] Add a recognizable photo or logo, Page description and optional cover image. * [ ] Add website and social links when useful. * [ ] Customize invoice branding and customer communications. * [ ] Add more products, payment methods or compatible provider connections. * [ ] Configure a custom domain if you need one. * [ ] Review recurring billing, reminder and cancellation policies for your business. * [ ] Set up API access and webhooks if your website or software needs automation; check the plan requirements first. ## Where to continue * [Quick start](https://docs.payreque.st/getting-started/quick-start-guide): the shortest route to sharing a link. * [Onboarding](https://docs.payreque.st/getting-started/onboarding): saved choices, provider requests and setup help. * [Payment providers](https://docs.payreque.st/payment-processing/setting-up-payment-providers): receiving permissions and existing connections. For help, use **I'm stuck** in onboarding or reply to your welcome email. Tell us the step you reached without sending passwords, verification codes or API credentials. # PayRequest for iOS Source: https://docs.payreque.st/getting-started/ios-app Manage products, orders, payments and your storefront from the PayRequest iOS app. The PayRequest iOS app is a companion for merchants. Use it to check business activity, manage products and orders, and respond to new sales while you are away from your desk. The app uses your PayRequest account and its existing permissions. It does not replace your payment provider setup or the web dashboard. ## Sign in Sign in with the PayRequest account you use for your business. The app uses PayRequest's secure sign-in flow; you do not need to create or paste an API key into the app. Your account permissions still apply. If you cannot access a feature in the dashboard, signing in to the app does not grant that access. ## Explore the app The tab bar gives you quick access to the main areas of your business: | Area | What you can do | | - | - | | **Home** | Review sales activity, revenue and recurring-revenue summaries, plus recent and upcoming business activity. | | **Sell** | Create products and payment links, then review product sales. Product sharing includes the iOS share sheet and a direct WhatsApp option when available. | | **Store** | Preview your public storefront, open or share its URL, show its QR code, review available performance data and access storefront customization. | | **Payments** | Review payments by status, open payment details and view the related invoice when one is available. | | **Manage** | Find and manage orders, customers, invoices, subscriptions, support requests and account settings. | The exact actions shown can depend on your account and the data available for it. ## Create and share a payment link In **Sell**, start a payment link and enter its amount and currency. Add the available details, review the link, and share it with your customer. If you need options that are not available in the app, continue in the PayRequest web dashboard. For a product, open its details to review sales information and share it through the system share sheet. You can choose WhatsApp or another installed sharing app, or copy the link where that action is available. ## Review payments and orders Use **Payments** to switch between the available payment statuses, such as paid, pending, refunded and failed. Open a payment to see its key details and follow its invoice link when present. Invoice documents open through PayRequest's authenticated web experience. In **Manage**, open an order to review its key information, customer and status. Customer views can include related order and payment history, subject to your access permissions. ## Storefront and performance The **Store** tab brings your public storefront actions together. Open the storefront, share its URL, display its QR code, or go to its existing customization tools. Performance figures are based on data available to your account. Some metrics or comparisons may not appear when reliable storefront tracking data is unavailable. Storefront analytics do not imply that unrelated payment-link activity is attributed to the store. ## Notifications When notifications are enabled for the app and your device, PayRequest can notify you about new orders and payments. Tapping a notification opens the related item in the app when you are signed in and have access to it. You can manage notification permissions in iOS **Settings**. Notification delivery depends on device permissions and network connectivity. ## When to use the web dashboard Use the web dashboard for workflows and advanced settings that are not available in the app. The app is a mobile way to monitor and handle common merchant tasks; customers still complete purchases through your PayRequest checkout page or payment link in a browser. The iOS app does not turn an iPhone into a Tap to Pay terminal. Accepting contactless in-person payments requires a supported payment product and setup; see [Stripe Tap to Pay documentation](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay.md?platform=ios) for Stripe's requirements and availability. # Set up your account and accept your first payment Source: https://docs.payreque.st/getting-started/onboarding Connect your payment provider, resolve setup problems and take the next step for your business. PayRequest helps you create payment links, sell files, send invoices and manage subscriptions. Your payment provider processes the payment; creating a PayRequest account does not create an approved payment-provider account. > [!TIP] > > Already started? [Return to onboarding](https://payrequest.app/onboarding). Your saved answers and payment-provider choice are remembered. ## One setup flow New accounts follow the standard onboarding flow: describe your goal, prepare payments, explicitly personalize your PayRequest Page and add a product when relevant. Older alternate onboarding URLs return to this flow. Saved answers and provider choices are retained. ## Start with your goal Tell us what you sell and what you want to automate. Describe your needs in at least three words and explain how you handle payments today. Your saved intake helps suggest a relevant next step; it does not connect a provider or activate a paid feature. * **Sharing payment links yourself?** You do not need an API integration. * **Connecting your website or software?** Describe what it should do automatically. API access requires an active Business plan. * **No payment provider yet?** Select that option. Each provider makes its own eligibility and approval decisions. Confirm your business details and choose the plan that fits your needs. Selecting a paid plan or opening checkout does not activate it. Your reported location does not confirm the legal country of your payment account. ## Connect your payment provider 1. Confirm the country where your business or payment account is legally registered using **Confirm account country**. A detected location is only a suggestion. 2. Choose an available provider. If you selected **Stripe, Mollie or PayPal** earlier, your saved choice appears first with a direct **Connect** button. 3. Sign in with that provider, authorize the connection and complete any verification it requires. 4. Return to PayRequest and use **Check Status**. Continue when your payment setup is ready. | Provider | What you need | | - | - | | Stripe | An eligible Stripe account approved to accept payments. A Paystack account is a separate service and cannot be used as a Stripe connection. | | Mollie | An eligible business account that can receive payments. Mollie may still need business verification after you authorize PayRequest. | | PayPal | A PayPal Business account approved to receive payments. Being able to send money does not confirm that you can receive customer payments. | The options shown depend on your confirmed account country and provider availability. Changing the country requires confirmation again. [More about payment providers](https://docs.payreque.st/payment-processing/setting-up-payment-providers). > [!NOTE] > > A successful sign-in or return to PayRequest does not necessarily mean your payment account is approved. PayRequest checks payment readiness separately. ## Payment connection not complete Use the message in onboarding to find your next step: | What you see | What to do | | - | - | | No connection started | Choose a supported provider. If you do not have an account, complete the provider's registration and approval process. | | Setup opened, or you returned without a completed connection | Resume from the provider card, finish the provider's steps and return to PayRequest. | | Setup cancelled or attempt failed | Retry the connection. If it fails again, note the screen or error and ask for help. | | Account linked but not ready | Check outstanding verification and receiving permissions with your provider, then check the status again. | | Connection unavailable for the selected country | Check that the confirmed country is correct. Choose another available option or ask us to review your situation. | Click **I'm stuck** to open your email app with your account number, provider and connection status already included. Add a sentence explaining where you stopped, review the message and send it. Opening the button does not send an email automatically. If your email app does not open, email [info@payrequest.io](mailto:info@payrequest.io) with the same details. Do not send passwords, API keys, verification codes or identity documents. ## Request another payment provider In the payment-provider step, use **Missing your payment provider?** to request **Square, Paystack, Razorpay, Payfast or Payoneer**. Choose **My payment provider is not listed** for another provider. Explain why you need it and which payment methods your customers use. Relevant saved intake text may be filled in for you; review it before clicking **Submit Request**. Your request is saved for review, and an existing open request for the same provider is reused. > [!NOTE] > > A request does not connect an account, enable payments or guarantee an integration or release date. A provider appearing in the intake list records your preference or existing usage; it does not mean that PayRequest supports it. Buying a plan does not make an unsupported payment account eligible. Ask us about your options before upgrading solely to solve a provider limitation. ### If you cannot connect your own provider If **Apply for PayRequest MoR** is offered, you can submit your business and payment needs for individual review. Verification, agreements, available methods, fees and payouts depend on your situation and approval. Applying does not activate payments or finish onboarding. Do not include identity documents, bank details or API keys in the application. ## Finish the setup shown for your account Add business details when requested, review your currency and tax settings, and create your PayRequest Page. Check these details before sharing a link or sending an invoice. Your Page gives you a public address such as `payrequest.me/yourhandle`. Choose an available handle and add a recognizable name, description and photo or logo. You can personalize it further later. **A product is optional for an amount-based payment link.** If onboarding offers a first-product step, you can skip it and add products later. A skipped product step does not replace the payment-readiness requirement. ## Take the next step for your business Once your payment setup is ready, follow the action that matches your goal: | Your goal | Next step | | - | - | | Send a payment link yourself | [Create an amount link](https://payrequest.app/smart-links/create?type=amount), enter the agreed amount and description, then copy and share it. No API integration is needed. | | Sell a PDF, workbook or newspaper issue | Open [Sell PDF](https://payrequest.app/products/sell-pdf), upload your PDF and set the name, total price and included VAT. Get a payment link and website button, with private delivery after successful payment. | | Sell another downloadable file | Use [Upload](https://payrequest.app/upload) for a supported file. See [digital products](https://docs.payreque.st/products-and-pricing/digital-products) for delivery details. | | Send invoices | [Create your first invoice](https://payrequest.app/invoices/new) with a customer, items and payment link. See [creating invoices](https://docs.payreque.st/invoices/creating-invoices). | | Bill customers regularly | Set up a recurring product and its billing terms. See [creating subscriptions](https://docs.payreque.st/subscriptions/creating-subscriptions); automatic collection depends on the payment provider and an agreed payment method. | | Use security deposits | Read [security deposits](https://docs.payreque.st/payment-processing/security-deposits) before creating a request. A card authorization and a payment you later refund are different flows. | | Connect your website or software | Review your plan and [API access](https://docs.payreque.st/api/overview), then configure the integration. A provider listed in your intake is not an API connection. | Existing links and products remain available according to their status and your account access. You do not need to recreate them just because you return to onboarding. ## Get help after signup Your welcome email uses your saved goal and current setup to suggest a next step. You can reply directly for help. If you have already described your business, tell us where you stopped rather than repeating the whole explanation. For account, language or business-detail changes, use Settings. Manage your Page and products from their own screens. For a short list of setup tasks, see the [initial setup checklist](https://docs.payreque.st/getting-started/initial-setup-checklist). ### Setup reminders and unused accounts You may receive a setup message if your account is eligible. Accounts with verifiable, entirely unused history can enter automatic cleanup after at least 30 days without activity. An account that has ever connected a provider or created business data is excluded. If you receive a deletion warning, sign in within 24 hours or reply to the notice to stop automatic cleanup; you do not need to connect a provider to keep the account. ## Personalize your Page before finishing After payment setup, review and explicitly save your Page title and available handle. The handle becomes your public address, such as `payrequest.me/yourhandle`. Review the avatar step too; uploading a photo or logo is optional. An existing generated handle alone does not complete this step. Use your own recognizable title and review any description before sharing the Page. If an avatar upload fails, resolve it or continue without an image before saving again. Complete the remaining steps shown for your account. A first product is optional where a skip action is offered; skipping it does not bypass payment readiness. Accounts that already completed onboarding are not required to repeat it. # Use PayRequest AI Source: https://docs.payreque.st/getting-started/payrequest-ai Review payments, prepare payment links, customers and products, and contact support from PayRequest AI. PayRequest AI helps you find information and prepare common tasks in your business account. Open the **PayRequest AI** bubble in the dashboard, or use the [full AI page](https://payrequest.app/payrequest-ai). ## Choose the right action | Task | What happens | | - | - | | Ask about payments or revenue | AI displays information from your account's recorded payments. This is not a live bank balance or payout confirmation. | | Check upcoming renewals | Review the upcoming subscription records and dates shown. | | **Create payment link** | Review an editable amount-link preview, then explicitly create the link. | | **Create customer** | Review the customer draft and any matching existing customer before saving. | | **Create product** | Review the product definition, then save it or continue in the product wizard. | | **Create invoice** / **Create subscription** | Continue in the existing creation form and complete its normal checks. | | **Contact Support** | Describe your problem, optionally read suggested help and explicitly submit a support request. | The controls available to you depend on your permissions, plan and connected integrations. The AI creation menu does not bypass those requirements. ## Create a payment link **1. Describe the request** Choose **Create payment link**, or ask for a link with an amount, currency and description, for example “Create a EUR 75 payment link for a consultation.” **2. Review the preview** Check the name, amount and currency. Edit the fields if AI interpreted something incorrectly. **3. Confirm creation** Select **Create payment link**. A preview alone is not a saved request. After success, copy the resulting URL and share it through your chosen channel. Creating an amount link does not charge a card. A customer must still complete its checkout. For invoices, subscriptions or security deposits, use their specific creation flows rather than treating an amount link as interchangeable. ## Create a customer Choose **Create customer**, supply the requested details and inspect the preview. If a matching customer is shown, check that existing record before creating another one. Use the extended customer form when you need more details than the card offers. Confirming creates the customer through the existing customer flow, including applicable sync and internal notification settings. It does not send an invoice, payment request or reminder to that customer. ## Create a product 1. Choose **Create product** and select a type from the available catalog. 2. Check its name, description, price, currency and VAT. For recurring products, also review the interval and any setup fee. 3. Review the **status**. Products start as **Concept** unless you select **Active**. 4. For a supported simple type, select **Create product** to save. For an advanced type, choose **Continue in product wizard**, complete the additional fields and save there. Simple services, subscriptions, licenses, add-ons and custom services can be confirmed in chat. Advanced types such as digital delivery, bundles, bookings and authorization holds need the full wizard. Available types also depend on your integrations. > [!NOTE] > > Creating a subscription **product** defines what you sell. It does not itself create a customer's subscription, issue an invoice or collect money. ## Ask about payments Use a specific question or an available report action. Check the period, currency and linked records in the answer. Revenue totals in different currencies should be read separately; a payment total is not the amount your provider has paid out to your bank. If a customer's bank entry disagrees with the recorded status, open the relevant invoice, transaction or deposit and verify its provider reference. See [Investigate an unclear payment](/troubleshooting/payment-failures) and [Security deposits](/payment-processing/security-deposits). ## Contact PayRequest support Choose **Contact Support** and describe what happened, what you expected and the relevant record or error reference. You may see suggested documentation first. * If the guidance solves the issue, indicate that it helped; no ticket is sent. * If you still need help, continue to the form, review the subject and message, and explicitly submit it. * After confirmation, keep the ticket reference. PayRequest Support replies by email and in your support inbox. If submission is not confirmed, check the support inbox before retrying. You do not need to create a billing customer profile to contact PayRequest support. You can also email [support@payrequest.io](mailto:support@payrequest.io). This is support for **your PayRequest account**. Your customers should contact your business through their customer portal or your published contact details; share [Getting help as a customer](/customer-guide/getting-help). ## Check the result before repeating an action A suggestion, an editable preview and a saved result are different states. Review financial details before confirming. If an action times out or its result is unclear, inspect the resulting customer, product, payment link or support inbox before starting over. > [card] [Create products](/products-and-pricing/creating-products) > > Use the full wizard for advanced product settings. > [card] [Smart Links](/payment-processing/smart-links) > > Manage links after creating them. # Quick start: your first payment Source: https://docs.payreque.st/getting-started/quick-start-guide Finish onboarding, connect an eligible payment account and share your first payment link. The shortest route is **onboarding → payment-ready connection → one payment link**. You do not need a product catalog, a custom domain or an API integration to share an amount-based link. Provider registration and verification can take additional time. There is no guaranteed time to your first payment. ## 1. Start in onboarding [Open onboarding](https://payrequest.app/onboarding), rather than starting in dashboard settings. Tell us what you sell, what you want to automate, your current workflow and payment situation. Your answers are saved when submitted. Choose a plan and complete the steps offered for your account. Add business details when requested and review currency and tax settings. Follow a checkout prompt for a selected paid plan; selecting it alone does not activate paid features. ## 2. Connect your payment account Confirm the actual legal country of your payment account. Choose an available Stripe, Mollie or PayPal connection and authorize it on the provider's website. Your saved provider choice appears first. Return to PayRequest and check payment readiness. A successful sign-in does not necessarily mean verification is complete. If you stop here, use **I'm stuck** or the [connection troubleshooting guide](https://docs.payreque.st/getting-started/onboarding#payment-connection-not-complete). If your provider is absent, [request it for review](https://docs.payreque.st/getting-started/onboarding#request-another-payment-provider). A request does not enable payments or replace an approved receiving account. ## 3. Finish the setup shown Create your PayRequest Page when prompted and choose an available handle. Add enough information for a customer to recognize you. You can add a banner, more branding and a custom domain later. If a first-product step is offered, skip it when you only need an amount-based link. [Full onboarding guide](https://docs.payreque.st/getting-started/onboarding). ## 4. Create and share a link Once the account is payment-ready and setup is complete: 1. Open [Create an amount link](https://payrequest.app/smart-links/create?type=amount). 2. Enter the agreed amount and a clear description. Review the currency and available options, then create the link. 3. Open the link to review what the customer will see. Opening checkout is not a payment. 4. Copy and share the link with your customer. Check the recorded payment status after they pay; a return to a success page alone is not a substitute for payment confirmation. You do not need to send yourself a real payment to finish this guide. Do not assume a live checkout is a sandbox. ## Prefer another first action? | Goal | Guide | | - | - | | Sell a PDF or workbook | [Digital products: quick PDF route](https://docs.payreque.st/products-and-pricing/digital-products#quick-route-for-a-workbook-or-pdf) | | Invoice a customer | [Creating invoices](https://docs.payreque.st/invoices/creating-invoices) | | Bill customers regularly | [Creating subscriptions](https://docs.payreque.st/subscriptions/creating-subscriptions) | | Automate your website | [API overview](https://docs.payreque.st/api/overview) | Use the [initial setup checklist](https://docs.payreque.st/getting-started/initial-setup-checklist) to separate essential setup from optional improvements. For personal help, reply to your welcome email or contact [info@payrequest.io](mailto:info@payrequest.io). # Understanding Your Dashboard Source: https://docs.payreque.st/getting-started/understanding-your-dashboard Master the PayRequest dashboard interface and discover all the powerful features at your fingertips # Understanding Your Dashboard 📊 Your PayRequest dashboard is mission control for your entire billing operation. This comprehensive guide will help you navigate every section and understand how to leverage each feature for maximum efficiency. > [!NOTE] > > **Dashboard Access**: Your dashboard is available 24/7 at [payrequest.app](https://payrequest.app) > **Mobile Friendly**: Access all features from any device with responsive design ## 🎛️ Dashboard Overview When you log into PayRequest, you'll see a clean, organized interface designed for efficiency and clarity. ### Top Navigation Bar > [card] PayRequest Logo > > Click to return to the main dashboard from anywhere in the platform > [card] Search Bar > > Quickly find customers, orders, invoices, or products across your entire account > [card] Notifications > > Stay updated on new orders, payment failures, and important account activities > [card] Profile Menu > > Access account settings, team management, and logout options ### Main Navigation Sidebar The left sidebar provides access to all major sections of your PayRequest account: > [accordion] > > **📈 Dashboard Home** > > **Your Command Center** > > * Real-time revenue metrics > * Recent activity feed > * Key performance indicators > * Quick action buttons > * Upcoming payment alerts > > **What You'll See:** > > * Today's revenue and transaction count > * Monthly recurring revenue (MRR) trends > * Failed payment alerts requiring attention > * Recent customer signups and cancellations > > **🛍️ Products** > > **Product Management Hub** > > * Create and edit products/services > * Manage pricing and subscriptions > * Configure custom fields > * Set up trial periods and setup fees > * Share product links and QR codes > > **Key Features:** > > * Visual product cards with status indicators > * Quick edit and duplicate options > * Revenue tracking per product > * Customer purchase analytics > > **👥 Customers** > > **Customer Relationship Center** > > * Complete customer profiles > * Communication history > * Subscription management > * Payment method details > * Customer health scoring > > **What You Can Do:** > > * View customer lifetime value > * Track payment history and preferences > * Manage customer tags and segments > * Access customer portal login > * Handle support requests and notes > > **🔄 Subscriptions** > > **Subscription Control Panel** > > * Active subscription monitoring > * Billing cycle management > * Failed payment recovery > * Trial-to-paid conversions > * Subscription analytics > > **Management Tools:** > > * Pause/resume subscriptions > * Change billing frequencies > * Update pricing and quantities > * Handle cancellation requests > * View upcoming renewals > > **📄 Invoices** > > **Invoice Management System** > > * Generated invoice overview > * Payment status tracking > * Manual invoice creation > * Payment reminders > * Invoice customization > > **Key Capabilities:** > > * Send payment links to customers > * Track invoice views and downloads > * Manage partial payments > * Handle refunds and credits > * Export invoice data > > **🛒 Orders** > > **Order Processing Center** > > * One-time purchase tracking > * Order fulfillment status > * Customer order history > * Revenue attribution > * Order analytics > > **Order Management:** > > * View order details and line items > * Track payment processing status > * Manage order fulfillment > * Handle order modifications > * Generate order reports > > **🏪 Shop** > > **Storefront Management** > > * Shop customization tools > * Product catalog organization > * Custom domain configuration > * Shop analytics and performance > * Customer experience optimization > > **Shop Features:** > > * Visual shop builder > * Theme and branding options > * SEO optimization tools > * Mobile responsiveness preview > * Customer journey analytics > > **🏷️ Tags** > > **Organization and Automation** > > * Customer segmentation tags > * Automated tagging rules > * Tag-based reporting > * Marketing automation triggers > * Workflow optimization > > **Tag Management:** > > * Create custom tag categories > * Set up automatic tagging conditions > * View tag usage analytics > * Export tagged customer lists > * Bulk tag operations > > **📊 Insights** > > **Business Intelligence Dashboard** > > * Revenue analytics and trends > * Customer acquisition metrics > * Churn analysis and predictions > * Product performance data > * Financial reporting tools > > **Analytics Features:** > > * Interactive charts and graphs > * Custom date range filtering > * Cohort analysis tools > * Export capabilities > * Automated report scheduling > > **⚙️ Settings** > > **Configuration and Administration** > > * Business profile management > * Payment provider setup > * Email template customization > * Team member administration > * Security and compliance settings > > **Settings Sections:** > > * Business Details & Branding > * Payment Providers & Methods > * Email Templates & Automation > * Team Members & Permissions > * API Keys & Integrations ## 🎯 Dashboard Home Deep Dive Your dashboard home provides a comprehensive overview of your business performance: ### Key Metrics Cards > [card] 💰 Revenue Metrics > > **Today's Revenue**: Real-time daily earnings > **Monthly Recurring Revenue (MRR)**: Predictable income stream > **Growth Rate**: Month-over-month percentage change > **Average Revenue Per User (ARPU)**: Customer value metrics > [card] 📈 Activity Indicators > > **Active Subscriptions**: Currently billing customers > **New Signups**: Recent customer acquisitions > **Payment Success Rate**: Transaction reliability > **Churn Rate**: Customer retention metrics ### Recent Activity Feed Monitor your business pulse with real-time activity updates: * **New Orders**: Customer purchases and order values * **Payment Events**: Successful payments and failures * **Subscription Changes**: Activations, pauses, and cancellations * **Customer Actions**: Profile updates and portal usage * **System Notifications**: Important platform updates ### Quick Actions Access frequently used features directly from your dashboard: **1. Create New Product** Launch the product creation wizard with one click **2. Add Customer** Quickly add new customers to your database **3. Generate Invoice** Create manual invoices for one-off charges **4. View Failed Payments** Address payment issues requiring immediate attention ## 🔍 Search and Navigation ### Global Search The dashboard search bar is your gateway to finding anything quickly: **Search Capabilities:** * **Customers**: Find by name, email, or company * **Orders**: Search by order number or customer * **Invoices**: Locate by invoice number or amount * **Products**: Find by name or SKU * **Transactions**: Search by payment reference **Search Tips:** * Use partial matches for broader results * Combine multiple terms for specific searches * Use quotation marks for exact phrase matching * Filter results by type using dropdown options ### Breadcrumb Navigation Always know where you are with clear breadcrumb trails: * **Dashboard** → **Customers** → **Customer Profile** * **Dashboard** → **Products** → **Edit Product** * **Dashboard** → **Settings** → **Payment Providers** ## 📱 Mobile Experience Your PayRequest dashboard is fully optimized for mobile devices: ### Mobile Navigation * **Collapsible sidebar**: Swipe to reveal navigation menu * **Touch-friendly interface**: Large buttons and easy scrolling * **Responsive tables**: Horizontal scroll for detailed data * **Quick actions**: Floating action buttons for common tasks ### Mobile-First Features * **Push notifications**: Stay informed on mobile devices * **Offline viewing**: Access cached data without internet * **Quick payments**: Process payments on the go * **Customer lookup**: Instant access to customer information ## 🎨 Customization Options ### Dashboard Themes * **Light Mode**: Clean, bright interface for daytime use * **Dark Mode**: Easy-on-eyes design for extended sessions * **Auto Mode**: Switches based on system preferences ### Widget Customization * **Rearrange metrics**: Drag and drop dashboard cards * **Hide/show sections**: Customize your dashboard layout * **Set default views**: Configure your preferred starting page * **Custom date ranges**: Set default reporting periods ## 🔔 Notifications and Alerts Stay informed with intelligent notification system: ### Notification Types > [card] Business Alerts > > * Failed payment notifications > * Subscription cancellation alerts > * Revenue milestone achievements > * Security and compliance updates > [card] Customer Activity > > * New customer registrations > * Subscription upgrades/downgrades > * Customer support requests > * Payment method updates ### Notification Settings * **Email notifications**: Configure which events trigger emails * **In-app alerts**: Customize dashboard notification preferences * **Mobile push**: Enable mobile app notifications * **Slack integration**: Send alerts to team channels ## 🚀 Pro Tips for Dashboard Mastery > [accordion] > > **💡 Keyboard Shortcuts** > > **Global Shortcuts:** > > * `Ctrl/Cmd + K`: Open global search > * `Ctrl/Cmd + /`: View all keyboard shortcuts > * `G + D`: Go to Dashboard > * `G + C`: Go to Customers > * `G + P`: Go to Products > * `G + S`: Go to Settings > > **Navigation Shortcuts:** > > * `Tab`: Move between interactive elements > * `Enter`: Activate buttons and links > * `Esc`: Close modals and dropdowns > > **🎯 Workflow Optimization** > > **Daily Routine:** > > 1. Check dashboard metrics and alerts > 2. Review failed payments and take action > 3. Monitor new customer signups > 4. Process manual invoices if needed > 5. Check upcoming subscription renewals > > **Weekly Tasks:** > > 1. Analyze revenue trends and growth > 2. Review customer churn and retention > 3. Update product pricing if needed > 4. Clean up customer data and tags > 5. Review and optimize email templates > > **📊 Data Management** > > **Best Practices:** > > * Use tags consistently for customer segmentation > * Keep customer profiles updated with latest information > * Regularly review and clean up duplicate customers > * Monitor payment method expirations > * Export data regularly for backup purposes > > **Reporting Tips:** > > * Set up automated reports for key metrics > * Use custom date ranges for specific analysis > * Export data in multiple formats (CSV, PDF, Excel) > * Create dashboard snapshots for presentations ## 🎓 Next Steps Now that you understand your dashboard, explore these advanced features: > [card] [Payment Processing](/payment-processing/payment-methods-overview) > > Learn about payment methods, providers, and processing options > [card] [Product Management](/products-and-pricing/creating-products) > > Master product creation, pricing strategies, and custom fields > [card] [Customer Management](/customer-management/customer-profiles) > > Discover customer relationship tools and automation features > [card] [Analytics & Insights](/analytics-and-reporting/insights-dashboard) > > Dive deep into business analytics and reporting capabilities ## 📞 Need Help Navigating? > [card] Video Tutorials > > Watch step-by-step dashboard walkthroughs > [card] Live Chat Support > > Get instant help with navigation questions > [card] Feature Requests > > Suggest dashboard improvements and new features *** > [!TIP] > > **Power User Tip**: Bookmark frequently accessed pages and use keyboard shortcuts to navigate your dashboard like a pro. The more you use PayRequest, the more efficient your billing operations become! # Use These Docs with AI Source: https://docs.payreque.st/getting-started/using-docs-with-ai Copy a guide as Markdown, open it in an AI conversation or give your AI tool the PayRequest documentation index. Use the menu beside a page title to bring the relevant PayRequest guide into your preferred AI tool. ## Copy a page or open it in an AI tool | Menu option | Use it when you want to… | | - | - | | **Copy page** | Copy the page as Markdown and paste it into an AI conversation or your notes. | | **View as Markdown** | Read or share a plain-text version of this page. | | **Open in ChatGPT** | Start a conversation about this page in ChatGPT. | | **Open in Claude** | Start a conversation about this page in Claude. | | **Open in Perplexity** | Ask Perplexity about the page. | Choose a specific guide and ask a concrete question, such as “Explain the difference between releasing this security deposit and refunding a charge.” Your chosen AI tool may require its own account. ## Give an AI tool the documentation index Mintlify maintains these files from the published documentation: * [llms.txt](https://docs.payreque.st/llms.txt): an index for discovering relevant guides. * [llms-full.txt](https://docs.payreque.st/llms-full.txt): a larger Markdown export of the published documentation. Start with the index or one relevant page rather than pasting the whole site into every question. Tools that can fetch URLs can use the index to find more context. ## Use the right guide > [card] [Business guides](/getting-started/welcome-to-payrequest) > > Configure PayRequest and manage payments, billing and customers. > [card] [Customer guide](/customer-guide/overview) > > Understand a payment link, customer account or security deposit. An AI explanation cannot confirm a private payment or release a reservation. Check the actual record with the business or payment provider. Keep login links, card details and other customers' information out of AI prompts. Developers who want their own agents to perform supported PayRequest actions can use the separate [PayRequest MCP integration](/mcp/overview). Copying a documentation page does not connect an agent to a PayRequest account. # PayRequest Documentation Source: https://docs.payreque.st/getting-started/welcome-to-payrequest Find the right guide to accept payments, manage billing, check a security deposit or access your customer account. PayRequest helps businesses accept payments, send invoices and manage subscriptions. Start with the guide that matches what you need to do. ## Choose your guide > [card] [I run a business](/getting-started/quick-start-guide) > > Connect a payment provider, create a payment page and manage your billing. > [card] [I'm a customer](/customer-guide/overview) > > Pay a business, sign in to your account or understand a security deposit. > [card] [I'm a developer](/api/overview) > > Build an integration with the API, webhooks or PayRequest MCP tools. ## Common tasks > [card] [Accept your first payment](/payment-processing/payment-forms) > > Set up your payment page and share a link with a customer. > [card] [Manage a security deposit](/payment-processing/security-deposits) > > Verify reserved funds, check a deadline and capture or release a hold. > [card] [Create and send an invoice](/invoices/creating-invoices) > > Prepare an invoice and give your customer a payment link. > [card] [Set up subscriptions](/subscriptions/creating-subscriptions) > > Configure recurring billing and understand the subscription lifecycle. ## Received a payment or deposit link? You do not need a PayRequest business account to follow a payment link. Use the business's original link and the email address associated with your purchase. * [Paying a business](/customer-guide/payments): check the amount, currency and result. * [Your customer account](/customer-guide/customer-account): sign in and find available invoices, orders and services. * [Security deposits for customers](/customer-guide/security-deposits): understand a pending hold, release or charge. * [Getting help](/customer-guide/getting-help): contact the business with the right reference. ## More step-by-step guides * [Use PayRequest AI](/getting-started/payrequest-ai) to prepare a link, customer or product and review it before confirming. * [From quote to invoice](/invoices/quotes-to-invoices) to agree on work and manage the resulting invoice. ## Find an answer Use search at the top of the page, or switch between **Business guides**, **Customer guide** and **Developers**. Each section has its own navigation so you can focus on the relevant instructions. You can also use **Copy page** beside a page title to copy a guide as Markdown or open it in an AI tool. See [Use these docs with AI](/getting-started/using-docs-with-ai). ## Contact support For a purchase, booking, deposit release or refund, contact the business that sent the request. For help with PayRequest itself, email [support@payrequest.io](mailto:support@payrequest.io). Business users can also open **Contact Support** in PayRequest AI. # Cloudflare Integration Source: https://docs.payreque.st/integrations/cloudflare Offer automatic domain DNS setup, customer-controlled nameserver switches, website forwarding and Google Workspace mail templates # Cloudflare Integration ☁️ Connect your Cloudflare account to PayRequest and give your customers the power to manage DNS records and set up domain forwarding — all from within their customer portal. No need to share Cloudflare login credentials or handle DNS changes manually. > [!NOTE] > > **Who is this for?** If you sell domain subscriptions through PayRequest (using OpenProvider for registration), the Cloudflare integration lets your customers manage their domain settings themselves — saving you time and support tickets. ## What You Can Do > [card] DNS Management > > Your customers can view, add, edit, and delete DNS records for their domain directly from their subscription page. No more back-and-forth emails about DNS changes. > [card] Domain Forwarding > > Customers can redirect their domain to any URL — like a social media page, a new website, or a landing page. Everything is handled through Cloudflare's redirect system. > [card] Admin Dashboard > > As a business owner, you get a full Cloudflare management panel in your dashboard. View all zones, manage DNS records, and configure forwarding for any domain. > [card] Automatic Setup > > When customers set up forwarding, the required DNS records are created automatically. No manual configuration needed. ## Getting Started ### Prerequisites Before connecting Cloudflare, make sure you have: * A Cloudflare account ([sign up free](https://dash.cloudflare.com/sign-up)) * An active OpenProvider connection and domain subscriptions in PayRequest * Your Cloudflare Account ID; PayRequest can create a zone when a customer chooses managed DNS * An API token with the right permissions ### Step 1: Create a Cloudflare API Token **1. Go to your Cloudflare dashboard** Log in at [dash.cloudflare.com](https://dash.cloudflare.com) and click on your profile icon in the top right corner. **2. Navigate to API Tokens** Go to **My Profile** → **API Tokens** → **Create Token** **3. Set up permissions** Create a custom token with the following permissions: | Permission | Access Level | What it does | | - | - | - | | **Zone** | Edit | Read zones and create new zones in the selected account | | **DNS** | Edit | Allows managing DNS records | | **Zone Rulesets** | Edit | Required for domain forwarding | Scope the token to the Cloudflare account you connect. Automatic setup needs permission to create zones in that account and manage newly created zones. A token restricted to a fixed list of existing zones may not cover new registrations. A successful connection test does not prove every action is permitted. If zone creation reports a missing `account.zone.create` permission, update the token's zone-creation access for the selected account. Forwarding also needs **Zone Rulesets: Edit**. **4. Copy your token** Click **Continue to summary** → **Create Token**. Copy the token — you'll only see it once! > [!WARNING] > > **Keep your token safe!** Store it somewhere secure before closing the page. Cloudflare only shows the token once. If you lose it, you'll need to create a new one. ### Step 2: Find Your Account ID Your Account ID is visible on your Cloudflare dashboard: 1. Go to [dash.cloudflare.com](https://dash.cloudflare.com) 2. Click on any domain 3. Look in the right sidebar under **API** — you'll see your **Account ID** 4. Copy it > [!TIP] > > Your Account ID is also visible in the URL when you're on your Cloudflare dashboard: `dash.cloudflare.com/ACCOUNT_ID_HERE` ### Step 3: Connect in PayRequest **1. Open the App Store** In your PayRequest dashboard, open **Services & integrations** → **Cloudflare**. **2. Add your credentials** Click **Add Cloudflare Integration** and enter: * **Account ID**: The ID you copied from Cloudflare * **API Token**: The token you just created **3. Sync your zones** After connecting, PayRequest will automatically sync all your Cloudflare zones (domains). You'll see them listed on the Cloudflare management page. **4. Verify the connection** Click **Test Connection** to make sure everything is working. You should see a green "Connected" badge. ## Managing DNS Records Once connected, DNS management is available for a domain subscription linked to a zone in your connected Cloudflare account. Customers can prepare records while a zone is still waiting for nameserver activation. Those settings become public after the domain uses the assigned nameservers and DNS activates. ## DNS choice when ordering a domain For a new domain, checkout offers: | Choice | What happens | | - | - | | **Manage DNS through your business** | After confirmed payment, PayRequest creates or reuses the domain's Cloudflare zone, uses its assigned nameservers for OpenProvider registration and makes DNS management available in the customer portal. | | **Use your own nameservers** | The customer enters two different nameserver hostnames and continues managing DNS at that provider. No Cloudflare zone is created for this choice. | The managed option uses your business name and appears when your Cloudflare integration is available. Nameservers are assigned per zone: do not promise the same pair for every domain. Automatic setup adds only DNS records explicitly configured for the domain product. It does not guess a hosting IP, create mailboxes or invent mail settings. A newly registered domain can therefore have an empty DNS zone. Customers can add records or configure website forwarding later. PayRequest checks pending Cloudflare activation every five minutes. Public DNS caches can take longer to reflect a nameserver change. Existing orders and domains using external DNS are not automatically switched. ## Switching an existing domain to managed DNS An authorized customer can open **My services → domain → Domain** and choose **Prepare DNS and forwarding** when the domain is active at OpenProvider and your Cloudflare integration is available. 1. Preparation creates or reuses the Cloudflare zone without changing the current nameservers. 2. The customer uses **DNS** to copy existing website, mail and subdomain records, or uses **Forwarding** to prepare a redirect. 3. **Review nameserver switch** shows current and assigned nameservers and the prepared record count. 4. The customer confirms that the needed records are complete or not required, then chooses **Switch nameservers now**. An empty zone is allowed, including for a domain that does not yet have a website or email. Existing records are not automatically imported from the previous DNS provider. The customer must copy any settings they need before switching. If registry DNSSEC is still enabled, the switch is blocked. Disable the existing DNSSEC first, review the switch again, and enable managed DNSSEC again after activation. A preview expires after ten minutes; changes to DNS or nameservers require a fresh preview. The portal shows progress on the switch button and the result in the **Domain** tab. PayRequest reads back the registrar's nameservers before confirming success. If the result is unclear, refresh the preview to check the current state rather than repeatedly submitting the switch. ### For Business Owners (Admin Dashboard) From the Cloudflare app page in your dashboard: 1. Find the domain in **Your Zones** 2. Click **Manage DNS** to view all DNS records 3. Edit or delete existing records 4. Add new records as needed ### For Your Customers (Customer Portal) Your customers will automatically see a **DNS** tab on their domain subscription page. From there, they can: * **View** all DNS records for their domain * **Add** new records (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA) * **Edit** existing records — change the content, TTL, or proxy settings * **Delete** records they no longer need * **Refresh** to see the latest state from Cloudflare The primary customer and enabled customer administrators or operations contacts can change DNS and forwarding. Billing and viewer contacts have read-only DNS access. Every change checks ownership and permissions again. ## Google Workspace mail template In the customer **DNS** tab, choose **Google Workspace → Preview mail settings → Apply Google Workspace template**. The template uses [Google's current MX setup](https://support.google.com/a/answer/174125): `MX @`, priority `1`, destination `smtp.google.com`, TTL **Auto**. It also adds `TXT @ v=spf1 include:_spf.google.com ~all` if no SPF record exists. * Existing Google MX records, including working legacy `aspmx` records, are kept. * MX records for another mail provider are listed for replacement and require explicit customer confirmation. Incoming mail will then go to Google Workspace. * Existing SPF is preserved. If it does not authorize Google, the portal asks the customer to review it alongside other mail senders. The template does not add a second SPF record. * Website records, subdomain MX, verification TXT, DKIM and DMARC records are preserved. Domain verification and DKIM need values from the customer's own Google Admin console. Add those TXT records separately and finish Gmail and DKIM activation there. Applying the template does not create a Google Workspace subscription or mailbox. > [!NOTE] > > DNS changes are applied through Cloudflare's network and typically take effect within minutes, though full global propagation can take up to 48 hours. ## Domain Forwarding Domain forwarding lets your customers redirect their entire domain to another URL. This is one of the most requested features for domain customers. ### Common Use Cases * **Social media redirect**: Forward `mybrand.com` to `instagram.com/mybrand` * **Website migration**: Redirect an old domain to a new one * **Short URL**: Use a short domain as a branded redirect to a longer URL * **Coming soon**: Point a domain to a temporary page while a website is being built ### How It Works **1. Customer opens their subscription** From the customer portal, your customer navigates to their domain subscription and clicks the **Forwarding** tab. **2. Enter the target URL** They enter the URL they want their domain to forward to — for example, `https://www.instagram.com/mybrand`. **3. Choose redirect options** * **Redirect Type**: Permanent (301) or Temporary (302) * **Preserve Path**: If enabled, `domain.com/about` forwards to `target.com/about` * **Preserve Query String**: If enabled, `domain.com?ref=abc` forwards to `target.com?ref=abc` **4. Save and done** Click **Set Up Forwarding**. PayRequest automatically: 1. Creates the required DNS record for Cloudflare to handle the redirect 2. Sets up the redirect rule in Cloudflare 3. Shows a confirmation with the active forwarding details For a domain that still uses external DNS, forwarding can be prepared before the switch. Complete the nameserver switch from the **Domain** tab and wait for activation before expecting the redirect to work publicly. Saving forwarding can replace an existing root A record; review the warning if that record currently serves a website. [Share the step-by-step domain guide with your customers](/customer-guide/manage-domain). ### Redirect Types Explained | Type | Code | Best For | | - | - | - | | **Permanent** | 301 | Moving to a new domain permanently. Search engines will update their index to the new URL. | | **Temporary** | 302 | Short-term redirects like promotions or maintenance. Search engines keep the original URL. | > [!TIP] > > **Not sure which to pick?** Use **Permanent (301)** if the redirect will stay forever (like forwarding to a social media page). Use **Temporary (302)** if you plan to use the domain for something else later. ### Managing Forwarding as a Business Owner You can also manage forwarding from the admin Cloudflare dashboard: 1. Go to **Services & integrations** → **Cloudflare** 2. Find the zone in **Your Zones** — domains with active forwarding show a purple **Forwarding** badge 3. Click **Edit Forwarding** to change settings, or **Set Up Forwarding** to configure a new one ## What Your Customers See When a customer has a domain subscription and the domain is managed in Cloudflare, their subscription page gets extra tabs: > [accordion] Domain Tab > > Shows domain information: domain name, expiry date, nameservers, authorization code, and auto-renewal status. This tab is always available for domain subscriptions. > [accordion] DNS Tab > > A full DNS record table where customers can view, add, edit, and delete records. Uses a clean table layout with record type badges, proxy status indicators, and action buttons. > [accordion] Forwarding Tab > > A simple form to set up or manage domain forwarding. Shows the current forwarding status (active or not configured), the target URL, and all forwarding options. > [!NOTE] > > The DNS and Forwarding tabs appear for linked active or pending Cloudflare zones. For an eligible domain with external DNS, customers can prepare a zone from the Domain tab first. Preparing settings does not make them public before nameserver activation. ## Troubleshooting > [accordion] Forwarding shows 'Authentication error' > > This means your Cloudflare API token is missing the **Zone Rulesets: Edit** permission. DNS features will still work, but forwarding requires this extra permission. > > **Fix**: Go to your Cloudflare dashboard → **My Profile** → **API Tokens** → edit your token → add **Zone Rulesets: Edit** permission. > [accordion] DNS and Forwarding tabs don't appear for a customer > > These tabs only show when: > > 1. The subscription is for a **domain** product > 2. The domain has a **domain registration** linked to it > 3. The domain exists as an **active or pending zone** in your connected Cloudflare account > 4. Your Cloudflare integration is **connected and active** in PayRequest > > Check each condition. Sync existing zones from the Cloudflare app page, or let an eligible customer choose **Prepare DNS and forwarding** in the Domain tab. > [accordion] Connection test fails > > * **Double-check your API token** — make sure you copied the full token > * **Verify the Account ID** — it should match what's in your Cloudflare dashboard URL > * **Check token permissions** — automatic setup needs zone-creation access in the selected account, DNS: Edit, and Zone Rulesets: Edit for forwarding > * **Token expired?** — Cloudflare tokens can have expiry dates. Create a new one if needed. > [accordion] Zones not showing after connection > > Click **Refresh Zones** on the Cloudflare management page. If zones still don't appear: > > * Make sure your domains are added to Cloudflare > * Check that the API token has access to the correct zones > * Check the zone's status; pending zones can be prepared, but need their assigned nameservers before activation ## Best Practices > [card] Use Descriptive Token Names > > Name your Cloudflare API token something like "PayRequest Integration" so you can easily find it later in your Cloudflare dashboard. > [card] Limit Token Scope > > Only give the token access to the zones you manage through PayRequest. This follows the principle of least privilege and keeps your other domains safe. > [card] Monitor Forwarding Usage > > Check the Cloudflare dashboard for zones with active forwarding. The purple "Forwarding" badge in PayRequest makes it easy to see which domains have redirects configured. > [card] Educate Your Customers > > Let your customers know they can manage DNS and forwarding themselves. This reduces support requests and gives them more control over their domains. ## Related Documentation > [card] [App Store](/business-settings/app-store) > > Manage all your integrations > [card] [Customer Portal](/customer-management/customer-portal) > > Learn about the customer experience > [card] [Subscriptions](/subscriptions/creating-subscriptions) > > Set up domain subscriptions *** > [!TIP] > > **Quick Access**: Manage your Cloudflare integration anytime from **Settings** → **App Store** → **Cloudflare** in your PayRequest dashboard. # Discord Memberships Source: https://docs.payreque.st/integrations/discord-memberships Sell paid access to your Discord community with product-linked roles, timed passes or unlimited access. Discord Memberships connects a PayRequest product to a role in your Discord server. A customer pays, connects their Discord account on your Discord access page and joins your server. PayRequest checks the purchase and gives them the role while their paid access is valid. > [!NOTE] > > PayRequest provides the shared Discord app. You do not need to create a Discord application or enter a bot token or client secret. You must own the Discord server you connect. ## What you can sell * A one-time community pass lasting between 1 and 3,650 days, or unlimited access without automatic expiry. * A native PayRequest subscription with a daily, weekly, monthly or yearly paid period. * Different products linked to different roles, such as Community and Workshop. Use a **service product** for one-time passes or a **subscription product** for native recurring access, with a positive price and one unit. Recurring products must have an interval count of one. Free trials, provider-managed subscriptions, existing purchases and products already using another automatic delivery integration are not supported by this first version. A standalone amount link without a purchased product does not grant a role. Active connected Discord products use their fixed product price even when it is below the Page minimum for open-amount payments. The Page maximum still applies. This integration sells community access. Downloadable bot software can continue to use [digital product delivery](/products-and-pricing/digital-products); Discord Memberships does not host or run a customer's bot. ## Set up your server **1. Create a dedicated access role** In Discord, create a role such as **Paid member**. Give it access to your private channels. Keep moderation, administrator and staff roles separate. PayRequest rejects administrative or otherwise unmanageable roles. **2. Install the PayRequest bot** Open **Services & integrations → Discord Memberships → Install Discord bot**. Select your server and approve the account connection and **Manage Roles** permission. Move the bot's role above the paid-access roles, then return to PayRequest. **3. Connect your Discord account and server** If you installed the bot separately, use **Connect Discord account** first. Select your server and use **Save server** to link it to your business. PayRequest verifies server ownership and the bot's role permissions. Installing the bot alone does not save the business connection. One PayRequest business connects one server; that server cannot also be connected to another PayRequest business. **4. Add a server invitation** Paste a Discord invitation to your server. PayRequest checks that it belongs to the connected server. Customers use it to join before claiming access. Replace it if it expires or is revoked. **5. Connect your product** With an active Discord server connection, open **Products → New product → Discord Membership**. Choose a one-time access pass or subscription, enter the product details and save. PayRequest then opens Discord Memberships with your new product selected. Choose its dedicated access role. You can also connect an existing eligible service or subscription product from this screen. Use **Create membership role** to create a role without extra permissions; PayRequest checks that the bot can manage it and reuses the same role on repeated setup. Choose the private channels it unlocks in Discord before selling access. For a one-time product, enter the number of access days or select **Unlimited access**. Confirm that you have checked which private channels the role unlocks. Saving the same active connection again is safe. Before any order, invoice, subscription or recorded access exists, you can explicitly switch the same role from a fixed one-time duration to **Unlimited access**. This preserves the role and original connection date. Once checkout or billing has started, the saved terms stay fixed. Role changes, shorter access, disabled connections and other changes require a new product. Selecting an already connected product loads its saved settings. Only purchases created after the product is connected are considered; existing customers are not imported automatically. ## Check your setup Discord Memberships has three tabs: **Setup**, **Products** and **Customer access**. The **Products** tab shows your connected products as cards with their role, status and access duration above the connection form. The **Setup status** checklist updates automatically about every 15 seconds while the page is visible, and checks again when you return to it. It shows your Discord account connection, bot installation, role permissions, saved server connection and connected product. **Not checked yet** means PayRequest still needs your Discord account connection or a server selection before it can verify the bot. If a step remains incomplete, check the server selection, the bot's **Manage Roles** permission and its position above the membership role. Complete **Save server** and connect a product before selling access. Discord rate limits can delay checks. ## Works with a Payment Page A shop is not required. Payment Page sellers use a dedicated Discord access page at `payrequest.me/{page-handle}/discord/access`. Discord access is a tab inside the existing Payment Page, using the same banner, merchant logo or avatar, theme and customer menu. The access screen, email login and status checks stay on `payrequest.me`. Open the **Discord access** tab or choose it from the signed-in customer menu; **Home** returns to the main Payment Page. Existing `payrequest.app/discord/access/{page-handle}` links redirect to the matching Payment Page. Customers sign in with the email address from their purchase and connect their own Discord account there. Existing shop customer access remains available for shop-only sellers. ## Your customer's experience 1. The customer purchases the connected product and completes payment. 2. The payment confirmation shows **Continue to Discord**. This opens the **Discord access** tab in the seller’s Payment Page. If needed, the customer signs in using the email address from their purchase; the login link then takes them back to Discord access. No shop account or shop setup is needed. 3. They connect the Discord account they want to use, join through your invitation and accept any Discord server rules. 4. Access checking starts automatically when they open the access page with a connected Discord account. The page watches for status changes for about 30 seconds. Once payment and membership are verified, the role is granted. **Check Discord access** remains available to retry. The access page names the connected Discord server and provides **Open Discord server**. Existing members can open it directly. New members first need your saved invitation. PayRequest grants a role; Discord channel permissions determine which channels become visible. It does not choose a channel or join the server for the customer. Paid order confirmations and completion emails also include the Discord role, access duration and a return link to this access page. The return link does not expire like an email login token; customers prove their identity when they sign in. Open the email login link and complete Discord sign-in in the same browser. Page email login links are single-use and valid for one hour; requesting a new link replaces the previous one. The primary customer connects their own Discord account. Delegated contacts and merchant impersonation sessions cannot claim access. A linked account cannot be switched automatically; contact support if the wrong account was connected. When connecting Discord, customers briefly visit Discord to authorize their account and then return to their Payment Page. The existing shared app handles the callback automatically; sellers do not need to change their Discord configuration. Purchases made on a custom domain also use this `payrequest.me` access page. It does not require a shop. ## Renewal, expiry and cancellation Each eligible paid purchase is recorded once. Repeated provider notifications or access checks do not extend it again. Native recurring renewals extend the paid period; an unpaid renewal does not. PayRequest checks access after relevant saved payments/subscriptions and through a five-minute recovery schedule. Changes can take longer when the queue is busy or Discord limits requests. No always-instant delivery is promised. Unlimited one-time access has no automatic expiry, but refunds, disputes, disabled delivery and account blocks still stop the affected purchase from granting managed access. Time-limited access ends when the paid period expires or the subscription's cancellation takes effect. A future scheduled cancellation does not remove access early. Paused or suspended subscriptions do not grant current access. Refunds, credit notes, chargebacks and unresolved payment disputes stop the affected purchase from granting automatic access. Partial credits/refunds are treated conservatively and need seller review. If more than one valid purchase grants the same role, one expired purchase does not remove it while another still qualifies. > [!WARNING] > > PayRequest only removes roles it has claimed responsibility for granting. A role already present before PayRequest handled the purchase is retained. Use dedicated roles and review existing manual assignments before selling access. PayRequest does not kick or ban customers, change channel permissions, cancel billing or issue refunds through this integration. ## Troubleshooting In **Discord Memberships → Setup**, connection checks run automatically when you open the page and about every 15 seconds while it is visible. A checkmark confirms the connection; problems show a short explanation without changing customer roles. The **Customer access** tab lists recent customers who bought a Discord product, including buyers who have not connected Discord yet. Connected customers show their last recorded access status and check time. **Check Discord access** queues a fresh payment/access check; it does not charge the customer or grant unpaid access. Product and order details also show their Discord role and access duration. Order details distinguish delivery configuration from the customer’s Discord connection and recorded access state. | Status | What to do | | - | - | | Join the Discord server | Use the seller's invitation, then check access again. | | Complete the Discord server rules | Open Discord, accept the rules and retry. | | No current paid access | Check the purchased product, payment, paid period and effective cancellation date. | | Existing Discord role retained | The account already had this role; PayRequest will not remove it automatically. | | Discord access needs attention | The seller should check the bot, role hierarchy, server ownership and permissions. | If you see **429 Too Many Requests**, wait about a minute before retrying. Use the newest email login link, or request a fresh one if it has expired or was already used. If no server invitation is shown, ask the seller to add one in **Setup**. A server link opens Discord for existing members but does not replace an invitation for new members. Disabling delivery for a product removes its managed access at the next successful check. It does not stop subscription billing. Review billing and tell affected customers separately before disabling a live product. # Hetzner Cloud Source: https://docs.payreque.st/integrations/hetzner-cloud Connect your own Hetzner project, link existing servers, sell VPS subscriptions and offer customer reboot and browser console access. Connect your own Hetzner Cloud project to manage server subscriptions in PayRequest. Link servers you already have, or sell VPS products with automatic delivery after confirmed payment. Customers see their server details and the controls you allow in their subscription’s **Server** tab. ## Connect your project 1. Open **Services & integrations → Hetzner Cloud**. 2. In [Hetzner Console](https://console.hetzner.com/projects), choose a separate project for your customer servers. 3. Go to **Security → API Tokens** and create a **Read & Write** token. 4. Paste it into PayRequest and select **Save connection**. Your token is encrypted and is not displayed again. The connection test reads project information; it does not create a paid test server. A successful read test cannot prove the token has write permission. ## All project servers and private notes The integration page lists **all servers in the connected project**, including servers you created outside PayRequest. Select **Refresh server list** to update their names, status, IP addresses, type and location. The **Subscription** column links to the PayRequest subscription when the server was provisioned through this integration or manually linked. Other servers show **Not linked to a PayRequest subscription**. Reading the server list never imports an existing server as a managed service, attaches it to a customer or performs a server action. Use **Edit notes** to keep private notes of up to 4,000 characters per server. Only your business owner account can access these notes. Refreshing the list preserves them. If a server is no longer found, its row and notes remain available with that status. ## Create a VPS product Select **Create VPS subscription** to open the full product wizard. Choose: * Your Hetzner connection, server type and location. * A compatible system image and an existing project SSH key. * Your selling price, currency and monthly or annual billing. PayRequest verifies the selected resources against your project when you save the product and again before creating a server. Capacity can change, so delivery may require review if Hetzner cannot fulfill the selection. One subscription delivers one VPS. The first payment is immediate; free trials, quantity selection and customer subscription pauses are disabled. Server configuration is preserved when editing a product. Create a new product to sell a different server configuration. Existing services keep their original configuration and billing interval. The selected SSH key is installed on the new server. Arrange the customer's SSH access yourself. PayRequest does not store private SSH keys or distribute your private key to customers. ## Delivery and customer controls Delivery starts only after a positive, fully paid order or a paid invoice line belonging to that subscription. The initial order and its invoice cannot deliver two servers or grant two periods. Payment verification and pending bank transfers do not deliver a server. The customer's subscription has a **Server** tab with IP addresses, configuration, the last synchronized status and the paid-until date. Primary customers and enabled **admin** or **operations** contacts can request start, graceful shutdown and restart during paid access. Billing and viewer contacts cannot operate the server. Each action checks current customer, shop, contact permissions, payment state and server identity. Actions run asynchronously at Hetzner. Use **Refresh server details** to check the result; the accepted request is not proof of completion. Status and pending actions are also reconciled every five minutes. ## Cancellation, unpaid periods and deletion > [!WARNING] > > Hetzner continues charging while a server exists, even when it is powered off. Cancelling the PayRequest subscription or missing a renewal does not automatically stop or delete the server. It also does not revoke operating-system SSH access. Review the server yourself and agree termination with your customer. Cancellation preserves customer controls through the remaining paid period. Expired, paused, archived or reversed paid access blocks customer controls. A credit against the latest paid invoice also requires owner review. None of these conditions automatically deletes server data. Only the business owner can delete a managed server through PayRequest. Deletion requires the exact server name, a reason and confirmation that customer readiness, remaining paid access, backups and exports have been addressed. This permanently destroys the server; it does not cancel the subscription, credit invoices or remove unrelated resources. Additional IPs, volumes or other resources may still incur costs. ## Uncertain delivery or actions If a response is lost, PayRequest looks for the original server using its unique name and ownership labels. It does not blindly create another server. After at least ten minutes, the owner can use **Verify and retry creation** to check for the original server before permitting another attempt. Uncertain power actions are blocked from automatic repetition. Check the server in Hetzner Console, then record a **manual review** after ten minutes. This clears the block without repeating the action. A server deleted or removed outside PayRequest is never recreated automatically. Do not rename managed servers or change their `payrequest.io/` labels: identity mismatches block actions. A replacement token must belong to the same project; resolve uncertain operations before rotating it. This integration manages Hetzner Cloud VPS servers. Dedicated servers through Robot, automatic resizing, cloud backups, usage-based billing are not supported by this integration. ## Link an existing server to a subscription Open **Services & integrations → Hetzner Cloud**. Find the existing server and click **Link to subscription**. Search by subscription name or number, select the subscription and confirm. Search by the subscription number shown in your dashboard when several subscriptions have similar names. The association appears in the server list and the business subscription detail. Each server and subscription can have one association. To change it, unlink the current association first. Private server notes are preserved. This is an administrative association. It preserves existing billing and server settings and does not enable automatic provisioning, customer server controls or deletion. Reboot and console access are separate options you can enable after linking. Products configured for automatic Hetzner delivery cannot be manually linked. ## Let customers restart an existing server After linking an existing server, enable **Allow customer reboot** in the server list. This permission applies to the linked subscription's current customer. It is off by default, and unlinking removes the permission. The customer sees a **Server** tab with server details and a confirmed normal restart action while the subscription is active. Primary customers and admin/operations contacts may restart; billing and viewer contacts cannot. Changing the customer requires enabling access again. This does not grant console, root, shutdown, rebuild or deletion access. If a restart result is uncertain, check the server in Hetzner Console. PayRequest blocks further restarts until the previous result is confirmed or the business owner explicitly reviews the blocked action after ten minutes. It never repeats a timed-out restart automatically. ## Open a server console In **Services & integrations → Hetzner Cloud**, enable **Allow console** for the linked server. This is a separate permission from reboot access. It applies to the selected subscription and its current customer. Changing the customer requires enabling access again; unlinking clears the permission. Console access is also available for PayRequest-provisioned servers with valid paid access. The customer opens the **Server** tab, clicks **Open console**, then **Connect**. Refresh, reboot and console actions are grouped in one responsive toolbar with icons. A full-screen window within the same subscription page provides the VPS screen and keyboard through Hetzner VNC. Closing the modal disconnects the browser console. The customer signs in with their own Linux username and server password; PayRequest does not sign in automatically or reset passwords. The console is available to the primary customer and enabled admin/operations contacts on an active subscription. Billing/viewer contacts cannot connect. Console connection credentials are issued only after Connect. Hetzner allows one minute to establish the connection; an established connection can last longer. PayRequest keeps these credentials only in browser memory, without analytics, session recording, URL parameters or stored credentials. Click **Disconnect** to close the browser connection. Log out of Linux first: disconnecting VNC does not end the server's login session. The browser checks access every 15 seconds and closes the console after 30 minutes. Disabling access blocks new credentials immediately. Hetzner's direct WebSocket connection cannot be forcibly revoked by PayRequest after it has been established; client checks are best effort, not provider-side session revocation. Review existing Linux sessions separately when removing access. ### Customer console steps **1. Open your server** Sign in to the business’s customer portal, open **My services**, select your subscription and choose **Server**. **2. Connect** Select **Open console**, then **Connect** in the full-screen window. Keep the window open while the connection starts. No new browser tab is needed. **3. Sign in to Linux** Click inside the server screen to use your keyboard. Enter your own Linux username and server password. An SSH private key does not sign you in through this console. Ask your hosting provider if you do not have console login details. **4. Finish your session** Log out of Linux, then select **Disconnect** or **Close console**. Closing the window disconnects the browser but does not log out of Linux for you. ### Troubleshooting > [accordion] The Server tab or console button is missing > > Check that the server is linked to the correct subscription and that **Allow console** is enabled for its current customer. The subscription must be active; automatically delivered servers also require valid paid access. Billing and viewer contacts cannot open the console. Reopen the subscription after your provider changes access. > [accordion] Wait before opening a new console connection > > Wait until the countdown finishes before selecting **Connect** again. PayRequest does not retry automatically. Avoid opening several sessions at once; after an uncertain response, the wait can be longer. > [accordion] The console cannot connect > > Refresh the server details and check that the server is running. Wait and try connecting again. If the issue continues, contact your hosting provider so they can check the server and project in Hetzner Console. A browser console is not an SSH connection and does not reset the server password. > [accordion] The server status has not changed after a restart > > Hetzner processes actions asynchronously. Use **Refresh server details** to check the result. An uncertain action is not automatically repeated; the business owner must review it before another attempt. ## Related guides * [Services & integrations](/business-settings/app-store) * [Customer portal](/customer-management/customer-portal) * [Contact persons and portal access](/customer-management/contact-persons) * [Subscription self-service](/subscriptions/customer-self-service) ## Record maintenance checks Use [Server care & SLA](/integrations/server-care) to review saved inventory across providers, record backup and update checks, and keep service agreements and evidence together. Checks are manual records; the overview does not perform maintenance. # Lock $PAYR for Free Premium Source: https://docs.payreque.st/integrations/lock-payr-for-premium Lock $PAYR tokens on Solana via Streamflow to unlock PayRequest Premium for free, without a card or bank payment # Lock \$PAYR for Free Premium Instead of paying for PayRequest Premium with a card or bank transfer, you can lock \$PAYR tokens in a non-cancelable, time-locked vault on Solana. As long as the lock stays in place, your account keeps free Premium access — no recurring card charge, no subscription to manage. > [!NOTE] > > This uses [Streamflow](https://streamflow.finance), an established on-chain token vesting/locking protocol on Solana. PayRequest never takes custody of your \$PAYR — the tokens stay in a Streamflow-controlled vault that only unlocks back to your own wallet after the lock period ends. ## Requirements | Requirement | Value | | - | - | | **Minimum lock amount** | 100 \$PAYR | | **Minimum lock duration** | 90 days | | **Network** | Solana | | **Wallet** | Any Solana wallet holding \$PAYR (e.g. Phantom, Solflare) | > [!WARNING] > > Once locked, your \$PAYR **cannot be cancelled or withdrawn early** — the lock is created as non-cancelable by both sender and recipient. Only lock an amount and duration you're comfortable committing to. ## How It Works **1. Go to the Lock page** Visit `/token` and connect a Solana wallet holding \$PAYR. You'll need to be logged in to your PayRequest account. **2. Choose your amount and duration** Enter how much \$PAYR to lock (minimum 100) and for how long (minimum 90 days). PayRequest builds an unsigned lock transaction for you to review. **3. Sign the transaction** Approve the transaction in your wallet. This creates a Streamflow lock stream — your tokens move into the on-chain vault at this point. **4. PayRequest verifies the lock on-chain** PayRequest checks the lock directly on Solana: correct token, correct amount, correct duration, and confirms it's genuinely non-cancelable. Premium is only activated once **all** of these checks pass. **5. Premium is activated** Your account gets a free, active Premium subscription (shown as "Premium (locked \$PAYR)" in your subscription list) for as long as the lock remains active. ## What Happens When the Lock Ends PayRequest continuously monitors active locks. When your lock's unlock date arrives: * The lock status changes to **expired** * Your Premium subscription is automatically cancelled (unless you have another active lock covering it) * Your \$PAYR becomes claimable back to your wallet through Streamflow directly > [!NOTE] > > If you want to keep Premium after your lock ends, create a new lock before the current one expires, or switch to a regular paid Premium subscription. ## Verification & Security Every lock goes through strict on-chain verification before Premium is granted: * **Correct token** — must be the \$PAYR mint, not a different token * **Correct amount** — must meet the 100 \$PAYR minimum * **Correct duration** — must be locked for at least 90 days from creation * **Genuinely non-cancelable** — both sender and recipient cancellation must be disabled on-chain If a lock transaction is submitted but never confirms on-chain within 30 minutes, it's automatically marked invalid and no Premium is granted. > [!WARNING] > > Early withdrawal is treated as a security anomaly and should not be possible given the lock is created as non-cancelable — but if PayRequest ever detects tokens were withdrawn before the agreed unlock date, Premium access is revoked immediately. ## FAQ > [accordion] Do I need to pay gas fees? > > Yes, standard Solana network fees apply when you sign the lock transaction — these are minimal (typically a fraction of a cent). > [accordion] Can PayRequest access or move my locked tokens? > > No. The lock is a Streamflow on-chain vault, not a PayRequest-controlled wallet. PayRequest only reads the lock's public on-chain state to decide whether to grant Premium — it never has the ability to move, cancel, or claim your tokens. > [accordion] Can I lock more than once? > > Yes. Multiple active locks can be linked to the same Premium subscription, and Premium stays active as long as at least one lock is still active. > [accordion] What happens if I lose access to my wallet? > > The lock and its unlock date are recorded on-chain independently of PayRequest. You'd need your wallet to eventually claim the tokens back from Streamflow when the lock expires — this is the same as any other Solana wallet/token custody situation. > [accordion] Is this the same \$PAYR used elsewhere in PayRequest? > > Yes — the same \$PAYR token used in PayRequest's Solana pump.fun integration. ## Next Steps > [card] [PayRequest Plans](/business-settings/payrequest-plans) > > See what's included in Premium and how it compares to paying by card > [card] [Solana Pay](/payment-processing/solana-pay) > > Accept Solana payments from your own customers # payments.txt Source: https://docs.payreque.st/integrations/payments-txt Every PayRequest page auto-publishes a machine-readable payments.txt manifest — so AI agents can discover your wallets, payment terms, and checkout URL without any integration work. # payments.txt `payments.txt` is an open standard that makes your payment profile readable by AI agents and autonomous billing systems. Think of it as `robots.txt` or `llms.txt` — but instead of telling crawlers what to skip or giving LLMs context, it tells agents exactly how to pay you. Every PayRequest page generates one automatically. No setup required. > [!NOTE] > > **Auto-generated.** Fill in your wallet address and business details in PayRequest settings — your `payments.txt` is live instantly at `payrequest.me/yourhandle/payments.txt`. ## What it looks like ```ini theme={null} # PAYMENTS.TXT MANIFEST (X402 COMPLIANT) # Generated by PayRequest.me for @yourhandle [meta] version = "1.0" status = "active" x402_discovery_url = "https://payrequest.app/api/v1/x402/yourhandle" x402_payment_endpoint = "https://payrequest.app/api/v1/x402/yourhandle/pay" [payment_terms] due_days = 14 late_fee_percentage = 2.0 preferred_fiat = "EUR" preferred_crypto = "USDC" [crypto_rails] supported_standards = ["EVM", "Solana"] primary_stablecoin = "USDC" evm_address = "0xYour…" solana_address = "YourSolana…" [fiat_rails] sepa_iban = "NL…" sepa_bic = "BUNQ…" [hosted_checkout] human_fallback_url = "https://payrequest.me/yourhandle" ``` Only sections with data are included — if you haven't connected a Solana wallet, the `solana_address` line won't appear. ## What gets included > [card] Crypto wallets > > Your EVM address (Base / Ethereum) and Solana address from Provider Settings. Only included if you've connected them. > [card] Bank details > > IBAN and BIC from your Business Details. Agents can use these for SEPA bank transfers. > [card] Payment terms > > Default due days and late fee percentage. Agents use these when creating invoices on your behalf. > [card] X402 endpoints > > Machine-payment URLs so agents can pay invoices autonomously via the X402 protocol — no human checkout needed. ## Your manifest URL Your `payments.txt` is always at: ``` https://payrequest.me/yourhandle/payments.txt ``` Replace `yourhandle` with your PayRequest handle (the one in `payrequest.me/yourhandle`). > [!TIP] > > You can check what your manifest looks like right now by visiting that URL in your browser. It's public and human-readable. ## HTML discovery tag Your payment page automatically includes a `` tag in its `` so agents parsing your page HTML can find the manifest without guessing: ```html theme={null} ``` ## How agents use it When an AI agent needs to pay you — for an invoice, a product, or API access — it can: 1. Read your `payments.txt` to discover your wallets and preferred payment method 2. Check your `x402_payment_endpoint` for autonomous USDC payment (see [X402 Autonomous Payments](/integrations/x402-autonomous-payments)) 3. Fall back to `human_fallback_url` if it needs a human to complete the payment ## Keeping it up to date Your manifest is generated live from your PayRequest account data. To update it: * **Change your EVM wallet** — go to Provider Settings → Crypto (USDC) → Connect Wallet * **Add a Solana wallet** — Provider Settings → Solana (pump.fun) * **Update your IBAN** — Business Settings → Business Details → IBAN / BIC * **Change your currency** — Business Settings → Business Details → Default Currency Changes appear in your manifest immediately — no cache to clear. ## Open standard `payments.txt` is an open standard. The full specification and implementation guides for PHP, Node.js, and other platforms are on GitHub: > [card] [PayRequest/payments-txt on GitHub](https://github.com/PayRequest/payments-txt) > > Full spec, format reference, and implementation guides. MIT licensed — free to implement on any platform. # Server care and SLA overview Source: https://docs.payreque.st/integrations/server-care Review Hetzner and DigitalOcean inventory, record backup and update checks, and keep service agreements together. Open [Server care & SLA](https://payrequest.app/apps/servers) as the business owner to review servers from your saved Hetzner Cloud and DigitalOcean inventory. This overview records your maintenance checks. It does not run backups, install updates or verify that your service agreements have been met. ## Find servers that need attention Choose **All**, **DigitalOcean** or **Hetzner**, then search by server name, IP address or provider. Enable **Attention required only** to focus on missing or overdue checks, stale inventory or inactive provider connections. Provider summaries reflect your search. The attention filter narrows the server list. **In order** means the recorded checks and inventory meet the overview’s criteria; it is not an uptime or application-health guarantee. If servers are missing, synchronize inventory using **Sync DigitalOcean** or **Sync Hetzner**, or open the provider app to check the connection. Wait at least 30 seconds before synchronizing the same provider again. Inventory timestamps show when a server was last seen, rather than continuous monitoring. ## Record a backup or update check 1. Open the server at the provider and do the relevant work. For backups, verify success, age and coverage. For updates, review required patches and restarts and verify services afterward. 2. Use **Settings** beside the relevant backup or update check to record the last successful date and supporting notes, then save. 3. To record today’s completed check quickly, select **Confirm** beside that check and confirm the date. Confirming a check only records your confirmation. Perform the maintenance first. Both backup and update checks default to a seven-day interval. In **Settings**, set each interval from 1 to 365 days and save. A check becomes overdue when its interval is reached; an absent or invalid date is shown as not checked. ## Keep agreements and evidence Use **Settings** to save SLA or service agreements and private evidence or notes for the server. Record useful references and outstanding work without passwords, tokens or other credentials. Server care records do not change subscriptions, billing, server permissions or provider settings. Use the provider integration for operations and customer access: * [Hetzner Cloud](/integrations/hetzner-cloud) * [Services & integrations](/business-settings/app-store) # Telegram Payment Bot Source: https://docs.payreque.st/integrations/telegram-bot Accept payments and receive instant payment notifications directly in Telegram — no coding required. Free for all PayRequest users. # Telegram Payment Bot Turn Telegram into your payment terminal. With the PayRequest Telegram bot, you can create a payment link in seconds, share it instantly in any chat, and get notified the moment money hits your account — all without leaving Telegram. > [!NOTE] > > **Free for all plans.** The Telegram bot is included with every PayRequest account. Connect once and it works forever. ## Why Use the Telegram Bot? > [card] Create links in seconds > > Type `/pay 50 for design work` and the bot instantly returns a payment link ready to share. No dashboard login needed. > [card] Instant payment alerts > > The moment a customer pays, you get a Telegram notification with the amount, customer name, and invoice number. > [card] Works in any chat > > Share payment links in private chats, group chats, channels, or anywhere else. The link opens your branded PayRequest checkout. > [card] No app switching > > If your business runs on Telegram, your payments can too. Stay in the app you already use all day. ## Who Is This For? The Telegram bot is especially useful for: * **Freelancers** who discuss projects with clients on Telegram and want to send a payment request without switching apps * **Community owners** selling access, courses, or memberships to their Telegram audience * **Online sellers** who take orders via Telegram and need a fast, professional way to collect payment * **Service businesses** that want instant payment alerts on the go ## How to Connect **1. Open the bot** Search for **@payrequestme_bot** in Telegram, or [click here to open it](https://t.me/payrequestme_bot). Tap **Start**. **2. Get your connect link** The bot sends you a personal connect link. Tap it — it opens PayRequest in your browser. **3. Log in to PayRequest** If you're not already logged in, enter your email to receive a magic link. Click it and you're in. **4. Done** Your Telegram account is now linked to PayRequest. The bot confirms with a message and you're ready to go. The connection is permanent — you only need to do this once. ## Commands Once connected, these commands are available inside the bot: | Command | What it does | | - | - | | `/pay 50 for design work` | Creates a payment link for €50 with the description "for design work" | | `/pay 125` | Creates a payment link for €125 (uses "Payment link" as description) | | `/links` | Shows your 5 most recent payment links with their URLs | | `/status` | Shows your 5 most recent transactions and their status | | `/disconnect` | Unlinks your PayRequest account from this Telegram chat | > [!TIP] > > You can send a payment link to a customer in seconds: `/pay 200 website project` → copy the URL the bot returns → paste it in your chat with the client. ## Payment Notifications Every time a payment is completed, you'll receive a message in the bot: ``` 💰 Payment received! Amount: €200.00 From: Jan Janssen Invoice: #INV-2026-042 Time: 14:32 ``` Notifications are instant — they arrive the moment the payment is processed, so you always know in real time. ## Managing Your Connection You can disconnect the bot at any time by sending `/disconnect`. This removes the link between your Telegram account and PayRequest — notifications will stop and commands will no longer work until you reconnect via `/start`. If you want to connect a different Telegram account to your PayRequest, first disconnect from the old account, then start fresh with the new one. > [accordion] Can multiple team members connect their own Telegram? > > Currently, one Telegram account can be connected per PayRequest account. If you use team members, the connected Telegram user receives all payment notifications for the account. > [accordion] What currency does /pay use? > > Payment links are created in your default account currency (EUR by default). You can change your default currency in **Business Settings → Invoice Settings**. > [accordion] Is the connect link safe to click? > > Yes. The link goes directly to `payrequest.app` and is unique to you. It expires after 15 minutes and can only be used once. > [accordion] Do payment links created via Telegram show up in my dashboard? > > Yes. Every link created via `/pay` appears as a Smart Link in your PayRequest dashboard under **Payment Links**, just like links created through the web interface. > [accordion] Can I use this in a Telegram group or channel? > > The bot works best in private messages. To share payment links in a group, create the link privately with `/pay` and then paste the URL in your group chat manually. ## Next Steps > [card] [Smart Links](/payment-processing/smart-links) > > Learn more about the payment links the bot creates — you can also manage them from your dashboard. > [card] [Webhooks](/organization-and-automation/webhook-configuration) > > Build custom automations triggered by payment events using webhooks. > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > See which payment methods your customers can use on your checkout page. > [card] [API Reference](/api/payment-links) > > Create payment links programmatically via the PayRequest API. # VPNresellers Source: https://docs.payreque.st/integrations/vpnresellers Connect your reseller account, sell VPN subscriptions, and let customers manage their VPN access in the customer portal # VPNresellers Connect your own VPNresellers account to deliver VPN access after confirmed payment. Each business uses its own API token and reseller balance. Customers receive one VPN account per subscription and manage their access from your customer portal. ## Before you start * Have a VPNresellers account with an API 4.1 access token and sufficient reseller credit. * Sign in as the PayRequest business owner. Team members cannot configure the connection or use the integration's recovery actions. * Configure your payment provider and customer portal for the subscriptions you want to sell. VPNresellers delivers the VPN service; it does not collect customer payments. ## Connect your account **1. Open VPNresellers** In the dashboard, go to **Sell → Services & integrations** and open **VPNresellers**, or visit `/apps/vpnresellers`. **2. Enter your API token** Paste your own API 4.1 token into **API access token** and click **Connect**. PayRequest checks the connection before saving it and stores the token encrypted. **3. Check your balance** Confirm the connection succeeds and review **Reseller balance**. Use **Test connection** to refresh the connection check. Active VPN accounts consume reseller credit daily, so keep your balance funded. To replace a token, enter the new token and click **Update connection**. Use a token for the same reseller account: existing VPN services remain linked to their original provider account. ## Create a VPN product 1. Click **Create VPN subscription** on the integration page or in **Products**. You can also select **VPN subscription** in the full product wizard when an active VPNresellers connection exists. 2. Enter the product name, description, positive price, currency and VAT settings. 3. Select your **VPN provider** under **VPN delivery**. 4. Choose billing every **one month** or **one year**. 5. Complete the wizard and save the product. Make it active and visible when you are ready to sell it. > [!NOTE] > > VPN products use recurring subscription billing with automatic VPN delivery. The first payment is charged immediately. Free trials, free plans, quantity selection and customer pausing are not supported; each subscription delivers one VPN account. When editing a VPN product, its delivery connection is preserved. Existing VPN services retain their original provider and billing period. ## Payment and access | Event | VPN access | | - | - | | First fully paid order or linked invoice | PayRequest queues VPN account creation and activation. | | Renewal paid before access expires | The new month or year extends the remaining paid access. | | Renewal paid after access expires | A new month or year starts from the payment time. | | Unpaid or failed renewal | No extra access is granted. Existing paid access lasts until its end date. | | Subscription canceled | Access remains available until the end of the paid period. | | Subscription paused, suspended or archived | VPN access is disabled during synchronization. | | Latest access-granting payment reversed | VPN access is disabled during synchronization. | PayRequest counts the initial order and its associated invoice as one paid period. Synchronization runs after relevant billing changes and reconciles services every five minutes. Delivery and status changes may therefore take a few minutes. > [!NOTE] > > The portal shows **Access paid until**. VPNresellers uses a date-only expiry, while PayRequest reconciles the paid-until time. Provider expiry processing can differ, so the remote cutoff is not guaranteed to occur at the exact displayed second. ## Customer setup Customers sign in to your customer portal, open **My services**, select their VPN subscription and open the **VPN** tab. Order details and order-completion emails can also include a **Manage VPN** link to the subscription when it is linked to the order. The tab shows the service status, **Access paid until** and the VPN username. While access is active, authorized customers can: * Click **Show VPN password** or **Hide password**. * Set a new VPN password of **12–50 characters**. Password changes are limited to one attempt per minute. * Choose a protocol and server location, then click **Download configuration**. | Protocol | Setup | | - | - | | WireGuard | Download the `.conf` file and import it into a WireGuard client. | | OpenVPN | Select a connection port, download the `.ovpn` file and import it into an OpenVPN client. Use the VPN username and password when prompted. | | VLESS | Download the `.txt` file and import its link into a compatible client. | The primary customer and contacts with **Admin** or **Operations** access can manage VPN credentials and download configurations. **Billing** and **Viewer** contacts cannot access credentials. > [!WARNING] > > Configuration files contain private access keys. Keep them private, along with the VPN password and reseller API token. ## Delivery problems Open `/apps/vpnresellers` and review **VPN services**. Each entry shows the username, status, paid-until date and any delivery error. ### Insufficient reseller credit Top up your VPNresellers balance, then click **Synchronize** for the affected service. Paying a PayRequest invoice does not top up your reseller balance. ### Connection or provider errors Use **Test connection** and check your API token. Update the connection if necessary. For a temporary provider failure, wait and retry **Synchronize**. Customers with delayed delivery should contact your business through the portal. ### Account creation needs verification If an account-creation request has an uncertain result, PayRequest searches for the original username before trying to deliver it again. It stops automatic recreation when it cannot confirm whether the account exists. 1. Click **Synchronize** to recover an existing account. 2. If the service still needs creation verification, wait at least **ten minutes** after the uncertain attempt. 3. As the business owner, click **Verify and retry creation** and confirm the action. PayRequest checks the provider account list and retries creation only if the original username is not found. ## Related guides * [Creating products](/products-and-pricing/creating-products) * [Customer portal](/customer-management/customer-portal) * [Subscription self-service](/subscriptions/customer-self-service) # X402 Autonomous Payments Source: https://docs.payreque.st/integrations/x402-autonomous-payments Let AI agents pay your invoices and access your payment page without any human interaction — using the X402 protocol and USDC on Base. # X402 Autonomous Payments X402 is an open payment protocol that uses the HTTP `402 Payment Required` status code to let AI agents pay for resources autonomously — no checkout page, no human click, no API key exchange. Your PayRequest page is already X402-compatible. Agents that speak the protocol can discover your payment requirements, sign an authorization off-chain, and settle USDC directly to your wallet in one round trip. > [!NOTE] > > X402 requires your EVM wallet to be connected in Provider Settings. The agent pays to that address directly — PayRequest never holds the funds. ## How it works **1. Agent discovers your payment endpoint** The agent reads your `payments.txt` manifest and finds your `x402_payment_endpoint`. Alternatively it calls the discovery JSON at `x402_discovery_url` to get the full payment requirements object. **2. Agent gets payment requirements (402)** The agent sends a `POST` to your payment endpoint without a payment header. PayRequest responds with HTTP `402 Payment Required` and a JSON body describing exactly what to pay: ```json theme={null} { "x402Version": 2, "error": "payment_required", "accepts": [{ "scheme": "exact", "network": "eip155:8453", "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "amount": "1000", "payTo": "0xYourWalletAddress", "maxTimeoutSeconds": 30 }] } ``` `amount` is in USDC atomic units (6 decimals): `1000` = \$0.001. **3. Agent signs the payment off-chain** The agent signs an ERC-3009 `transferWithAuthorization` message with its wallet — no gas, no on-chain transaction yet. This is just a cryptographic signature authorizing the USDC transfer. **4. Agent retries with X-Payment header** The agent sends the same request again, this time including: ``` X-Payment: base64({"x402Version":2,"payload":{"signature":"0x...","authorization":{...}},...}) ``` **5. PayRequest verifies and settles** PayRequest verifies the signature, then broadcasts `transferWithAuthorization` on Base — moving USDC from the agent's wallet directly to yours. No intermediary. The transaction is final within seconds. **6. Agent receives confirmation (200)** PayRequest responds `200 OK` with: ```json theme={null} { "success": true, "onchain_tx": "0xTxHash…", "payer": "0xAgentWalletAddress", "amount_usdc": 0.001 } ``` Plus an `X-Payment-Response` header with the settlement receipt. ## Pay a specific invoice Agents can pay a specific outstanding invoice by hitting: ``` POST /api/v1/x402/yourhandle/invoice/{invoiceId}/pay ``` The `402` response will include the exact invoice amount as the required payment. On success, the invoice is automatically marked as paid in PayRequest. This is the primary use case: an AI agent receives an invoice email, extracts the invoice ID, pays it autonomously via X402, and the invoice closes — all without a human touching the checkout. ## Discovery endpoints | Endpoint | Method | Description | | - | - | - | | `/yourhandle/payments.txt` | `GET` | Human + machine readable manifest | | `/api/v1/x402/yourhandle` | `GET` | JSON discovery: wallets, accepted networks, payment URL | | `/api/v1/x402/yourhandle/pay` | `POST` | X402 payment endpoint | | `/api/v1/x402/yourhandle/invoice/{id}/pay` | `POST` | Pay a specific invoice | ## Supported networks | Network | Token | Chain ID | | - | - | - | | Base (mainnet) | USDC | `eip155:8453` | | Base Sepolia (testnet) | USDC | `eip155:84532` | | Solana (mainnet) | USDC | `solana:5eykt4...` | ## Settlement PayRequest settles payments by calling `transferWithAuthorization` on the USDC contract. This moves funds directly from the agent's wallet to yours — PayRequest acts as a broadcast relay, not a custodian. Settlement uses the Base public RPC by default. No Coinbase CDP account is required. > [!TIP] > > You can use Base Sepolia testnet USDC to test X402 payments before going live. Set `X402_TESTNET=true` in your environment to switch endpoints to testnet. ## For developers building agents If you're building an AI agent that needs to pay PayRequest users autonomously: 1. **Discover** — `GET https://payrequest.me/{handle}/payments.txt` or the JSON discovery endpoint 2. **Get requirements** — `POST` to the payment endpoint, expect a `402` response 3. **Sign** — Use `viem`, `ethers.js`, or any EIP-712 library to sign `TransferWithAuthorization` 4. **Pay** — Retry the `POST` with the `X-Payment` header 5. **Confirm** — `200` response + `X-Payment-Response` header = settled The full protocol specification is at: > [card] [X402 spec on GitHub](https://github.com/PayRequest/payments-txt/blob/main/spec/x402-integration.md) > > Complete request/response format, header schemas, and network reference. ## Frequently asked questions > [accordion] Does this require gas fees? > > No — not for the agent. The agent only signs an off-chain ERC-3009 authorization; it never needs ETH or any gas balance. PayRequest's own wallet broadcasts the `transferWithAuthorization` transaction on Base and pays the (tiny, roughly \$0.001) gas cost itself. Agent developers don't need to fund a wallet with ETH to use X402. > [accordion] What wallets can agents use? > > Any EVM-compatible wallet that can sign EIP-712 typed data. Smart contract wallets (Safe, Coinbase Smart Wallet) are also supported since ERC-3009 handles those signatures. > [accordion] Can I set a minimum payment amount? > > The default per-call amount is \$0.001 USDC. For invoice payments, the amount is always the invoice total. Custom minimum amounts per-user are on the roadmap. > [accordion] What if verification fails? > > If the signature is invalid, expired, or the amount is too low, PayRequest returns another `402` with the `verification_error` field explaining what went wrong. The agent can retry with a fresh signature. > [accordion] Is this the same X402 as Coinbase's? > > Yes — PayRequest implements the [open X402 spec](https://github.com/coinbase/x402) published by Coinbase. Any agent built against that spec works with PayRequest. No Coinbase account is needed on your end. # Zapier Integration Source: https://docs.payreque.st/integrations/zapier Connect PayRequest to thousands of apps and automate payments, subscriptions, and payment links without code. # Automate PayRequest with Zapier The official PayRequest integration for Zapier lets you start workflows from successful payments and subscription events. You can also create PayRequest payment links from other apps. > [!NOTE] > > Zapier uses real-time REST Hooks for the new payment and subscription triggers. Your Zap runs as soon as PayRequest records the event; it does not need to wait for a polling interval. ## What You Can Automate > [card] Payment succeeded > > Run a Zap after a payment is successfully completed in PayRequest. > [card] Subscription created > > Run a Zap when a subscription is created, including subscriptions that are still pending activation. > [card] Subscription activated > > Run a Zap when a subscription or trial becomes active. > [card] Subscription renewed > > Run a Zap after a subsequent recurring subscription payment succeeds. The initial payment is not reported as a renewal. > [card] Subscription cancelled > > Run a Zap when a subscription is cancelled in PayRequest. > [card] Create payment link > > Create an amount-based PayRequest payment link from another Zapier app. You can also use **Find Subscription** to retrieve a subscription by its PayRequest ID. ## Connect Your Account **1. Open Zapier settings in PayRequest** Sign in to PayRequest and open [Settings → Integrations](https://payrequest.app/zapier). **2. Create a dedicated token** Select **Create Zapier token**. PayRequest creates a token with the `billing.read` and `billing.write` permissions required by the integration. Copy the token immediately. For security, its value is shown only once. **3. Open PayRequest in Zapier** Select **Open Zapier**, or open the [PayRequest integrations page](https://zapier.com/apps/payrequest/integrations). Create a Zap and choose PayRequest as the trigger or action app. **4. Connect your PayRequest account** When Zapier asks for your PayRequest API token, paste the token you just created. Zapier tests the connection before continuing. **5. Choose an event and test** Select a payment or subscription event. Zapier loads recent PayRequest data so you can map fields into the next step of your workflow. > [!WARNING] > > Treat the API token like a password. Do not send it by email, place it in a spreadsheet, or paste it into a Zap field other than the PayRequest account connection screen. ## Payment Data The **Payment succeeded** trigger includes fields such as: | Field | Description | | - | - | | Payment ID | Unique PayRequest transaction ID | | Amount and currency | Paid decimal amount and ISO currency code | | Customer | Customer ID, display name, and email address | | Payment method | Method used for the payment | | Payment provider | Provider that processed the payment | | Paid at | ISO 8601 payment timestamp | | Invoice, order, or subscription ID | Related PayRequest record when available | PayRequest uses its transaction record as the source of truth for the amount and payment timestamp. ## Subscription Data Subscription triggers include: | Field | Description | | - | - | | Subscription ID | Unique PayRequest subscription ID | | Status | Current subscription status | | Name and product | Subscription and product information | | Amount, currency, and interval | Recurring billing details | | Customer | Customer ID, display name, and email address | | Next payment at | Scheduled next billing time, when available | | Cancellation details | Cancellation time and reason, when available | | Renewal payment ID | Transaction that caused a renewal event | > [!TIP] > > Use **Subscription created** when you need to prepare work before payment activation. Use **Subscription activated** when the next step should happen only after access or billing becomes active. ## Example Zaps * Add a customer to your CRM after a successful payment * Send a Slack or Microsoft Teams message for a new subscription * Grant course or community access after subscription activation * Update a customer record after every renewal * Start an offboarding workflow after cancellation * Create a PayRequest payment link from a form submission ## Manage Tokens and Connections The PayRequest **Settings → Integrations** page shows: * How many active Zap subscriptions are registered * Which dedicated Zapier tokens exist * When each token was created and when it expires * A control to revoke tokens that are no longer used Existing token values cannot be displayed again. If you lose a token, create a new one, reconnect the PayRequest account in Zapier, and then revoke the old token. Revoking a token immediately prevents Zapier from accessing PayRequest with that connection. Zaps using it will stop until you reconnect them with a valid token. ## Troubleshooting > [accordion] Zapier says "Unauthenticated" > > Open **Settings → Integrations**, create a new Zapier token, and reconnect the PayRequest account inside Zapier. Make sure you paste only the token value and do not add `Bearer` before it. > [accordion] Zapier cannot pull subscriptions > > First test the PayRequest account connection in Zapier. If authentication succeeds, make sure the PayRequest account contains at least one subscription that matches the selected trigger. The subscription sample must belong to the same PayRequest business as the token. > [accordion] A trigger test returns no records > > Create or update the relevant record in PayRequest, then test the trigger again. For example, **Subscription cancelled** needs a cancelled subscription to provide a real sample. > [accordion] A Zap stopped running after I revoked a token > > Reconnect the PayRequest account in Zapier with a new token, then update the affected Zaps to use that connection. > [accordion] Will the same payment trigger a Zap more than once? > > Each event includes a stable unique ID. Zapier uses this ID for deduplication, while PayRequest delivers each active REST Hook subscription independently. ## Next Steps > [card] [API authentication](/api/authentication) > > Learn how PayRequest API tokens and permissions work. > [card] [Webhooks](/api/webhooks) > > Build a direct webhook integration when you need custom code. > [card] [Subscription lifecycle](/subscriptions/subscription-lifecycle) > > Understand subscription statuses and lifecycle events. > [card] [Payment links API](/api/payment-links) > > Create payment links directly through the API. # Bulk Invoice Actions Source: https://docs.payreque.st/invoices/bulk-invoice-actions Mark multiple invoices as paid, send reminders in bulk, or export your invoices to CSV # Bulk Invoice Actions Instead of opening invoices one at a time, the **Bulk Actions** tool lets you select a group of invoices and apply an action to all of them at once. > [!NOTE] > > Bulk Actions is available from **Bulk Actions** in your dashboard. It works across several entity types (customers, subscriptions, products, invoices, orders) — this page covers the invoice-specific actions. ## How It Works **1. Choose the entity type** Open **Bulk Actions** and select **Invoices**. **2. Select which invoices to include** Choose **Manual** selection to pick individual invoices from the list (with search), or **Tags** selection to automatically include every invoice matching one or more tags (match **any** tag or **all** tags). **3. Choose an action** * **Mark as Paid** — sets the selected invoices' status to Paid * **Send Reminders** — sends a payment reminder email to each selected invoice's customer **4. Review and confirm** PayRequest shows a summary of the affected invoices before you confirm. **5. Execute** The action runs against every selected invoice in a single transaction. If it fails partway through, nothing is applied. ## Send Reminders Behavior The **Send Reminders** bulk action only sends to invoices that are actually eligible: * Skips invoices that aren't **Open** or **Pending** * Skips invoices where the customer has no email address * Skips customers whose email has been suppressed (e.g., due to previous bounces) * Each reminder sent is recorded in the invoice's reminder history, same as a reminder sent from the invoice detail page ## Exporting Invoices Exporting is a separate bulk type from the invoice actions above. Choose **Export** as the entity type, then **Export Invoices** as the action. This downloads a CSV with one row per invoice: | Column | Description | | - | - | | ID | Internal invoice ID | | Number | Invoice number | | Customer | Customer display name, email, or client name snapshot | | Amount (EUR) | Invoice amount before tax | | Tax (EUR) | Calculated tax amount | | Total (EUR) | Amount including tax | | Status | Current invoice status | | Date | Invoice date | | Due Date | Due date | | Tags | Comma-separated list of applied tags | You can export all of your invoices, or filter the export to invoices matching selected tags — same tag matching options as manual bulk actions. ## Action History Every bulk action run — successful or failed — is recorded, including: * How many invoices were affected * Which specific invoices were included * Whether the action completed or failed (and the error, if it failed) This history is viewable from the Bulk Actions screen so you can confirm what ran and when. > [!WARNING] > > Bulk actions validate that every selected invoice belongs to your account before running — you can't accidentally act on another business's invoices even if an ID were guessed or tampered with. ## FAQ > [accordion] Can I bulk-apply payment reminders schedules or late fees? > > Bulk actions for invoices currently cover marking as paid and sending reminder emails. Reminder **schedules** (days before/after, frequency) are configured per invoice or via your business's default — see [Payment Reminders](/invoices/payment-reminders). > [accordion] Will Send Reminders send a duplicate email if I already sent one manually? > > Yes, bulk reminders don't check whether a reminder was already sent recently — each run sends a new email to every eligible selected invoice. > [accordion] Can I undo a bulk action? > > No, bulk actions aren't reversible automatically. For "Mark as Paid," you'd need to manually change the status back on each invoice. ## Next Steps > [card] [Payment Reminders](/invoices/payment-reminders) > > Configure automatic reminder schedules > [card] [Creating Invoices](/invoices/creating-invoices) > > Learn the invoice creation flow > [card] [Email Templates](/invoices/email-templates) > > Customize the reminder emails sent in bulk > [card] [Debt Collection](/debt-collection/overview) > > Escalate invoices that reminders haven't resolved # Consolidated Invoicing Source: https://docs.payreque.st/invoices/consolidated-invoicing Combine multiple subscription charges into a single invoice per customer to reduce emails and transaction costs # Consolidated Invoicing When customers have multiple subscriptions, they normally receive a separate invoice for each one. Consolidated invoicing bundles all subscription charges into a single periodic invoice per customer — reducing email noise and saving on transaction costs. > [!NOTE] > > Consolidated invoicing requires a two-step setup: enable it globally in **Settings**, then opt in individual customers. Only subscription charges are consolidated — manual invoices and shop orders are not affected. > [card] Fewer Emails > > Customers receive one invoice instead of many, reducing inbox clutter and improving the payment experience. > [card] Lower Costs > > Each Mollie SEPA Direct Debit transaction costs \~€0.29. Consolidating 5 subscriptions into 1 invoice saves €1.16 per billing cycle. > [card] Flexible Scheduling > > Choose monthly, bi-weekly, or weekly consolidation with a configurable anchor day. > [card] Per-Customer Control > > Enable consolidation globally, then opt in specific customers. Each customer can have their own frequency override. ## How It Works **1. Enable in Settings** Go to **Settings** > **Consolidated Invoicing** and toggle the feature on. Choose a default frequency (monthly, bi-weekly, or weekly) and set the anchor day using the slider. **2. Opt In Customers** Edit a customer and scroll to the **Invoice Consolidation** section. Toggle **Enable Consolidated Invoicing** for that customer. Optionally set a custom frequency or anchor day override. **3. Charges Are Collected** When a subscription billing cycle triggers, instead of creating an invoice immediately, the charge is stored as a **pending item**. The subscription's next billing date still advances normally. **4. Consolidated Invoice Generated** On the anchor day, all pending items for the customer are bundled into a single consolidated invoice. For customers with a Mollie mandate, a single payment is created automatically. For bank transfer customers, a single invoice email is sent. ## Setting Up ### Global Settings Navigate to **Settings** > **Consolidated Invoicing** to configure the defaults. | Setting | Description | | - | - | | **Enable Consolidated Invoicing** | Master toggle for the entire feature | | **Default Frequency** | How often consolidated invoices are generated: Monthly, Bi-weekly, or Weekly | | **Anchor Day** | Day of the month (1-28) when invoices are generated. For weekly frequency, this becomes day of the week | The settings page also shows how many customers are opted in and how many pending items are waiting. > [!TIP] > > Use anchor day **28** if you want end-of-month invoicing. This avoids issues with months that have fewer than 31 days. ### Per-Customer Settings Edit any customer and look for the **Invoice Consolidation** section (only visible when the global feature is enabled). | Setting | Description | | - | - | | **Enable Consolidated Invoicing** | Opt this customer in to receive consolidated invoices | | **Frequency Override** | Override the business default frequency for this customer. Leave empty to use the default | | **Anchor Day Override** | Override the anchor day. Slide to **0** to use the business default | ## Consolidated Invoices Consolidated invoices appear in your invoice list with an **indigo "Consolidated" badge**. You can filter the invoice list by the **Consolidated** tab to see only these invoices. ### What's on the Invoice Each consolidated invoice includes: * A line item for each subscription charge in the period * The billing period (e.g., "Mar 2026") shown in the invoice notes * Subscription name and amount per line item * Total amount combining all charges ### Invoice Detail View When viewing a consolidated invoice, line items are grouped by subscription with a header showing the subscription name. ## Cancellation Handling If a subscription is canceled while it has pending (not yet invoiced) items, those pending items are automatically **voided** — they won't appear on the next consolidated invoice. ## FAQ > [accordion] What happens if a customer only has one subscription? > > The consolidation still works — they'll receive a single invoice with one line item. This is useful for consistency if you plan to add more subscriptions later. > [accordion] Can I consolidate manual invoices or shop orders? > > No. Only subscription charges are consolidated. Manual invoices and shop orders are created and sent independently. > [accordion] What if a customer has subscriptions in different currencies? > > Separate consolidated invoices are generated per currency. For example, a customer with EUR and USD subscriptions would receive two consolidated invoices. > [accordion] Does the customer see that it's a consolidated invoice? > > Yes. The invoice notes indicate it's a consolidated invoice and show the billing period. Each line item shows the subscription it belongs to. > [accordion] When are consolidated invoices generated? > > Consolidated invoices are generated automatically every morning on the anchor day you configured. Subscription charges are collected throughout the period and bundled into a single invoice. ## Next Steps > [card] [Billing Cycles](/subscriptions/billing-cycles) > > Learn about subscription billing intervals and timing > [card] [Payment Reminders](/invoices/payment-reminders) > > Set up automatic reminders for unpaid invoices # Creating Invoices Source: https://docs.payreque.st/invoices/creating-invoices How to create one-off invoices and credit notes with line items, tax, and payment reminders # Creating Invoices Invoices in PayRequest let you bill a customer directly, outside of a shop order or subscription — for services, one-off products, or anything you need to charge for manually. Each invoice supports product-based or custom line items, automatic tax calculation, and optional payment reminders. > [!NOTE] > > You need at least one customer on file before you can create an invoice — the customer is a required field on the invoice form. ## How It Works **1. Open the invoice form** Go to **Invoices** in the sidebar, then click **New Invoice**. **2. Review the invoice details** * **Invoice Number** is pre-filled based on your [numbering format](/business-settings/invoice-settings) and is editable, but must be unique per business * **Invoice Date** defaults to today * **Due Date** defaults to 14 days from today * **Reference** is an optional free-text field **3. Select the customer** Pick a customer from the dropdown. If the customer is marked **tax exempt**, all line item tax rates are automatically set to 0%. **4. Add line items** Click **Add Product Item** or **Add Custom Item** for each line: * **Product items** — selecting a product auto-fills its name, description, unit price, and tax rate * **Custom items** — enter the name, description, quantity, unit price, and tax rate manually Quantity, unit price, and tax rate can all be edited per line regardless of item type. Totals (subtotal, tax, grand total) recalculate live as you edit. **5. Configure payment reminders (optional)** Toggle **Enable Payment Reminders** to have PayRequest automatically email the customer before and after the due date. This toggle is on by default if your business has **Auto-enable payment reminders** turned on. See [Payment Reminders](/invoices/payment-reminders) for the full schedule options. **6. Save the invoice** Saving creates the invoice with status **Pending**, advances your invoice number sequence, and automatically emails an "Invoice Created" notification to the customer (using your [Email Templates](/invoices/email-templates) if configured). ## Invoice Statuses | Status | Meaning | | - | - | | **Draft** | Not yet finalized | | **Open / Pending** | Sent to the customer, awaiting payment (new invoices start as **Pending**) | | **Paid** | Payment received — set automatically when the linked Mollie payment succeeds, or manually | | **Overdue** | Not a stored status — a computed view of any open/pending/unpaid invoice past its due date | | **Cancelled** | Voided, no longer collectible | | **Chargeback** | Payment was disputed/reversed after being marked paid | > [!NOTE] > > Status can also be changed manually from the invoice detail page. Changing an invoice **away from Paid** requires entering a reason, which is logged to the invoice's activity history. ## Credit Notes For corrections to an existing invoice, follow the [Credit Notes guide](/invoices/credit-notes). It covers full and partial credits, Mollie and manual refunds, customer notifications, and status checks. The same form doubles as a credit note creator. Toggle **Credit Note** at the top of the form to switch modes: * For an existing invoice, use **Credit invoice** on that invoice's detail page. Selecting **Original Invoice** here takes you to that page when you save, so credit limits and refund tracking use the same protected flow. * Line item amounts are stored as negative values * The credit note is created with status **Paid** immediately (it represents a reduction, not something awaiting payment) * An email is sent to the customer if they have an email address on file > [!NOTE] > > Payment reminders aren't available for credit notes — the reminder toggle is disabled automatically when Credit Note mode is on. ## Tax on Line Items Each line item stores its own tax rate. When line pricing is tax-inclusive, PayRequest extracts the tax portion from the line total rather than adding it on top. See [Tax Configuration for Invoices](/invoices/tax-configuration) for the full breakdown of tax-exempt customers, product tax rates, and mixed rates. ## FAQ > [accordion] Can I edit an invoice after saving it? > > Yes. Open the invoice and use the **Edit** action — you can change the customer, dates, and line items. Editing replaces all existing line items with the ones on the edit form. > [accordion] Is the customer emailed automatically when I create an invoice? > > Yes, an "Invoice Created" email is dispatched automatically (or "Credit Note Created" for credit notes), using your custom email template if you've set one up, or a default template otherwise. > [accordion] What happens to my invoice number sequence? > > Every saved invoice (regular or credit note) advances your next invoice number, based on the format configured in [Invoice Settings](/business-settings/invoice-settings). > [accordion] Can I create an invoice for a tax-exempt customer and still charge tax on one item? > > The tax rate defaults to 0% for all items when the customer is tax exempt, but you can manually change an individual line's tax rate afterward if needed. ## Start from an agreed quote For proposed work that needs approval first, use [From quote to invoice](/invoices/quotes-to-invoices). Approval is not payment; check for a linked invoice before converting an approved quote again. A quote advance-payment invoice collects money and is separate from a security-deposit hold. ## Next Steps > [card] [Invoice Settings](/business-settings/invoice-settings) > > Configure your invoice numbering format > [card] [Invoice Templates](/invoices/invoice-templates) > > Customize your invoice logo and footer > [card] [Payment Reminders](/invoices/payment-reminders) > > Automate follow-ups for unpaid invoices > [card] [Bulk Invoice Actions](/invoices/bulk-invoice-actions) > > Mark invoices as paid or send reminders in bulk # Credit Notes Source: https://docs.payreque.st/invoices/credit-notes Correct an invoice with a linked credit note and track refunds separately A credit note reduces an amount previously invoiced. PayRequest creates a numbered negative document with a PDF and a link to the original invoice. The original invoice stays available for your records. > [!NOTE] > > Issuing a credit note does not mean a refund has completed. The credit document and the return of money are tracked separately. ## Credit a paid invoice **1. Open the original invoice** Open its detail page and choose **Credit invoice**. **2. Choose the amount** Choose **Full remaining amount**, **A specific amount**, or **Selected invoice lines**. Custom amounts include VAT; credits preserve the original lines' VAT rates. Existing credits and refunds reduce the amount available. **3. Enter a reason and choose the refund method** Enter a reason, such as a charge after cancellation. Choose **Refund through Mollie** to return money through the original Mollie payment, or **Refund manually** to transfer it yourself. **4. Choose whether to notify the customer** Leave **Email the credit note to the customer** selected if you want a notification. Review the negative total, then select **Issue credit note**. **5. Check the result** The original invoice shows the linked credit note and its refund status. Customers can also see the credit document and settlement status in their portal. ## Understand refund statuses | Status | What it means | What to do | | - | - | - | | Refund in progress | Mollie has a pending, queued, or processing refund | Wait for completion; use **Check refund status** to refresh | | Refund completed | The provider reports the refund completed | No further refund action is needed | | Manual refund required | The credit exists, but you still need to transfer the money | Transfer it, then enter the bank or payment reference and select **Record completed manual refund** | | Refund needs verification | The outcome of a provider request is uncertain | Use **Check refund status**; verify the existing refund before taking further action | | Rejected, failed, or canceled | The refund was rejected or the provider confirmed it failed or was canceled | Review the cause and use **Retry refund** when appropriate | PayRequest checks outstanding Mollie refund statuses every five minutes. **Check refund status** searches for the existing refund. A retry after a confirmed failure uses the same credit note. > [!WARNING] > > Do not issue another credit note or transfer money manually just because a Mollie refund is still pending or needs verification. First establish what happened to the original refund. The original paid invoice remains **Paid**. A credit document may also have an accounting status of **Paid**; use its separate refund status to determine whether money has been returned. ## Credit an unpaid invoice Choose **Credit invoice** to credit an eligible unpaid invoice in full. PayRequest creates the linked credit note, cancels the original invoice, stops its payment link and reminders, and cancels awaiting bank-transfer matching instructions. No refund is requested. An existing or in-flight payment, or an active debt-collection case, must be checked before crediting. Partial credits on unpaid invoices and credits to a customer balance are not currently supported by this flow. ## Customer email and language The notification uses the **Credit Note Created** email template. An inactive template prevents this notification from being sent. Without a saved template, PayRequest uses its default content. Default text uses the customer's configured language when translations are available; without a customer language, the fallback is English. Your custom template text is used as written and is not automatically translated. After issuing the credit, check the invoice's email history to confirm sending. The credit note's existence and a pending refund are not proof that an email was sent. A send confirmation also does not prove delivery to the customer's inbox. ## Limits and older invoices You can issue multiple credits while enough amount remains available. Refunds linked to credit notes are counted once. The minimum credit is €0.01. Older credits or refunds without known line allocations can prevent selected-line credits; use the amount option when available. > [card] [Email Templates](/invoices/email-templates) > > Configure credit notifications and customer language. > [card] [Refund Requests](/invoices/refund-requests) > > Review customer requests before issuing a credit. # Duplicate Invoices Source: https://docs.payreque.st/invoices/duplicate-invoices Learn how to quickly create copies of existing invoices to save time when billing for similar services or recurring work # Duplicate Invoices The invoice duplication feature allows you to quickly create copies of existing invoices, saving you time when you need to bill for similar services or create recurring invoices with the same line items. ## Why Use Invoice Duplication? Invoice duplication is perfect when you need to: * Bill a customer for the same services again * Create similar invoices for different customers * Set up recurring billing without subscription automation * Re-issue an invoice that was cancelled or voided * Create template-style invoices for common billing scenarios ## How to Duplicate an Invoice ### Step 1: Navigate to the Invoice 1. Go to your dashboard 2. Click on **Invoices** in the sidebar 3. Find the invoice you want to duplicate 4. Click on the invoice to open its detail page ### Step 2: Duplicate the Invoice 1. On the invoice detail page, look for the **Duplicate** button in the action menu 2. Click the **Duplicate** button 3. The system will automatically create a new invoice ### Step 3: Review Your New Invoice After duplication, you'll be automatically redirected to the new invoice where you can: * Review all copied details * Make any necessary adjustments * Send it to your customer when ready ## What Gets Copied? When you duplicate an invoice, the following information is copied: ### Customer Information * Customer name and contact details * Billing address * Any customer-specific settings ### Invoice Items * All line items (products and custom items) * Quantities and unit prices * Descriptions and notes * Tax rates and calculations ### Invoice Settings * Currency * Tax configuration * Notes and terms ## What Gets Changed Automatically? To ensure your duplicated invoice is ready to use, these fields are automatically updated: | Field | Original Value | New Value | | - | - | - | | Invoice Number | Original number | New sequential number | | Status | Any status | **Concept** | | Invoice Date | Original date | **Today's date** | | Due Date | Original due date | **30 days from today** | | Payment ID | Linked payment | **Cleared** | > [!NOTE] > > The new invoice always starts as a **Concept** so you can review and edit it before sending to your customer. ## Common Use Cases ### Monthly Retainer Billing For clients on a monthly retainer: 1. Create the first month's invoice with all services 2. Each month, open the previous invoice and duplicate it 3. Adjust the date range or description if needed 4. Send to your client ### Similar Services for Different Clients When you provide the same service package to multiple clients: 1. Create a detailed invoice for one client 2. Duplicate it 3. Change the customer to the new client 4. Adjust pricing if needed ### Correcting Invoices If you need to re-issue an invoice: 1. Open the original invoice 2. Duplicate it 3. Make the necessary corrections 4. Cancel or void the original if appropriate ### Creating Invoice Templates Build a library of "template" invoices: 1. Create invoices for your common service packages 2. Keep them as concepts 3. Duplicate when needed for actual billing 4. Customize for each customer ## Step-by-Step Workflow ### For Recurring Monthly Billing ``` Original Invoice (#2024-001) ├── Service: Monthly Retainer ├── Amount: €500.00 ├── Customer: Acme Corp └── Status: Paid ↓ Click "Duplicate" New Invoice (#2024-002) ├── Service: Monthly Retainer ├── Amount: €500.00 ├── Customer: Acme Corp ├── Date: Today ├── Due Date: 30 days from now └── Status: Concept ← Ready to edit and send! ``` ## Tips for Effective Invoice Duplication ### Before Duplicating * Ensure the original invoice has accurate line items * Verify tax rates are correct * Check that product references are up to date ### After Duplicating 1. **Update the description** if it contains date references 2. **Verify the customer** is correct (especially when duplicating for a different client) 3. **Check the amounts** - prices may have changed 4. **Review the due date** - 30 days may not suit all clients 5. **Add any new items** that should be included ### Organization Tips * Use clear invoice numbers for easy tracking * Add internal notes to track duplicated invoices * Consider using tags to group related invoices ## Frequently Asked Questions **Q: Does duplicating an invoice affect the original?** A: No, the original invoice remains completely unchanged. Duplication creates an entirely new, independent invoice. **Q: Can I duplicate a paid invoice?** A: Yes! You can duplicate invoices regardless of their status (concept, sent, paid, overdue, etc.). The new invoice will always start as a concept. **Q: What happens to the invoice number?** A: A new invoice number is automatically generated following your invoice numbering sequence. This ensures all your invoices have unique numbers. **Q: Can I duplicate an invoice to a different customer?** A: The duplicate is created for the same customer, but you can change the customer after duplication by editing the new invoice. **Q: Are attachments duplicated?** A: Attachments are not duplicated to avoid unnecessary file duplication. You can add attachments to the new invoice manually if needed. **Q: Is there a limit to how many times I can duplicate an invoice?** A: No, you can duplicate invoices as many times as needed. **Q: Can I undo a duplication?** A: You can delete the duplicated invoice if you don't need it. The original invoice is never affected. ## Related Features * [Creating Invoices](/invoices/creating-invoices) - Learn how to create invoices from scratch * [Invoice Templates](/invoices/invoice-templates) - Set up reusable invoice templates * [Bulk Invoice Actions](/invoices/bulk-invoice-actions) - Manage multiple invoices at once * [Payment Reminders](/invoices/payment-reminders) - Automate payment follow-ups # Email Templates Source: https://docs.payreque.st/invoices/email-templates Customize the emails PayRequest sends automatically for invoices, orders, and subscriptions # Email Templates Every new PayRequest account gets a set of default email templates for the automated emails PayRequest sends — invoice notifications, payment reminders, order confirmations, and subscription lifecycle emails. You can customize the subject and content of each one to match your brand's voice. > [!NOTE] > > Email Templates are managed on the **Email Templates** page in your dashboard. A default template is created automatically for every template type when your account is created, so customization is optional. ## Template Types Templates that affect invoices: | Type | Sent When | | - | - | | **Invoice Created** | A new invoice is created and (if applicable) emailed to the customer | | **Invoice Paid** | An invoice's status changes to Paid | | **Payment Reminder** | An automatic or manual payment reminder is sent for an unpaid invoice | | **Credit Note Created** | A credit note is created | Other template types cover orders and subscriptions (Order Confirmation, Order Completed, Subscription Created, Subscription Renewal, Subscription Ended, Subscription Payment Failed, Subscription Suspended, Subscription Price Increase) and use the same editor. ## How It Works **1. Open Email Templates** Go to **Email Templates** in your dashboard. **2. Select a template to edit** Click on any template type to open the editor. **3. Edit the subject and content** Both fields support the template variables listed below — wrap a variable name in double curly braces, e.g. `{{invoice_number}}`. **4. Toggle active/inactive** For **Invoice Created** and **Credit Note Created**, turning an existing template **off** prevents the notification from being sent. When no saved template exists, these notifications use PayRequest's default content. **5. Save** Changes apply to every future email of that type immediately. > [!TIP] > > Click **Use Default Content** in the editor at any time to reset a template's body back to PayRequest's built-in version, in case you want to start over. ## Available Variables Variables are replaced with real values when the email is sent. All templates have access to these common variables: | Variable | Description | | - | - | | `{{business_name}}` | Your business name | | `{{business_email}}` | Your account email | | `{{customer_name}}` | The recipient's display name | | `{{customer_email}}` | The recipient's email address | | `{{current_date}}` | Today's date | Invoice-related templates (**Payment Reminder**, **Invoice Created**, **Invoice Paid**, **Credit Note Created**) additionally have: | Variable | Description | | - | - | | `{{invoice_number}}` | The invoice number | | `{{invoice_amount}}` | The invoice total, formatted as currency | | `{{invoice_due_date}}` | The invoice due date | | `{{payment_link}}` | Direct link to pay the invoice | | `{{invoice_items}}` | An HTML table of the invoice's line items with subtotal, tax, and total | > [!NOTE] > > Available variables are shown in the editor for the template type you're editing, so you don't need to memorize them. ## Localization If you haven't customized a template's subject or content, PayRequest automatically shows it in the customer's language when translations are available. As soon as you type your own custom text into a template, your text is used as-is and is not automatically translated. ## FAQ > [accordion] What happens if I delete all the text from a template? > > Use **Use Default Content** to restore the built-in body. Do not leave an active template empty. Turning an invoice-created or credit-note-created template inactive stops that notification instead of restoring its content. > [accordion] Can I use HTML in my templates? > > Yes. Template content is rendered as HTML, so you can use basic tags for formatting, links, and styling — this is how the default templates create buttons and tables. > [accordion] Do email templates apply to manually resent invoices? > > Yes. Any time PayRequest sends an "Invoice Created," "Invoice Paid," "Payment Reminder," or "Credit Note Created" email — whether triggered automatically or by a manual action like a bulk reminder — it uses your active template for that type. ## Next Steps > [card] [Payment Reminders](/invoices/payment-reminders) > > Configure when reminder emails are sent > [card] [Creating Invoices](/invoices/creating-invoices) > > Learn the invoice creation flow that triggers these emails > [card] [Invoice Templates](/invoices/invoice-templates) > > Customize the visual appearance of the invoice document itself > [card] [Bulk Invoice Actions](/invoices/bulk-invoice-actions) > > Send reminder emails to multiple invoices at once # Invoice Payment Links Source: https://docs.payreque.st/invoices/invoice-payment-links Learn how to share payment links with customers and manage invoice payments ## Overview Invoice payment links make it easy for your customers to pay their invoices online. Every invoice in PayRequest automatically gets a unique payment link that you can share with customers via email, messaging apps, or any other channel. ## How Payment Links Work When you create an invoice, PayRequest automatically generates a secure payment link for it. This link: * **Pre-fills all invoice information** - Amount, customer details, and invoice items * **Shows invoice status** - Customers see if the invoice is paid, pending, or overdue * **Works on any device** - Mobile-friendly payment experience * **Never expires** - The link remains valid until the invoice is paid * **Is unique per invoice** - Each invoice has its own dedicated link ## Payment Link Format Payment links use your PayRequest business name: ``` https://payrequest.me/yourbusiness?invoice=132 ``` **Why payrequest.me?** Payment links always use the PayRequest.me domain for security and reliability, even if you have a custom shop domain configured. Your custom domain is reserved for your shop storefront. ## Sharing Payment Links ### From the Invoice List 1. Go to **Invoices** in your dashboard 2. Find the invoice you want to share 3. Click the **three dots (⋮)** next to the invoice 4. Click **"Payment Link"** 5. The link opens in a new tab - copy the URL to share it ### From Invoice Details When viewing a specific invoice, you have two options: #### Share Link Button 1. Open the invoice details page 2. Click the **"Share Payment Link"** button in the header 3. A modal opens with: * The full payment link (click to copy) * A QR code for easy mobile scanning * Options to share directly #### Pay Now Button * If the invoice is unpaid, you'll see a **"Pay Now"** button * Click it to open the payment page in a new tab * Copy the URL from your browser to share with the customer ## What Customers See When customers open a payment link, they see: ### Invoice Information Header * **Your business name and logo** * **Invoice number** (e.g., "Invoice #132") * **Status badge** with color coding: * 🟢 **Green** = Paid * 🟡 **Yellow** = Pending payment * ⚪ **Gray** = Open/Draft * 🔴 **Red** = Overdue or Failed ### For Unpaid Invoices * All invoice items with descriptions and prices * Payment method options (iDEAL, Credit Card, etc.) * Customer information pre-filled * "Pay Now" button to complete payment ### For Paid Invoices * ✅ **Success message** confirming payment * Payment date and time * Complete list of purchased items * Total amount paid * **No payment form** (prevents accidental double payments) ## Using Payment Links in Emails ### Automatic Email Links When you send invoice emails from PayRequest, payment links are automatically included in the email template. Customers can click directly from their inbox. ### Manual Email Sharing To share a payment link via your own email: 1. Get the payment link from your dashboard 2. Write your email message 3. Add the link as a button or hyperlink: ``` Hi [Customer Name], Your invoice #132 is ready for payment. Click here to pay: https://payrequest.me/yourbusiness?invoice=132 Thank you! ``` ## Payment Link Best Practices ### ✅ Do's * **Include context** - Always mention the invoice number when sharing links * **Add due dates** - Let customers know when payment is expected * **Use reminders** - Set up automatic payment reminders for overdue invoices * **Test the link** - Click it yourself before sharing to ensure it works * **Track payments** - Check your dashboard for payment confirmations ### ❌ Don'ts * **Don't share via unsecured channels** - Avoid posting payment links publicly * **Don't modify the URL** - Share the complete link as-generated * **Don't create duplicate invoices** - Use the retry feature if payment fails * **Don't share expired links** - Links work until paid, but keep invoices current ## Sharing Payment Links via QR Code QR codes make it easy for customers to pay from their mobile devices: ### Generating QR Codes 1. Open the invoice details 2. Click **"Share Payment Link"** 3. The modal displays a QR code automatically 4. Customers can scan with their phone camera ### Where to Use QR Codes * **Printed invoices** - Include QR code on PDF invoices * **In-person payments** - Show QR code on tablet or phone * **Physical locations** - Display on counters or signage * **Receipts** - Add to printed receipts for easy re-ordering ## Payment Methods Available When customers use payment links, they can pay with: * **iDEAL** - Direct bank payments (Netherlands) * **Credit/Debit Cards** - Visa, Mastercard, American Express * **SEPA Direct Debit** - For recurring subscriptions * **Bank Transfer** - Manual payment instructions * **Other local methods** - Based on your payment provider settings The available methods depend on which payment providers you've connected in your PayRequest settings. ## Security & Privacy Payment links are secure: * ✅ **HTTPS encryption** - All payment pages use secure connections * ✅ **No sensitive data** - Links don't contain payment information * ✅ **PCI compliant** - Payment processing meets industry standards * ✅ **Fraud prevention** - Built-in security checks * ✅ **Audit trail** - All payments are logged and tracked ## Tracking Payment Link Usage ### Monitor Link Activity In your dashboard, you can track: * **Payment status** - See which invoices have been paid * **Payment date/time** - Know exactly when payment was received * **Payment method** - Track how customers prefer to pay * **Failed payments** - Identify invoices needing follow-up ### Activity Log Every time a customer uses a payment link, the action is recorded: 1. Go to **Activity** in your dashboard 2. Filter by invoice number 3. See all payment attempts and completions ## Common Scenarios ### Scenario 1: Customer Wants to Pay Later **Situation:** Customer receives invoice but wants to pay next week **Solution:** * Payment link remains valid * Customer can bookmark the link * Or you can resend it when they're ready ### Scenario 2: Payment Link Not Working **Situation:** Customer reports the link doesn't work **Check these things:** 1. Ensure link wasn't cut off in email (send as clickable button) 2. Verify invoice isn't already marked as paid 3. Check payment provider is connected and active 4. Try the link yourself to reproduce the issue ### Scenario 3: Customer Lost the Link **Situation:** Customer can't find the payment link email **Solution:** 1. Go to invoice in your dashboard 2. Click "Share Payment Link" 3. Send the link again via email, SMS, or messaging app ### Scenario 4: Multiple Payment Reminders **Situation:** Invoice is overdue and you want to send reminders **Solution:** * Use the same payment link in all reminders * Set up automatic payment reminders in settings * Each reminder includes the original payment link ## Integration with Other Features ### Works With Payment Reminders Payment links are automatically included in: * Initial invoice emails * Overdue reminders * Payment confirmation emails ### Works With Subscriptions For subscription-based invoices: * Each billing cycle gets a new invoice with its own link * Links connect to subscription payment methods * Customers can update payment details via the link ### Works With Custom Domains Even if your shop uses a custom domain (e.g., yourshop.com): * Payment links use payrequest.me for consistency * Your branding still appears on the payment page * This ensures payment security and reliability ## Troubleshooting ### Link Shows 404 Error **Cause:** Invoice was deleted or business name changed **Fix:** Verify invoice exists in dashboard, regenerate link if needed ### Payment Form Not Showing **Cause:** Invoice already marked as paid **Fix:** Check invoice status, use payment retry if needed ### Wrong Business Name in Link **Cause:** Shop name was changed after link creation **Fix:** Links automatically update to current business name ### Customer Can't Select Payment Method **Cause:** Payment provider not connected or inactive **Fix:** Go to Settings → Payment Providers and verify connection ## Related Articles * [Invoice Payment Retry](/invoices/invoice-payment-retry) * [Creating Invoices](/invoices/creating-invoices) * [Payment Reminders](/invoices/payment-reminders) * [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) * [Email Templates](/invoices/email-templates) # Invoice Payment Retry Source: https://docs.payreque.st/invoices/invoice-payment-retry Learn how customers can retry payments for unpaid invoices and what happens when invoices are already paid ## Overview When customers encounter issues during payment (such as canceling an iDEAL transaction or experiencing a payment failure), PayRequest makes it easy for them to try again without creating duplicate invoices. The payment retry system ensures a smooth experience while maintaining accurate records. ## How Payment Retry Works ### Sharing Invoice Payment Links When you create an invoice in PayRequest, you can share a payment link with your customer. This link includes the invoice number and automatically pre-fills all payment information. **Example payment link:** ``` https://payrequest.me/yourbusiness?invoice=132 ``` When customers open this link, they'll see all invoice details pre-filled, including: * Invoice amount * Product or service details * Customer name and email * Any notes or descriptions ### When Payment Fails or Is Canceled If a customer cancels their payment or encounters an error (for example, closing the iDEAL payment screen), they can simply click the **"Try Again"** button to return to the payment page. **What happens:** 1. Customer is returned to the payment page with all information pre-filled 2. The same invoice number is maintained (no duplicates created) 3. Customer can immediately retry the payment without re-entering information 4. If an order was created, it remains linked to the original invoice ### Benefits of the Retry System ✅ **No Duplicate Invoices** - The system reuses the existing invoice instead of creating a new one ✅ **Pre-filled Information** - Customers don't need to re-enter their details ✅ **Order Preservation** - If products were ordered, they remain linked correctly ✅ **Clean Records** - Your invoice numbering stays sequential without gaps from failed payments ## Viewing Paid Invoices ### What Customers See When a customer opens a payment link for an invoice that's already been paid, they'll see: * A **green success message** confirming the invoice has been paid * The **invoice number** and payment date * A detailed list of **all items** on the invoice with quantities and prices * The **total amount paid** **No payment form is shown** - this prevents customers from accidentally paying twice. ## Pending Payment Protection ### SEPA Direct Debit Processing When a customer pays an invoice via SEPA Direct Debit (bank transfer), the payment takes 1-3 business days to complete. During this time, the invoice status is "pending" rather than "paid". **Duplicate Payment Prevention:** If a customer opens a payment link for an invoice with a pending SEPA payment, they'll see: * A **yellow warning callout**: "Payment Processing" * Message: "SEPA Direct Debit is pending. This typically takes 1-3 business days to complete." * Full invoice details (items, quantities, total amount) * **No payment form** - completely hidden to prevent duplicate charges This protection ensures customers cannot accidentally pay twice while waiting for their bank transfer to complete. ### Why This Matters SEPA Direct Debit payments can take several days to process. Without this protection: * Customers might think their payment failed * They could try to pay again, resulting in double charges * Business owners would need to manually process refunds With pending payment protection: * ✅ Customers see clear status information * ✅ Duplicate payments are impossible * ✅ No manual intervention needed * ✅ Professional, transparent experience ### Invoice Items Display Paid invoices show a clear breakdown including: * Product or service names * Quantities ordered * Price per item * Total for each line item * Grand total amount paid This gives customers a complete record of their purchase without the risk of duplicate charges. ## Best Practices ### For Business Owners 1. **Share Specific Invoice Links** - When following up on unpaid invoices, include the invoice parameter in the link (`?invoice=132`) 2. **Enable Email Notifications** - Set up automatic email reminders for unpaid invoices with retry links 3. **Monitor Failed Payments** - Check your dashboard regularly for invoices that need attention ### For Customers 1. **Don't Refresh During Payment** - Wait for payment confirmation before closing the page 2. **Use the Try Again Button** - If payment fails, use the provided button rather than the browser back button 3. **Check Your Email** - Payment confirmations and retry links are sent automatically ## Common Scenarios ### Scenario 1: Customer Cancels iDEAL Payment **What happens:** * Customer clicks "Cancel" on their bank's iDEAL screen * They're redirected to a PayRequest page with a "Try Again" button * Clicking the button returns them to the payment page with all details pre-filled * They can immediately start a new iDEAL payment for the same invoice ### Scenario 2: Payment Link Already Paid **What happens:** * Customer opens a payment link for invoice they already paid * Green success callout appears: "This invoice has already been paid" * Full invoice details are displayed (items, quantities, total) * No payment button is shown - prevents double charging ### Scenario 3: Following Up on Unpaid Invoice **What happens:** * You send customer the payment link from your dashboard * Customer opens link and sees all invoice details pre-filled * They complete payment using their preferred method * Both you and the customer receive confirmation ## Troubleshooting ### Customer Says They Can't Pay **Check these things:** 1. Ensure the invoice isn't already marked as paid in your dashboard 2. Verify the payment link includes the correct invoice number 3. Confirm your payment provider (Mollie/Stripe) is properly connected ### Duplicate Invoices Appearing **This shouldn't happen with the retry system**, but if you see duplicates: 1. Check if customer clicked "Pay" multiple times rapidly 2. Verify only one invoice has actual payment associated 3. You can safely delete/void the duplicate invoice without payment ## Related Articles * [Creating Invoices](/invoices/creating-invoices) * [Payment Reminders](/invoices/payment-reminders) * [Payment Methods](/payment-processing/payment-methods-overview) * [Customer Portal](/customer-management/customer-portal) # Invoice Templates Source: https://docs.payreque.st/invoices/invoice-templates Customize your invoice's logo, footer, and branding # Invoice Templates PayRequest generates invoice PDFs and pages using a single, consistent layout — you customize its branding (logo, footer text and styling) rather than choosing between multiple template designs. Changes apply to every invoice you generate going forward. > [!NOTE] > > Invoice branding is managed at **Settings → Business → Invoice Design**. The same screen also has a **Numbering** tab — see [Invoice Settings](/business-settings/invoice-settings) for that part. ## Logo **1. Upload your logo** On the **Logo** tab, upload an image file (max 1MB). It's stored and served from your account's file storage. **2. Choose a logo size** Pick **Small**, **Medium**, or **Large** to control how large the logo appears at the top of your invoices. **3. Remove it if needed** Click **Remove Logo** to delete the uploaded file and fall back to no logo. ## Footer The **Footer** tab controls the block of text shown at the bottom of every invoice, plus one invoice-wide display setting: | Setting | Description | | - | - | | **Show IBAN on Invoice** | Toggle whether your bank IBAN is displayed on invoices (appears under your VAT number) | | **Footer Text** | Free-text message shown at the bottom of the invoice (e.g., "Thank you for your business!") | | **Footer Text Size** | Small, Medium, or Large | | **Footer Alignment** | Left, Center, or Right | | **Footer Text Color** | A color picker for the footer text | ## Preview The **Preview** tab renders a live sample invoice using your current logo, footer, and numbering settings, so you can check how a real invoice will look before saving. The preview uses placeholder customer and line item data — it doesn't pull from a real invoice. ## FAQ > [accordion] Can I use a different template layout for different customers or products? > > No — there's one invoice layout per business. All invoices you generate use the same logo, footer, and numbering settings. > [accordion] Do changes apply to invoices I already sent? > > No. Styling changes apply to invoices generated after you save — previously generated PDFs aren't regenerated. > [accordion] What image formats are supported for the logo? > > Standard image formats are accepted, up to 1MB in size. ## Next Steps > [card] [Invoice Settings](/business-settings/invoice-settings) > > Configure your invoice numbering format > [card] [Creating Invoices](/invoices/creating-invoices) > > Learn the invoice creation flow > [card] [Tax Configuration for Invoices](/invoices/tax-configuration) > > How VAT/BTW is displayed on your invoice PDFs > [card] [Business Details](/business-settings/business-details) > > Set your company name, address, and VAT number shown on invoices # Partial Payments Source: https://docs.payreque.st/invoices/partial-payments How partial refunds work on paid invoices, and your options when a customer can't pay in full # Partial Payments An individual invoice in PayRequest is paid in a single payment for the full amount — there's no built-in "pay half now, half later on this invoice" option at checkout. What PayRequest does support is **partial refunds** on invoices that have already been paid, plus a separate installment mechanism for invoices that have gone to debt collection. > [!NOTE] > > For a new project, [Split a payment into two links](/payment-processing/split-payments) lets you collect an upfront payment and the balance as two one-time payments. This flow lives under Payment Links and collects the payments separately from your invoice. > > If you're looking for a way to split an unpaid invoice into monthly installments, see [Payment Plans](/debt-collection/payment-plans) — that feature is available once an invoice is in a debt collection case. ## Partial Refunds From a **paid** invoice's detail page, choose **Credit invoice**. Every refund through this flow has a numbered credit note, a PDF and a link to the original invoice. The credit note and the movement of money have separate statuses. See [Credit Notes](/invoices/credit-notes) for the complete workflow, refund statuses, manual settlement, and customer-email checks. **1. Open the paid invoice** Go to the invoice detail page and click **Credit invoice**. **2. Choose what to credit** | Option | What it does | | - | - | | **Full remaining amount** | Credits the amount still available | | **A specific amount** | Credits a custom amount including VAT, distributed over remaining invoice lines | | **Selected invoice lines** | Credits the remaining amount of the selected services, including their original VAT rates | **3. Enter the reason and choose the settlement** Provide a reason, then choose **Refund through Mollie** or **Refund manually**. Check the amount in the preview. Customer email is enabled by default and can be switched off. **4. Issue the credit note** PayRequest preserves the original invoice and creates a linked negative credit document. With Mollie, the matching refund is requested through the original payment. For a manual refund, transfer the money yourself and then record the bank or payment reference on the original invoice. ### How the Remaining Amount Is Tracked The available credit amount accounts for existing credit notes and refunds already reserved or completed. A refund linked to a credit note is counted once. Credits can start at €0.01. Invoices with older credits may require the custom-amount option because their individual credited lines are not known. > [!WARNING] > > If the outcome of a refund request is uncertain, use **Check refund status**. PayRequest looks for the existing provider refund and does not blindly submit another one. If no refund can be verified, the credit remains marked as needing verification. A definite rejection or a confirmed failed/canceled refund can be retried against the same credit note. ### Credit Invoice + Refund Refund states include **Refund in progress**, **Refund completed**, **Manual refund required**, and **Refund needs verification**. A credit note being issued does not mean that money has already reached the customer. Provider statuses are reconciled every five minutes and can also be checked from the original invoice. The customer portal shows the credit document and its settlement status. ### Crediting an unpaid invoice Choose **Credit invoice** on the original unpaid invoice to credit it in full. PayRequest preserves the original amount, creates the credit note, cancels collection on the original invoice, disables its reminders and cancels any awaiting PayRequest bank-transfer matching instruction. There is no refund to initiate. An in-flight or already recorded payment, or an active debt-collection case, must be checked before proceeding. Partial credits on unpaid invoices and customer-balance credits are not supported in this flow yet. ## Splitting an Unpaid Invoice Into Installments If a customer genuinely can't pay an invoice in full, PayRequest doesn't support partial/installment collection on a standalone invoice directly. Instead, escalate the invoice to a **Debt Collection** case, where you (or the customer) can set up a [Payment Plan](/debt-collection/payment-plans) that splits the outstanding balance into 2, 3, 6, or 12 monthly installments, billed automatically via a linked subscription. ## Authorization Holds (Partial Capture) A related but distinct concept: [Security Deposits](/payment-processing/security-deposits) let you place a credit card authorization hold on a product order and later **capture only part of it** (e.g., charging €75 of a €500 hold for minor damage). This applies to deposit-enabled products, not to standard invoices. ## FAQ > [accordion] Can a customer pay only part of an invoice at checkout? > > No — invoices are paid in full in a single Mollie payment. If the customer needs to spread the cost, use a Debt Collection [Payment Plan](/debt-collection/payment-plans) instead. > [accordion] Can I refund an invoice more than once? > > Yes, provided enough credit capacity remains. Repeated confirmation of the same credit recovers the existing document and refund rather than creating another. > [accordion] What happens to the invoice status after a partial refund? > > The original paid invoice stays **Paid**. The linked credit note and refund status show the adjustment separately. > [accordion] Can I refund an invoice that hasn't been paid yet? > > No. Refunds require an existing Mollie payment on the invoice — there's nothing to refund on an unpaid invoice. ## Next Steps > [card] [Refund Requests](/invoices/refund-requests) > > How customers can request a refund themselves > [card] [Payment Plans](/debt-collection/payment-plans) > > Split an overdue invoice into monthly installments > [card] [Security Deposits](/payment-processing/security-deposits) > > Authorization holds with partial capture for products > [card] [Handling Chargebacks](/payment-processing/handling-chargebacks) > > What happens when a payment is disputed instead of refunded # Payment Reminders Source: https://docs.payreque.st/invoices/payment-reminders Automated follow-up sequences to get invoices paid on time # Payment Reminders PayRequest can automatically remind your customers about unpaid invoices, so you don't have to chase payments manually. ## How Reminders Work When you enable payment reminders on an invoice, PayRequest sends automatic email reminders based on your schedule. ### Setting Up Reminders 1. Open any invoice 2. Go to the **Payment Reminders** tab 3. Toggle reminders **on** 4. Configure your preferences: | Setting | Description | | - | - | | **Days before due date** | Send a reminder X days before the invoice is due | | **Days after due date** | Send a reminder X days after the due date | | **Frequency** | How often to send reminders (e.g., every 7 days) | ### Automatic Schedule Reminders are processed daily at **9:00 AM**. The system checks all invoices with reminders enabled and sends emails according to your schedule. ### Manual Reminders You can also send reminders manually at any time: * **Single invoice**: Click **Send Reminder** on the invoice detail page * **Bulk action**: Select multiple invoices and use the **Send Reminder** bulk action ## Reminder Email Each reminder includes: * Your business branding * Invoice number and amount * Due date (and how many days overdue) * Direct payment link * Your custom message (if configured) ## Tracking Reminders The Payment Reminders tab on each invoice shows a complete history: * Date and time each reminder was sent * Whether it was automatic or manual * Delivery status ## When Reminders Aren't Enough If regular payment reminders don't result in payment, you can escalate to formal debt collection: 1. Invoice reminders go unanswered for 14+ days 2. Open a **Debt Collection** case from the invoice 3. The collection pipeline takes over with escalating communication > [card] [Debt Collection](/debt-collection/overview) > > Escalate unpaid invoices to formal collection > [card] [Invoice Payment Links](/invoices/invoice-payment-links) > > Share payment links with customers > [card] [Bulk Invoice Actions](/invoices/bulk-invoice-actions) > > Send reminders to multiple invoices at once > [card] [Email Templates](/invoices/email-templates) > > Customize your reminder email templates > [card] [Email Health & Suppression](/customer-management/customer-health) > > Bounced emails are automatically suppressed with delivery confirmation # Projects: one quote for your project and subscription Source: https://docs.payreque.st/invoices/projects Combine one-time work, a deposit, a final invoice and a recurring service in one customer agreement. Use **Projects** when you sell initial work together with an ongoing service. Agree on a website build and monthly maintenance in one quote, then manage the deposit, final invoice and subscription from the same project overview. > [card] [Create a project](https://payrequest.app/projects) > > Open Projects in your PayRequest dashboard and choose **Project with subscription**. ## Example: a website with monthly maintenance You quote a website for **€3,000 excluding VAT** and maintenance for **€49 per month excluding VAT**. With 21% VAT and a 50% deposit, the agreement contains: | Part of the agreement | Amount including VAT | When it is invoiced | | - | - | - | | Website deposit | €1,815 | After the customer accepts the quote | | Website final payment | €1,815 | After you confirm delivery | | Maintenance | €59.29 per month | From the agreed start, then each month | The website total is **€3,630 including VAT**. Maintenance is separate from that one-time total. The customer sees both prices and the recurring start conditions before accepting. > [!NOTE] > > Project subscriptions use recurring invoices that customers pay themselves. Accepting a project quote does not authorize automatic debits, and quote approval is not proof of payment. ## Before you start Have these details ready: * A verified PayRequest account with a current paid Business subscription. * An existing customer with the correct billing details. * Invoice-based subscriptions enabled in your portal settings. * The one-time work, deposit percentage, ongoing service and cancellation terms. The first version supports one customer, one account currency, one deposit and final payment, and one recurring service per project. The recurring service can be billed monthly, quarterly or yearly. ## Create your project **1. Choose the customer** Open **Projects → Project with subscription**. You can also choose **Project with subscription** from Quotes. Enter a project name and select an existing customer. The project uses your account currency for the one-time work and the recurring service. **2. Add the one-time work** Add the descriptions, quantities, unit prices **excluding VAT** and tax rates. Use **Add item** for additional work. Set the **Deposit (%) after approval**, between 1% and 99%. PayRequest invoices the remaining amount when you confirm delivery. A saved customer tax exemption is applied when you create the agreement. **3. Add the recurring service** Enter the service name, price **excluding VAT**, tax rate and billing frequency. Choose when recurring invoicing should start: * **After confirmed delivery:** the service becomes eligible to start after you confirm delivery in the project. * **On a specific date:** select the start date. Customer approval is still required before the service can start. Add your terms, including what the service includes and how cancellation works. **4. Review and send the quote** Choose **Create project and draft quote**, then **Review and send quote**. Check the one-time total, deposit, final payment, recurring price including VAT, frequency and start conditions. The agreement details also appear in the quote email and PDF. Use the quote's normal send action when everything is correct. Saving the project creates a draft; it does not send the quote or start billing. > [!NOTE] > > Project agreement prices and start conditions are fixed after creation. If you need a different agreement, stop the unstarted project and prepare a new one. Existing invoices remain available. ## Customer approval and the deposit Your customer opens the quote link and reviews the one-time work and ongoing service. They must explicitly accept the recurring service, price, frequency and start conditions before approving. After approval, PayRequest creates the deposit invoice through the existing invoice workflow. The customer pays using the available payment methods. The invoice's normal payment verification determines whether it is paid. An unapproved, declined, expired or stopped project quote cannot start a new project subscription. ## Confirm delivery and invoice the balance When the work is ready, open the project and choose **Confirm delivery and create final invoice**. This creates the remaining invoice once. Open **Final invoice** to review and send it through the normal invoice screen. Confirming delivery does not mark the deposit or final invoice paid. The customer can return to the original quote link to see project progress and open the final invoice when it is available. ## Start and manage recurring invoicing Once the customer has accepted and the chosen start condition has been reached, PayRequest starts the service on the next scheduled project activation run. The normal subscription billing schedule creates and sends the recurring invoices. You can also choose **Start recurring invoicing** on an eligible project. Customers pay each recurring invoice themselves; no automatic debit mandate is created by this action. If the selected date has already passed when the customer approves, invoicing starts from the current day. Earlier periods are not backfilled. Use **Manage subscription** to open the connected subscription for its invoices, payment history and normal subscription controls. Customer self-service continues through the existing customer portal. ## Stop a project or cancel its service Before the connected subscription starts, choose **Stop project** to prevent delivery actions and recurring activation. Existing invoices are not canceled or changed by this action. After the subscription starts, use **Manage subscription** and the normal cancellation controls. A canceled, paused or deleted subscription is never automatically replaced or reactivated by its project. ## Related guides > [card] [Quotes and invoices](https://docs.payreque.st/invoices/quotes-to-invoices) > > Learn how to send a quote and follow the customer's decision. > [card] [Subscription lifecycle](https://docs.payreque.st/subscriptions/subscription-lifecycle) > > Manage an ongoing service after it starts. # From Quote to Invoice Source: https://docs.payreque.st/invoices/quotes-to-invoices Create and send a quote, review the customer’s decision, and find or create the invoice after approval. Use a quote to agree on work and pricing before invoicing. Quotes are available on **Premium and higher eligible plans**. Open [Quotes](https://payrequest.app/quotes) in the business dashboard. ## Before you start Have the customer's correct email, the proposed items and prices, currency, VAT, validity date and terms ready. A quote's approval is an agreement on the proposal; it is not proof of payment. ## Create a quote **1. Open a new quote** From **Quotes**, choose the new-quote action. Select the existing customer and check the quote number, date, expiration date and reference. **2. Add the work or products** Add product or custom lines. Review names, quantities, unit prices and tax rates. Check which items are optional and what the proposed total includes. **3. Set payment terms** Add notes and terms. If you need an advance payment, enter the **Deposit Percentage**; otherwise leave it empty for full invoicing. Review the amount before saving. **4. Save and review** Open the saved quote, check the customer-facing details and PDF, and correct anything necessary before sending. ## Send it to the customer Use the quote's **Send** action when it is available. PayRequest queues the quote email for the customer. The customer can review the shared quote page and approve or decline an eligible quote. You can also copy the approval link where shown. Keep customer-specific approval links private and send them to the intended recipient. Saving a quote alone does not mean the customer has received or approved it. ## Check the result | Status | What to do | | - | - | | **Draft** | Review the quote before sending. | | **Sent / viewed** | The customer has not yet approved it. Check the validity date before following up. | | **Approved** | Check whether an invoice was created or linked before converting it yourself. | | **Rejected** | Read any reason, discuss changes with the customer and review the next proposal. Do not invoice it as an approved quote. | | **Expired** | Review the validity and terms with the customer before arranging a new approval. | | **Converted** | Open the linked invoice and manage payment from that invoice. | ## Find or create the invoice After approval, open the quote and check for the linked invoice. Some approval flows attempt conversion automatically; **approval and invoice creation are still separate outcomes**. The quote may remain approved if no invoice has been created. If there is no linked invoice and **Convert to Invoice** is available, review the approved quote and confirm conversion. PayRequest creates the invoice and links it to the quote. If an invoice already exists or the result is unclear, check that invoice before creating another one. Conversion does not mark the invoice paid. Open it to review the amount, due date, payment link and sending actions. See [Creating invoices](/invoices/creating-invoices). ## An advance payment is not a security-deposit hold > [!WARNING] > > **Deposit Percentage** on a quote creates an advance-payment invoice. It collects money when paid. It is different from a [security deposit](/payment-processing/security-deposits), which reserves funds for later capture or release. For a quote with an advance-payment percentage, conversion uses that advance amount for the first invoice. The remaining amount must be invoiced separately; do not assume it has been billed or collected automatically. For example, a EUR 1,000 quote with a 25% advance creates a EUR 250 advance invoice. Review the remaining EUR 750 and your agreement before preparing its separate invoice. ## When something looks wrong * **The customer says they approved, but there is no invoice:** check the quote status and linked invoice first. Use the conversion action only if the quote is eligible and no invoice was created. * **The invoice is unpaid after approval:** approval is not payment. Share or check the invoice's own payment link. * **The customer wants different items:** review the agreement and update or prepare the appropriate quote rather than collecting a different amount without explanation. * **The approval link no longer works:** check the quote's status and validity before sending another link. > [card] [Custom services](/products-and-pricing/commissions) > > Use proposals for custom-scoped work. > [card] [Customer payment help](/customer-guide/invoice-still-open) > > Explain a payment that has not yet been confirmed. # Refund Requests Source: https://docs.payreque.st/invoices/refund-requests How customers can request refunds for paid invoices through the customer portal ## Overview Customers can request refunds for paid invoices directly from their customer portal. Instead of needing to contact you through a generic support form, they get a dedicated, streamlined refund request page linked to the specific invoice they want refunded. > [!NOTE] > > Refund requests don't process refunds automatically. They create a support ticket of type "Refund Request" for you to review and act on. You remain in full control of whether to approve or decline the refund. ## How It Works ### Customer Experience When a customer views a **paid** invoice in their customer portal, they see a **"Request Refund"** button next to the "Download PDF" button in the invoice actions area. **1. View Paid Invoice** Customer navigates to their invoice detail page in the customer portal and sees the "Request Refund" button alongside other actions **2. Review Invoice Summary** After clicking the button, a dedicated refund request page loads showing the full invoice summary: invoice number, date, amount, and line items **3. Provide Reason** Customer fills in a subject (pre-filled with the invoice number) and writes a reason for their refund request using a rich text editor **4. Submit Request** Customer submits the form. A support ticket is created with type "Refund Request", linked directly to the invoice, and the customer is redirected back to the invoice detail page with a success message ### What Gets Created When a customer submits a refund request, a **Support Request** record is created with: | Field | Value | | - | - | | **Type** | Refund Request | | **Priority** | Medium | | **Related Record** | The specific invoice (automatically linked) | | **Subject** | Pre-filled with "Refund request for invoice \[number]" | | **Message** | Customer's reason for the refund | | **Status** | Open | ### Duplicate Prevention The system prevents customers from submitting multiple refund requests for the same invoice: * If an **open or in-review** refund request already exists for that invoice, the "Request Refund" button on the invoice detail page changes to a disabled **"Refund Requested"** button * If the customer navigates directly to the refund request page, they see a callout informing them that a request has already been submitted, with a link to view their existing ticket ## Managing Refund Requests ### Viewing Requests Refund requests appear in your **Support Requests** section alongside all other customer requests. You can filter by type "Refund Request" to see only refund-related tickets. Each refund request is automatically linked to the relevant invoice, so you can quickly see: * Which invoice the customer wants refunded * The invoice amount and items * The customer's stated reason ### Processing a Refund **1. Review the Request** Open the refund request from your Support Requests page. Review the customer's reason and the linked invoice details **2. Decide on the Refund** Determine whether to approve a full refund, partial refund, or decline the request based on your business policies **3. Process via Mollie** If approved, open the original invoice and choose **Credit invoice**. Follow the [Credit Notes guide](/invoices/credit-notes) to issue the document and request a Mollie refund or record a manual refund. A customer request does not create a credit note or move money by itself. **4. Update the Ticket** Respond to the customer through the support ticket and mark it as Resolved (or Rejected if declined) > [!TIP] > > Respond to refund requests promptly. Quick, clear communication builds customer trust even when you need to decline a refund. ## Where Customers Find It The "Request Refund" button appears in two locations, depending on your shop setup: * **Standard shop URL**: `yourshop.payrequest.shop/customer/invoices/{id}` * **Custom domain**: `shop.yourbusiness.com/customer/invoices/{id}` The refund request page is accessible at: * **Standard**: `/shop/{storename}/customer/invoices/{id}/refund` * **Custom domain**: `/customer/invoices/{id}/refund` > [!WARNING] > > The "Request Refund" button only appears for invoices with a **paid** status. Unpaid, pending, or canceled invoices do not show the refund option. ## Next Steps > [card] [Customer Portal](/customer-management/customer-portal) > > Learn more about the full customer portal experience > [card] [Handling Chargebacks](/payment-processing/handling-chargebacks) > > Understand the difference between refund requests and chargebacks > [card] [Invoice Payment Links](/invoices/invoice-payment-links) > > Share payment links with customers for unpaid invoices > [card] [Payment Reminders](/invoices/payment-reminders) > > Set up automated reminders for unpaid invoices # Tax Configuration for Invoices Source: https://docs.payreque.st/invoices/tax-configuration Configure VAT/BTW rates, tax display, and exemptions on your invoices # Tax Configuration for Invoices PayRequest automatically calculates and displays taxes on your invoices based on your business settings, product configurations, and customer tax status. This guide explains how tax appears on invoices and how to configure it. ## How Invoice Tax Works When you create an invoice, PayRequest: 1. **Checks the customer's tax status** - Is the customer tax exempt? 2. **Applies product tax rates** - Each line item uses its product's configured tax rate 3. **Calculates tax amounts** - Based on tax-included or tax-excluded pricing 4. **Generates the invoice** - With full tax breakdown for compliance > [!NOTE] > > Tax settings are determined hierarchically: Customer exemption > Product tax rate > Business default rate ## Tax on Invoice Line Items Each invoice item shows: | Field | Description | | - | - | | **Description** | Product/service name | | **Quantity** | Number of units | | **Unit Price** | Price per unit | | **Tax Rate** | VAT/BTW percentage | | **Tax Amount** | Calculated tax for this line | | **Total** | Line total including/excluding tax | ### Example Invoice Breakdown **Standard Customer (21% BTW):** ``` ┌──────────────────────────────────────────────────────┐ │ Invoice #2025-0042 │ │ Customer: Acme B.V. │ ├──────────────────────────────────────────────────────┤ │ Item Qty Price Tax Total │ ├──────────────────────────────────────────────────────┤ │ Web Hosting 1 €50.00 21% €60.50 │ │ SSL Certificate 1 €25.00 21% €30.25 │ │ Support Hours 3 €75.00 21% €90.75 │ ├──────────────────────────────────────────────────────┤ │ Subtotal (excl. BTW) €150.00 │ │ BTW 21% €31.50 │ │ Total €181.50 │ └──────────────────────────────────────────────────────┘ ``` **Tax-Exempt Customer (BTW Verlegd):** ``` ┌──────────────────────────────────────────────────────┐ │ Invoice #2025-0043 │ │ Customer: Euro Partners GmbH │ │ VAT: DE123456789 │ │ BTW VERLEGD │ ├──────────────────────────────────────────────────────┤ │ Item Qty Price Tax Total │ ├──────────────────────────────────────────────────────┤ │ Consulting 10 €100.00 0% €1,000.00 │ ├──────────────────────────────────────────────────────┤ │ Subtotal €1,000.00 │ │ BTW (Verlegd) €0.00 │ │ Total €1,000.00 │ └──────────────────────────────────────────────────────┘ ``` ## Configuring Tax Rates ### Business Default Tax Rate Set your default tax rate in **Settings > Tax & Currency**: **1. Navigate to Settings** Go to **Settings** in your dashboard sidebar. **2. Open Tax & Currency** Click on the **Tax & Currency** tab. **3. Set Default Rate** Enter your standard tax rate (e.g., **21** for 21% Dutch BTW). **4. Save Changes** Click **Save** to apply the new default rate. This default rate is used when: * Creating new products (as their initial tax rate) * Adding manual invoice items without a product reference ### Per-Product Tax Rates Each product can have its own tax rate that overrides the default: 1. Go to **Products > \[Select Product] > Edit** 2. Find the **Tax Settings** section 3. Set the **Tax Rate** for this product 4. Toggle **Tax Included** if the price includes tax > [accordion] When to Use Different Tax Rates > > **21% Standard Rate (Algemeen tarief)** > > * Most goods and services > * Software licenses > * Consulting services > * Digital products > > **9% Reduced Rate (Verlaagd tarief)** > > * Books and e-books > * Food products > * Medications > * Hotel accommodations > * Cultural events > > **0% Zero Rate (Nultarief)** > > * Exports outside EU > * Intra-EU B2B supplies > * Certain medical services ## Tax Included vs Excluded ### Tax Included (Recommended for B2C) When **Tax Included** is enabled on a product: * The price you set is what customers see * Tax is calculated backwards: `Tax = Price - (Price / (1 + Rate/100))` * Better for consumer-facing pricing **Example:** * Price set: €121.00 * Tax rate: 21% * Tax calculation: €121 - (€121 / 1.21) = €21.00 * Net amount: €100.00 ### Tax Excluded (Common for B2B) When **Tax Included** is disabled: * The price you set is the net price * Tax is added on top: `Tax = Price × (Rate/100)` * Common for wholesale/B2B pricing **Example:** * Price set: €100.00 * Tax rate: 21% * Tax calculation: €100 × 0.21 = €21.00 * Total: €121.00 ## Creating Invoices with Tax ### Manual Invoice Items When adding items manually to an invoice: 1. Enter the item description 2. Set quantity and unit price 3. Select the tax rate from dropdown 4. Toggle tax included if needed PayRequest calculates the totals automatically. ### Product-Based Invoice Items When adding a product to an invoice: 1. Select the product from the dropdown 2. The product's tax settings are applied automatically 3. Tax rate and inclusion settings come from the product 4. Adjust quantity as needed ### Handling Mixed Tax Rates An invoice can contain items with different tax rates. PayRequest: * Calculates tax per line item * Shows a tax breakdown by rate in the invoice * Totals all amounts correctly **Example with Mixed Rates:** ``` ┌─────────────────────────────────────────────────┐ │ Tax Breakdown: │ ├─────────────────────────────────────────────────┤ │ 21% BTW over €200.00 €42.00 │ │ 9% BTW over €50.00 €4.50 │ │ 0% BTW over €25.00 €0.00 │ ├─────────────────────────────────────────────────┤ │ Total BTW €46.50 │ └─────────────────────────────────────────────────┘ ``` ## Customer Tax Exemption When a customer is marked as **Tax Exempt**: ### Automatic Behavior * All invoice items are set to **0% tax** * Invoice displays **"BTW VERLEGD"** indicator * Tax totals show €0.00 * Customer is not charged any VAT ### Manual Override Even for tax-exempt customers, you can manually adjust tax rates on specific invoice items if needed (though this is rarely required). > [!WARNING] > > Be careful when manually overriding tax for exempt customers. This should only be done in special circumstances with proper documentation. ## Invoice PDF Tax Display Your invoice PDFs include: ### Header/Footer * Your business VAT number * Customer's VAT number (if applicable) * "BTW Verlegd" notice for reverse charge ### Line Items * Each item shows its tax rate * Tax amounts calculated per line ### Summary Section * Subtotal (excluding tax) * Tax breakdown by rate * Total amount * Payment instructions ### Legal Requirements For EU VAT compliance, your invoices should show: > [card] Your Business Info > > * Business name and address > * VAT/BTW registration number > * KvK number (Dutch companies) > [card] Customer Info > > * Customer name and address > * VAT number (for B2B reverse charge) > * Country > [card] Invoice Details > > * Unique invoice number > * Invoice date > * Payment due date > * Currency > [card] Tax Information > > * Tax rate per line item > * Tax amounts > * Total tax > * Reverse charge notice if applicable ## Editing Invoice Tax ### Before Invoice is Sent You can freely edit: * Tax rates on any line item * Tax included setting * Add or remove items ### After Invoice is Sent > [!WARNING] > > Editing sent invoices affects your accounting records. If significant changes are needed, consider issuing a credit note instead. Minor corrections are allowed, but changing tax rates after sending may require: * Notifying the customer * Updating your accounting records * Potentially issuing a corrected invoice ## Tax in Invoice Templates Customize how tax appears in your invoice templates: ### Available Template Variables | Variable | Description | | - | - | | `{tax_subtotal}` | Total before tax | | `{tax_amount}` | Total tax amount | | `{tax_rate}` | Applied tax rate (%) | | `{invoice_total}` | Grand total including tax | | `{tax_exempt_notice}` | "BTW Verlegd" text if applicable | ### Customization Options In **Settings > Invoice Settings**, you can: * Add custom footer text for tax notices * Include payment terms * Add reverse charge statements * Customize the tax breakdown display ## Subscription Invoice Tax For recurring subscription invoices: ### Automatic Tax Application * Tax is calculated based on the subscription product's settings * Customer exemption status is checked each billing cycle * Tax rates can be updated and will apply to future invoices ### Subscription Amount Changes If you change a subscription's tax settings: * Past invoices remain unchanged * Future invoices use the new settings * Proration calculations include tax ## Common Tax Scenarios > [accordion] Dutch B2C Invoice > > **Settings:** > > * Customer: Dutch individual, not tax exempt > * Product: Standard rate (21%) > > **Result:** Invoice shows full 21% BTW, customer pays total including tax. > [accordion] Dutch B2B Invoice > > **Settings:** > > * Customer: Dutch business, not tax exempt > * Product: Standard rate (21%) > > **Result:** Same as B2C - 21% BTW charged. Customer reclaims on their VAT return. > [accordion] EU B2B Reverse Charge > > **Settings:** > > * Customer: German business, marked tax exempt > * Customer VAT number stored: DE123456789 > > **Result:** Invoice shows 0% VAT, "BTW Verlegd" notice, customer accounts for VAT in Germany. > [accordion] Export Invoice > > **Settings:** > > * Customer: US company, marked tax exempt > * Delivery: Outside EU > > **Result:** Invoice shows 0% VAT, marked as export sale. > [accordion] Mixed Rate Invoice > > **Settings:** > > * Line 1: Software (21%) > * Line 2: Training manual/book (9%) > > **Result:** Tax breakdown shows amounts per rate, totals calculated correctly. ## Troubleshooting > [accordion] Tax not showing on invoice > > **Check:** > > 1. Is your business registered for VAT in Settings? > 2. Does the product have a tax rate set? > 3. Is the customer marked as tax exempt? > > If VAT registration is disabled, no tax will be applied. > [accordion] Wrong tax rate on invoice > > **Possible causes:** > > 1. Product has a different rate than expected > 2. Invoice item was manually adjusted > 3. Business default rate changed after invoice was created > > **Solution:** Edit the invoice item and select the correct tax rate. > [accordion] Tax exempt customer showing tax > > **Check:** > > 1. Was the customer marked exempt before the invoice was created? > 2. Was the invoice created from an older order? > > **Solution:** Edit the invoice and set tax rates to 0%, or recreate the invoice. > [accordion] Tax amounts don't add up > > This usually happens with tax-included pricing. The calculation extracts tax from the total, which can result in rounding differences. > > **Example:** €10.00 at 21% = €8.26 net + €1.74 tax (rounds correctly) > > PayRequest handles rounding to 2 decimal places. ## Tax Reporting PayRequest provides tax data for your bookkeeping: ### Available Reports * **Transaction Reports**: Show tax amounts per transaction * **Invoice Export**: CSV export with tax breakdown * **Revenue Tracking**: Separates net revenue from tax collected ### Bookkeeping Integration Export your invoice data including: * Invoice number and date * Net amounts * Tax amounts by rate * Gross totals * Customer information This data integrates with common Dutch bookkeeping software. ## Related Documentation > [card] [Tax & VAT Guide](/business-settings/tax-vat-guide) > > Complete guide to tax settings in PayRequest > [card] [Tax Exemptions](/customer-management/tax-exemptions) > > Managing customer tax exemption status > [card] [Creating Products](/products-and-pricing/creating-products) > > Configure product pricing and tax settings > [card] [Invoice Templates](/invoices/invoice-templates) > > Customize your invoice appearance *** > [!NOTE] > > This documentation explains PayRequest's tax features. For advice on which tax rates to apply or how to handle specific tax situations, consult with a qualified tax professional familiar with Dutch and EU VAT regulations. # MCP Overview Source: https://docs.payreque.st/mcp/overview Connect Claude Desktop or ChatGPT to PayRequest using the Model Context Protocol # Model Context Protocol (MCP) PayRequest provides an MCP server that allows AI assistants to interact with your billing data securely using natural language. > [!NOTE] > > **Now available for Claude Desktop and ChatGPT!** Connect your favorite AI assistant to PayRequest and manage your billing with simple conversations. ## Supported AI Assistants > [card] [Claude Desktop](/mcp/setup#claude-desktop-setup) > > Full MCP support with OAuth authentication > [card] [ChatGPT](/mcp/setup#chatgpt-setup) > > MCP connector support for ChatGPT Plus users ## What is MCP? The [Model Context Protocol](https://modelcontextprotocol.io/) is an open standard that enables AI applications to connect to external data sources and tools. With PayRequest's MCP integration, your AI assistant can: * **View billing statistics** - Get real-time insights into your invoices * **List invoices** - Search and filter your invoice data * **Identify overdue payments** - Find invoices that need attention * **Send payment reminders** - Automate follow-up emails ## Why Use MCP? > [card] Natural Language Queries > > Ask questions like "How many invoices are overdue?" and get instant answers > [card] Automated Workflows > > Let AI assistants handle routine billing tasks like sending reminders > [card] Secure Access > > OAuth 2.0 authentication ensures only authorized access > [card] Real-Time Data > > Always work with the latest billing information ## Server Endpoint The PayRequest MCP Billing Server is available at: ``` https://payrequest.app/mcp/billing ``` ## Available Tools | Tool | Description | Scope Required | | - | - | - | | `get-invoice-stats` | Get invoice statistics (totals, pending, paid, overdue) | `billing.read` | | `list-invoices` | List invoices with optional status filtering | `billing.read` | | `get-overdue-invoices` | Get all overdue invoices with customer details | `billing.read` | | `send-invoice-reminder` | Send payment reminder email for an invoice | `billing.read` | ## Quick Example Once connected, you can ask your AI assistant questions like: > "Show me all overdue invoices" The assistant will use the MCP tools to fetch your data and respond: ``` Overdue Invoices (3 total): - Invoice #INV-2025-042: €1,250.00 Customer: Acme Corp Due: 2025-01-15 (14 days overdue) Status: sent - Invoice #INV-2025-038: €600.00 Customer: TechStart BV Due: 2025-01-10 (19 days overdue) Status: viewed Total Overdue Amount: €1,850.00 ``` ## Get Started > [card] [Claude Desktop Setup](/mcp/setup#claude-desktop-setup) > > Connect Claude Desktop to PayRequest in minutes > [card] [ChatGPT Setup](/mcp/setup#chatgpt-setup) > > Connect ChatGPT to access your billing data > [card] [Tools Reference](/mcp/tools) > > Detailed documentation for all MCP tools > [card] [Dashboard Setup](/mcp/setup#finding-your-setup-instructions) > > Find setup instructions in your PayRequest dashboard # MCP Setup Source: https://docs.payreque.st/mcp/setup Connect Claude Desktop or ChatGPT to PayRequest using the Model Context Protocol # Setting Up MCP This guide walks you through connecting AI assistants to PayRequest using the Model Context Protocol (MCP) with OAuth authentication. ## Supported AI Assistants > [card] Claude Desktop > > Anthropic's desktop application with full MCP support > [card] ChatGPT > > OpenAI's ChatGPT with MCP connector support ## Prerequisites Before you begin, ensure you have: * A PayRequest account with active billing data * Claude Desktop app or ChatGPT Plus subscription * Your PayRequest dashboard accessible *** ## Claude Desktop Setup **1. Open Claude Desktop Settings** In Claude Desktop, go to **Settings** → **MCP Servers** → **Add Server**. **2. Enter Server Details** Configure the MCP server with these settings: | Setting | Value | | - | - | | Server URL | `https://payrequest.app/mcp/billing` | | Name | PayRequest Billing | **3. Authenticate with PayRequest** Claude Desktop will open a browser window to authenticate with PayRequest. Log in with your PayRequest account and authorize the connection. **4. Grant Permissions** Review the requested permissions and click **Authorize** to allow Claude Desktop to access your billing data. **5. Verify Connection** Back in Claude Desktop, you should see "PayRequest" listed under your connected MCP servers. Try asking: > "What are my invoice statistics?" ### Claude Desktop Configuration File For advanced users, you can also configure Claude Desktop via the config file: > [tab] macOS > > Edit `~/Library/Application Support/Claude/claude_desktop_config.json`: > > ```json theme={null} > { > "mcpServers": { > "payrequest-billing": { > "url": "https://payrequest.app/mcp/billing" > } > } > } > ``` > [tab] Windows > > Edit `%APPDATA%\Claude\claude_desktop_config.json`: > > ```json theme={null} > { > "mcpServers": { > "payrequest-billing": { > "url": "https://payrequest.app/mcp/billing" > } > } > } > ``` *** ## ChatGPT Setup **1. Open ChatGPT** Go to [chat.openai.com](https://chat.openai.com) and ensure you have a ChatGPT Plus subscription. **2. Access MCP Connectors** In ChatGPT, go to **Settings** → **Connected Apps** or look for the MCP connector option. **3. Add PayRequest Server** Add a new MCP server with: | Setting | Value | | - | - | | Server URL | `https://payrequest.app/mcp/billing` | | Name | PayRequest Billing | **4. Authenticate** ChatGPT will redirect you to PayRequest to log in and authorize the connection. **5. Start Using** Once connected, you can ask ChatGPT about your billing data: > "Show me my overdue invoices" *** ## Finding Your Setup Instructions The easiest way to set up MCP is from your PayRequest dashboard: 1. Go to **Settings** → **API** in PayRequest 2. Select the **Claude Desktop** or **ChatGPT** tab 3. Follow the on-screen instructions with pre-configured values *** ## Test the Connection After setup, verify everything works by asking your AI assistant: > "What are my invoice statistics?" You should receive a response like: ``` Invoice Statistics: - Total invoices: 150 - Pending: 23 (€15,750.00 outstanding) - Paid: 120 - Overdue: 7 (€4,200.00) ``` ## Available Commands Once connected, you can ask questions like: * "What are my invoice statistics?" * "Show me all overdue invoices" * "List my recent invoices" * "Send a payment reminder for invoice #INV-2025-042" *** ## OAuth Endpoints (Technical Reference) For developers building custom MCP clients: | Endpoint | URL | | - | - | | MCP Server | `https://payrequest.app/mcp/billing` | | OAuth Discovery | `https://payrequest.app/.well-known/oauth-authorization-server` | | Authorization | `https://payrequest.app/oauth/authorize` | | Token Endpoint | `https://payrequest.app/oauth/token` | ### OAuth Flow PayRequest MCP uses OAuth 2.0 with PKCE for secure authentication: 1. Client initiates authorization request with `code_challenge` 2. User authenticates with PayRequest 3. Authorization code returned to client 4. Client exchanges code for access token using `code_verifier` 5. Access token used for MCP requests *** ## Troubleshooting ### "Permission denied" or "Authentication failed" * Ensure you're logged into the correct PayRequest account * Try disconnecting and reconnecting the MCP server * Clear your browser cookies and try again ### "Invalid client" error * Make sure you're using the correct server URL: `https://payrequest.app/mcp/billing` * Contact support if the issue persists ### Connection timeout * Verify you can access `https://payrequest.app` in your browser * Check your firewall or VPN settings * Try from a different network ### No data returned * Ensure you have invoices in your PayRequest account * Verify you authorized the correct PayRequest account *** ## Security > [accordion] OAuth 2.0 with PKCE > > PayRequest uses industry-standard OAuth 2.0 with PKCE (Proof Key for Code Exchange) for secure authentication without exposing secrets. > [accordion] Scoped Access > > MCP connections only have access to billing data (invoices, statistics). They cannot access payment provider credentials or modify account settings. > [accordion] Revoke Access > > You can disconnect MCP clients at any time from Settings → API in your PayRequest dashboard. > [accordion] Activity Logging > > All MCP actions are logged in your Activity Log for audit purposes. *** ## Next Steps > [card] [Tools Reference](/mcp/tools) > > Learn about all available MCP tools and their parameters > [card] [API Documentation](/api/overview) > > Explore the full PayRequest API for custom integrations # MCP Tools Reference Source: https://docs.payreque.st/mcp/tools Complete reference for PayRequest MCP billing tools # MCP Tools Reference The PayRequest Billing Server provides four tools for managing invoices through AI assistants. ## get-invoice-stats Get aggregated statistics about your invoices including totals, pending amounts, and overdue counts. ### Parameters This tool takes no parameters. ### Example Usage > "What are my invoice statistics?" ### Response ``` Invoice Statistics: - Total invoices: 150 - Pending: 23 (€15,750.00 outstanding) - Paid: 120 - Overdue: 7 (€4,200.00) ``` ### Response Fields | Field | Type | Description | | - | - | - | | `total_invoices` | integer | Total number of invoices | | `pending_invoices` | integer | Invoices awaiting payment | | `paid_invoices` | integer | Fully paid invoices | | `overdue_invoices` | integer | Invoices past due date | | `total_outstanding` | decimal | Sum of all unpaid invoices (EUR) | | `total_overdue` | decimal | Sum of overdue invoices (EUR) | *** ## list-invoices List invoices with optional filtering by status. Returns invoice details including customer information, amounts, and dates. ### Parameters **status** `string` Filter by invoice status. Options: * `pending` - Includes pending, sent, and viewed invoices * `paid` - Only paid invoices * `canceled` - Only canceled invoices * `refunded` - Only refunded invoices **limit** `integer` (default: 20) Maximum number of invoices to return (1-100) ### Example Usage > "Show me all pending invoices" > "List my last 10 paid invoices" ### Response ``` Invoices (filtered by: pending) - showing 5 results: - #INV-2025-050: €2,500.00 | Pending | Due: 2025-02-15 Customer: Acme Corp | Created: 2025-01-30 - #INV-2025-048: €750.00 | Sent | Due: 2025-02-10 Customer: TechStart BV | Created: 2025-01-28 - #INV-2025-045: €1,200.00 | Viewed | Due: 2025-02-05 Customer: Digital Agency | Created: 2025-01-25 ``` *** ## get-overdue-invoices Get a list of all overdue invoices with customer details, amounts, and days overdue. Sorted by due date (oldest first). ### Parameters **limit** `integer` (default: 20) Maximum number of overdue invoices to return (1-100) ### Example Usage > "Which invoices are overdue?" > "Show me the 5 most overdue invoices" ### Response ``` Overdue Invoices (3 total): - Invoice #INV-2025-042: €1,250.00 Customer: Acme Corp Due: 2025-01-15 (14 days overdue) Status: sent - Invoice #INV-2025-038: €600.00 Customer: TechStart BV Due: 2025-01-10 (19 days overdue) Status: viewed - Invoice #INV-2025-035: €450.00 Customer: StartupXYZ Due: 2025-01-05 (24 days overdue) Status: pending Total Overdue Amount: €2,300.00 ``` ### Use Cases > [accordion] Daily billing review > > Ask: "What invoices are overdue?" to start your day with a clear picture of outstanding payments. > [accordion] Priority follow-up > > Ask: "Show me the 5 most overdue invoices" to focus on the oldest unpaid invoices first. > [accordion] Revenue recovery > > Ask: "How much revenue is tied up in overdue invoices?" to understand your cash flow impact. *** ## send-invoice-reminder Send a payment reminder email for a specific invoice. The reminder is sent to the customer's email address and logged in your activity history. ### Parameters **invoice_id** `integer` The ID of the invoice to send a reminder for **invoice_number** `string` The invoice number (e.g., "INV-2025-042") to send a reminder for > [!NOTE] > > Provide either `invoice_id` OR `invoice_number`, not both. ### Example Usage > "Send a reminder for invoice INV-2025-042" > "Remind the customer about invoice 1234" ### Response ``` Payment reminder sent successfully! Invoice: #INV-2025-042 Amount: €1,250.00 (14 days overdue) Customer: Acme Corp Email sent to: billing@acme.com ``` ### Validation The tool validates before sending: | Check | Error Message | | - | - | | Invoice not found | "Invoice not found or does not belong to your account." | | Already paid | "Invoice #X is already paid. No reminder needed." | | Canceled | "Invoice #X is canceled. Cannot send reminder." | | No customer email | "Invoice #X has no customer email address." | ### Activity Logging Each reminder sent via MCP is logged with: * Timestamp * Customer email * Days overdue at time of sending * Source marked as "MCP API" You can view these in **Activity Log** → filter by "Invoice reminder sent". *** ## Error Handling All tools return errors in a consistent format: ``` Error: Authentication required to access invoice statistics. ``` ### Common Errors | Error | Cause | Solution | | - | - | - | | "Authentication required" | Missing or invalid token | Check your API token configuration | | "Invoice not found" | Invalid ID or wrong account | Verify the invoice ID/number | | "Already paid" | Invoice status is 'paid' | No action needed | *** ## Workflow Examples ### Morning Billing Review ``` You: "Give me a billing summary" AI: Here's your invoice summary: - Total invoices: 150 - Pending: 23 (€15,750.00 outstanding) - Paid: 120 - Overdue: 7 (€4,200.00) You: "Which invoices are overdue?" AI: You have 7 overdue invoices totaling €4,200.00... ``` ### Automated Follow-up ``` You: "Send reminders for all invoices more than 14 days overdue" AI: I found 3 invoices more than 14 days overdue. Let me send reminders: ✓ Sent reminder for INV-2025-042 to billing@acme.com ✓ Sent reminder for INV-2025-038 to finance@techstart.nl ✓ Sent reminder for INV-2025-035 to ap@startupxyz.com All 3 reminders sent successfully. ``` ### Customer Query ``` You: "Show me all pending invoices for Acme Corp" AI: I found 2 pending invoices for Acme Corp: - #INV-2025-050: €2,500.00 | Due: Feb 15 - #INV-2025-042: €1,250.00 | Due: Jan 15 (14 days overdue) Total outstanding: €3,750.00 ``` # Billing Activity Log Source: https://docs.payreque.st/organization-and-automation/activity-tracking Track all billing activities, changes, and events across your PayRequest account ## Overview The Billing Activity Log provides a comprehensive audit trail of all actions and events in your PayRequest account. Every subscription change, invoice update, customer modification, and payment event is automatically recorded with timestamps, user attribution, and detailed context. > [!TIP] > > Use the Activity Log to answer questions like "When was this subscription canceled?", "Who sent this invoice?", or "What changed on this customer record?" - all with complete audit history. ## Key Features * **Complete Audit Trail**: Every action automatically logged with timestamp and user * **31+ Event Types**: Subscriptions, invoices, customers, payments, and more * **Advanced Filtering**: Filter by entity type, action, date range, and search * **User Attribution**: See who performed each action (or "System" for automated events) * **IP & Device Tracking**: Security audit with IP address and user agent * **JSON Details**: Rich contextual data for each event * **Real-Time Updates**: Activity appears immediately after actions ## Accessing the Activity Log Navigate to **Activity Log** (or **Logs**) in your dashboard sidebar to view all billing activities. > [!NOTE] > > The Activity Log shows only your own account's activities. Multi-user accounts see activities from all team members. ## Tracked Events PayRequest automatically tracks 31+ distinct event types across your billing operations: ### Subscription Events | Event | Description | Details Captured | | - | - | - | | `subscription_paused` | Subscription manually paused | Pause date, reason | | `subscription_resumed` | Subscription reactivated | Resume date | | `subscription_canceled` | Subscription canceled | Cancellation reason, effective date | | `subscription_completed` | Trial or billing cycle completed | Completion type | | `subscription_settings_updated` | Name, amount, interval, or quantity changed | Old values, new values, changed fields | | `subscription_custom_fields_updated` | Custom field values modified | Field names, old/new values | | `subscription_mandate_updated` | SEPA mandate associated or changed | Mandate ID | | `subscription_fields_synced` | Subscription synced with product changes | Synced fields | ### Invoice Events | Event | Description | Details Captured | | - | - | - | | `invoice_created` | New invoice generated | Invoice number, amount, customer | | `invoice_email_sent` | Invoice email sent automatically | Customer email, invoice number | | `invoice_email_resent` | Invoice manually resent | Resend reason | | `invoice_payment_email_sent` | Payment confirmation sent | Payment amount, method | | `invoice_payment_email_resent` | Payment confirmation resent | Resend timestamp | | `invoice_status_changed` | Invoice status transitioned | Old status, new status, reason | | `invoice_reminder_sent` | Payment reminder sent | Reminder number, days overdue | ### Customer Events | Event | Description | Details Captured | | - | - | - | | `customer_archived` | Customer archived | Archive reason, note, warnings | | `customer_reactivated` | Archived customer reactivated | Reactivation date | ### Payment & Mandate Events | Event | Description | Details Captured | | - | - | - | | `mandate_request_sent` | SEPA mandate request emailed | Customer email | | `mandate_activation_sent` | Mandate activation email sent | Mandate type | | `mandate_activated` | Mandate confirmed via payment | Mandate ID, activation method | | `chargeback_received` | Payment chargeback processed | Amount, reason, payment ID | ### Bulk Operations | Event | Description | Details Captured | | - | - | - | | `bulk_action` | Bulk operation initiated | Action type, affected count | | Individual actions | Each item in bulk operation | Item-specific details | ### Migration Events | Event | Description | Details Captured | | - | - | - | | `mollie_selective_migration_initiated` | Single Mollie subscription migrated | Migration status | | `mollie_bulk_migration_prepared` | Bulk migration prepared | Eligible count | | `mollie_subscription_canceled` | Legacy Mollie subscription canceled | Mollie subscription ID | ## Using the Activity Log ### Viewing Activities The main Activity Log displays: 1. **Date & Time** - When the action occurred (with relative time like "2 hours ago") 2. **Action** - The event type with color-coded badge 3. **User** - Who performed the action (avatar + name, or "System") 4. **Entity Type** - What type of record was affected 5. **Entity** - The specific record (ID and friendly name) 6. **Details** - Expandable section with full context > [!NOTE] > > Color-coded action badges help you quickly identify event types: > > * **Green**: Create, reactivate, activate > * **Red**: Cancel, delete, archive > * **Amber**: Update, change, modify > * **Blue**: Payment, email sent > * **Gray**: Other system events ### Filtering Activities Use the filter controls to narrow down activities: **By Entity Type** * Subscription * Invoice * Customer * Mandate * Payment * And more... **By Action** * Select specific actions like "subscription_canceled" or "invoice_paid" * Shows only available actions from your activity history **By Date Range** * Today * Yesterday * This Week * Last Week * This Month * Last Month **By Search** * Full-text search across entity ID, name, action, and details * Example: Search "INV-2025" to find all activity for that invoice ### Sorting Click column headers to sort by: * **Date** (default, newest first) * **Action** (alphabetical) * **Entity Type** (alphabetical) Click again to reverse sort direction. ## Activity Details Each activity log entry contains rich contextual data in the Details section. ### Invoice Status Change Example ```json theme={null} { "old_status": "open", "new_status": "paid", "reason": "Customer paid via iDEAL", "customer_email": "john@example.com" } ``` ### Subscription Update Example ```json theme={null} { "old_amount": 12.50, "new_amount": 15.00, "changes": ["recurring_amount"], "updated_by": "Admin User" } ``` ### Chargeback Example ```json theme={null} { "amount": 49.00, "reason": "Customer disputed transaction", "payment_id": "tr_AbCdEfGh", "invoice_number": "INV-2025-00123" } ``` ### Customer Archive Example ```json theme={null} { "customer_email": "john@example.com", "archived_reason": "inactive", "archive_note": "No activity for 6 months", "archived_by": "Admin Name", "warnings": ["Active subscription exists"] } ``` ## Dashboard Activity Widget The main dashboard includes a Recent Activity widget showing your latest billing activities at a glance. **Widget Features:** * Shows last 10 activities * Color-coded action icons * Quick link to full Activity Log * Auto-updates with new activities > [!TIP] > > The dashboard activity widget is perfect for monitoring daily operations without navigating to the full Activity Log. ## Security & Compliance ### Audit Trail Benefits The Activity Log serves as your compliance audit trail: * **Who**: User attribution for every action * **What**: Detailed action description with context * **When**: Precise timestamp with timezone * **Where**: IP address and device information * **Why**: Contextual details explaining changes ### Data Captured For security and compliance purposes, each log entry includes: | Field | Description | | - | - | | `user_id` | The user who performed the action | | `ip_address` | Source IP address | | `user_agent` | Browser/client information | | `created_at` | Precise timestamp | | `details` | Full context as JSON | > [!WARNING] > > Activity logs are permanent records and cannot be edited or deleted. This ensures audit trail integrity for compliance purposes. ### Multi-User Accounts For accounts with multiple team members: * Each user's actions are attributed to their account * Admin users can view all team activity * Standard users see only their own activity * System-generated events show "System" as the user ## Common Use Cases ### Investigating Issues **"When was this subscription canceled?"** 1. Go to Activity Log 2. Filter by Entity Type: Subscription 3. Filter by Action: subscription_canceled 4. Search for the subscription name or ID 5. View the details for cancellation reason and timestamp ### Compliance Audits **"Show all invoice status changes this month"** 1. Go to Activity Log 2. Filter by Entity Type: Invoice 3. Filter by Action: invoice_status_changed 4. Set Date Range: This Month 5. Export or screenshot for audit records ### Team Monitoring **"What did my team do today?"** 1. Go to Activity Log 2. Set Date Range: Today 3. Review all activities with user attribution 4. Click on specific entries for details ### Payment Tracking **"Track all payment-related activities"** 1. Go to Activity Log 2. Search for "payment" or "paid" 3. Or filter by actions containing "payment" 4. Review chronological payment history ## Best Practices ### Regular Review * **Daily**: Check dashboard widget for unusual activity * **Weekly**: Review Activity Log for trends * **Monthly**: Audit critical actions (cancellations, chargebacks) ### Search Effectively * Use invoice numbers: "INV-2025-00123" * Use customer emails: "[john@example.com](mailto:john@example.com)" * Use subscription names: "Monthly Plan" * Combine with filters for precise results ### Document Important Events When investigating issues: 1. Note the activity timestamp 2. Record the user who performed the action 3. Save the details JSON for reference 4. Use this information for support tickets or internal documentation ## Troubleshooting ### Activities Not Appearing **Check:** 1. Refresh the page to load latest activities 2. Clear any active filters 3. Expand date range (activities may be older than expected) 4. Verify the action type is logged (not all actions create logs) ### Search Not Finding Results **Try:** 1. Use partial terms instead of full phrases 2. Search by ID instead of name 3. Remove special characters 4. Check spelling of search terms ### Missing User Attribution **Cause:** Action was performed by the system (automated job, webhook) **Solution:** System-generated activities show "System" as the user. This is normal for: * Scheduled billing * Webhook-triggered updates * Automated email sends * Background sync jobs ### Old Activities Not Visible **Note:** Activity logs are retained indefinitely, but very old logs may take longer to load. Use date filters to narrow your search range for better performance. ## Integration with Other Features ### Tags System When tags are added or removed from entities, activity is logged: * Tag additions and removals tracked * Automation-triggered tag changes recorded * Bulk tag operations logged ### Email Automations Email automation triggers create activity logs: * Email bounce events logged * Automated tag actions recorded * Trigger execution tracked ### Bulk Operations All bulk actions are comprehensively logged: * Bulk action initiation recorded * Individual item changes logged * Success/failure status captured ## Frequently Asked Questions > [accordion] How long are activity logs retained? > > Activity logs are retained indefinitely. All historical activity remains accessible for compliance and audit purposes. There is no automatic deletion of activity history. > [accordion] Can I export activity logs? > > Currently, activity logs are view-only in the dashboard. For export needs, contact support for assistance with compliance reports or use the API for programmatic access. > [accordion] Who can see activity logs? > > Standard users see only their own activity. Admin users can view activity from all team members. Activity logs are never visible to your customers. > [accordion] Are automated actions logged? > > Yes. System-generated actions (scheduled billing, webhooks, automated emails) are logged with "System" as the user. This provides complete visibility into both manual and automated operations. > [accordion] Can I delete or edit activity logs? > > No. Activity logs are immutable records that cannot be modified or deleted. This ensures audit trail integrity for compliance and security purposes. > [accordion] Why don't I see some actions in the log? > > Not all actions generate activity logs. The system focuses on billing-critical events: subscription changes, invoice updates, customer modifications, and payment events. Minor UI interactions are not logged. > [accordion] How do I find activities for a specific customer? > > Use the search function to search for the customer's email address or name. You can also filter by Entity Type "Customer" to see customer-specific events, or search for their related invoice/subscription IDs. > [accordion] What timezone are timestamps in? > > Timestamps are displayed in your local timezone (Europe/Amsterdam for PayRequest). The relative time display (e.g., "2 hours ago") adjusts automatically. ## Related Features > [card] [Tags System](/organization-and-automation/tags-system) > > Organize entities with tags (changes logged) > [card] [Email Automations](/organization-and-automation/email-automations) > > Automate actions based on events > [card] [Subscription Management](/subscriptions/subscription-lifecycle) > > Manage subscriptions (all changes logged) > [card] [Invoice Management](/invoices/creating-invoices) > > Create and manage invoices (all actions logged) # Bulk Operations Source: https://docs.payreque.st/organization-and-automation/bulk-operations Perform mass updates, price adjustments, and exports across subscriptions, customers, products, invoices, and orders. # Bulk Operations The Bulk Actions wizard lets you perform mass operations on multiple items at once. Select your items manually or filter by tags, validate before executing, and track every action in the history log. > [!NOTE] > > Access Bulk Operations from **Dashboard > Bulk Actions** or navigate directly to `/bulk`. ## Supported Entity Types > [card] Subscriptions > > Price adjustments, pause, resume, cancel, change interval > [card] Customers > > Apply tags, change language, toggle tax exemption, send email > [card] Products > > Update prices, change tax rate, toggle active status, apply category > [card] Invoices > > Mark as paid, send reminders, apply late fees, export PDF > [card] Orders > > Update status, apply shipping, send notifications > [card] Export > > Export any entity type to CSV ## How It Works **1. Select Type** Choose the entity type you want to work with (subscriptions, customers, products, etc.) **2. Select Items** Pick items manually from a searchable list, or use **tag-based selection** with AND/OR logic to filter automatically. **3. Choose Action** Select the action and configure its parameters. Different actions show different configuration fields. **4. Validate** Review validation results. Errors block execution, while warnings allow you to proceed with caution. **5. Execute** Confirm and run the action. Results are saved to the action history for auditing. ## Subscription Actions | Action | Description | | - | - | | **Apply Inflation Adjustment** | Increase prices by percentage, fixed amount, or set a specific price. Supports rounding, scheduling, and customer notifications. [Full guide](/subscriptions/price-adjustments) | | **Pause Until Date** | Pause selected subscriptions until a specific date, then auto-resume | | **Resume Subscriptions** | Resume paused or canceled subscriptions immediately or on a specific date | | **Cancel at End of Period** | Schedule cancellation at the end of the current billing period | | **Change Billing Interval** | Switch between daily, weekly, monthly, quarterly, or yearly billing | ## Customer Actions | Action | Description | | - | - | | **Apply Tags** | Add one or more tags to selected customers | | **Change Language** | Update the preferred language for communications | | **Toggle Tax Exemption** | Enable or disable tax-exempt status | | **Send Email** | Send a custom email to selected customers | ## Selection Methods ### Manual Selection Browse or search the paginated item list and select individual items with checkboxes. Use **Select All** to pick everything on the current page. ### Tag-Based Selection Filter items by tags using two logic modes: * **OR** — Items with **any** of the selected tags (broader selection) * **AND** — Items with **all** of the selected tags (narrower selection) > [!TIP] > > Use tags to organize subscriptions into groups like "Annual Review", "Enterprise", or "Legacy Pricing". This makes it easy to select the right subscriptions for targeted price adjustments. ## Action History Every bulk action is logged with full details: * Entity type and action performed * Number of items affected * Action parameters used * Success or failure status * Timestamp View recent history at the bottom of the Bulk Actions page, or click **View Details** on any entry for a full breakdown. ## Next Steps > [card] [Bulk Price Adjustments](/subscriptions/price-adjustments) > > Detailed guide for subscription inflation and pricing changes > [card] [Tags System](/organization-and-automation/tags-system) > > Organize items with tags for easier bulk selection # Email Automations Source: https://docs.payreque.st/organization-and-automation/email-automations Automatically tag customers and take action when emails bounce, get spam complaints, or fail to deliver # Email Automations Email automations let you trigger actions when email delivery events occur. The most common use case is automatically tagging customers with an "Invalid Email" tag when their email bounces, making it easy to find and fix problematic addresses. > [!NOTE] > > Email automations work together with the [Email Health & Bounce Suppression](/customer-management/customer-health) system, which automatically blocks emails to bounced addresses. *** ## Default Automation: Bounce Tagging PayRequest comes with a pre-built automation template: **Email Bounce → Add Invalid Email Tag** This automation: 1. Triggers when a customer's email bounces 2. Creates an "Invalid Email" tag (red) if it doesn't exist 3. Attaches the tag to the affected customer ### Setting It Up **1. Go to Automations** Navigate to **Automations** from the sidebar. **2. Create the default automation** Click **Create Automation** — the bounce tagging template is pre-filled. **3. Customize (optional)** Change the tag name or color if you prefer a different label. **4. Save** The automation activates immediately and processes all future bounces. *** ## Available Triggers | Trigger | When It Fires | | - | - | | **Email Bounced** | Recipient server rejects the email (permanent or transient) | | **Email Complained** | Recipient marks the email as spam | | **Email Failed** | Email fails to send for any other reason | ## Available Actions | Action | What It Does | | - | - | | **Add Tag** | Attaches a tag to the customer | | **Remove Tag** | Removes a tag from the customer | *** ## Automatic Tag Cleanup When you update a customer's email address to a different one, PayRequest automatically removes any tags that were added by email bounce automations. This means fixing an email address also cleans up the "Invalid Email" tag without manual work. > [!TIP] > > Combine bounce tagging with the **Email Issues** filter on the customer list to quickly review and fix all affected customers at once. *** ## Next Steps > [card] [Email Health & Suppression](/customer-management/customer-health) > > How bounce suppression protects your sender reputation > [card] [Tags System](/organization-and-automation/tags-system) > > Learn more about organizing with tags # Tags System Source: https://docs.payreque.st/organization-and-automation/tags-system Organize your business data with color-coded labels for segmentation, filtering, and automation ## Overview Tags are customizable labels that help you organize and segment your business data in PayRequest. Apply tags to customers, subscriptions, products, invoices, smart links, and expenses to create powerful workflows, filter data, and trigger automations. > [!TIP] > > Tags are essential for organizing large datasets. Create tags for customer segments (VIP, trial users), product categories (services, physical), or campaigns (Summer 2025) to quickly filter and analyze your data. ## Key Features * **Color-Coded Labels**: 18 color options for visual organization * **Multi-Entity Support**: Tag customers, subscriptions, products, invoices, smart links, and expenses * **Filtering & Segmentation**: Filter any entity list by tags with AND/OR logic * **Automation Triggers**: Automatically add/remove tags based on email events * **Usage Tracking**: See how many entities use each tag * **CSV Export**: Export tagged entities for reporting * **Per-Business Isolation**: Tags are private to your business account ## Accessing Tags Navigate to **Tags** in your dashboard sidebar to access the tag management interface. > [!NOTE] > > Tags are available for all PayRequest accounts. You can create unlimited tags per entity type. ## Supported Entity Types PayRequest supports tagging 8 different entity types: | Type | Description | Common Use Cases | | - | - | - | | **Customer** | Customer profiles | VIP, Active, Churned, Lead Source | | **Subscription** | PayRequest & Mollie subscriptions | Plan tier, Trial, Annual, Monthly | | **Product** | Digital products and services | Category, Featured, On Sale | | **Order** | Shop orders | Fulfilled, Needs Review, Wholesale | | **Invoice** | Invoices and bills | Urgent, Overdue, Paid, Disputed | | **Smart Link** | Marketing payment links | Campaign, Channel, Season | | **Expense** | Recurring expenses | Software, Marketing, Operations | | **Support** | Support-related items | Priority, Department, Status | > [!NOTE] > > A `DebtCollection` tag type also exists at the data level but isn't selectable in the tag creation UI yet — you can't create a Debt Collection tag from the Tags page today. ## Creating Tags ### Step 1: Open Tag Creation From the Tags page, click **Create Tag** in the top right corner. ### Step 2: Configure Tag Details **Required Fields:** * **Name**: Descriptive label (e.g., "VIP Customer", "Summer Campaign") * **Type**: Select entity type (Customer, Subscription, Product, etc.) * **Color**: Choose from 18 color options > [!NOTE] > > Tag names must be unique within each type. You can have a "VIP" customer tag and a "VIP" product tag, but not two "VIP" customer tags. ### Step 3: Save Tag Click **Create Tag** to save. The tag is immediately available for use across your dashboard. ## Available Colors Choose from 18 color options to visually distinguish your tags: > [card] Neutral > > zinc > [card] Warm > > red, orange, amber, yellow > [card] Cool > > lime, green, emerald, teal, cyan, sky, blue, indigo > [card] Accent > > violet, purple, fuchsia, pink, rose > [!TIP] > > Use consistent color schemes for similar tags. For example, all subscription tier tags could use shades of blue, while all campaign tags use warm colors. ## Applying Tags ### To Products 1. Go to **Products** in the sidebar 2. Click on a product to view details 3. Click **Manage Tags** button 4. Select tags from the dropdown or create new ones inline 5. Click **Save Tags** ### To Subscriptions 1. Go to **Subscriptions** in the sidebar 2. Click on a subscription to view details 3. Scroll to the **Tags** section 4. Click **Manage Tags** 5. Select or create tags 6. Click **Save Tags** ### To Customers 1. Go to **Customers** in the sidebar 2. Click on a customer profile 3. Locate the **Tags** section 4. Add or remove tags as needed ### To Orders 1. Go to **Orders** in the sidebar 2. Open an order to view details 3. Use the tag management interface to add tags ### To Invoices 1. Go to **Invoices** in the sidebar 2. Click on an invoice to view details 3. Use the tag management interface to add tags ### To Smart Links When creating or editing a smart link: 1. Scroll to the **Tags** field 2. Select existing tags or create new ones 3. Tags help organize links by campaign, channel, or purpose ### To Expenses In the Expense Tracker: 1. Open an expense record 2. Add tags to categorize by department, type, or project ## Filtering by Tags ### Basic Filtering Most entity list pages support tag filtering: 1. Locate the **Tag Filter** dropdown 2. Select one or more tags 3. The list updates to show only matching items ### AND vs OR Logic When selecting multiple tags: **ANY (OR Logic)** - Default * Shows items that have **at least one** of the selected tags * Example: Select "VIP" and "Trial" → Shows VIP customers OR trial customers **ALL (AND Logic)** - Toggle available * Shows items that have **all** selected tags * Example: Select "VIP" and "Annual" → Shows only customers who are BOTH VIP AND on annual plans > [!NOTE] > > The filter logic toggle appears when you select multiple tags. Click to switch between ANY and ALL matching modes. ## Tag View & Analytics ### Accessing Tag Details Click on any tag name to view its detail page, which shows: **Tag Information** * Name, color, and type * Total usage count * Creation date **Tagged Entities** * List of all entities using this tag * Searchable and paginated * Organized by entity type ### Usage Breakdown For Subscription tags, you'll see separate counts: * PayRequest subscriptions (native) * Mollie subscriptions (legacy) ### CSV Export Export tagged entities for reporting: 1. Open a tag detail page 2. Navigate to the entity type section 3. Click **Export CSV** 4. Download includes entity details with tag information ## Tag Automations Tags integrate with PayRequest's automation system for powerful workflow automation. ### Automatic Tagging via Email Events Set up automations to automatically tag customers based on email delivery status: **Available Triggers:** * `email_bounced` - Email couldn't be delivered * `email_complained` - Recipient marked as spam * `email_failed` - Email delivery failed **Common Automation Example:** ``` Trigger: email_bounced Action: add_tag Tag: "Invalid Email" ``` > [!WARNING] > > Email automations help maintain clean customer data. Tag bounced emails to prevent sending to invalid addresses and protect your sender reputation. ### Setting Up Tag Automations 1. Go to **Automations** in the sidebar 2. Click **Create Automation** 3. Select trigger type (e.g., Email Bounced) 4. Choose action: **Add Tag** or **Remove Tag** 5. Select or create the target tag 6. Save and activate > [!TIP] > > Create a "Verified Email" tag and remove it when emails bounce. Use this tag for filtering customers with confirmed email addresses. ### Automatic Tagging via Smart Links Smart Links support automatic customer tagging after successful payments. This is powerful for tracking campaign conversions and customer lifecycle. **Available Actions:** | Action | Description | | - | - | | **Apply Tag** | Add a Customer tag after payment | | **Remove Tag** | Remove a Customer tag after payment | **Common Use Cases:** ``` Smart Link: "Summer Campaign 2025" Customer: John Doe After Payment: Apply tag "Summer 2025 Customer" ``` ``` Smart Link: "Upgrade to Premium" Customer: Jane Smith After Payment: - Remove tag "Free Tier" - Apply tag "Premium Customer" ``` **Setting Up Smart Link Tag Automation:** 1. Go to **Smart Links** and create or edit a link 2. Select a customer in **Send smart payment link to customer** 3. Scroll to **After Payment Actions** 4. Configure **Apply Tag to Customer** to add a tag 5. Configure **Remove Tag from Customer** to remove a tag 6. Save the smart link > [!NOTE] > > The Remove Tag dropdown only shows tags that the selected customer currently has, plus any tag you've selected to apply (since it will be added upon payment). **Combining with Redirect:** You can combine tag automation with redirect actions: 1. Apply a tag (e.g., "Paid Customer") 2. Remove a tag (e.g., "Lead") 3. Redirect to a thank-you page All three actions execute after successful payment. > [!TIP] > > Use Smart Link tag automation to move customers through your sales funnel automatically. Remove "Prospect" tags and add "Customer" tags upon payment completion. ## Managing Tags ### Editing Tags 1. From the Tags list, click **Edit** on any tag 2. Modify name, color, or type 3. Changes apply immediately to all tagged entities ### Deleting Tags 1. Click **Delete** on a tag 2. If the tag is in use, you'll see a warning with usage count 3. Confirm deletion > [!WARNING] > > Deleting a tag removes it from ALL entities that use it. This action cannot be undone. Consider renaming or deactivating tags instead. ### Tag Type Restrictions Once a tag is created with a specific type, it can only be applied to that entity type: * Customer tags → Customers only * Product tags → Products only * Subscription tags → Both PayRequest and Mollie subscriptions ## Best Practices ### Naming Conventions **Do:** * Use descriptive names: "Q4 2025 Campaign" instead of "Campaign1" * Be consistent: "VIP Customer" and "VIP Product" are clear * Use categories: "Lead Source: Website", "Lead Source: Referral" **Don't:** * Use vague names: "Tag1", "Test", "New" * Create duplicates: "VIP" and "V.I.P." and "vip" * Use overly long names (max 255 characters) ### Color Strategy Assign colors with meaning: | Color | Suggested Use | | - | - | | **Green** | Positive status (Active, Paid, Verified) | | **Red** | Negative/Urgent (Overdue, Churned, Invalid) | | **Blue** | Information (Plan tier, Category) | | **Yellow/Orange** | Warning/Attention (Trial ending, Needs review) | | **Purple** | Special (VIP, Featured, Premium) | ### Organization Tips 1. **Start Simple**: Begin with 3-5 essential tags per type 2. **Review Regularly**: Remove unused tags quarterly 3. **Document Purpose**: Use consistent naming so team members understand tag meanings 4. **Combine with Automations**: Let automations handle routine tagging ## Use Cases ### Customer Segmentation **Lifecycle Tags:** * Trial User * Active Customer * At Risk * Churned **Value Tags:** * VIP * High Value * New Customer * Referral Partner ### Subscription Management **Plan Tags:** * Freelancer Plan * Business Plan * Enterprise * Legacy Plan **Status Tags:** * Annual Billing * Monthly Billing * Trial Period * Pending Cancellation ### Marketing Campaigns **Smart Link Tags:** * Black Friday 2025 * Email Campaign * Social Media * Partner Referral ### Invoice Organization **Status Tags:** * Urgent * Disputed * Partial Payment * Sent Reminder ## Troubleshooting ### Tags Not Appearing **Check:** 1. Tag type matches entity type (Customer tag won't appear on Products) 2. You're filtering by the correct type 3. Clear browser cache and refresh ### Can't Delete Tag **Cause:** Tag is currently in use **Solution:** 1. View tag details to see which entities use it 2. Remove tag from all entities first 3. Then delete the tag ### Duplicate Tags **Cause:** Tags were created with similar names or different capitalizations **Solution:** 1. Identify the duplicate tags 2. Update entities to use one tag consistently 3. Delete the unused duplicate ### Automations Not Adding Tags **Check:** 1. Automation is set to **Active** 2. Trigger conditions are met 3. Tag exists and matches entity type 4. No errors in automation logs ## API Integration For developers integrating with PayRequest: ### Tag Structure ```json theme={null} { "id": 1, "name": "VIP Customer", "color": "purple", "type": "Customer", "user_id": 1, "created_at": "2025-01-15T10:30:00Z" } ``` ### Polymorphic Relationship Tags use Laravel's polymorphic many-to-many relationships: * **tags** table: Tag definitions * **taggables** table: Pivot table linking tags to entities * `tag_id`: Reference to tag * `taggable_id`: Entity ID * `taggable_type`: Entity class (Customer, Product, etc.) ## Frequently Asked Questions > [accordion] Can I use the same tag across different entity types? > > No. Each tag is specific to one entity type. However, you can create tags with the same name for different types (e.g., "VIP" for both Customers and Products). They will be separate tags with independent usage tracking. > [accordion] Is there a limit to how many tags I can create? > > No, there's no limit. However, for practical organization, we recommend keeping your tag count manageable - typically under 50 tags per type. > [accordion] Can my customers see tags? > > No. Tags are internal organizational tools only. They're visible only in your dashboard and never shown in the customer portal, shop, or invoices. > [accordion] What happens to tags when I delete an entity? > > When you delete a customer, subscription, or other entity, the tag associations are automatically removed. The tags themselves remain available for other entities. > [accordion] Can I bulk-apply tags to multiple entities? > > Currently, tags are applied individually. For bulk operations, consider using the CSV import feature with tag assignments or setting up automations for automatic tagging. > [accordion] Do tags work with both PayRequest and Mollie subscriptions? > > Yes! The Subscription tag type works with both PayRequest native subscriptions and legacy Mollie subscriptions. You can tag and filter both types using the same tags. > [accordion] Can I search for entities by tag? > > Yes. Most entity list pages include a tag filter dropdown. Select one or more tags to filter the displayed items. You can also search within tagged entities on tag detail pages. > [accordion] How do tag automations work with new customers? > > Automations run when specific events occur (like email bounces). For new customer tagging, you'll need to manually apply tags or use future automation triggers like "customer_created" when available. > [accordion] Can Smart Links automatically tag customers after payment? > > Yes! When creating or editing a Smart Link, you can configure automatic tag actions in the After Payment Actions section. You can apply a Customer tag, remove a Customer tag, or do both. These actions execute automatically when the customer completes payment. This is useful for tracking campaign conversions and moving customers through your sales funnel. ## Related Features > [card] [Email Automations](/organization-and-automation/email-automations) > > Set up automatic tagging based on email events > [card] [Customer Management](/customer-management/customer-profiles) > > Organize and segment your customers > [card] [Smart Links](/payment-processing/smart-links) > > Tag marketing links by campaign > [card] [Activity Tracking](/organization-and-automation/activity-tracking) > > Monitor tag changes in activity log # Webhook Configuration Source: https://docs.payreque.st/organization-and-automation/webhook-configuration Real-time event notifications # Webhook Configuration Get notified the instant a payment succeeds. PayRequest can send a signed HTTP request to your own server every time a `Transaction` is marked paid — regardless of which payment method or provider was used (Mollie, Stripe, PayPal, bank transfer, crypto, etc). > [!NOTE] > > Currently one event is supported: **`payment.succeeded`**. You can configure a single webhook URL per account. ## Setting Up Your Webhook **1. Open API & Webhook settings** Go to **Settings → API Tokens** in your dashboard. **2. Enter your webhook URL** Enter the HTTPS endpoint on your server that should receive payment notifications. **3. Save — a signing secret is generated** The first time you save a webhook URL, PayRequest generates a **webhook secret** used to sign every request. You'll need this to verify incoming requests. **4. Verify signatures on your server** Use the secret to validate the `X-PayRequest-Signature` header on every request you receive (see below). > [!TIP] > > You can regenerate your webhook secret at any time from the same settings page if you suspect it's been exposed. Doing so immediately invalidates the old secret. ## Payload When a transaction is marked paid, PayRequest sends a `POST` request with this JSON body: ```json theme={null} { "event": "payment.succeeded", "timestamp": "2026-07-13T10:15:00+00:00", "data": { "id": 48213, "amount": 49.00, "currency": "EUR", "description": "Invoice #1042", "payment_link_id": 1809, "payment_method": "ideal", "reference": "tr_abc123", "paid_at": "2026-07-13T10:14:58+00:00", "customer": { "id": 512, "name": "Jane Doe", "email": "jane@example.com" } } } ``` | Field | Description | | - | - | | `event` | Always `payment.succeeded` currently | | `timestamp` | When the webhook was dispatched (ISO 8601) | | `data.id` | PayRequest transaction ID | | `data.amount` | Amount as a decimal (never divided/multiplied — matches what the customer paid) | | `data.currency` | ISO currency code, defaults to `EUR` | | `data.payment_link_id` | Smart Link ID, if the payment came from one | | `data.payment_method` | Payment method used (`ideal`, `creditcard`, `crypto_usdc`, etc) | | `data.reference` | Provider-specific transaction reference | | `data.customer` | `null` if no customer is attached to the transaction | ## Verifying the Signature Every request includes an `X-PayRequest-Signature` header in the form `sha256={hmac}`, where `{hmac}` is an HMAC-SHA256 of the raw JSON body, signed with your webhook secret. ```php theme={null} $payload = file_get_contents('php://input'); $signature = $_SERVER['HTTP_X_PAYREQUEST_SIGNATURE'] ?? ''; $expected = 'sha256=' . hash_hmac('sha256', $payload, $yourWebhookSecret); if (! hash_equals($expected, $signature)) { http_response_code(401); exit; } ``` > [!WARNING] > > Always compare signatures with a constant-time function (like PHP's `hash_equals`) to avoid timing attacks. Never compare with `==` or `===`. ## Delivery Behavior * Webhooks are dispatched asynchronously via a queued job as soon as a transaction is marked paid * Requests time out after **10 seconds** * Delivery is **best-effort** — PayRequest does not currently guarantee automatic retries if your endpoint is unreachable or returns an error, so make sure your endpoint responds quickly and reliably * Only one webhook URL is supported per account; every `payment.succeeded` event goes to the same endpoint > [!TIP] > > Since delivery isn't guaranteed to retry, treat webhooks as a fast notification layer rather than your only source of truth. You can always confirm a payment by checking the transaction or invoice status in the PayRequest dashboard or via the [API](/api/overview). ## Testing Your Endpoint There's no built-in webhook test-send tool yet — the simplest way to test is to trigger a real (or testmode) payment and confirm your endpoint receives and correctly verifies it. Tools like [webhook.site](https://webhook.site) or [ngrok](https://ngrok.com) are useful for inspecting payloads during local development. ## FAQ > [accordion] What events can I subscribe to? > > Currently only `payment.succeeded`. Additional events (subscription lifecycle, invoice status changes) are on the roadmap. > [accordion] Can I have multiple webhook URLs? > > Not yet — one webhook URL per account. If you need to notify multiple systems, have your endpoint fan the event out internally. > [accordion] What happens if my endpoint is down? > > The request will fail and the failure is logged on PayRequest's side, but it is not automatically retried. Make sure your endpoint has good uptime, and reconcile periodically against the dashboard or API as a safety net. > [accordion] Does this fire for crypto and manual/bank transfer payments too? > > Yes. The webhook fires whenever a `Transaction` record is marked paid, regardless of payment method — including crypto (USDC), bank transfers, and manually recorded payments. ## Next Steps > [card] [API Reference](/api/overview) > > Query transactions and invoices directly instead of (or alongside) webhooks > [card] [Webhook Development](/advanced-features/webhook-development) > > Advanced patterns for building against PayRequest webhooks > [card] [Smart Links](/payment-processing/smart-links) > > See how payment_link_id maps back to a Smart Link # Payment methods Source: https://docs.payreque.st/payment-methods Find setup instructions and troubleshooting for the payment methods you offer through PayRequest. Choose a payment method to learn how to enable it, what your customers need and what to check if it is missing from checkout. > [!NOTE] > > Available methods depend on your connected payment provider, merchant approval, country, currency and payment flow. A payment method such as Apple Pay is not a separate merchant-provider account. > [card] [Apple Pay](https://docs.payreque.st/payment-methods/apple-pay) > > Enable Apple Pay through Mollie and check browser and device availability. > [card] [Klarna](https://docs.payreque.st/payment-methods/klarna) > > Enable Klarna through Mollie and understand billing details and payment approval. > [card] [Pay by Bank](https://docs.payreque.st/payment-processing/pay-by-bank) > > Accept bank payments and understand the first payment for automatic EUR subscriptions. > [card] [Bank transfer](https://docs.payreque.st/payment-processing/bank-transfer) > > Receive bank transfers and understand payment matching. For cards, PayPal, other wallets and regional options, see the [payment methods overview](https://docs.payreque.st/payment-processing/payment-methods-overview). Need to connect your merchant account first? Start with [payment-provider setup](https://docs.payreque.st/payment-processing/setting-up-payment-providers). # Apple Pay Source: https://docs.payreque.st/payment-methods/apple-pay Offer Apple Pay through Mollie on your PayRequest Page and payment links, and troubleshoot browser and device availability. Customers can choose **Apple Pay** on your PayRequest Page and payment links when it is available through your connected Mollie account. You keep using your existing Page and links. > [!NOTE] > > You need your own approved, payment-ready Mollie account. A PayRequest plan or a buyer's ability to use Apple Pay does not establish payment-provider eligibility for your business country. ## Enable Apple Pay **1. Connect your Mollie account** Complete [payment-provider setup](https://docs.payreque.st/payment-processing/setting-up-payment-providers) and confirm that the connection is ready to receive payments. **2. Enable cards and Apple Pay in Mollie** Open the Mollie website profile connected to PayRequest. Enable both **cards** and **Apple Pay**, and complete any additional verification requested by Mollie. **3. Check your PayRequest method selection** Open [Provider Settings](https://payrequest.app/provider-settings). If you have selected a custom list of Mollie payment methods, include Apple Pay. **4. Review your public Page** Open your normal public Page or payment link in a supported browser. Checking that the option is visible does not confirm a successful payment. ## What customers see Apple Pay appears when your Mollie profile offers it and the customer's browser supports it. Supported desktop browsers can also offer Apple Pay; the page does not have to be opened on an iPhone. The customer selects **Apple Pay** and continues to Mollie's secure checkout to authorize the payment. The available authorization options depend on the customer's browser, device and Apple Pay setup. ## Apple Pay is missing | What you see | What to check | | - | - | | Apple Pay is missing everywhere | Confirm that your Mollie connection is payment-ready, cards and Apple Pay are enabled on the connected profile, and your PayRequest method selection includes Apple Pay. | | Apple Pay appears on one device but not another | Check the second browser's compatibility and the customer's Apple Pay setup. | | A supported browser still does not show Apple Pay | Check whether browser extensions or blocked payment scripts prevent the availability check. | > [!TIP] > > A missing option on one browser does not by itself mean your Mollie connection has failed. Try another supported browser before reconnecting your account. ## If you use Stripe The setup above describes the Mollie flow. Stripe has its own browser and payment-domain requirements. Apple Pay appearing through Mollie does not confirm it is configured on a separate Stripe connection. See [connecting Stripe](https://docs.payreque.st/payment-processing/connect-stripe). ## Fees and help Your PayRequest plan and provider processing fees are separate. Review your [plan](https://docs.payreque.st/business-settings/payrequest-plans) and provider agreement for the fees that apply. For help, send your Page URL, browser/device, error message and time of the attempt to [PayRequest support](mailto:support@payrequest.io). Do not send card details, passwords or API keys. If a payment is pending or the buyer has already been charged, check its status before asking them to pay again. Provider reference: [Mollie Apple Pay](https://docs.mollie.com/docs/apple-pay). Browse [all payment methods](https://docs.payreque.st/payment-methods). # Klarna Source: https://docs.payreque.st/payment-methods/klarna Offer Klarna through Mollie on your PayRequest Page and payment links, collect billing details and understand payment approval. Customers can choose **Klarna** on your PayRequest Page and payment links when it is available through your connected Mollie account. You keep using your existing Page and links. > [!NOTE] > > You need your own approved, payment-ready Mollie account with Klarna available for your business. Enabling Klarna does not guarantee a pay-later offer or payment approval for every buyer. ## Enable Klarna **1. Connect your Mollie account** Complete [payment-provider setup](https://docs.payreque.st/payment-processing/setting-up-payment-providers) and confirm that the connection is ready to receive payments. **2. Enable Klarna in Mollie** Open the Mollie website profile connected to PayRequest and enable **Klarna** if it is available. Complete any additional approval or verification requested by Mollie. **3. Check your PayRequest method selection** Open [Provider Settings](https://payrequest.app/provider-settings). If you have selected a custom list of Mollie payment methods, include Klarna. **4. Review your public Page** Open your normal Page or payment link and select Klarna to review the billing fields. Viewing the method or filling its fields does not confirm a successful payment. ## Required billing details The payment option is labelled **Klarna** and displays the Klarna logo. Selecting it opens fields for: * First and last name * Email address * Street and house number * Postal code, city and country The buyer completes these details and continues to Mollie/Klarna to review the available payment options. These billing fields are required for Klarna; they do not block payment with another selected method. ## Payment approval Klarna decides which options to offer and whether to approve each payment. Availability depends on factors such as the customer, country, currency and amount. Connecting Mollie does not override this decision. Choosing Klarna does not set up automatic recurring collection. For subscriptions, follow the separate [subscription payment methods](https://docs.payreque.st/subscriptions/payment-methods) guide. ## Klarna is missing or a payment fails | What you see | What to check | | - | - | | Klarna is not offered | Check that the connected Mollie profile is payment-ready, Klarna is enabled and eligible there, and your PayRequest method selection includes it. | | Klarna asks for more details | Complete all the displayed name, email and billing-address fields. | | Klarna declines the payment | The buyer can choose another available method. Reconnecting Mollie does not override Klarna's decision. | If the buyer has already been charged or the payment is pending, check the payment status before asking them to pay again. See [payment failures](https://docs.payreque.st/troubleshooting/payment-failures). ## Fees and help Your PayRequest plan and provider processing fees are separate. Review your [plan](https://docs.payreque.st/business-settings/payrequest-plans) and Mollie agreement for the fees that apply. For help, send your Page URL, error message and time of the attempt to [PayRequest support](mailto:support@payrequest.io). Do not send card details, passwords or API keys. Provider reference: [Mollie Klarna](https://docs.mollie.com/docs/klarna). Browse [all payment methods](https://docs.payreque.st/payment-methods). # AI Name Suggestions Source: https://docs.payreque.st/payment-processing/ai-name-suggestions Offer optional customer name suggestions from email addresses on your payment and product pages AI Name Suggestions offers visitors a possible name based on their email address. They can accept the suggestion with one click or enter their name themselves. It works in the editable payment form on your PayRequest Page, including product and Smart Link payment forms that use that Page. > [!NOTE] > > AI Name Suggestions is available with an active **Premium or Business** subscription. Eligible complimentary Premium or Business subscriptions explicitly granted by PayRequest also qualify. It is **off by default** and can be switched on or off separately for each Page. ## Enable AI Name Suggestions **1. Open your Page settings** In your dashboard, open **PayRequest Page**, select **Settings**, and find **Options**. **2. Turn on AI Name Suggestions** Enable the **AI Name Suggestions** switch. The change is saved automatically. **3. Check your public form** Open your payment or product page as a visitor. Enter an email address and leave the name field empty. Allow a few seconds for a possible suggestion to appear. ## What visitors see The visitor enters their email address first. If a possible name can be recognized, a **Use suggested name** option appears below the name field. Clicking that option fills the name field. The visitor can edit it before paying. An existing, manually entered or read-only name is not replaced. | Example email | Possible suggestion | | - | - | | `john.smith@example.com` | John Smith | | `oliverbramwell8@example.com` | Oliver Bramwell | | `j.van.der.meer@example.com` | J van der Meer | | `anne-marie.vermeer@example.com` | Anne-Marie Vermeer | | `support42@example.com` | No suggestion: a general mailbox | These are illustrative examples. Names can have several valid spellings, so the visitor should choose the name they actually use. ## Which email patterns work? AI Name Suggestions can recognize names separated by dots, underscores or hyphens, as well as some joined names. It also supports separated initials, compound given names and surname particles such as **van der** or **de la**. Trailing mailbox numbers, such as the `8` in `oliverbramwell8`, are excluded from the name suggestion. Plus-address tags, such as `+orders` in `john.smith+orders@example.com`, are excluded too. The visitor's email address itself is not changed. General mailboxes such as `info@`, `support@` and `accounts@` do not receive personal name suggestions. Some addresses contain too little recognizable name information to produce a useful result. ## What information is used? Only the name-shaped part before `@`, without plus-address tags or trailing numbers, is sent to the AI service. The email domain, payment details and other customer records are not sent for this feature. The feature interprets the address text; it does not search for a person or confirm who owns the mailbox. Suggestions may be temporarily cached. > [!NOTE] > > A name suggestion is not a verified identity. The visitor remains responsible for entering the name they want to use for their order. ## Turn it off Return to **PayRequest Page → Settings → Options** and disable **AI Name Suggestions**. The change saves automatically. New AI lookups are blocked, even from a payment page that was already open. The feature also stops if your account no longer has eligible Premium or Business access. Normal name entry and browser autofill remain available. ## If no suggestion appears * Check that the feature is enabled for the Page and your eligible subscription is active. * Leave the editable name field empty. Saved or prefilled names are preserved. * Allow a few seconds after entering the email address. * If the address has no recognizable personal name, or the AI service is temporarily unavailable, enter the name normally. AI Name Suggestions is optional. Visitors can complete their payment without using it. # Bank Sync (Ponto) Source: https://docs.payreque.st/payment-processing/bank-sync-ponto Connect your bank account for automatic transaction syncing and Bank Transfer payments # Bank Sync (Ponto) Ponto is an open banking platform that connects your business bank account to PayRequest. This enables automatic transaction syncing and powers the Bank Transfer payment method. > [!NOTE] > > **Powered by Isabel Group**: Ponto is a trusted open banking solution used by thousands of European businesses for secure bank connectivity. ## What Ponto Enables > [card] Transaction Syncing > > Automatically import your bank transactions into PayRequest for reconciliation and reporting > [card] Bank Transfer Payments > > Accept bank transfers with automatic payment matching using reference codes > [card] Balance Monitoring > > View your real-time bank balance directly in PayRequest > [card] Financial Insights > > Better understand your cash flow with integrated bank data ## Connecting Ponto ### Prerequisites Before connecting Ponto, ensure you have: * A **business bank account** with a Ponto-supported bank * **Admin access** to your PayRequest account * Your **bank login credentials** ready ### Supported Banks Ponto supports most major European banks including: > [tab] Netherlands > > * ABN AMRO > * ING > * Rabobank > * SNS Bank > * ASN Bank > * RegioBank > * Triodos Bank > [tab] Belgium > > * KBC > * BNP Paribas Fortis > * ING Belgium > * Belfius > * Argenta > * AXA Bank > [tab] Other EU > > * Deutsche Bank > * Commerzbank > * BNP Paribas > * Crédit Agricole > * And many more... > [!TIP] > > **Check Availability**: Visit the Ponto website to verify your specific bank is supported before starting the connection process. ### Connection Steps **1. Navigate to Settings** Go to **Settings → Ponto** in your PayRequest dashboard **2. Initiate Connection** Click **Connect Ponto API** to start the connection process **3. Select Your Bank** Choose your bank from the list of available financial institutions **4. Authorize Access** Log in to your bank and authorize Ponto to access your account data. This uses your bank's secure authentication (often including 2FA) **5. Complete Setup** Return to PayRequest where your account will be synced automatically > [!WARNING] > > **Security Note**: PayRequest never sees your bank login credentials. Authentication happens directly with your bank through Ponto's secure infrastructure. ## Managing Your Connection ### Connection Status On the Ponto settings page, you can see: * **Connected Date**: When the connection was established * **Last Synced**: Most recent transaction sync timestamp * **Account Details**: Your IBAN and current balance ### Available Actions > [card] View Banks > > See all available financial institutions if you want to connect additional accounts > [card] Refresh Accounts > > Manually trigger an account refresh to get the latest transactions > [card] Remove Connection > > Disconnect your bank account from PayRequest (this doesn't affect your bank) ## Transaction Syncing ### Automatic Sync Once connected, Ponto automatically syncs your transactions: * **Frequency**: Every few minutes during business hours * **History**: Imports recent transaction history * **Direction**: Both incoming (credits) and outgoing (debits) ### Transaction Data Each synced transaction includes: | Field | Description | | - | - | | Date | Transaction execution date | | Amount | Transaction amount with direction | | Description | Bank-provided transaction description | | Counterpart | Name of the other party | | Reference | Payment reference/communication | | Status | Booked or pending | ### Viewing Transactions To view your synced bank transactions: 1. Go to **Settings → Ponto** 2. Find your connected bank account 3. Click **View Transactions** Transactions are displayed with color coding: * **Green**: Incoming payments (credits) * **Red**: Outgoing payments (debits) ## Bank Transfer Payments One of the most powerful features enabled by Ponto is automatic Bank Transfer payment matching. ### How It Works **1. Enable Bank Transfer** Toggle "Bank Transfer Payment Method" on in your Ponto settings **2. Customer Pays** Customer receives your IBAN and a unique reference (e.g., `PAY-12345`) **3. Transfer Made** Customer transfers the exact amount with the reference to your account **4. Auto-Match** PayRequest detects the incoming transaction and matches it by reference **5. Invoice Paid** The invoice/order is automatically marked as paid ### Configuration In the Bank Transfer section of Ponto settings: * **Toggle**: Enable/disable Bank Transfer as a payment option * **IBAN Display**: Your IBAN shown to customers (auto-detected from bank) * **Account Name**: Your account name shown to customers * **Custom Instructions**: Add your own guidance text for customers > [accordion] Custom Instructions Example > > Add helpful instructions like: > > ``` > Please include the reference code exactly as shown in your payment description. > Payments are typically matched within 24 hours. For urgent orders, please > contact us after making your transfer. > ``` ### Where Bank Transfer Appears When enabled, Bank Transfer shows as a payment option on: * Payment pages * Invoice payment portal * Smart links * Checkout (coming soon) > [!NOTE] > > Bank Transfer is **not available** for recurring payments or subscriptions. Use SEPA Direct Debit for those use cases. For complete Bank Transfer documentation, see [Bank Transfer Payments](/payment-processing/bank-transfer). ## Transaction Categorization PayRequest helps you organize synced transactions: ### VAT Categories Categorize transactions for accounting: * Standard Rate (21%) * Reduced Rate (9%) * Zero Rate (0%) * Exempt * Out of Scope ### Bulk Editing Select multiple transactions and: * Assign VAT category * Add notes * Mark as reviewed * Export for accounting ## Security & Privacy > [card] PSD2 Compliant > > Ponto operates under EU PSD2 regulations for open banking security > [card] Bank-Level Security > > All data transmission uses bank-grade encryption > [card] No Credential Storage > > PayRequest never stores your bank login credentials > [card] Revocable Access > > You can revoke access anytime through your bank or PayRequest ### Data Access Ponto provides **read-only** access to: * Account balances * Transaction history * Account holder information Ponto does **not** have access to: * Initiate payments from your account * Modify your account settings * Access other bank accounts you haven't authorized ## Troubleshooting > [accordion] Connection Failed > > **Common causes:** > > 1. **Bank not supported**: Check if your bank is in Ponto's network > 2. **Authentication timeout**: Try again - bank sessions can expire > 3. **2FA issues**: Ensure you complete all authentication steps > 4. **Browser issues**: Try a different browser or clear cache > > **Solution**: Wait a few minutes and try again. If persistent, contact support. > [accordion] Transactions Not Syncing > > **Check these:** > > 1. Is the connection still active? (Check for "Connected" status) > 2. Click "Refresh Accounts" to force a sync > 3. Some banks have sync delays (especially weekends) > 4. Very recent transactions may take a few hours to appear > > **Note**: Bank transaction availability varies by institution. > [accordion] Bank Transfer Not Matching > > **Matching requires:** > > 1. Exact reference (e.g., `PAY-12345`) in payment description > 2. Exact amount (to the cent) > 3. Transaction synced to PayRequest > > **Debug steps:** > > * Check if transaction appears in Ponto transactions list > * Verify the reference in the transaction description > * Compare amounts exactly > [accordion] Need to Reconnect > > Bank connections may need reconnection if: > > * Your bank requires periodic reauthorization > * You changed bank credentials > * The bank updated their systems > > **To reconnect**: Remove the existing connection and add it again following the setup steps. ## Pricing > [tab] PayRequest > > **No additional cost** for Ponto integration within PayRequest. Bank Transfer payments have no transaction fees from PayRequest. > [tab] Ponto > > Ponto may have its own pricing for API access. Check [Ponto's pricing](https://myponto.com) for current rates. > > Typical costs include: > > * Monthly subscription for API access > * Per-transaction fees for certain operations ## Related Documentation > [card] [Bank Transfer Payments](/payment-processing/bank-transfer) > > Complete guide to accepting bank transfers with automatic matching > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > Compare all available payment methods > [card] [Transaction Reports](/analytics-and-reporting/transaction-reports) > > Analyze your payment and bank transaction data > [card] [SEPA Direct Debit](/payment-processing/payment-methods-overview#sepa-direct-debit) > > For recurring payments, use SEPA Direct Debit instead ## Allocate an existing receipt to invoices For an incoming bank payment that covers one or more open invoices, use the reviewed [bank-payment allocation flow](https://docs.payreque.st/payment-processing/reconcile-bank-payments). You choose the invoices for one customer, check an exact total and currency match, and explicitly confirm a preview. This can include older or already bookkeeping-booked receipts. It does not send money or replay customer payment emails. Bookkeeping status is separate from invoice settlement. # Bank Transfer Payments Source: https://docs.payreque.st/payment-processing/bank-transfer Accept bank transfers with automatic payment matching via Ponto integration # Bank Transfer Payments Accept direct bank transfers from your customers with automatic payment matching. When customers transfer money to your bank account with the correct reference, PayRequest automatically detects and marks the payment as complete. > [!NOTE] > > **Automatic Reconciliation**: Bank Transfer payments use the Ponto integration to automatically match incoming bank transactions with pending payments - no manual work required. ## How It Works **1. Customer Selects Bank Transfer** At checkout, the customer chooses "Bank Transfer" as their payment method **2. Payment Details Displayed** Customer receives your IBAN, account name, exact amount, and a unique payment reference (e.g., `PAY-12345`) **3. Customer Transfers Funds** Customer logs into their bank and transfers the exact amount with the reference in the payment description **4. Automatic Matching** PayRequest syncs your bank transactions via Ponto and automatically matches the payment by reference and amount **5. Payment Confirmed** Invoice/order is marked as paid, and customer receives confirmation ## Requirements > [card] Ponto Connection > > You need an active Ponto bank connection to use Bank Transfer payments. Ponto syncs your bank transactions automatically. > [card] Business Bank Account > > A business bank account connected to Ponto. Most European banks are supported through the Ponto network. ## Enabling Bank Transfer ### Step 1: Connect Ponto First, ensure you have Ponto connected: 1. Go to **Settings → Ponto** 2. Click **Connect Ponto API** if not already connected 3. Authorize access to your bank account 4. Wait for initial account sync ### Step 2: Enable Bank Transfer Payment Method Once Ponto is connected: 1. On the **Settings → Ponto** page, find the **Bank Transfer Payment Method** section 2. Toggle the switch to **enable** Bank Transfer 3. Your IBAN and account name will be displayed (pulled from your connected bank) > [!TIP] > > **Custom Instructions**: You can add custom instructions that will be shown to customers when they select Bank Transfer. Use this to provide additional guidance or expected processing times. ## Customer Experience When a customer selects Bank Transfer at checkout, they see: > [accordion] Payment Details Screen > > **What customers see:** > > * **Account Name**: Your business name from the bank account > * **IBAN**: Your bank account number > * **Amount**: Exact amount to transfer > * **Reference**: Unique payment reference (e.g., `PAY-12345`) > > Each field has a **copy button** for easy copying to their banking app. > [accordion] Reference Importance > > The payment reference is crucial for automatic matching. Customers are instructed to: > > * Include the **exact reference** in their payment description > > * Transfer the **exact amount** (not more, not less) > > * Use standard SEPA transfer (not instant/express which may truncate references) > > > [!WARNING] > > > > If the reference is missing or incorrect, automatic matching won't work and manual reconciliation may be needed. > [accordion] After Transfer > > After the customer initiates the transfer: > > 1. Invoice status changes to **Pending** > 2. Customer can return to the payment page anytime to see the bank details > 3. Once matched, status updates to **Paid** > 4. Customer receives email confirmation (if email templates are configured) ## Automatic Matching PayRequest automatically matches bank transfers using this logic: **1. Transaction Sync** Ponto syncs your bank transactions regularly (typically every few minutes) **2. Reference Detection** System scans incoming transactions for payment references matching the `PAY-XXXXX` pattern **3. Amount Verification** The transaction amount must match the pending payment amount exactly **4. Status Update** When matched, the invoice/order is automatically marked as paid with a transaction record ### Matching Criteria | Criteria | Requirement | | - | - | | Reference | Must contain exact `PAY-XXXXX` reference | | Amount | Must match exactly (to the cent) | | Direction | Must be an incoming payment (credit) | | Timeframe | Transaction within last 30 days | > [!NOTE] > > **Partial Payments**: Bank Transfer currently requires the exact amount. Partial payments are not automatically matched. ## Where Bank Transfer Appears Bank Transfer is available as a payment option in: > [card] Payment Pages > > Your public payment page (e.g., `payrequest.me/yourbusiness`) > [card] Invoice Payments > > Customer portal where customers pay their invoices > [card] Smart Links > > Payment links created for specific amounts or products > [card] Shop Checkout > > Your online shop checkout (coming soon) > [!NOTE] > > **Not for Recurring**: Bank Transfer is only available for one-time payments. For subscriptions and recurring billing, use SEPA Direct Debit instead. ## Use Cases ### B2B Payments Business customers often prefer bank transfers for: * Accounting and audit trails * Internal approval workflows * Avoiding credit card fees * Large transaction amounts ### High-Value Transactions For large payments where: * Credit card limits may apply * Lower fees are important * Customer prefers bank-level security ### Cost-Conscious Customers Some customers prefer bank transfers to: * Avoid card processing fees being passed on * Not share card details online * Use their familiar banking app ## Pricing > [card] Transaction Fee > > **€0.00** > > No PayRequest fee for bank transfers > [card] Percentage Fee > > **0%** > > No percentage-based fees > [card] Ponto Costs > > **Varies** > > Check your Ponto subscription for API usage costs ## Troubleshooting > [accordion] Payment Not Matching > > **Possible causes:** > > 1. **Wrong reference**: Customer didn't include the reference or made a typo > 2. **Wrong amount**: Amount doesn't match exactly > 3. **Sync delay**: Ponto hasn't synced yet (wait a few minutes) > 4. **Reference truncated**: Some banks truncate long descriptions > > **Solution**: Check your Ponto transactions manually and verify the reference/amount. Contact support if needed. > [accordion] Bank Transfer Option Not Showing > > **Check these settings:** > > 1. Is Ponto connected? (Settings → Ponto) > 2. Is Bank Transfer enabled? (Toggle in Ponto settings) > 3. Is your IBAN available? (Refresh accounts if needed) > 4. Is this a recurring product? (Bank Transfer not available for subscriptions) > [accordion] Customer Can't Find Reference > > **Advise your customer:** > > 1. Return to the payment page with `?invoice=ID` parameter > 2. The reference and IBAN are displayed there > 3. They can also check their email for the invoice ## Best Practices > [card] Clear Instructions > > Add custom instructions explaining your expected processing time and any special requirements > [card] Reference Format > > Inform customers to copy the reference exactly - including the hyphen > [card] Amount Precision > > Remind customers to transfer the exact amount shown, not rounded > [card] Bank Selection > > Advise customers to use standard SEPA transfers, not instant transfers that may truncate references ## Related Documentation > [card] [Bank Sync (Ponto)](/payment-processing/bank-sync-ponto) > > Learn more about connecting and configuring Ponto for bank synchronization > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > Compare all available payment methods and their features > [card] [Invoice Payment Links](/invoices/invoice-payment-links) > > Creating and managing payment links for invoices > [card] [Smart Links](/payment-processing/smart-links) > > Create reusable payment links with Bank Transfer support ## Allocate an existing receipt to invoices For an incoming bank payment that covers one or more open invoices, use the reviewed [bank-payment allocation flow](https://docs.payreque.st/payment-processing/reconcile-bank-payments). You choose the invoices for one customer, check an exact total and currency match, and explicitly confirm a preview. This can include older or already bookkeeping-booked receipts. It does not send money or replay customer payment emails. Bookkeeping status is separate from invoice settlement. # Checkout Links Source: https://docs.payreque.st/payment-processing/checkout-links Generate direct checkout URLs for products, invoices, and custom amounts ## Overview Checkout links are URLs that take customers directly to a payment flow. PayRequest offers several types of checkout links depending on your use case. ## Types of Checkout Links ### Payment Page Links Your payment page is always available at: ``` https://payrequest.me/[your-handle] ``` You can pre-fill amounts and customer details using dynamic URL parameters: ``` https://payrequest.me/[your-handle]/25.00 https://payrequest.me/[your-handle]?amount=25&name=John&email=john@example.com ``` See [Payment Page Dynamic Links →](/payment-processing/payment-page-dynamic-links) for full URL parameter documentation. ### Smart Links Branded, reusable URLs with built-in analytics: ``` https://payrequest.me/[your-handle]/summer-sale ``` Smart links provide permanent URLs, QR codes, payment limits, delivery options, and conversion tracking. See [Smart Links →](/payment-processing/smart-links) for full documentation. ### Product Links Direct links to specific products in your shop: ``` https://payrequest.me/shop/[your-handle]/product/[product-id] ``` Or via payment page with product parameter: ``` https://payrequest.me/[your-handle]?product=[product-id] ``` ### Invoice Payment Links Every invoice includes a unique payment link that customers can use to pay. These are automatically generated and included in invoice emails. See [Invoice Payment Links →](/invoices/invoice-payment-links) for details. ## Choosing the Right Link Type | Use Case | Recommended Link Type | | - | - | | Marketing campaign | Smart Link | | One-time payment request | Payment Page Dynamic Link | | Product promotion | Smart Link (Product type) | | Invoice payment | Invoice Payment Link | | QR code on flyer | Smart Link | | Security deposit | Smart Link (Deposit product) | | Custom amount with pre-filled data | Payment Page Dynamic Link | | Reusable donation link | Smart Link (Amount type) | ## Explain the link to your customer Share [Paying a business](/customer-guide/payments) with a normal payment request, or [Security deposits for customers](/customer-guide/security-deposits) with an authorization request. Keep using the exact original link when investigating an unclear result; creating another link does not resolve an existing pending payment or reservation. ## Need Help? > [card] [Smart Links](/payment-processing/smart-links) > > Branded payment links with analytics > [card] [Dynamic Links](/payment-processing/payment-page-dynamic-links) > > URL parameters for payment pages > [card] [Security Deposits](/payment-processing/security-deposits) > > Authorization hold links > [card] [Invoice Links](/invoices/invoice-payment-links) > > Invoice payment URLs # Payoneer availability and integration requests Source: https://docs.payreque.st/payment-processing/connect-payoneer Understand the Payoneer request option and what must be confirmed before a Checkout integration is available. **Payoneer is available as an integration request in PayRequest onboarding. It is not a generally available onboarding connection.** An existing Payoneer balance, receiving account or payout relationship does not confirm that Payoneer Checkout can be used through PayRequest. ## Does Payoneer have an API? Yes. Payoneer's [developer platform](https://www.payoneer.com/developers-docs/) describes APIs and services, including Checkout. Access to a specific product, merchant eligibility and a suitable integration arrangement must still be confirmed. API availability is not the same as availability for every Payoneer accountholder. Do not create or paste API credentials into PayRequest based solely on this guide. We do not promise a self-service Payoneer connection, supported currencies, checkout methods or a release date here. ## Request Payoneer 1. Open the payment-provider step in [onboarding](https://payrequest.app/onboarding). 2. Under **Missing your payment provider?**, choose **Request Payoneer**. 3. Explain what you sell, which payment methods you need and whether you already have a Payoneer merchant or Checkout arrangement. 4. Review the text and submit your request. Do not include passwords, API keys or identity documents. Your request is saved for review. It does not activate payments or complete the provider step. Selecting Payoneer in the earlier intake alone does not submit an integration request. ## What happens next? PayRequest can review demand and the technical and commercial requirements for a possible integration. Payoneer decides access to its products and merchant approval. A request does not guarantee either decision. If you need to accept payments now, review the connections actually offered for your account and confirmed legal country. Do not change your country to one where you are not legally eligible or upgrade a plan solely to bypass a provider limitation. * [Available provider setup](https://docs.payreque.st/payment-processing/setting-up-payment-providers) * [Help with an incomplete connection](https://docs.payreque.st/getting-started/onboarding#payment-connection-not-complete) * [Ask PayRequest about your setup](mailto:info@payrequest.io) # Connecting PayPal Source: https://docs.payreque.st/payment-processing/connect-paypal Add PayPal, Pay Later, and Venmo to your payment links — for the millions of buyers who already trust the PayPal checkout. # Connecting PayPal PayPal is the world's most familiar payment button — many buyers prefer it because their card and shipping details are already saved with PayPal. Connecting your account to PayRequest adds **PayPal**, **Pay Later**, and (where eligible) **Venmo** to your payment links. > [!NOTE] > > **Phase 1 scope**: PayPal currently powers payment links only. Invoices, subscriptions, and customer billing flows continue to use Mollie. We're rolling out wider PayPal support in upcoming releases. ## Why Add PayPal > [card] Trusted by 400M+ buyers > > Buyers can pay with their existing PayPal balance, linked bank, or saved cards in two clicks. > [card] Pay Later > > For orders above PayPal's regional threshold (typically €30+), buyers see Pay Later options — split payments or 30-day delay. > [card] Venmo > > For US buyers on mobile, Venmo appears as a checkout option. Higher conversion in the US Gen-Z and Millennial segments. > [card] Buyer Protection > > PayPal's buyer protection program reassures hesitant first-time buyers — often the deciding factor for higher-ticket purchases. ## How to Connect **1. Open Provider Settings** Go to `/provider-settings` and find the **PayPal** card. **2. Click Connect** PayRequest opens PayPal's Partner onboarding page. Sign in with your PayPal Business account, or create one if you don't have it yet. **3. Approve permissions** PayPal asks you to grant PayRequest permission to charge customers and issue refunds on your behalf. Approve, and you're returned to PayRequest. **4. Confirm in PayRequest** The PayPal card now shows a green **Connected** banner with your PayPal merchant ID and account email. > [!TIP] > > **Already have a PayPal Business account?** The onboarding flow detects it and links it instantly — no need to create a new account or migrate anything. ## What Customers See When a customer opens a payment link with PayPal enabled, they see one or more buttons appear directly on your payment page: > [card] PayPal button > > The familiar yellow **Pay with PayPal** button. Opens PayPal's checkout in a popup so the buyer never leaves your page. > [card] Pay Later button > > Appears automatically for eligible orders. Lets the buyer split the payment or delay it for 30 days. > [card] Venmo button > > Shows up only for US-based mobile buyers. Tap-to-pay using their Venmo account. After confirming in the PayPal popup, the buyer lands back on your success page and the transaction is recorded in your PayRequest dashboard within seconds. ## Renewable Access Links PayPal Amount Links can grant access for a fixed number of days after every successful payment. Customers use the same public Smart Link to buy or renew, while PayRequest maintains an independent expiry date for each customer. You can optionally connect a private Telegram group or channel. After payment, the success page gives the buyer a personal, one-use invitation, and the PayRequest bot removes the member when their paid period ends. See [Renewable Timed Access](/payment-processing/smart-links#step-3c-grant-renewable-timed-access-optional) for setup instructions and renewal behavior. ## Checkout Recovery When [Checkout Recovery](/shop-and-checkout/checkout-recovery) is enabled, PayPal orders started through Smart Links are included in checkout-attempt tracking. This lets you identify buyers who began PayPal checkout but did not complete the payment. The setting must be enabled before the attempt occurs. ## Login with PayPal If you'd like new merchants to sign up to PayRequest faster, the **Login with PayPal** option on `/login` and `/register` lets people skip the standard form. They authenticate with PayPal, and PayRequest automatically chains a PayPal Connect step right after — so by the time they finish signup, their account is already wired up to take payments. ## Refunds and Disputes > [accordion] Issuing a refund > > Open the transaction in your dashboard and click **Refund**. You can issue a full refund or a partial amount up to the original charge. PayPal returns the money to the buyer's original funding source. > [accordion] Disputes and claims > > If a buyer files a dispute with PayPal (claiming "item not received" or "not as described"), PayPal notifies PayRequest and the dispute is logged on the transaction. You respond through the PayPal Resolution Center; the [Handling Chargebacks](/payment-processing/handling-chargebacks) guide covers the workflow. > [accordion] Partial refunds > > Supported. Issue any amount up to the full charge value. Multiple partial refunds are allowed until the total reaches the original amount. ## Eligibility Notes PayPal's checkout buttons are dynamically gated by PayPal itself based on: * **Buyer location**: Venmo only renders for US IPs; Pay Later thresholds vary by region * **Order amount**: Pay Later requires the cart value to exceed the regional minimum (typically €30+ in EU, \$30+ in US) * **Currency**: Some methods only work with specific currencies — Venmo with USD, regional Pay Later schemes with the local currency * **Buyer eligibility**: PayPal's risk engine may suppress Pay Later for buyers who don't qualify If a buyer doesn't see Pay Later or Venmo, it's PayPal's own eligibility check — not a PayRequest setting. ## Currency Conversion Your payment pages can display prices in whatever currency you've chosen, but PayPal always settles funds into **one fixed currency** for your account — the "primary currency" set when your PayPal Business account was created, based on your country. If a buyer pays through PayPal while your page currency is different from your PayPal account's settlement currency, PayRequest automatically converts the amount using live exchange rates before sending it to PayPal — so your account receives the correct value, not the raw number relabeled with a different currency code. > [!NOTE] > > **Example**: Your payment page shows prices in USD, but your PayPal account settles in PHP. A buyer paying **\$10.00** will have PayPal charge **≈ ₱607.50** (the live USD → PHP equivalent) — not "PHP 10.00". Buyers see this converted estimate on the PayPal button itself before they pay, so there are no surprises at checkout. Exchange rates refresh regularly from a live market-rate feed, and the rate shown to the buyer matches the rate used for the actual charge. ## Disconnecting PayPal You can disconnect PayPal at any time from Provider Settings. Existing transactions stay accessible, and refunds on past transactions continue to work. Only new payments are blocked while PayPal is disconnected. > [!WARNING] > > If you disconnect PayPal while it's your only payment provider, your payment links will be unavailable until you reconnect (or connect another provider). ## Frequently Asked Questions > [accordion] What does PayPal charge? > > PayPal's standard merchant fees apply — typically 2.9% + a fixed fee for domestic transactions, slightly higher for cross-border. PayRequest itself only charges its own platform fee on free-plan accounts (2% per transaction); paid plans pay nothing on top. > [accordion] Do I need a PayPal Business account? > > Yes. PayPal requires a Business (not Personal) account to accept payments through a partner integration. The onboarding flow can convert a Personal account during signup if needed. > [accordion] Can I use my existing PayPal Business account? > > Yes. The connect flow detects existing accounts and links them — no need to create a new one or move existing transactions. > [accordion] Why don't I see Pay Later on my payment page? > > Pay Later only renders when the order amount exceeds PayPal's regional threshold (typically €30+ in the EU, \$30+ in the US). For amounts below that, only the standard PayPal button appears. > [accordion] Why don't I see Venmo? > > Venmo only renders for buyers in the US, on mobile, with USD as the transaction currency. EU and UK buyers won't see it. If you're testing from outside the US and want to verify Venmo is configured, you'll need to use a US IP. > [accordion] Can I run PayPal alongside Stripe and Mollie? > > Yes. All three can be connected simultaneously. Buyers see whichever methods you've enabled, and each transaction routes to the right provider based on what the buyer picks. > [accordion] Why does PayPal charge a different currency than my payment page? > > PayPal settles funds in your account's fixed primary currency, which may differ from the currency your payment page displays. PayRequest converts the amount automatically using live exchange rates, so PayPal charges the correct equivalent value — see [Currency Conversion](#currency-conversion) above. ## Next Steps > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See every payment method available through PayPal and other providers. > [card] [Connect Stripe](/payment-processing/connect-stripe) > > Add Stripe alongside PayPal for cards, Apple Pay, Klarna, and Adaptive Pricing. > [card] [Create a Payment Link](/payment-processing/payment-page-dynamic-links) > > Build the shareable link or QR code your customers will pay through. > [card] [Handle Chargebacks](/payment-processing/handling-chargebacks) > > Learn how to respond to PayPal disputes and chargebacks from other providers. # Connecting Revolut Pay Source: https://docs.payreque.st/payment-processing/connect-revolut-pay Connect your own Revolut Merchant account and accept Revolut Pay payments directly into your business account. # Connecting Revolut Pay Revolut Pay lets customers pay through Revolut, cards, and the payment methods enabled in your Revolut Merchant checkout. PayRequest uses Revolut's Merchant API and Merchant Web SDK; payments settle directly to your own Revolut Merchant account. > [!NOTE] > > Revolut Pay is tenant-scoped. PayRequest never uses a shared Revolut account for your checkout. The button appears only on payment pages owned by a merchant with an active Revolut connection. ## What you need You need an approved **Revolut Merchant account** under Revolut Business. The Merchant account is separate from the ordinary Business account and must be approved before production payments can be accepted. From **Revolut Business → Settings → APIs → Merchant API**, obtain: * **Production Public API key** (`pk_...`) for the browser checkout * **Production Secret API key** (`sk_...`) for server-side API calls * **Webhook signing secret** from the webhook details page Never paste the secret key into frontend code, a payment link, or a support message. ## Connect your account **1. Open Provider Settings** In PayRequest, open **Settings → Providers**, or go directly to `/provider-settings`. **2. Choose Revolut Pay** Open the **Revolut Pay** provider card and click **Connect**. **3. Enter production credentials** Enter your Public API key and Secret API key. Select **Production**. Sandbox credentials must only be used with the Sandbox environment. **4. Save the connection** Click **Connect Revolut**. Your credentials are encrypted before storage and are never shown again in full. ## Configure the webhook Create a Merchant API webhook for: `https://payrequest.app/webhooks/revolut` Subscribe at minimum to: * `ORDER_COMPLETED` * `ORDER_CANCELLED` * `ORDER_FAILED` * `ORDER_PAYMENT_DECLINED` * `ORDER_PAYMENT_FAILED` Copy the webhook's **signing secret** into the PayRequest Revolut provider form. PayRequest verifies the raw request body, HMAC-SHA256 signature, and five-minute timestamp window before processing an event. > [!WARNING] > > The webhook secret is different from the Merchant Secret API key. Use the signing secret shown in the webhook details, not the `sk_...` API key. ## Customer checkout On an eligible PayRequest payment page, customers see a dark **Revolut Pay** button after entering a valid amount, name, and email address. The checkout uses the Revolut Payments module and creates an order on demand through PayRequest's server. After a successful payment: 1. Revolut sends an `ORDER_COMPLETED` webhook. 2. PayRequest retrieves the order server-side and verifies the final state. 3. The matching invoice and transaction are marked paid idempotently. 4. The customer returns to the PayRequest success page. The webhook is the reliable source for fulfillment; the browser return is only a confirmation and recovery path. ## Current scope The current Phase 1 integration supports one-time amounts on simple payment pages. It does not yet appear on product URLs such as `?product=123`, subscriptions, deposits, or existing invoice checkouts. These flows need product/order fulfillment and recurring-payment handling before Revolut can be enabled safely for them. Revolut Pay can be connected alongside Mollie, Stripe, PayPal, and Payoneer. Each merchant's payments remain scoped to the provider account they connected. ## Sandbox testing For testing, connect Sandbox public and secret keys and select **Sandbox** in the provider form. The SDK mode and Merchant API endpoint are selected per connection; production keys cannot be used in Sandbox and vice versa. Revolut's Sandbox Revolut Pay flow uses a simulated account-creation experience because there is no Sandbox version of the Revolut retail app. Sandbox behavior can therefore differ from production. ## Disconnecting Return to **Settings → Providers** and click **Disconnect Revolut**. New payment pages stop showing the button immediately. Existing transactions retain their provider reference for reconciliation. ## Related guides > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > Compare PayRequest payment providers and methods. > [card] [Create Payment Links](/payment-processing/payment-page-dynamic-links) > > Create the payment page where Revolut Pay appears. # Connecting Stripe Source: https://docs.payreque.st/payment-processing/connect-stripe Accept cards, Apple Pay, Google Pay, Klarna, iDEAL and more through Stripe — with prices auto-localized to your buyer's currency. # Connecting Stripe Stripe gives PayRequest payment links a worldwide reach. Customers can pay with cards, Apple Pay, Google Pay, Klarna, Afterpay, iDEAL, Bancontact, and many more — and **Adaptive Pricing** automatically shows them the price in their own local currency. > [!NOTE] > > **Phase 1 scope**: Stripe currently powers payment links only. Invoices, subscriptions, and customer billing continue to use Mollie. We're rolling out wider Stripe support over the coming releases. ## Why Add Stripe > [card] Global checkout > > Cards in 200+ countries, plus regional methods that drop in automatically based on the buyer's location. > [card] Adaptive Pricing > > A buyer in Canada sees CAD, a buyer in Japan sees JPY — without you doing the FX math. The conversion fee is paid by the buyer, not you. > [card] Apple & Google Pay > > One-tap mobile checkout that consistently lifts conversion. Enabled out of the box on supported devices. > [card] Buy Now, Pay Later > > Klarna and Afterpay surface for orders above the regional threshold, helping convert higher-ticket sales. ## How to Connect **1. Open Provider Settings** Go to `/provider-settings` and find the **Stripe** card. **2. Click Connect** You'll be sent to Stripe's secure onboarding page. Sign in to your Stripe account, or create one if you don't have it yet. **3. Approve the connection** Stripe asks for permission to charge on your behalf. Approve, and you're returned to PayRequest with the connection live. **4. Confirm in PayRequest** The Stripe card now shows a green **Connected** banner with your account name and email. > [!TIP] > > First time using Stripe? The onboarding wizard guides you through identity verification, bank details, and payout settings — required by Stripe before you can take live payments. ## What Customers See When a customer opens a payment link, the Stripe checkout shows up as an embedded form on your payment page — no redirect to a separate site. They pick their preferred method, fill in card or bank details, and confirm. Cards are charged instantly; methods like iDEAL or Bancontact bounce briefly through the buyer's bank for authorization. > [card] Branded experience > > The payment form uses a dark theme that matches PayRequest's checkout chrome. Buyers stay on your payment page from start to finish. > [card] Smart method labels > > The pay button updates as the buyer picks a method — "Pay with iDEAL", "Pay with Apple Pay", and so on — so they always know what they're confirming. ## Choosing Your Currency PayRequest offers 139 Stripe presentment currencies in its currency selectors, including AUD, CAD, NZD, JPY, SGD, and USD. Select the currency when creating or editing a product. Product checkout uses the product's saved price and currency: a product priced at **9 AUD** starts checkout in Australian dollars. Stripe decides which currencies and payment methods your connected account can accept. Availability depends on your account country, verification, payment method, and Stripe's minimum charge amounts. A currency appearing in PayRequest does not guarantee that every payment method supports it. See [Stripe's supported currencies](https://docs.stripe.com/currencies). ### Amounts and Refunds PayRequest converts amounts to Stripe's required units for payment creation, payment verification, and refunds. For example, **900 JPY means 900 yen**, while **9.00 AUD means nine Australian dollars**. JPY and KRW require whole amounts; ISK and UGX also require whole amounts under Stripe's special rules. Unsupported fractional amounts are rejected rather than silently changing the amount charged. Refund amounts use the original payment's currency. Enter a partial refund in that currency, rather than your account's settlement currency. > [!NOTE] > > Your product currency, the currency a buyer may see through Adaptive Pricing, and your Stripe payout currency can differ. Adding currency choices does not change existing product prices, convert saved prices, or expand another payment provider's currency support. ## Adaptive Pricing Adaptive Pricing is what makes Stripe especially valuable for international payment links. Stripe detects each buyer's country and shows the price converted to their local currency, with the exchange rate locked in for 24 hours. > [!NOTE] > > **You don't pay anything extra.** Stripe takes a 2–4% conversion fee, and that fee is added to the buyer's price — not yours. You receive the original amount in your account's settlement currency. ### How It Works for Buyers 1. Buyer opens a €25 payment link from Toronto 2. Stripe detects their location and converts the price (e.g., to CAD 36.50) 3. The Currency Selector lets them switch back to your default currency if they prefer 4. They pay in their own currency through whichever method they choose 5. You receive €25 in your Stripe account — Stripe handles the conversion ### Managing Adaptive Pricing Adaptive Pricing is **enabled by default** when you connect Stripe. To turn it off for your account: **1. Open Provider Settings** Visit `/provider-settings` and find your connected Stripe card. **2. Toggle Adaptive Pricing** In the Stripe section there's a panel labelled **Adaptive Pricing** with a switch. Flip it off if you want all buyers to see your account currency only. > [!TIP] > > Most merchants leave Adaptive Pricing on — it's a free conversion lift for international buyers. The only common reason to disable it is if you have legal or pricing constraints that require a single currency display. ## Choosing Which Payment Methods Show Stripe supports dozens of payment methods — cards, wallets, regional bank methods, Buy Now Pay Later, and more. You decide which ones appear on your checkout from inside PayRequest, so you don't have to bounce into the Stripe Dashboard. **1. Open Provider Settings** Visit `/provider-settings` and find your Stripe card. **2. Switch to the Payment Methods tab** Inside the Stripe card, click the **Payment Methods** tab. Methods are grouped — Cards & wallets, European bank methods, Buy now pay later, Regional methods, and Bank debits. **3. Enable or disable a method** Click **Enable** to turn on a method, or **Disable** to turn it off. PayRequest handles both sides of the switch in one click — it tells Stripe you want the method **and** flips it on for your checkout, so buyers see it next time they pay. > [!NOTE] > > **Why this matters.** Stripe actually has two settings per method: one for "is my account allowed to use this", and one for "show it to buyers at checkout". They're separate, and turning on only the first one is a common gotcha that leaves a method invisible. PayRequest now toggles both for you in a single click. ### The "Hidden at checkout" badge Sometimes a method is enabled on your account but Stripe still won't show it to a particular buyer. The most common reasons: * **Currency mismatch** — e.g. MobilePay only displays for payments in DKK or EUR. * **Buyer region** — e.g. iDEAL only shows to buyers Stripe identifies as being in the Netherlands. * **Verification pending** — Stripe is still checking your account details. When PayRequest detects this, the method card shows an amber **Hidden at checkout** badge next to its green Active status. That's Stripe telling you: "the merchant has it on, but right now, this buyer won't see it." It's not an error you need to fix — it's just useful context so you know why a method isn't appearing on a test page. > [!TIP] > > If you're a Danish merchant testing MobilePay from a non-Danish IP (e.g. via a VPN), Stripe may hide it even though everything is set up correctly. Test from your real location, or use a payment-link currency that matches the method's supported list. ### Methods to Consider Enabling > [card] Cards & wallets > > Card payments, Link, Apple Pay, Google Pay, Amazon Pay. Recommended for every merchant — these cover the bulk of global checkouts. > [card] Nordic & local wallets > > MobilePay (Denmark, Finland), Swish (Sweden), TWINT (Switzerland), Bizum (Spain), Satispay (Italy). Enable the ones that match your customer base. > [card] Bank redirects > > iDEAL (Netherlands), Bancontact (Belgium), EPS (Austria), Przelewy24 / BLIK (Poland), Multibanco / MB WAY (Portugal). Strong conversion for European buyers. > [card] Buy Now Pay Later > > Klarna, Afterpay, Affirm, Alma. Surfaces above regional minimums to boost higher-ticket sales. ## Refunds and Disputes > [accordion] Issuing a refund > > Open the transaction in your dashboard and click **Refund**. You can issue a full refund or a partial amount. Stripe handles the conversion if the original payment was in a different currency — the buyer gets back the exact amount they paid. > [accordion] Chargebacks and disputes > > If a buyer disputes a charge with their bank, Stripe notifies PayRequest via webhook and the dispute is logged on the transaction. Use the Stripe Dashboard to upload evidence; the [Handling Chargebacks](/payment-processing/handling-chargebacks) guide covers the workflow. > [accordion] Partial refunds > > Supported. Issue any amount up to the full charge value. Multiple partial refunds on a single transaction are allowed until the total reaches the original amount. ## Disconnecting Stripe You can disconnect Stripe at any time from Provider Settings. Existing transactions stay accessible in your dashboard, and refunds on past transactions continue to work. Only new payments are blocked while Stripe is disconnected. > [!WARNING] > > If you have payment links or QR codes that route to Stripe specifically, disconnecting will fall back to your other connected providers. If Stripe is your only provider, your payment links will be unavailable until you reconnect. ## Frequently Asked Questions > [accordion] What does Stripe charge? > > Stripe's standard processing fees apply — typically 2.9% + €0.25 for European cards, varying by region and method. Adaptive Pricing's 2–4% currency conversion fee is paid by the buyer, not you. PayRequest itself only charges its own platform fee on free-plan accounts (2% per transaction); paid plans pay nothing on top. > [accordion] Do I need to verify my identity? > > Yes. Stripe requires identity verification (KYC) for any merchant taking live payments. The onboarding form asks for business details, owner identification, and payout bank details. Most merchants finish in under 10 minutes. > [accordion] Which currencies can I accept? > > Stripe lets you settle in your account's primary currency (typically EUR, USD, GBP, CHF, or your local currency). Adaptive Pricing then handles displaying prices to buyers in any of 150+ presentment currencies. > [accordion] Does it work with my custom domain? > > Yes, but make sure your custom domain is allowed to load Stripe's scripts. PayRequest's standard payment domain (`payrequest.me`) is configured out of the box. > [accordion] Can I migrate from another payment provider? > > Yes. Connect Stripe alongside Mollie or PayPal, test with a small payment, then update your payment links once you're happy. You don't have to disconnect anything during the transition. ## Next Steps > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See every payment method available through Stripe and other providers. > [card] [Connect PayPal](/payment-processing/connect-paypal) > > Add PayPal, Pay Later, and Venmo alongside Stripe for broader buyer reach. > [card] [Create a Payment Link](/payment-processing/payment-page-dynamic-links) > > Build the shareable link or QR code your customers will pay through. > [card] [Handle Chargebacks](/payment-processing/handling-chargebacks) > > Learn how to respond to disputes from Stripe and other providers. # Crypto Payments (USDC) Source: https://docs.payreque.st/payment-processing/crypto-payments Accept USDC payments on the Base network through WalletConnect — zero chargebacks, instant settlement, worldwide reach # Crypto Payments (USDC) PayRequest supports **USDC payments on the Base network** — a fast, low-cost stablecoin payment method that works worldwide. Customers pay USDC from their own wallet to a PayRequest treasury address; once the transaction is confirmed on-chain, PayRequest automatically forwards 98% to your connected wallet. > [!NOTE] > > Crypto payments are available on your payment page alongside your existing payment methods (iDEAL, credit card, bank transfer, etc.). Enable it once in your settings and it appears on all your payment pages automatically. ## Why Add Crypto Payments > [card] Worldwide reach > > Crypto works everywhere — no country restrictions, no currency conversion issues. Anyone with a wallet on Base can pay you in seconds. > [card] Zero chargebacks > > USDC payments are irreversible once confirmed on-chain. No disputes, no chargeback fees, no refund fraud. > [card] Instant settlement > > Funds arrive in your wallet within seconds of the customer confirming the transaction. No 2–3 day bank delays. > [card] Automatic forwarding > > Once a payment is confirmed on-chain, PayRequest automatically forwards 98% to your connected wallet — 2% covers the platform fee. No manual transfers. ## How It Works **1. Connect your wallet** Go to **Provider Settings** and find the **Crypto (USDC)** card. Click **Connect Wallet** and scan the QR code with your wallet app (MetaMask, Coinbase Wallet, or any WalletConnect-compatible wallet). **2. Sign to verify ownership** Your wallet asks you to sign a short message. This confirms you own the wallet address. No gas fee — no transaction is sent. **3. Your wallet is connected** You'll see your wallet address displayed with a green **Connected** badge. Crypto is now available as a payment method on all your payment pages. **4. Customers pay with USDC** When a customer selects "Pay with Crypto" on your payment page, a WalletConnect QR code appears. They scan it with their wallet, confirm the USDC amount, and the transaction is signed and sent to the Base network — to a PayRequest treasury address. **5. PayRequest confirms and forwards your share** PayRequest monitors the Base network for the transaction. Once it has at least **2 confirmations**, PayRequest automatically forwards **98% to your connected wallet** and keeps 2% as the platform fee. This usually takes a few seconds to a couple of minutes depending on network conditions. > [!TIP] > > **First time using crypto?** You'll need a wallet app like MetaMask or Coinbase Wallet. See the [supported wallets guide](/payment-processing/crypto-supported-wallets) for setup instructions. ## Wallet Balance Once your wallet is connected you can see your live balances directly in **Provider Settings → Crypto (USDC)**: * **USDC balance** — your current USDC on Base, ready to spend or send to an exchange * **ETH balance** — your ETH available for gas fees on Base (\~\$0.001 per transaction) Balances are read directly from the Base blockchain (no sign-in required) and cached for 5 minutes. Hit **Refresh** at any time to see the latest figures. > [!NOTE] > > ETH is only needed when you initiate transactions yourself (e.g., sending USDC from your wallet). Customers pay the gas when they send payments to you — you don't need ETH to receive. ## Customer Experience Your customers don't need an account or prior crypto knowledge — just a wallet with USDC on Base. > [card] Scan & pay > > A WalletConnect QR code appears on the payment page. Customers scan it with their phone wallet app or click to open their browser extension. > [card] See the exact amount > > The total is shown in USDC (converted from EUR at the current rate). No surprise fees. > [card] Fast confirmation > > Base confirms transactions in under 1 second. The payment page updates automatically once confirmed. > [card] Works on mobile > > WalletConnect works on iOS Safari and Android Chrome. No app switching required on most devices. ## Fees & Costs > [accordion] What does it cost? > > PayRequest charges a **2% platform fee** on each crypto payment. > > **Example:** > > * Customer pays 100 USDC to PayRequest's treasury wallet > * Once confirmed on-chain, 98 USDC is forwarded to your wallet > * 2 USDC stays with PayRequest (platform fee) > > The customer also pays a small Base network gas fee (typically under \$0.01). > [accordion] Are there any hidden costs? > > No hidden costs. The 2% fee is the only PayRequest charge. > > Unlike credit cards, there are no monthly minimums, no statement fees, no chargeback fees, and no currency conversion costs. > [accordion] Why 2%? > > The 2% fee covers infrastructure, WalletConnect integration, on-chain payment monitoring, and support. This fee only applies to crypto payments — your other payment methods (iDEAL, cards, etc.) are unaffected. ## How Settlement Works PayRequest currently settles crypto payments in **treasury mode**: 1. The customer sends the full USDC amount to a PayRequest-controlled treasury wallet on Base 2. PayRequest's on-chain monitor watches for the transaction and waits for **2 confirmations** 3. Once confirmed, PayRequest automatically forwards **98% to your connected wallet** and keeps **2%** as the platform fee 4. Both the customer's payment and the forwarding transaction are verifiable by anyone on [Basescan](https://basescan.org) > [!NOTE] > > Your funds pass through a PayRequest-controlled wallet for the brief period between confirmation and forwarding — they are not held in escrow or available for withdrawal by PayRequest beyond the 2% fee. If a forward ever fails (e.g. a network hiccup), it is automatically retried by PayRequest's background monitor. > [!NOTE] > > The USDC contract address on Base is `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. This is the native USDC issued by Circle on Base — not a bridged or wrapped version. ## Supported Wallet Apps Any wallet supporting **WalletConnect on the Base network** works. Popular choices: | Wallet | Platform | Best for | | - | - | - | | MetaMask | Mobile + browser | Most popular, wide support | | Coinbase Wallet | Mobile + browser | Easy USDC purchase via Coinbase | | Rabby | Mobile + browser | Multi-chain power users | | Rainbow | Mobile | Clean, beginner-friendly UX | | Trust Wallet | Mobile | Built-in dApp browser | | Kraken Wallet | Mobile | Kraken exchange users | | Blockchain.com DeFi Wallet | Mobile | DeFi-focused users | See the [full supported wallets guide](/payment-processing/crypto-supported-wallets) for setup instructions and tips. ## Refunds > [accordion] Can I refund a crypto payment? > > Cryptocurrency payments are irreversible on-chain. If you need to refund a customer, send USDC directly from your wallet to their address. The customer's wallet address and transaction hash are available in your PayRequest transaction history. > [accordion] What about disputes? > > Because crypto payments are final, there are no chargebacks or disputes. This is a key advantage — once a customer pays, the transaction is settled permanently. For customer service issues, handle refunds directly with the customer. ## Frequently Asked Questions > [accordion] What is USDC? > > USDC is a **stablecoin** — a cryptocurrency always worth exactly \$1 USD. Unlike Bitcoin or Ethereum, the value doesn't fluctuate. It's issued by Circle and backed by real dollar reserves, making it ideal for invoicing. > [accordion] What is Base? > > Base is a blockchain network built by Coinbase. It's fast (under 1 second confirmation), cheap (gas under \$0.01), and widely supported. PayRequest chose Base for its speed, cost, and wallet ecosystem. > [accordion] Do I need to buy crypto to accept crypto payments? > > No. You just need a wallet to receive USDC. You don't need to hold or buy any crypto in advance. To convert received USDC to euros, send it to an exchange like Coinbase or Kraken and withdraw to your bank. > [accordion] How long does it take for the money to reach my wallet? > > Base confirms the customer's transaction in under 1 second, but PayRequest waits for 2 confirmations before forwarding your share to avoid chain reorganizations. In practice, your 98% typically arrives within a couple of minutes of the customer paying. > [accordion] What network does USDC need to be on? > > USDC must be on the **Base network** (native USDC, contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). Not bridged or wrapped versions. Most major wallets support Base out of the box. > [accordion] Can I use this outside the Netherlands? > > Yes. Crypto payments work worldwide — no country restrictions. Anyone with an internet connection and USDC on Base can pay. Especially useful for international customers who don't have access to iDEAL or SEPA. > [accordion] Is this safe? > > All transactions are publicly verifiable and cryptographically signed on the Base blockchain. PayRequest never holds your private keys or seed phrase. The 2% fee split is enforced consistently by PayRequest's payment processing code — the same rate applies to every crypto payment. ## Crypto for Subscriptions (Recurring Billing) Crypto works for **recurring subscriptions** too. When a subscription uses USDC as its payment method, an invoice is generated each billing cycle and the customer pays it from their wallet — 98% is forwarded to your wallet once confirmed, just like one-time payments. > [card] [Crypto Recurring Payments](/subscriptions/crypto-recurring-payments) > > Read the full guide on using USDC for subscription billing — setup, customer experience, and FAQs. > [card] [Payment Methods for Subscriptions](/subscriptions/payment-methods) > > See all subscription payment methods and how to switch between them. ## Next Steps > [card] [Supported Wallets](/payment-processing/crypto-supported-wallets) > > See all supported wallets and how to get USDC on Base for both you and your customers. > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See all payment methods PayRequest supports — crypto, iDEAL, credit cards, and more. > [card] [Share Your Crypto Address](/payment-processing/share-wallet-address) > > Get a branded link with your wallet address, QR code, and copy button — great for giveaways and tips. # Supported Crypto Wallets Source: https://docs.payreque.st/payment-processing/crypto-supported-wallets Every wallet app that works with PayRequest USDC payments on Base — for merchants receiving payments and customers paying invoices # Supported Crypto Wallets PayRequest uses **WalletConnect** to connect wallets on the **Base network**. Any wallet that supports WalletConnect and the Base network will work — for both merchants connecting to receive payments and customers paying invoices. > [!NOTE] > > You need **USDC on Base** to pay, and a **Base-compatible wallet address** to receive. See the sections below for how to get set up with each wallet. ## Wallets at a Glance | Wallet | iOS | Android | Browser extension | Best for | | - | - | - | - | - | | MetaMask | ✅ | ✅ | ✅ Chrome, Firefox, Edge | Most popular, widest support | | Coinbase Wallet | ✅ | ✅ | ✅ Chrome | Easy USDC purchase via Coinbase | | Rabby | ✅ | ✅ | ✅ Chrome | Multi-chain power users | | Rainbow | ✅ | ✅ | — | Clean beginner-friendly UX | | Trust Wallet | ✅ | ✅ | ✅ Chrome | Built-in dApp browser | | Kraken Wallet | ✅ | ✅ | — | Kraken exchange users | | Blockchain.com DeFi Wallet | ✅ | ✅ | — | DeFi-focused users | | Any WalletConnect wallet | varies | varies | varies | If it supports Base + WalletConnect | ## Wallet Details > [accordion] MetaMask > > The most widely used crypto wallet. Available as a mobile app and browser extension. > > **Getting USDC on Base:** > > 1. Open MetaMask and switch to the **Base** network (Settings → Networks → Add Base if not listed) > 2. Tap **Buy** and select USDC — MetaMask will route you through an available on-ramp > 3. Alternatively, bridge USDC from Ethereum mainnet using the [Base Bridge](https://bridge.base.org) > > **Connecting to PayRequest:** > > * Desktop: install the MetaMask browser extension, then click **Connect Wallet** on the payment page > * Mobile: scan the WalletConnect QR code with the MetaMask app's built-in scanner > > [Download MetaMask](https://metamask.io/download/) > [accordion] Coinbase Wallet > > Made by Coinbase. The easiest option if you already have a Coinbase account — you can buy USDC directly inside the app and transfer it to Base in one step. > > **Getting USDC on Base:** > > 1. Buy USDC on Coinbase exchange (coinbase.com) > 2. In Coinbase Wallet app, tap **Receive** and share your Base address > 3. In Coinbase exchange, withdraw USDC to that address — select **Base** as the network > > **Connecting to PayRequest:** > > * Mobile: scan the WalletConnect QR code with Coinbase Wallet > * Desktop: use the Coinbase Wallet browser extension > > [Download Coinbase Wallet](https://www.coinbase.com/wallet/downloads) > [accordion] Rabby Wallet > > A modern multi-chain wallet built by DeBank. Excellent for users managing multiple chains. Shows clear transaction previews before you sign. > > **Getting USDC on Base:** > Same as MetaMask — switch to Base network and use the built-in swap or bridge. > > **Connecting to PayRequest:** > > * Mobile: scan the WalletConnect QR code > * Desktop: use the Rabby browser extension > > [Download Rabby](https://rabby.io/) > [accordion] Rainbow > > A mobile-first wallet with a clean, beginner-friendly design. Great if you're new to crypto. > > **Getting USDC on Base:** > Rainbow has a built-in swap and bridge. Switch to Base and buy or swap for USDC inside the app. > > **Connecting to PayRequest:** > Mobile only — scan the WalletConnect QR code from the Rainbow app. > > [Download Rainbow](https://rainbow.me/en/) > [accordion] Trust Wallet > > A popular mobile wallet with a built-in dApp browser and support for hundreds of chains. > > **Getting USDC on Base:** > > 1. Open Trust Wallet and select the Base network > 2. Use the built-in buy feature or receive USDC from another wallet/exchange > > **Connecting to PayRequest:** > Scan the WalletConnect QR code from Trust Wallet's scanner or dApp browser. > > [Download Trust Wallet](https://trustwallet.com/) > [accordion] Kraken Wallet > > Kraken's self-custody wallet app. Ideal for Kraken exchange users. > > **Getting USDC on Base:** > Buy USDC on Kraken exchange, then withdraw to your Kraken Wallet address on Base network. > > **Connecting to PayRequest:** > Scan the WalletConnect QR code from the Kraken Wallet app. > > [Download Kraken Wallet](https://www.kraken.com/wallet) > [accordion] Blockchain.com DeFi Wallet > > The self-custody wallet from Blockchain.com, focused on DeFi users. > > **Getting USDC on Base:** > Transfer USDC from Blockchain.com exchange or another wallet to your Base address in the DeFi Wallet. > > **Connecting to PayRequest:** > Scan the WalletConnect QR code from the app's WalletConnect scanner. > > [Download Blockchain.com DeFi Wallet](https://www.blockchain.com/explorer/assets/usdc) ## For Merchants — Connecting to Receive Payments To receive USDC from your customers, you connect your wallet once in **Provider Settings**. PayRequest stores your public wallet address and routes all USDC payments there via the on-chain FeeSplitting contract. **1. Open Provider Settings** From your dashboard, go to **Settings → Providers** and find the **Crypto (USDC)** card. **2. Click 'Connect Wallet'** A WalletConnect modal opens. Scan the QR code with your wallet app or click your wallet's name if you have a browser extension installed. **3. Approve the connection** Your wallet asks you to approve the connection. Tap **Connect** — no gas fee, no transaction. **4. Sign to verify ownership** Sign the verification message in your wallet (free — no gas). This proves you own the address. **5. Done** Your address appears in Provider Settings with a green **Connected** badge. All future crypto payments go directly to this address (98% of each payment). > [!TIP] > > **Check your balance anytime.** Once connected, your USDC and ETH balances on Base are shown right in Provider Settings — no need to open your wallet app. ## For Customers — Paying an Invoice Customers don't need to create an account. They just need a wallet with USDC on Base. **1. Open the payment page** Click the payment link shared by the business. Select **Pay with Crypto** on the checkout page. **2. Scan the QR code** A WalletConnect QR code appears. Scan it with your wallet app, or if you have a browser extension, click **Connect** instead. **3. Approve USDC spending (first time only)** Your wallet asks you to approve the PayRequest contract to spend USDC on your behalf. This is a one-time step per wallet — you won't need to do it again. **4. Confirm the payment** Your wallet shows the exact USDC amount. Confirm the transaction. Base confirms it in under 1 second. **5. Payment confirmed** The invoice is marked as paid instantly. You'll see a confirmation on the payment page. > [!WARNING] > > Make sure you have **USDC on the Base network** — not Ethereum mainnet, not Polygon, not Arbitrum. Sending USDC on the wrong network will not be received. Check that Base is selected in your wallet before confirming. ## Getting USDC on Base If you're new to crypto and need USDC on Base, here are the easiest paths: > [card] Buy on Coinbase > > Buy USDC on [Coinbase](https://coinbase.com), then withdraw to your wallet address on the **Base** network. Coinbase supports Base natively — no bridge needed. > [card] Buy on Kraken > > Buy USDC on [Kraken](https://kraken.com) and withdraw to your Base wallet address. Select "Base" as the withdrawal network. > [card] Bridge from Ethereum > > Already have USDC on Ethereum mainnet? Use the [Base Bridge](https://bridge.base.org) to move it to Base. Bridging takes a few minutes. > [card] Swap inside your wallet > > Most wallets (MetaMask, Rainbow, Coinbase Wallet) have a built-in swap feature. Switch to the Base network and swap ETH or another token for USDC directly in the app. ## Troubleshooting > [accordion] The QR code opens the wrong app on my phone > > This is a known issue on some Android devices where a QR scanner app intercepts the WalletConnect link instead of opening your wallet. **Fix:** long-press the QR code and copy the link, then open it directly in your wallet app's browser or WalletConnect scanner. > [accordion] iOS Chrome doesn't open my wallet > > WalletConnect deep links are blocked in Chrome on iOS (WKWebView limitation). **Fix:** use **iOS Safari** instead — WalletConnect works correctly there. > [accordion] My wallet isn't listed > > Any wallet supporting WalletConnect and Base will work, even if it's not in the list above. Look for a **WalletConnect** or **Scan QR** option in your wallet's settings or dApp browser. > [accordion] Transaction failed — not enough ETH for gas > > Base transactions require a tiny amount of ETH for gas (typically \$0.001). If you see a "insufficient gas" error, add a small amount of ETH on Base to your wallet. You can buy ETH on Coinbase or Kraken and withdraw to Base. > [accordion] I sent USDC on the wrong network > > If you sent USDC on Ethereum mainnet instead of Base, the funds are not lost — they're just on the wrong chain. Use the [Base Bridge](https://bridge.base.org) to move them to Base, or contact the exchange you used to check if they support a network correction. ## Next Steps > [card] [Crypto Payments Overview](/payment-processing/crypto-payments) > > How USDC payments work on PayRequest, fees, and the FeeSplitting contract. > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See all payment methods available on PayRequest. > [card] [Share Your Crypto Address](/payment-processing/share-wallet-address) > > Get a branded link with your wallet address, QR code, and copy button — great for giveaways and tips. # Security Deposit Deadlines and Release Timing Source: https://docs.payreque.st/payment-processing/deposit-hold-duration Understand the difference between an authorization deadline, an expired checkout and the time a bank needs to remove a released hold. There are **three different timelines** when managing a [security deposit](/payment-processing/security-deposits). Do not use one as proof of another. | Timeline | What it means | What to check | | - | - | - | | **Checkout availability** | How long the customer can complete a particular checkout attempt. | An expired checkout does not rule out a hold from another attempt or link. | | **Authorization deadline** | The provider's deadline for capturing an existing reservation. | The exact deadline and latest provider status on the deposit. | | **Bank processing after release** | When a released reservation disappears and available funds update. | The confirmed release time and the customer's card issuer. | ## Use the provider-confirmed authorization deadline The actual window depends on the provider, payment method, transaction type and merchant eligibility. Once authorization is confirmed, PayRequest stores the provider deadline where available and shows it in deposit details. Check that deadline before committing to a booking or deciding when to inspect a rental. If the deadline is absent or the provider check fails, verify the reservation before promising the customer a particular hold period. > [!WARNING] > > A duration selected on a product is not a guarantee that the bank will hold funds for that many days. It also does not schedule an automatic release on your inspection date. Explicitly release the reservation when it is no longer needed. ## Stripe For online card authorizations, standard windows are often around seven days, with exceptions by transaction type and market. The exact deadline comes from the authorized charge. See [Stripe's authorization windows](https://docs.stripe.com/payments/place-a-hold-on-a-payment-method#authorization-validity-windows). PayRequest requests extended authorization when available. Availability and the resulting deadline depend on Stripe's eligibility rules and the connected account; selecting a longer product duration does not enable it. See [Stripe's extended authorization documentation](https://docs.stripe.com/payments/extended-authorization). An existing Stripe hold cannot be extended in place. For new deposits with prior customer consent, Business can request a replacement authorization near expiry using the saved card. Bank approval is required and the replacement must fit within 30 days of the first authorization; see [Stripe deposit renewal](/payment-processing/security-deposits#renew-a-stripe-deposit-on-business). The current Stripe capture flow also makes one final capture: charging part releases the unused amount. Do not plan a second charge from that same reservation. Use **Check linked authorization** for a tracked deposit or **Check Stripe** in the Stripe reservations overview to verify the latest records. A missing or incomplete search result does not prove there are no holds. ## Mollie Mollie's authorization expiry depends on the payment method. PayRequest uses the returned capture deadline where available. Check the actual authorized payment rather than relying on a card-brand estimate selected before checkout. The payment methods Mollie supports in general may differ from those offered by PayRequest's deposit checkout. Do not assume that every method described by Mollie is selectable in your deposit flow. See [Mollie's explanation of authorization holds](https://docs.mollie.com/docs/place-a-hold-for-a-payment). ## Direct PayPal PayPal separates its overall authorization period from an initial honor period. Its documentation describes a 29-day authorization period and a three-day initial honor period; later capture depends on availability and PayPal's rules. Reauthorization has its own eligibility and timing requirements. See [PayPal authorization and honor periods](https://developer.paypal.com/payment-methods/auth-honor/). PayRequest has scheduled reauthorization handling for eligible direct PayPal deposits. A scheduled attempt does not guarantee success or an uninterrupted reservation. Check the latest result and displayed deadline; investigate a failed reauthorization rather than assuming funds remain available. ## An expired checkout is not an expired hold A customer can have used a different link or an earlier attempt. Before asking them to authorize again, check the exact provider records and whether another reservation exists. For the same tracked Stripe request, PayRequest reuses an existing open session. An uncertain provider response or an ended session blocks a new authorization start until it has been reviewed. Contact support if the request cannot continue; do not create a replacement to work around that check. ## When an actual authorization expires An expired authorization cannot be captured. Provider confirmation and synchronization determine when the application reflects the result. For Stripe, PayRequest requires confirmation that the authorization is canceled with no remaining reserved or charged amount before marking an authorized deposit expired automatically. If the business still needs a deposit, review the old provider records first and arrange any new request separately with the customer. If a charge is due after expiry, an expired hold itself cannot be used to collect it. ## After a confirmed release The provider's confirmation and the bank's customer-facing display can update at different times. A bank may continue showing a pending reservation for several days. Do not promise that all banks will remove it within a fixed number of business days. A release of uncaptured funds is not a refund: the pending reservation may simply disappear rather than appear as an incoming credit. Previously charged amounts require separate refund handling. Give the customer the released amount, date and time with timezone, and payment reference if their bank needs to investigate. If they report two holds, investigate both references before describing the second entry as ordinary processing. > [!TIP] > > Share [Security deposits for customers](/customer-guide/security-deposits) with the cardholder. It explains pending entries and the difference between a release and a refund in plain language. # Supported Digital Wallets Source: https://docs.payreque.st/payment-processing/digital-wallets Accept payments from 26+ digital wallets and P2P platforms worldwide — from Wise and Revolut in Europe to GCash in the Philippines, UPI in India, and Pix in Brazil. # Supported Digital Wallets PayRequest lets you accept payments from **26+ digital wallets and P2P payment platforms** across 6 continents. Add your handle once in Settings — customers see the button on your payment page and transfer via their own app. > [card] 26+ Platforms > > Global P2P wallets, regional apps, and instant transfer networks > [card] 6 Regions > > Europe, Americas, Asia, Africa — wherever your customers are > [card] Zero gateway fees > > Customer pays you directly — no PayRequest transaction fees apply > [!NOTE] > > Add your handles under **Settings → Payment Providers → Other Ways to Pay**. Only platforms you've configured appear on your payment page. Customers pay in their app, then click **I have paid** to confirm. *** ## 🌍 Europe & Global The most popular P2P and instant payment apps used by European and international customers. > [card] [🇪🇺 Revolut](/payment-processing/other-ways-to-pay) > > **Payment link** > > Europe's fastest-growing digital bank. Enter your Revolut username — PayRequest builds the `revolut.me/` link automatically. > [card] [🌍 Wise](/payment-processing/other-ways-to-pay) > > **Payment link** > > Cross-border transfers in 40+ currencies. Enter your Wise username — PayRequest generates the `wise.com/pay/me/` link. > [card] [🇪🇺 bunq.me](/payment-processing/other-ways-to-pay) > > **Payment link with amount** > > Dutch digital bank popular across Europe. The link includes the exact invoice amount — customers pay with one tap. > [card] [🌍 Paxum](/payment-processing/other-ways-to-pay) > > **Display only** > > Global e-wallet used by digital and creative professionals. Enter your Paxum email — shown to the customer as text. > [card] [🌍 Skrill](/payment-processing/other-ways-to-pay) > > **Display only** > > Worldwide digital wallet with prepaid cards. Enter your Skrill email — shown to the customer as text. > [card] [🌍 Bank Transfer](/payment-processing/bank-transfer) > > **Display only** > > IBAN / SWIFT / routing number. Enter account holder, bank name, IBAN, and BIC. Shown as structured text to the customer. *** ## 🇺🇸 United States The three dominant P2P apps used by US consumers. > [card] [🇺🇸 Cash App](/payment-processing/other-ways-to-pay) > > **Payment link with amount** > > Square's P2P wallet, popular with 50M+ US users. Enter your `$cashtag` — the link includes the invoice amount. > [card] [🇺🇸 Venmo](/payment-processing/other-ways-to-pay) > > **Payment link** > > PayPal's social payments app. Enter your Venmo username — PayRequest builds the `venmo.com/` link. > [card] [🇺🇸 Zelle](/payment-processing/other-ways-to-pay) > > **Display only** > > Bank-to-bank instant transfers embedded in most US banking apps. Enter your email or phone number. *** ## 🌎 Latin America Regional instant payment systems used across South and Central America. > [card] [🌎 Mercado Pago](/payment-processing/other-ways-to-pay) > > **Display only** > > Latin America's largest fintech, spanning Argentina, Brazil, Mexico, Colombia and more. Enter your alias, phone, or CVU. > [card] [🇧🇷 Pix](/payment-processing/other-ways-to-pay) > > **Display only** > > Brazil's instant payment system, created by the Central Bank of Brazil — used by 140M+ people. Enter your CPF, email, phone, or random key. > [card] [🇲🇽 SPEI](/payment-processing/other-ways-to-pay) > > **Display only** > > Mexico's interbank electronic transfer network. Enter your CLABE (18-digit bank key). > [card] [🇻🇪 Pago Móvil](/payment-processing/other-ways-to-pay) > > **Display only** > > Venezuela's mobile payment system linked to bank accounts. Enter bank · phone number · cédula (national ID). *** ## 🇮🇳 South Asia India's unified instant payment infrastructure. > [card] [🇮🇳 UPI — Unified Payments Interface](/payment-processing/other-ways-to-pay) > > **Payment link with amount** > > India's government-built real-time payment rails used by 300M+ people daily via PhonePe, Google Pay, Paytm, and all bank apps. Enter your UPI ID (e.g. `name@upi`) — PayRequest generates a `upi://pay` deep link with the exact amount pre-filled, opening the customer's preferred UPI app directly. *** ## 🌏 Southeast & East Asia The most widely used digital wallets across Asia's fastest-growing markets. > [card] [🇨🇳 Alipay](/payment-processing/other-ways-to-pay) > > **Display only** > > Ant Group's super-app wallet with 1B+ users in China and across Asia. Enter your Alipay account or phone number. > [card] [🇨🇳 WeChat Pay](/payment-processing/other-ways-to-pay) > > **Display only** > > Tencent's payment layer inside WeChat — ubiquitous in China. Enter your WeChat ID. > [card] [🇰🇷 KakaoPay](/payment-processing/other-ways-to-pay) > > **Display only** > > South Korea's leading mobile wallet, integrated into KakaoTalk (95%+ Korean smartphone users). Enter your KakaoTalk ID. > [card] [🇵🇭 GCash](/payment-processing/other-ways-to-pay) > > **Display only** > > The Philippines' #1 e-wallet with 90M+ registered users. Enter your registered GCash phone number. > [card] [🇸🇬 PayNow](/payment-processing/other-ways-to-pay) > > **Display only** > > Singapore's interbank real-time transfer system. Enter your phone number, NRIC, or UEN (business registration). > [card] [🇹🇭 PromptPay](/payment-processing/other-ways-to-pay) > > **Display only** > > Thailand's national instant payment network, managed by the Bank of Thailand. Enter your phone number or national ID. > [card] [🇻🇳 MoMo](/payment-processing/other-ways-to-pay) > > **Display only** > > Vietnam's largest e-wallet with 31M+ users. Enter your registered MoMo phone number. > [card] [— Binance Pay](/payment-processing/other-ways-to-pay) > > **Display only (crypto equivalent)** > > P2P crypto transfers via Binance. Enter your numeric Binance Pay ID. PayRequest shows the USDT-equivalent amount to the customer and captures the Order ID for easy reconciliation. *** ## 🌍 Africa Mobile money networks that power financial access across sub-Saharan Africa. > [card] [🇰🇪 M-Pesa](/payment-processing/other-ways-to-pay) > > **Display only** > > Safaricom's pioneering mobile money platform, the dominant payment method across Kenya, Tanzania, Ethiopia, and 7 other African markets. Enter your M-Pesa phone number (+254 7XX XXX XXX). *** ## 🇪🇺 European Regional Country-specific instant payment apps deeply embedded in local banking ecosystems. > [card] [🇳🇱 Tikkie](/payment-processing/other-ways-to-pay) > > **Display only** > > ABN AMRO's payment request app, used by 7M+ Dutch consumers to split bills and pay each other. Enter your Dutch mobile number. > [card] [🇪🇸 Bizum](/payment-processing/other-ways-to-pay) > > **Display only** > > Spain's bank-backed instant mobile payment system, supported by all major Spanish banks with 24M+ users. Enter your Spanish phone number. *** ## 🇨🇦 Canada > [card] [🇨🇦 Interac e-Transfer](/payment-processing/other-ways-to-pay) > > **Display only** > > Canada's bank-to-bank payment network available through virtually every Canadian bank app. 99% of Canadians with a bank account can send and receive Interac transfers. Enter your email address or phone number. *** ## ₿ Crypto Wallets Beyond P2P platforms, PayRequest also supports on-chain crypto payments with automatic settlement. > [card] [Base USDC](/payment-processing/crypto-payments) > > **Automatic settlement** > > Accept USDC stablecoin on Coinbase's Base L2 network. Near-zero fees, 2-second finality. Customers pay from any Base-compatible wallet (Coinbase Wallet, MetaMask, Rainbow, etc.). > [card] [Solana USDC](/payment-processing/solana-pay) > > **Automatic settlement** > > Accept USDC on Solana via Solana Pay QR codes. Sub-cent fees, instant finality. Works with Phantom, Solflare, Backpack, and all Solana wallets. > [!TIP] > > Crypto payments settle automatically on-chain — no "I have paid" confirmation needed. See [Crypto Payments](/payment-processing/crypto-payments) for setup. *** ## How the payment flow works **1. You add your handle** Go to **Settings → Payment Providers → Other Ways to Pay**. Enter your username, phone number, or account ID for each platform you want to offer. **2. Customer selects a wallet** On your payment page, every active wallet appears as a button. The customer picks the one they use. **3. Customer pays in their app** For link-type wallets (Revolut, Wise, Cash App, bunq.me, UPI), a deep link opens the customer's app with amount pre-filled. For display-only wallets, they see your handle and transfer manually. **4. Customer clicks «I have paid»** After transferring, the customer confirms on your payment page. You receive a notification and verify receipt in your wallet app. > [!WARNING] > > PayRequest cannot automatically verify transfers for P2P wallets. Always check your app before delivering goods or services. For zero-manual-work reconciliation, use [Bank Transfer with Ponto](/payment-processing/bank-transfer) or [Crypto Payments](/payment-processing/crypto-payments) instead. *** ## Link types at a glance | Type | How it works | Platforms | | - | - | - | | **Payment link with amount** | Button opens the wallet app with amount pre-filled | bunq.me, Cash App, UPI | | **Payment link** | Button opens the wallet app with your profile | Wise, Revolut, Venmo | | **Display only** | Handle shown as text — customer opens their own app | All others | *** > [card] [Set up Other Ways to Pay](/payment-processing/other-ways-to-pay) > > Step-by-step guide to configuring your wallet handles and toggling them on your payment page. > [card] [Crypto Payments](/payment-processing/crypto-payments) > > Accept USDC on Base or Solana with fully automatic on-chain settlement. > [card] [Bank Transfer (Auto-match)](/payment-processing/bank-transfer) > > Accept bank transfers with automatic Ponto reconciliation — no manual confirmation. > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See all payment methods including cards, iDEAL, SEPA, and more. # Handling Chargebacks Source: https://docs.payreque.st/payment-processing/handling-chargebacks Understanding and managing SEPA chargebacks in PayRequest # Handling Chargebacks A chargeback (terugboeking) occurs when a customer reverses a payment, typically for SEPA Direct Debit transactions. PayRequest provides comprehensive tools to track, understand, and manage chargebacks effectively. ## Accessing Chargebacks Navigate to **Payment Processing > Chargebacks** to view all chargebacks in your account. PayRequest automatically syncs chargebacks from Mollie every 4 hours in the background. ## Chargeback Detail Page Click on any chargeback to view detailed information: ### Customer Information * **Customer card** with avatar and contact details * Direct link to customer profile * View complete customer history ### Subscription & Transaction Links PayRequest intelligently links chargebacks to their related: * **Subscription** - Shows the product, status, and recurring amount * **Transaction** - Payment details including date, method, and description * **Invoice** - If applicable ### Chargeback Details * **Amount** - The charged-back amount * **Created Date** - When the chargeback was initiated * **Reversed Date** - If the chargeback was later reversed * **Settlement Amount** - Only shown if different from the chargeback amount ## Invoice Chargeback Status When a chargeback is received, the linked invoice is automatically updated: * Invoice status changes from **Paid** to **Chargeback** (shown as a red badge) * The chargeback amount, date, and reason are stored on the invoice > [!NOTE] > > The chargeback status is protected — webhooks and payment syncs will never overwrite it back to "Paid". This ensures your records accurately reflect the reversed payment. ### Chargeback Details on Invoice Page When viewing an invoice with chargeback status, a **Chargeback Details** card appears in the sidebar showing: * **Chargeback amount** — The reversed amount * **Date** — When the chargeback was initiated * **Reason code** — The SEPA reason code with description (e.g., MD06 - Return of funds requested by end customer) * **Chargeback ID** — The Mollie chargeback reference If the invoice is linked to a subscription, the card also shows the **Payment Retry Status**: * **Failed attempts** — Current failures vs maximum allowed (e.g., "1 / 2") * **Last failure date** — When the most recent failure occurred * **Next retry** — When the next automatic retry is scheduled (if applicable) * **Retry history** — Complete timeline of all retry attempts with amounts and reasons * **Direct link** to the associated subscription for further management > [!TIP] > > You can see chargeback and retry information directly on the invoice page without navigating to the subscription. This gives you a complete picture of the payment issue at a glance. ## SEPA Reason Codes PayRequest displays color-coded reason codes to help you quickly understand why a chargeback occurred: ### Critical Issues (Red/Rose) * **AC01** - IBAN incorrect or unknown * **MD01** - Invalid mandate (expired, missing, or incorrect type) ### Account Issues (Orange/Amber) * **AC04** - Account closed * **AC06** - Direct debit not allowed on this account ### Transaction Issues (Yellow) * **AG02** - Transaction information incorrect (wrong payment type or mandate reference) ### Insufficient Funds (Lime) * **AM04** - Insufficient funds in customer's account ### Customer Actions (Purple/Blue) * **MD06** - Customer reversed the payment (possible within 8 weeks) * **MS02** - Customer declined before processing ### Special Cases * **MD07** - Customer deceased (Zinc) * **MS03** - Multiple possible reasons (Cyan) * **SL01** - Bank refused (daily limit or blocked account) (Indigo) ### Retryable vs Non-Retryable Reason Codes | Retryable | Non-Retryable | | - | - | | AM04 (Insufficient Funds) | MD06 (Customer Reversed) | | MS03 (Not Specified) | MS02 (Customer Declined) | | | AC04 (Account Closed) | | | MD07 (Customer Deceased) | | | AG01 (Transaction Forbidden) | Retryable chargebacks automatically schedule payment retries on the linked subscription. Non-retryable chargebacks mark the subscription as **Payment Failed** immediately. ## What to Do When You Receive a Chargeback 1. **Check the Reason Code** - Understand why the chargeback occurred 2. **Review the Invoice** - Open the invoice to see chargeback details and retry status in one place 3. **Contact Your Customer** - For codes like MD06, MS02, or MS03, reach out to understand the issue 4. **Update Payment Details** - For AC01, AC04, or AC06, request new bank account information 5. **Fix Technical Issues** - For AG02, review your payment type settings 6. **Retry if Appropriate** - For AM04, you may retry after confirming funds are available ## Prevention Tips ### Mandate Management * Ensure mandates are created before charging customers * Keep track of mandate expiration (36 months) * Always use unique mandate references ### Clear Communication * Inform customers about upcoming charges * Use clear payment descriptions * Maintain up-to-date customer contact information ### Payment Timing * Don't charge immediately after mandate creation * Allow time for first payments (FRST) before recurring (RCUR) ### Account Verification * Validate IBANs before creating mandates * Confirm account status with customers * Update banking details when customers notify you ## Automatic Syncing PayRequest automatically syncs chargeback data from Mollie: * **Frequency**: Every 4 hours * **Scope**: Last 90 days of transactions * **Background**: No manual refresh needed All chargeback information is kept up-to-date automatically, ensuring you always have the latest status and details. ## Related Resources * [Failed Payment Handling](/subscriptions/failed-payment-handling) * [Payment Methods Overview](/payment-processing/payment-methods-overview) * [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) * [Customer Management](/customer-management) * [Subscriptions](/subscriptions) ## Need Help? If you're experiencing frequent chargebacks or need assistance understanding a specific case, our support team is here to help. Contact us with your chargeback ID for personalized assistance. # Merchant Affiliate Marketing Source: https://docs.payreque.st/payment-processing/merchant-affiliates Recruit affiliates, track one-time product sales, and record commissions paid directly by your business. Affiliate Marketing lets you run a referral program for your own Payment Page products. You set the commission rules, review applications, and pay affiliates directly. **PayRequest tracks commissions and manual payment records. It never holds or transfers affiliate earnings.** ## Requirements * An active **Business** or **Growth** plan. * A Payment Page with eligible products. * An enabled affiliate program in your merchant dashboard. Provider-specific product and checkout restrictions still apply. Affiliate Marketing does not enable additional payment methods or provider payout services. ## Set up your program 1. Open **Affiliates** in your [PayRequest dashboard](https://payrequest.app/affiliates). 2. Open **Settings** and enter your default commission percentage. 3. Choose an attribution window and an approval delay. Both default to 30 days. 4. Add a program description, merchant contact address, and payout instructions. Explain how and when your business pays affiliates. 5. Choose whether to accept public applications, then enable the program. Your program belongs to your merchant account. An affiliate can promote multiple eligible products within that program. ### Product commission overrides Use the **Products** tab to set a different commission percentage for an individual product. A zero commission excludes that product from earning commissions. Rates are frozen when a new checkout is created. Changing a rate applies to future checkouts and does not reprice historical commissions. ## Invite and manage affiliates Invite affiliates by email or enable public registration. Public applicants verify their email and wait for your approval before their links can earn commissions. Use the **Affiliates** tab to review applications, approve or reject an affiliate, or suspend their participation. You can open an affiliate to review their referral links, attributed sales, commission history, and payment records. An affiliate can join programs from different merchants using the same email identity. Each merchant program has its own membership, referral code, approval, and reporting. ## Affiliate access on your Payment Page Affiliates open the **Affiliates** tab on your Payment Page, or visit: ```text theme={null} https://payrequest.me/your-handle/affiliates ``` The portal follows your Payment Page branding. It shows your program terms, product cards, commission rates, and payout instructions. Affiliates use the normal Payment Page login entry at `/your-handle/login`. They do not need a PayRequest merchant account. Customers already signed in to your Payment Page can apply using that session; other affiliates verify their email through a one-time sign-in link. After approval, affiliates can copy product referral links, for example: ```text theme={null} https://payrequest.me/your-handle/p/your-product?ref=affiliate-code ``` Their dashboard shows their own clicks, attributed sales, commissions, and payment history. It does not expose customer names, email addresses, or full payment details. ## Attribution and consent Visitors who follow a valid referral link can consent to referral tracking. With consent, a first-party cookie remembers a random attribution receipt for your configured window. The last valid affiliate referral within the same merchant program receives attribution. Attribution does not carry across merchants. It is fixed when checkout is created, so changing the referral parameter afterward cannot redirect the commission. Visitors can decline tracking or clear their saved referral through the program's privacy details. Without valid consented attribution, a purchase does not earn an affiliate commission. ## Eligible sales and commission amounts The first version covers eligible, one-time native product checkouts on Payment Pages. Recurring purchases and renewals, deposits, generic amount links, Shop carts, and historical payments are excluded. Commissions are calculated from the eligible product subtotal after applicable discounts, excluding tax, shipping, and setup fees. Payment processing fees and PayRequest fees do not reduce that commission base. For example, an eligible subtotal of €100 with a 10% commission earns the affiliate €10. Zero-value payments do not earn commissions. Self-referrals are excluded where the merchant, affiliate, and buyer can be reliably matched by email. A commission is recorded only after the existing payment lifecycle confirms successful payment. Failed, canceled, and unpaid transactions do not earn commissions. ## Review commissions Commissions move through three main statuses: * **Pending:** the payment succeeded, but the approval delay has not finished. * **Approved:** the delay has passed and payment, refund, and dispute checks allow payment to the affiliate. * **Paid:** you recorded that your business paid the approved commission directly. Pending refunds or unresolved disputes can hold approval and payment eligibility. Completed partial refunds reduce commissions proportionally; full refunds and lost chargebacks can reverse unpaid commissions. If a commission was already marked paid, its payment record is preserved. A separate negative adjustment records the reversal for you to settle directly with the affiliate. PayRequest does not automatically reclaim those funds or deduct the adjustment from another payout. ## Record a manual payout 1. Open **Payouts** and select approved commissions for the affiliate. 2. Pay the affiliate directly using the method agreed in your payout instructions. 3. Record the payment date and a reference or note in PayRequest. 4. Confirm the manual payout. You can group eligible commissions into a payment record. PayRequest records the confirming merchant user and prevents the same commissions from being paid twice through duplicate submissions. The affiliate can see the recorded payout reference. Use a reference suitable for sharing with them. ## Reporting and exports The merchant overview shows affiliate performance and pending, approved, and paid commissions. Use the affiliate and commission views for more detail, and export commission data to CSV for your records. Keep amounts in their reported currencies when reconciling payments. Recording a payout confirms your own payment to the affiliate; it does not initiate a transfer through PayRequest. # Other Ways to Pay Source: https://docs.payreque.st/payment-processing/other-ways-to-pay Let customers pay you via Wise, Revolut, Cash App, Venmo, GCash, WeChat Pay, Mercado Pago, and 20+ more platforms — they confirm payment manually after transferring. # Other Ways to Pay PayRequest lets you display your personal handles for **26 peer-to-peer and regional payment platforms** directly on your payment page. Customers pay you outside PayRequest, then click **I have paid** to confirm. No card processor required. > [!NOTE] > > Configure your handles under **Settings → Payment Providers → Other Ways to Pay**. Only platforms you've saved with a handle appear on your customer-facing payment page. ## How It Works **1. Add your handle** Go to **Settings → Payment Providers → Other Ways to Pay**. Find the platform, enter your username, phone number, or account identifier, and click **Save**. **2. Toggle visibility** Use the green toggle next to each saved platform to show or hide it on your payment page without deleting the handle. **3. Customer pays you directly** On your payment page the customer sees a button for each active platform. They tap it, transfer the amount in their own app, then return and click **I have paid**. **4. You confirm receipt** You receive a notification and can verify the transfer in your platform's app before marking the invoice as paid on your end. > [!WARNING] > > PayRequest cannot automatically verify "I have paid" confirmations for these platforms. Always check your platform app or bank before delivering goods or services. ## Smart Handle Correction PayRequest automatically cleans up common input mistakes when you save a handle, so your payment links always work correctly. | Platform | Auto-corrected | | - | - | | **Wise** | Strips leading `@` and full URL prefix | | **Revolut** | Strips leading `@` and full URL prefix | | **Venmo** | Strips leading `@` and full URL prefix | | **bunq.me** | Strips full URL prefix and leading `/` | | **Cash App** | Strips `$` and full URL prefix | | **Binance Pay** | Digits only — non-numeric characters removed | For example, pasting `https://wise.com/pay/me/johndoe` or `@johndoe` both save as `johndoe` and generate the correct `https://wise.com/pay/me/johndoe` link. *** ## Supported Platforms ### 🌍 Global & European | Platform | Type | What to enter | | - | - | - | | **Wise** | Payment link | Your Wise username (e.g. `johndoe`) | | **Revolut** | Payment link | Your Revolut username | | **bunq.me** | Payment link (with amount) | Your bunq.me name | | **Paxum** | Display only | Your Paxum email address | | **Skrill** | Display only | Your Skrill email address | | **Bank Transfer** | Display only | Account holder, IBAN, BIC/SWIFT | ### 🇺🇸 United States | Platform | Type | What to enter | | - | - | - | | **Cash App** | Payment link | Your `$cashtag` (without the `$`) | | **Venmo** | Payment link | Your Venmo username | | **Zelle** | Display only | Your email or phone number | ### 🌎 Latin America | Platform | Flag | What to enter | | - | - | - | | **Mercado Pago** | 🌎 | Your alias, phone number, or CVU | | **Pix** | 🇧🇷 | CPF, email, phone, or random key | | **SPEI** | 🇲🇽 | Your CLABE (18 digits) | | **Pago Móvil** | 🇻🇪 | Bank · phone · cédula | ### 🇮🇳 South Asia | Platform | Flag | What to enter | | - | - | - | | **UPI** | 🇮🇳 | Your UPI ID (e.g. `name@upi`) | ### 🌏 Southeast & East Asia | Platform | Flag | What to enter | | - | - | - | | **GCash** | 🇵🇭 | Your registered phone number | | **PayNow** | 🇸🇬 | Phone number, NRIC, or UEN | | **PromptPay** | 🇹🇭 | Phone number or national ID | | **KakaoPay** | 🇰🇷 | Your KakaoTalk ID | | **MoMo** | 🇻🇳 | Your registered phone number | | **WeChat Pay** | 🇨🇳 | Your WeChat ID | | **Alipay** | 🇨🇳 | Your Alipay account or phone | | **Binance Pay** | — | Your Binance Pay ID (numbers only) | ### 🌍 Africa & Middle East | Platform | Flag | What to enter | | - | - | - | | **M-Pesa** | 🇰🇪 | Your M-Pesa phone number | ### 🇪🇺 European Regional | Platform | Flag | What to enter | | - | - | - | | **Tikkie** | 🇳🇱 | Your Dutch phone number | | **Bizum** | 🇪🇸 | Your Spanish phone number | ### 🇨🇦 Canada | Platform | Flag | What to enter | | - | - | - | | **Interac e-Transfer** | 🇨🇦 | Your email or phone number | *** ## Platform Link Types Platforms fall into three categories based on how the customer-facing button behaves: | Type | What happens | Platforms | | - | - | - | | **Payment link (static)** | Button opens a fixed URL with your handle | Wise, Revolut, Venmo, UPI | | **Payment link (with amount)** | Button opens a URL that includes the invoice amount | bunq.me, Cash App, UPI | | **Display only** | Handle is shown as text — customer opens their own app | All others | *** ## Frequently Asked Questions > [accordion] Do these platforms get verified automatically? > > No. PayRequest displays the "I have paid" button and records the customer's confirmation, but cannot check whether the transfer actually happened. Always verify in your platform app before fulfilling orders. > [accordion] Can I show multiple platforms at once? > > Yes. Enable as many platforms as you like. All active platforms appear as buttons on your payment page, so customers can choose whichever they use. > [accordion] What if a customer enters the wrong amount? > > Since the transfer happens in an external app, you'll see the actual amount when you check your platform. If there's a discrepancy, follow up with the customer directly before confirming payment. > [accordion] Can I hide a platform without deleting my handle? > > Yes. Use the green toggle next to each platform. Toggling it off hides the platform from your payment page but keeps the handle saved so you can re-enable it anytime. > [accordion] Why is my Binance Pay ID only accepting numbers? > > Binance Pay IDs are always numeric. The input field is restricted to digits only, and any non-numeric characters are automatically stripped when you save. > [accordion] I pasted my full Wise profile URL — will it work? > > Yes. PayRequest strips the URL prefix automatically. Whether you enter `johndoe`, `@johndoe`, or `https://wise.com/pay/me/johndoe`, the saved handle is always `johndoe` and the generated link is correct. ## Next Steps > [card] [Bank Transfer (Automatic)](/payment-processing/bank-transfer) > > Accept bank transfers with automatic matching via Ponto — no manual confirmation needed. > [card] [Crypto Payments](/payment-processing/crypto-payments) > > Accept USDC on Base or Solana with automatic on-chain settlement. > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See all payment methods available in PayRequest. > [card] [Smart Links](/payment-processing/smart-links) > > Send a single payment link that works across all your active payment methods. # P2P Wallet Payments Source: https://docs.payreque.st/payment-processing/p2p-wallet-payments Send USDC directly between PayRequest users — prominent pay card on every payrequest.me page. No checkout, no fees, instant on-chain settlement. # P2P Wallet Payments Anyone with a Solana wallet can **send USDC directly to a PayRequest user** right from their `payrequest.me` page — no invoice, no checkout form, no platform fee. One amount field, one button, money sent. > [!NOTE] > > P2P payments appear automatically on your `payrequest.me` page when you have a **Solana wallet connected** in Provider Settings. No extra setup required. ## What Makes It Different > [card] Prominent pay card > > The P2P section is the first thing visitors see — a prominent card with your avatar, a big amount field, and a single "Send" button. Standard payment methods appear below. > [card] No platform fee > > 100% of the USDC goes to your wallet. No PayRequest cut, no processing charge of any kind. > [card] Instant on-chain settlement > > Solana confirms in under a second. The USDC is in your wallet before the sender closes their phone. > [card] Pay faster with PayRequest > > Senders who have a PayRequest account can click **Log in →** to pre-fill their name, email, and wallet — one tap to pay, just like PayPal's quick checkout. ## How to Enable P2P Payments You only need to connect your Solana wallet once. **1. Go to Provider Settings** In your PayRequest dashboard, open **Settings → Provider Settings**. **2. Connect your Solana wallet** Scroll to the **Solana Wallet (P2P)** card and click **Connect Solana Wallet**. Approve the connection in your wallet extension. Your address is saved to your account. **3. That's it** Your `payrequest.me` page now shows the P2P hero section to every visitor. No further configuration needed. ## How Senders Use It When someone visits your `payrequest.me/{handle}` page, the P2P card is the first thing they see — above the standard payment form. **1. Enter an amount** The sender types an amount directly in the large amount field on the P2P card. A note field below it is optional. **2. Connect their Solana wallet** They click **Connect wallet to pay**. Their wallet (Phantom, Solflare, Coinbase Wallet, MetaMask, etc.) connects in one click. Once connected, the button updates to show exactly what will happen: **Send €25.00 → \[Your Name]**. **3. Confirm in their wallet** One more click opens their wallet with the pre-filled transfer to approve. The USDC leaves their wallet and arrives in yours — on-chain, permanent, instant. > [!TIP] > > Senders need a tiny amount of SOL in their wallet (less than \$0.01 worth) to pay the Solana network fee. USDC alone isn't enough — they need SOL for gas. ## Pay Faster with a PayRequest Account Senders who have their own PayRequest account can skip entering their name and email entirely. **1. Click Log in →** A small **Pay faster with your PayRequest account** bar appears at the top of the page. Clicking **Log in →** opens a small popup to payrequest.app. **2. Authenticate in the popup** If already logged in, the popup closes in under a second. If not, a quick login form appears. After login, the popup closes automatically. **3. Pre-filled and ready** The payment page updates: the name and email fields fill in, and a **● Paying as \[Name]** badge replaces the login button. If the sender has a Solana wallet connected to their PayRequest account, their wallet address is shown immediately — no manual connect needed before they enter an amount. > [!NOTE] > > This works like PayPal's express checkout. The popup is hosted on payrequest.app, so no credentials are ever shared with the page owner. Senders can click **Not you?** at any time to clear their identity. ## Supported Sender Wallets | Wallet | Platforms | Notes | | - | - | - | | **Phantom** | Chrome, Firefox, Brave, Edge, iOS, Android | Most popular Solana wallet. Recommended for first-time users. | | **Solflare** | Chrome, Firefox, Brave, Edge, iOS, Android | Full-featured with hardware wallet support. | | **Coinbase Wallet** | Chrome, iOS, Android | Supports both Solana and EVM. Use the Solana network. | | **Trust Wallet** | Chrome, iOS, Android | Multi-chain. Ensure Solana is selected. | | **Backpack** | Chrome, iOS, Android | xNFT wallet with native Solana support. | | **MetaMask** | Chrome, Firefox, Brave, Edge, iOS, Android | Supported via native Solana (recent versions) or via Solana Snap. | | **Any Wallet Standard wallet** | Varies | Any wallet implementing the [Solana Wallet Standard](https://github.com/wallet-standard/wallet-standard) is detected automatically. | > [!NOTE] > > **MetaMask and Solana:** Newer MetaMask versions support Solana natively via Wallet Standard. You can also install the **Solflare Snap** from inside MetaMask (Snaps → Search "Solflare") to add full Solana support in one click. > [!WARNING] > > Senders must have **USDC on the Solana network** — not USDC on Ethereum or Base. These are different tokens despite sharing the same name. Solana USDC can be obtained on any major exchange (Coinbase, Kraken, Binance) or bridged via [Wormhole](https://wormhole.com). ## Viewing Your Received Transfers All completed P2P transfers are recorded in your **Wallet Dashboard**: 1. Go to **Wallet** in the sidebar 2. Scroll to the **P2P Transfers** section 3. Each entry shows the sender's wallet address (shortened), the amount, the note if one was left, and a **Solscan** link to the on-chain transaction Transfers you received show in green with a down-arrow icon. Transfers you've sent show in grey with an up-arrow. ## P2P vs. Standard Payments | | P2P Wallet Payment | Standard Payment | | - | - | - | | **Requires name/email** | No (optional via PayRequest login) | Yes | | **Creates an invoice** | No | Yes | | **Platform fee** | None | Varies by method | | **Settlement** | Instant (on-chain) | 1–3 days (bank) | | **Refundable** | No (blockchain final) | Yes (via PayRequest) | | **Appears in** | Wallet Dashboard | Transactions page | | **Best for** | Tips, quick sends, peer payments | Invoiced work, products | > [!WARNING] > > P2P transfers are **irreversible** — like cash. Once a sender confirms in their wallet, the USDC is gone. If someone sends the wrong amount or to the wrong page, you'll need to return the funds manually from your own wallet. ## Frequently Asked Questions > [accordion] Which wallets can senders use? > > Phantom, Solflare, Coinbase Wallet, Trust Wallet, Backpack, MetaMask (native Solana or Solana Snap), and any wallet implementing the Solana Wallet Standard. See the full table above. > [accordion] Do senders need a PayRequest account? > > No. Anyone with a compatible Solana wallet can send a P2P payment. The **Log in → Pay faster** feature is optional — it just pre-fills their details if they happen to have a PayRequest account. > [accordion] Do I need the Solana USDC payment option enabled too? > > No. P2P payments are separate from the standard Solana checkout (which routes through the pump.fun system). Connecting your Solana wallet in Provider Settings is all that's needed for P2P. > [accordion] What if the sender doesn't have a Solana wallet? > > If no compatible wallet is detected, the sender is directed to Phantom.app to download one. Phantom is free on all major browsers and mobile platforms. > [accordion] Can senders use MetaMask? > > Yes — newer MetaMask versions support Solana natively via Wallet Standard. Alternatively, install the **Solflare Snap** from inside MetaMask (Snaps → Search "Solflare") for full Solana support in one click. > [accordion] Is there a minimum or maximum amount? > > The minimum is **0.01 USDC**. There's no hard maximum, but very large amounts are subject to Solana network rules. > [accordion] Where do I enter the amount? > > Directly in the P2P card at the top of the page — it has its own large amount field. The standard payment form below it is separate. > [accordion] Can I turn off P2P payments without disconnecting my wallet? > > Not yet — if your Solana wallet is connected, the P2P card appears automatically. Disconnect your Solana wallet in **Provider Settings → Solana Wallet (P2P)** to remove it. This only affects P2P; your Base USDC wallet (if connected separately) is unaffected. > [accordion] Do P2P payments show up in my revenue stats? > > P2P transfers are tracked in the Wallet Dashboard under P2P Transfers, separately from your main transaction history. They don't count toward subscription or invoice revenue analytics. > [accordion] Does connecting a Solana wallet affect my Base USDC payments? > > No. Your **Solana wallet** (for P2P) and your **Base wallet** (for USDC on Base payments) are stored separately in Provider Settings. Connecting one doesn't affect the other. ## Next Steps > [card] [Connect Your Wallet](/business-settings/business-details) > > Set up your Solana wallet in Provider Settings to enable P2P payments on your page. > [card] [Crypto Page Themes](/shop-and-checkout/crypto-page-themes) > > Give your page a Solana or Crypto Native visual theme to match your Web3 brand. > [card] [Solana USDC Payments](/payment-processing/crypto-payments) > > Accept USDC payments through the full checkout flow with invoice tracking. > [card] [Supported Wallets (Base)](/payment-processing/crypto-supported-wallets) > > See which wallets work for Base USDC payments and how to connect them. # Pay by Bank Source: https://docs.payreque.st/payment-processing/pay-by-bank Accept a first bank payment through Mollie and collect subscription renewals with SEPA Direct Debit Pay by Bank lets customers pay from their bank account without entering card details. PayRequest redirects them to Mollie to choose their bank and authorize the payment in their banking app or online banking. For an automatically collected euro subscription, the first payment establishes a **SEPA Direct Debit mandate**. Later payments are collected through that mandate. > [!NOTE] > > Pay by Bank is the first-payment method. Subscription renewals use SEPA Direct Debit, with its usual processing times and refund rights. This is not recurring open banking or Variable Recurring Payments (VRP). ## Enable Pay by Bank **1. Connect your Mollie account** Open PayRequest's payment-provider settings and connect your own Mollie account. See [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers). **2. Activate the methods at Mollie** Enable **Pay by Bank** on the Mollie website profile used by PayRequest. For automatic euro subscriptions, also enable **SEPA Direct Debit**. Availability depends on your Mollie account and profile. **3. Check your PayRequest method selection** If you selected specific payment methods in PayRequest, include **Pay by Bank** in that selection. Activating a method at Mollie does not override your PayRequest selection. **4. Use an automatic subscription checkout** Share your recurring product's PayRequest Page or portal product link. Eligible customers can choose **Pay by Bank** when setting up automatic payments. Manual invoice billing does not establish a mandate; review the product and shop's manual-payment settings if checkout offers only a one-time payment. ## What the customer does 1. Reviews the product, amount and recurring terms in PayRequest. 2. Chooses **Pay by Bank** and continues to Mollie. 3. Selects their bank on the Mollie payment page. 4. Authorizes the first payment in their bank's app or online banking. 5. Returns to PayRequest to see the payment status. The customer chooses the bank **after leaving PayRequest**. Their billing-address country does not automatically select a bank: someone may have a bank account in a different country. The checkout language changes the interface text, not the payment method itself. ## Supported payments | Payment | How it works | | - | - | | One-time payment | Customer authorizes the bank payment at Mollie. EUR and GBP are supported where available. | | First automatic subscription payment | PayRequest supports EUR Pay by Bank payments that establish a SEPA mandate. | | Subscription renewal | PayRequest collects through the saved SEPA Direct Debit mandate. The customer does not select their bank again each month. | Bank availability can vary. Some business bank accounts are not supported. See [Mollie's Pay by Bank documentation](https://docs.mollie.com/docs/pay-by-bank) for current coverage and limitations. ## Pending payments and returns from the bank > [!WARNING] > > Returning from the bank does not prove that payment is complete. A Pay by Bank payment can remain **pending** while Mollie waits for the funds. PayRequest confirms payment after Mollie reports it as paid. Some banks may take longer than others. If the bank or bank-connection provider displays a blank page or an error after authorization, check the order and payment status before starting another payment. A payment can still succeed despite a return-page error. If the status is unclear, contact the merchant with your order number; the merchant can verify the payment in Mollie. ## Manage future payments The mandate is linked to the customer's subscription. Use [Managing Mandates](/subscriptions/managing-mandates) to inspect its status and [Payment Methods for Subscriptions](/subscriptions/payment-methods) to manage collection. Canceling a subscription and refunding its first payment are separate actions. Customers can use the available [self-service cancellation options](/subscriptions/customer-self-service) to stop future billing according to the product's cancellation settings. ## Troubleshooting > [accordion] Why is Pay by Bank missing? > > Check Mollie activation, your PayRequest method selection, and SEPA Direct Debit activation for subscriptions. The amount, currency and checkout's collection settings must be suitable. The automatic subscription flow supports EUR. > [accordion] Why do I see a one-time payment instead of mandate options? > > Your shop or product may permit manual subscription billing. That checkout collects a separate payment for the invoice rather than establishing automatic renewal payments. Review [subscription payment methods](/subscriptions/payment-methods). > [accordion] Are renewals also instant bank payments? > > No. Only the first payment uses Pay by Bank. Renewals are SEPA Direct Debit payments and may remain pending while collection is processed. > [accordion] Do I need to choose banks or embed a bank picker in PayRequest? > > No. Mollie handles bank selection and authorization on its payment page. # Payment Forms Source: https://docs.payreque.st/payment-processing/payment-forms Collect answers, product selections, private files and payments together on your branded PayRequest Payment Page. Payment Forms let customers answer your questions and pay through one shared link. Use a fixed amount or let customers choose existing products, with your Payment Page branding and available payment methods. > [card] [Create a payment form](https://payrequest.app/payment-forms/create) > > Start with a template or build your own form. ## Before you publish You can prepare a private draft first. Publishing requires an active Payment Page and an available connected payment provider for the form's currency. Forms work with eligible **PayPal, Mollie, Stripe, Revolut and Payoneer** connections. Availability depends on your account, provider and currency. You do not need to connect PayPal specifically. When there is one eligible connection, customers do not need to choose a provider. Your normal PayRequest plan fees and payment-provider fees apply. ## Create and publish a form **1. Choose a template or start from scratch** Open **Payment Forms → Create payment form**. Search the template library or filter by events and courses, orders, services or contributions. Select a card, then choose **Use template**. You can also start entering your own offer without applying a template. **2. Describe your offer** Enter a title and description. Optionally upload a JPG, PNG or WebP cover image, up to 5 MB. The cover is separate from files customers upload as answers. **3. Choose your pricing** Select **Fixed amount** or **Existing products**, then choose a supported currency and review the tax settings. All paid options and the final total are calculated by PayRequest. **4. Add questions and availability** Add the details you need, optional paid extras, conditional questions or customer uploads. Add terms, a closing date or a booking limit if appropriate. **5. Save and publish** **Save draft** keeps your changes private. **Publish** makes the form available through your Payment Page. Review and publish later draft changes explicitly. ## Available templates Templates configure editable questions; they do not automatically create products, reserve appointments or establish a subscription. | Template | What it prepares | | - | - | | Workshop | Participant name, experience, learning goals and accessibility requirements | | Event registration | Participant and company details, dietary or accessibility requirements | | Service request | Request details, preferred delivery date and an optional briefing file | | Personalized order | Personalization text, a logo or reference image and additional instructions | | Sponsorship | Organization details, public sponsor name and an optional logo | | Product order | Existing-product mode, order instructions and company details; select your products before saving | | Consultation payment | Discussion goals, a preferred date/time and an optional reference file | | Course registration | Student details, experience, learning goals and accessibility requirements | | Photography request | Photography type, preferred date/location, shoot briefing and an optional reference image | | Fixed contribution | An optional public display name and message, with an amount set by you | | Coaching session | Coaching goals, a preferred date/time and relevant background; arrange the session separately | | Design brief | Design project details, a preferred delivery date and an optional briefing or reference file | | Translation request | Required source and target languages, a required document upload and optional instructions; agree the fee separately | | Repair assessment | Item/model, problem description and an optional photo; charge an assessment fee and quote repairs separately | | Catering request | Event date/location, guest count, dietary requirements and instructions; agree the amount and confirm availability separately | | Webinar registration | Participant name, company and questions for the speaker | The library has sixteen illustrated cards, a search field and category filters. Scroll within the gallery to see more cards; the apply button stays below it. Filtering does not discard your selected template. > [!NOTE] > > Preferred dates are requests, not confirmed bookings. Fixed contributions use a seller-set amount. Payment Forms currently do not provide security-deposit authorizations, recurring subscriptions or customer-chosen amounts. Use the appropriate native PayRequest flow for those needs. ## Fixed amounts and paid options With **Fixed amount**, set a base price of at least 0.50 in your selected currency. The base price and paid question options include the chosen form tax rate. You can add up to 20 questions using short answers, long answers, email, choice lists, checkboxes and file uploads. A choice or checkbox can add a fixed amount. Mark answers as required where needed. For example, an event form can collect a participant's details, offer standard or priority registration, and add a paid extra. Customers see an updated total before paying. ## Sell existing products Choose **Existing products** to include up to ten compatible active, one-time products in the same currency. * Let customers choose exactly one product or select multiple products. * In multiple-product mode, mark products that must always be included. * Set permitted quantities for products that support quantity selection. * Keep each product's existing price, tax settings and supported delivery. There is no additional base charge in product mode. The form tax rate applies to paid question options; product tax settings remain authoritative. A one-product form can use that product's image when you have not uploaded a form cover. Bookings, subscriptions, physical shipping, limited stock, Discord provisioning and products with their own checkout options use their existing checkout flows. They cannot be added simply by choosing a template. If product pricing changes while someone has the form open, they may need to reload before paying. For supported digital products, verified payment creates the native product order and starts the existing delivery flow. A completed form alone does not grant downloads or access. ## Show questions conditionally For a dependent question, choose **Show this question when**, select an earlier choice list or checkbox, and choose the matching answer. For example, show a personalization text field only when a customer selects a personalization extra. Hidden questions are not required and their paid options are not charged. Conditions must reference earlier questions. If you remove or reorder a source question, correct its dependent conditions before saving. ## Receive private customer files Add a **File upload** question for a customer's logo, briefing, photo or reference document. | Limit | Supported value | | - | - | | File formats | JPG/JPEG, PNG, WebP, PDF and TXT | | Per file | Up to 10 MB | | Per submission | Up to 20 MB total | | Upload questions | Up to three per form | | Recorded customer uploads | Up to 1 GB per account owner | Files are private. The account owner downloads them from the form's submissions dashboard; they do not receive public image URLs and are not sent as email attachments. File answers can also be required or conditional. ## Set a booking limit or closing date Under **Availability**, optionally configure: * **Maximum paid bookings** to limit the number of checkouts. * **Close for new payments at** to set a closing date and time in **UTC**. * **Closed message** to explain why new payments are no longer accepted. Each checkout reserves **one booking**, regardless of product quantity. Pending or uncertain payments keep their place until the final payment outcome is known. Recorded failed, canceled, expired or refunded payments release it. > [!WARNING] > > This is a form-wide checkout limit, not per-product inventory or a count of all attendees in a group booking. Use separate forms or the appropriate native product flow when capacities differ. A closed form remains readable, but its checkout is disabled. Existing payment attempts can still complete after the closing time. Unpublishing also stops new checkouts without deleting existing submissions or canceling payments already started. ## Share your form Published forms use your Payment Page address: ```text theme={null} https://payrequest.me/yourhandle/forms/your-form ``` Your avatar, banner and Page branding remain visible. Customers can select their language in the header. Desktop separates the offer from the scrollable form; mobile stacks the content. Share the link directly or use **Send to customer** to email a published form to an existing customer in your account. Sending a link does not create a paid order. Older UUID-based form links redirect to the current readable address. ## Checkout and payment confirmation Customers see selectable payment methods supported by the connected provider. Methods depend on the merchant account, currency, amount and, where applicable, the customer's device. Some methods require additional billing details. The standard payment button starts the provider's secure checkout; PayPal uses its PayPal payment flow. Submitting answers, returning from checkout or receiving a customer record is not proof of payment. PayRequest confirms the provider's payment status before granting paid delivery. If a payment is still being checked, customers should wait for confirmation rather than paying again. ## Manage submissions and export Open a form's submissions to: * Filter **All**, **Paid**, **Open**, **Failed** or **Refunded** payments. * See confirmed-paid totals grouped by currency. * Review answers, selected products, paid options and accepted terms. * Download private customer files. * See reserved bookings when a capacity limit is configured. * Inspect linked product-order delivery and open the native order. * Export a CSV using the selected payment-status filter. A submission marked **Not confirmed** is not a paid sale. Product delivery follows the existing order flow; some services or manual deliveries need further action from you. ## Related guides * [Payment Pages](https://docs.payreque.st/payment-processing/payment-pages) * [Connect a payment provider](https://docs.payreque.st/payment-processing/setting-up-payment-providers) * [Smart Links](https://docs.payreque.st/payment-processing/smart-links) * [Security deposits](https://docs.payreque.st/payment-processing/security-deposits) # Payment Methods Overview Source: https://docs.payreque.st/payment-processing/payment-methods-overview Comprehensive guide to all payment methods available in PayRequest, including European and international options # Payment Methods Overview 💳 PayRequest supports a comprehensive range of payment methods to accommodate customers worldwide. From European-focused solutions like iDEAL and SEPA Direct Debit to international options like credit cards and digital wallets, we've got you covered. > [!NOTE] > > **Multi-Provider Support**: PayRequest integrates with multiple payment providers, giving you flexibility and redundancy for your payment processing needs. ## Currencies and Payment Method Availability PayRequest offers 139 Stripe presentment currencies in its currency selectors. A currency choice and an available payment method are different: Stripe checks the connected account, currency, customer, and payment method before offering a payment option. A card payment and a local bank method may support different currencies. For a product purchase, Stripe checkout starts with the product's saved currency. Adaptive Pricing may offer the buyer a localized currency; your payout currency is configured separately at Stripe. Other providers retain their own currency restrictions. See [Choosing your Stripe currency](/payment-processing/connect-stripe#choosing-your-currency) and [Creating products](/products-and-pricing/creating-products#choosing-a-product-currency). ## 🌍 Payment Method Categories PayRequest organizes payment methods into logical categories to help you choose the best options for your customers: > [card] 🇪🇺 European Methods > > **Regional Specialists** > > * iDEAL (Netherlands) > * Bancontact (Belgium) > * SEPA Direct Debit (EU-wide) > * Sofort (Germany) > * Giropay (Germany) > [card] 🌎 International Methods > > **Global Solutions** > > * Credit/Debit Cards (Visa, Mastercard, Amex) > * PayPal > * Revolut Pay > * Apple Pay > * Google Pay > * Bank Transfers ## 💳 Credit and Debit Cards The most universally accepted payment method, perfect for international customers. ### Supported Card Types > [tab] Major Card Networks > > **Visa** > > * Global acceptance > * Debit and credit variants > * 3D Secure authentication > * Instant payment processing > > **Mastercard** > > * Worldwide recognition > * SecureCode protection > * Corporate card support > * Real-time fraud detection > > **American Express** > > * Premium card network > * Enhanced security features > * Corporate travel cards > * Higher interchange fees > [tab] Regional Cards > > **Maestro** > > * European debit card standard > * PIN-based authentication > * Lower processing fees > * Bank account direct debit > > **V PAY** > > * Visa's European debit solution > * Chip and PIN security > * EMV compliance > * Cost-effective for merchants ### Card Processing Features > [card] Security > > * 3D Secure authentication > * PCI DSS compliance > * Fraud detection algorithms > * Tokenization support > [card] User Experience > > * One-click checkout > * Saved payment methods > * Mobile-optimized flow > * Guest checkout options > [card] Business Tools > > * Real-time processing > * Automatic retries > * Chargeback protection > * Detailed reporting ## 🏦 European Bank Payment Methods Optimized for European customers with local banking preferences and lower processing costs. ### iDEAL (Netherlands) > [accordion] 🇳🇱 iDEAL - Netherlands' Leading Payment Method > > **Market Dominance**: Used by 60%+ of Dutch online shoppers > **Bank Coverage**: All major Dutch banks supported > **Security**: Bank-level authentication and authorization > **Customer Experience**: Direct bank-to-bank transfer with instant confirmation > > **How it Works:** > > 1. Customer selects iDEAL at checkout > 2. Chooses their bank from a list > 3. Redirected to secure bank environment > 4. Authenticates using bank credentials > 5. Confirms payment amount and details > 6. Returns to merchant with payment confirmation > > **Business Benefits:** > > * Lower transaction fees than cards > * Guaranteed payment (no chargebacks) > * Instant payment confirmation > * High customer trust and adoption > * No setup fees or monthly costs > [accordion] 💰 iDEAL Pricing and Costs > > **Transaction Fees**: Typically €0.29 per transaction > **No Percentage Fee**: Fixed cost regardless of amount > **No Setup Costs**: Free to activate through PayRequest > **Volume Discounts**: Available for high-transaction merchants > > **Cost Comparison Example:** > > * €100 payment via iDEAL: €0.29 fee (0.29%) > * €100 payment via credit card: €2.50+ fee (2.5%+) > * €1000 payment via iDEAL: €0.29 fee (0.029%) ### Bancontact (Belgium) > [accordion] 🇧🇪 Bancontact - Belgium's National Payment Scheme > > **Market Share**: 70%+ of Belgian online payments > **Bank Integration**: All Belgian banks participate > **Mobile App**: Bancontact by Payconiq for mobile payments > **QR Code Support**: In-store and online QR payments > > **Customer Flow:** > > 1. Select Bancontact at checkout > 2. Enter card number or use mobile app > 3. Authenticate with card reader or mobile PIN > 4. Confirm payment in banking environment > 5. Instant payment confirmation > > **Advantages:** > > * Trusted by Belgian consumers > * Lower costs than international cards > * Instant payment processing > * Mobile-first innovation > * Fraud protection through bank security ### SEPA Direct Debit > [accordion] 🏦 SEPA Direct Debit - European Recurring Payments > > **Coverage**: All 36 SEPA countries (EU + EEA + others) > **Use Cases**: Perfect for subscriptions and recurring billing > **Mandate System**: Customer authorization for automatic payments > **Settlement**: T+1 settlement (next business day) > > **SEPA Direct Debit Process:** > > 1. Customer provides mandate authorization > 2. Merchant collects signed mandate > 3. First payment processed with advance notice > 4. Subsequent payments automatically debited > 5. Customer retains refund rights (8 weeks) > > **Business Benefits:** > > * Lowest cost payment method in Europe > * Automatic recurring billing > * High success rates > * Predictable cash flow > * Reduced payment friction for customers > > **Requirements:** > > * Valid SEPA mandate from customer > * 14-day advance notice for first payment > * 5-day notice for subsequent payments > * Creditor identifier (provided by PayRequest) > [accordion] 📋 SEPA Mandate Management > > **Digital Mandates**: Electronic signature collection > **Mandate Storage**: Secure, compliant mandate archiving > **Customer Communication**: Automated mandate notifications > **Compliance**: Full SEPA regulation adherence > > **Mandate Types:** > > * **One-off**: Single payment authorization > * **Recurring**: Multiple payment authorization > * **Business-to-Business**: B2B specific mandates with shorter refund periods > > **PayRequest Automation:** > > * Automatic mandate creation during checkout > * Digital signature collection > * Mandate status tracking and management > * Automatic pre-notification emails > * Failed payment retry logic ## 🌐 International Payment Methods Reach customers worldwide with globally recognized payment solutions. ### Digital Wallets > [card] PayPal > > **Global Reach**: 400+ million active users > **Buyer Protection**: Built-in fraud protection > **Express Checkout**: Skip form filling > **Currency Support**: 25+ currencies > **Mobile Optimized**: App and mobile web > [card] [Apple Pay](https://docs.payreque.st/payment-methods/apple-pay) > > Offer Apple Pay through your connected Mollie account when cards and Apple Pay are enabled on its website profile. > > Customers using supported mobile or desktop browsers continue to Mollie's secure checkout. Browser and device availability determine whether the option is shown. > [card] Google Pay > > **Android Native**: Built into Android devices > **Chrome Integration**: Browser-based payments > **Contactless**: NFC payment support > **Security**: Tokenized transactions > **Global Availability**: 40+ countries > [card] Microsoft Pay > > **Windows Integration**: Native Windows 10/11 > **Edge Browser**: Seamless web payments > **Xbox Support**: Gaming platform integration > **Enterprise Focus**: B2B payment solutions > **Security**: Enterprise-grade protection ### Bank Transfers > [accordion] 🏛️ Automatic Bank Transfer Matching > > **Zero Fee Payments**: Accept bank transfers with no PayRequest transaction fees > **Automatic Matching**: Ponto integration matches incoming payments automatically > **Unique References**: Each payment gets a unique reference code (PAY-12345) > **Instant Recognition**: Payments matched within minutes of arriving in your bank > > **How It Works:** > > 1. Customer selects Bank Transfer at checkout > 2. Customer sees your IBAN and unique reference code > 3. Customer transfers exact amount via their bank > 4. Ponto syncs your bank transactions automatically > 5. PayRequest matches the reference and marks invoice as paid > > **Requirements:** > > * Ponto bank connection (Settings → Ponto) > * Business bank account with Ponto-supported bank > * Bank Transfer payment method enabled > > **Use Cases:** > > * High-value B2B transactions > * Cost-conscious customers (0% fees) > * Customers preferring bank-direct payments > * Markets with strong bank transfer culture (Netherlands, Belgium, Germany) > > **PayRequest Features:** > > * Automatic bank details display with copy buttons > * Unique payment reference generation > * Automatic payment matching via Ponto > * Real-time bank transaction syncing > * No manual reconciliation needed > > [Learn more about Bank Transfer Payments →](/payment-processing/bank-transfer) > [accordion] 🌐 International Bank Transfers > > **SWIFT Network**: International bank transfers for global payments > **Manual Process**: Customer-initiated transfers without automatic matching > **Settlement Time**: 3-5 business days for international transfers > > **Use Cases:** > > * International customers outside SEPA zone > * High-value cross-border transactions > * Customers without access to other payment methods ## 🚀 Emerging Payment Methods Stay ahead with next-generation payment technologies. ### Buy Now, Pay Later (BNPL) > [card] [Klarna](https://docs.payreque.st/payment-methods/klarna) > > Offer Klarna when it is enabled and eligible on your connected Mollie profile. > > Buyers complete their name, email and billing address before continuing. The payment options and approval depend on Klarna, the buyer, country, currency and amount. > [card] Afterpay > > **4 Installments**: Split into equal payments > **No Interest**: Fee-free for on-time payments > **Instant Approval**: Real-time credit decisions > **Consumer Friendly**: Transparent fee structure > **Merchant Protection**: Payment guarantee ### Cryptocurrency PayRequest supports **USDC stablecoin payments** on Base (Coinbase's L2) and Solana — automatic on-chain settlement, near-zero fees, no "I have paid" confirmation required. > [card] [Base USDC](/payment-processing/crypto-payments) > > Coinbase's Base L2 — 2-second finality, MetaMask / Coinbase Wallet > [card] [Solana USDC](/payment-processing/solana-pay) > > Solana Pay QR codes — sub-cent fees, Phantom / Backpack ### 26+ Digital Wallets & P2P Platforms Accept payments from regional wallets worldwide — Revolut, Wise, Cash App, GCash, UPI, Pix, M-Pesa, WeChat Pay, and 18 more. Customers pay in their own app and confirm with "I have paid." > [card] [See all supported digital wallets →](/payment-processing/digital-wallets) > > Europe · Americas · South Asia · SE & East Asia · Africa · Canada ## 📊 Payment Method Comparison Choose the right payment methods for your business model: > [tab] Cost Comparison > > | Payment Method | Transaction Fee | Percentage Fee | Best For | > | - | - | - | - | > | iDEAL | €0.29 | 0% | Dutch customers, any amount | > | Bancontact | €0.35 | 0% | Belgian customers | > | SEPA Direct Debit | €0.15 | 0% | Recurring payments, EU | > | Credit Cards | €0.25 | 2.9% | International customers | > | PayPal | €0.35 | 2.9% | Global reach, buyer protection | > | Bank Transfer | €0.00 | 0% | High-value, B2B payments | > [tab] Geographic Reach > > **European Focus:** > > * iDEAL: Netherlands (essential) > * Bancontact: Belgium (essential) > * SEPA: All EU countries > * Sofort: Germany, Austria, Switzerland > > **Global Coverage:** > > * Credit Cards: Worldwide > * PayPal: 200+ countries > * Apple Pay: 70+ countries > * Google Pay: 40+ countries > > **Emerging Markets:** > > * Local payment methods vary by country > * Research local preferences > * Consider regulatory requirements > [tab] Settlement Times > > **Instant Settlement:** > > * Credit cards (authorization) > * Digital wallets > * Real-time bank transfers > > **Next Day Settlement:** > > * iDEAL, Bancontact > * SEPA Direct Debit > * Most local payment methods > > **Delayed Settlement:** > > * International bank transfers (3-5 days) > * Some BNPL providers (30+ days) > * Cryptocurrency (varies) ## 🎯 Choosing the Right Payment Methods ### For European Businesses **1. Start with Local Methods** Enable iDEAL for Netherlands, Bancontact for Belgium, and SEPA for EU-wide coverage **2. Add International Cards** Support Visa and Mastercard for international customers and tourists **3. Consider Digital Wallets** Add PayPal and Apple Pay for mobile-first customers **4. Enable SEPA for Subscriptions** Set up SEPA Direct Debit for recurring billing and subscription models ### For Global Businesses **1. Universal Card Support** Enable all major card networks (Visa, Mastercard, Amex) **2. Digital Wallet Integration** Support PayPal, Apple Pay, and Google Pay for broader reach **3. Regional Specialists** Research and add local payment methods for your target markets **4. Alternative Methods** Consider BNPL and bank transfers for specific customer segments ## 🔧 Payment Method Configuration Configure payment methods through your PayRequest dashboard: > [accordion] ⚙️ Setup Process > > **Navigation**: Settings → Payment Providers → \[Select Provider] > > **Configuration Steps:** > > 1. Connect your payment provider account > 2. Enable desired payment methods > 3. Configure method-specific settings > 4. Test payment flows > 5. Monitor performance and adjust > > **Testing Requirements:** > > * Process test transactions > * Verify webhook delivery > * Test mobile payment flows > * Validate error handling > * Confirm settlement processes > [accordion] 📈 Performance Monitoring > > **Key Metrics:** > > * Payment success rates by method > * Average transaction values > * Customer preference trends > * Geographic usage patterns > * Cost analysis and optimization > > **PayRequest Analytics:** > > * Real-time payment method performance > * Customer payment preference insights > * Revenue attribution by payment type > * Failed payment analysis > * Conversion rate optimization data ## 🚨 Security and Compliance All payment methods in PayRequest maintain the highest security standards: > [card] PCI Compliance > > * PCI DSS Level 1 certification > * Secure card data handling > * Tokenization for stored data > * Regular security audits > [card] Fraud Protection > > * Real-time fraud detection > * Machine learning algorithms > * Risk scoring systems > * Merchant protection programs > [card] Data Protection > > * GDPR compliance > * Data encryption in transit > * Secure data storage > * Privacy by design ## 📞 Need Help with Payment Methods? > [card] Setup Assistance > > Get help configuring payment methods for your specific business needs > [card] Provider Support > > Direct support for payment provider integration and troubleshooting > [card] Optimization Consulting > > Analyze and optimize your payment method mix for better conversion ## 🎓 Next Steps > [card] [Set Up Payment Providers](/payment-processing/setting-up-payment-providers) > > Connect Mollie, Stripe, PayPal, Payoneer, or Revolut Pay to start accepting payments > [card] [Create Payment Forms](/payment-processing/payment-forms) > > Build custom payment forms for specific use cases and campaigns > [card] [QR Code Payments](/payment-processing/qr-code-payments) > > Enable contactless payments with QR codes for in-person transactions > [card] [Handle Chargebacks](/payment-processing/handling-chargebacks) > > Learn to manage and prevent payment disputes effectively *** > [!TIP] > > **Pro Tip**: Start with 2-3 payment methods that match your customer base, then gradually add more based on customer requests and geographic expansion. Monitor performance metrics to optimize your payment method mix for maximum conversion and minimum costs. # Payment Page Dynamic Links Source: https://docs.payreque.st/payment-processing/payment-page-dynamic-links Create powerful pre-filled payment links with dynamic parameters for seamless customer experiences ## Overview Payment Page Dynamic Links allow you to create customized payment URLs with pre-filled information, making it easier for your customers to complete payments. These links can include customer details, product information, amounts, and even custom fields - all automatically populated when your customer clicks the link. > [!TIP] > > Dynamic links are perfect for email campaigns, invoices, customer portals, and any situation where you want to streamline the payment process. ## Base URL Structure Your payment page is accessible via a clean, branded URL: ``` https://payrequest.me/{your-handle} ``` **Example:** ``` https://payrequest.me/acme-corp ``` > [!NOTE] > > You can customize your handle in Settings → Payment Page. If you haven't set a handle, your business name is used by default. ## Crypto Wallet Address Links Besides query-parameter links to your main payment page, PayRequest also generates dedicated **path-based links** for sharing a connected crypto wallet address directly — useful for X/social giveaways, tip jars, or quick one-off requests. ``` https://payrequest.me/{your-handle}/sol https://payrequest.me/{your-handle}/btc https://payrequest.me/{your-handle}/eth https://payrequest.me/{your-handle}/10usd/sol ``` These pages use the same branding (avatar, tagline, social links, accent color) as your main payment page, but show a QR code and a copy-to-clipboard address field instead of a payment form. See [Share Your Crypto Address](/payment-processing/share-wallet-address) for the full guide. ## Language Support ### Language Switcher (Interactive) All payment pages now include a **language switcher dropdown** in the top-right corner, allowing customers to switch between languages with a single click. **Features:** * **21 languages available**: English 🇬🇧, Nederlands 🇳🇱, Deutsch 🇩🇪, Français 🇫🇷, Español 🇪🇸, Italiano 🇮🇹, Português 🇵🇹, Polski 🇵🇱, Svenska 🇸🇪, Dansk 🇩🇰, Norsk 🇳🇴, Suomi 🇫🇮, Ελληνικά 🇬🇷, Čeština 🇨🇿, Română 🇷🇴, Magyar 🇭🇺, Türkçe 🇹🇷, Русский 🇷🇺, 中文 🇨🇳, 日本語 🇯🇵, and Українська 🇺🇦 * Flag emoji indicators for easy recognition * Preserves all URL parameters when switching (invoice numbers, product IDs, etc.) * Automatically updates all text, buttons, and labels **What customers see:** * Fixed position button showing the current language flag * Dropdown menu listing all 21 language options * Instant language switching without losing payment context > [!TIP] > > The language switcher is especially useful for international businesses or when customers share payment links with others who prefer a different language. ### Language URL Parameter You can also set the language via URL parameter using any of the 21 supported language codes: | Parameter | Language | Example | | - | - | - | | `?lang=en` | English (default) | `https://payrequest.me/acme-corp?lang=en` | | `?lang=nl` | Dutch | `https://payrequest.me/acme-corp?lang=nl` | | `?lang=de` | German | `https://payrequest.me/acme-corp?lang=de` | | `?lang=fr` | French | `https://payrequest.me/acme-corp?lang=fr` | | `?lang=es` | Spanish | `https://payrequest.me/acme-corp?lang=es` | > [!NOTE] > > Any of the 21 supported codes work the same way: `en`, `nl`, `de`, `fr`, `es`, `it`, `pt`, `pl`, `sv`, `da`, `no`, `fi`, `el`, `cs`, `ro`, `hu`, `tr`, `ru`, `zh`, `ja`, `uk`. **Example:** ``` https://payrequest.me/acme-corp?invoice=1505&lang=nl ``` All payment page text, buttons, and labels will automatically translate based on the selected language. The language switcher dropdown will reflect the currently selected language and allow customers to change it if needed. ## Query Parameter Format (Recommended) The query parameter format provides maximum flexibility and readability. **Basic Structure:** ``` https://payrequest.me/{handle}?parameter=value¶meter2=value2 ``` ### Supported Parameters | Parameter | Type | Description | Example | | - | - | - | - | | `product` | integer | Product ID to display | `?product=1814` | | `amount` | decimal | Payment amount (EUR) | `?amount=25.50` | | `method` | string | Pre-select payment method | `?method=ideal` | | `name` | string | Customer name | `?name=John%20Doe` | | `email` | string | Customer email | `?email=john@example.com` | | `address` | string | Street address | `?address=Main%20Street%20123` | | `city` | string | City name | `?city=Amsterdam` | | `postal` | string | Postal/ZIP code | `?postal=1012AB` | | `notes` | string | Payment notes | `?notes=Monthly%20subscription` | | `lang` | string | Language (21 supported codes) | `?lang=nl` | | `customfield_*` | string | Custom field value | `?customfield_size=large` | | `disabled` | boolean | Lock custom fields (read-only) | `?disabled=true` | > [!NOTE] > > When a `product` parameter is provided, the amount is automatically set to the product price (including setup fees and custom field markups) and cannot be changed by the customer. ## Common Use Cases ### 1. Product Payment Link Direct customers to pay for a specific product: ``` https://payrequest.me/acme-corp?product=1814 ``` **What happens:** * Product details are displayed (name, description, image) * Price is automatically set (including setup fees if applicable) * Amount field is hidden (customer cannot change price) * Recurring badge shown for subscription products ### 2. Pre-filled Customer Details Send personalized payment links with customer information already filled in: ``` https://payrequest.me/acme-corp?product=1814&name=John%20Doe&email=john@example.com ``` **Benefits:** * Faster checkout experience * Reduced data entry errors * Professional customer experience > [!TIP] > > Enable "Readonly dynamic fields" in Settings → Payment Page to prevent customers from editing pre-filled information. ### 3. Complete Payment Request Create a fully pre-configured payment link: ``` https://payrequest.me/acme-corp?product=1814&name=John%20Doe&email=john@example.com&address=Main%20Street%20123&city=Amsterdam&postal=1097CR&lang=nl ``` **Includes:** * Product information * Customer details * Address information * Language preference (Dutch) ### 4. Custom Amount Payment For flexible payment amounts without a specific product: ``` https://payrequest.me/acme-corp?amount=150.00&name=John%20Doe&email=john@example.com&method=ideal ``` **Use cases:** * Donation requests * Partial payments * Flexible invoicing * Service deposits ### 5. Custom Fields Integration Pass additional information using custom fields: ``` https://payrequest.me/acme-corp?product=1814&customfield_productcode=PROD-2024&customfield_size=large&customfield_color=blue ``` **Custom field format:** * Prefix: `customfield_` * Field name: Any alphanumeric name * Example: `customfield_reference`, `customfield_order_number` **Display:** Custom fields appear in the "Additional Information" section on the payment page and are stored with the order. ### 6. Per-Unit Pricing with Number Fields For products with quantity-based pricing (like rental days or seats): ``` https://payrequest.me/acme-corp?product=1880&customfield_days=5&disabled=true ``` **How per-unit pricing works:** 1. Your product has a number field with "per unit markup" configured (e.g., €16/day) 2. Pass the quantity via URL: `customfield_days=5` 3. Total markup is calculated automatically: 5 × €16 = €80 **Price breakdown displayed:** * Base product price: €100.00 * Days (5 × €16.00): +€80.00 * **Total: €180.00** > [!TIP] > > Add `&disabled=true` to lock the custom field values, preventing customers from changing quantities you've pre-set. ### 7. Locked Custom Fields Pre-fill custom fields and prevent customers from changing them: ``` https://payrequest.me/acme-corp?product=1880&customfield_days=3&disabled=true ``` **Use cases:** * Quotes with specific quantities * Pre-configured packages * Invoices with fixed specifications **What happens:** * Custom field inputs are grayed out * Values are visible but cannot be changed * Price is calculated based on pre-filled values ## Setup Fees Display When linking to a product with a setup fee: ``` https://payrequest.me/acme-corp?product=1814 ``` **Automatic display:** * Product price: €34.50/month * Setup fee: €100.00 (with custom name like "Borg" or "Installation") * **Total Today:** €134.50 > [!NOTE] > > Setup fees are automatically included in the payment amount. The customer pays both the recurring price and setup fee in the first payment. ## Recurring Products & Mandates For subscription products with recurring payments: ``` https://payrequest.me/acme-corp?product=1859 ``` **Automatic behavior:** 1. Payment page shows "Recurring" badge 2. Customer pays first installment + setup fee 3. SEPA mandate is automatically created during payment 4. Future payments process automatically using the mandate 5. Subscription becomes active after successful mandate creation > [!NOTE] > > This only works with payment methods that support mandates (iDEAL, SEPA Direct Debit, credit card). ## Payment Recovery When a payment is interrupted (cancelled, failed, or browser closed), customers can return to complete their payment without losing their selections. ### How It Works 1. Customer fills in custom fields and starts payment 2. Payment is interrupted (any reason) 3. Customer receives link: `https://payrequest.me/yourhandle?invoice=1234` 4. **All custom field values are restored** from the original order 5. Customer can complete payment immediately **Retained Information:** * All custom field selections (dropdowns, numbers, toggles) * Per-unit quantities and calculated markups * Customer name and email > [!NOTE] > > This only works when returning via the invoice link (`?invoice=`). If customers visit the product page directly, they'll need to re-enter their selections. ### Cancelled Invoices If you've cancelled an invoice, customers will see a clear message and cannot make a payment: * Red warning: "This invoice has been cancelled" * Invoice items displayed with strikethrough * Payment form is hidden This prevents confusion and accidental payments on orders you've already cancelled. ## Read-Only Fields Control whether customers can edit pre-filled information: **Setting Location:** Settings → Payment Page → Options → "Readonly dynamic fields" **When enabled:** * Pre-filled fields are locked (grayed out) * Customer cannot modify name, email, or other pre-filled data * Ideal for personalized payment requests **Example with read-only enabled:** ``` https://payrequest.me/acme-corp?product=1814&name=John%20Doe&email=john@example.com ``` → Name and email fields are visible but cannot be changed ## Payment Page Settings Configure payment page behavior in Settings → Payment Page: ### Display Options | Setting | Description | Impact on Links | | - | - | - | | **Show customer login** | Display login prompt | Customers can log in to auto-fill their saved details | | **Show order notes** | Display notes field | Customers can add custom notes to payments | | **Readonly dynamic fields** | Lock pre-filled fields | URL parameters cannot be edited by customer | | **Page active** | Enable/disable payment page | All payment page links return 404 when disabled | ### Amount Constraints * **Minimum amount:** Enforce minimum payment value * **Maximum amount:** Set upper limit for payments * **Allow custom amount:** Let customers enter their own amount > [!WARNING] > > When using `?product=` links, amount constraints are ignored as the product price is fixed. ## Advanced Integration Examples ### Email Campaign Links Create personalized payment links for email campaigns: ```html theme={null} Pay Now ``` ### CRM Integration Generate dynamic links from your CRM: ```javascript theme={null} const paymentLink = `https://payrequest.me/yourhandle?` + `product=${productId}` + `&name=${encodeURIComponent(customer.name)}` + `&email=${encodeURIComponent(customer.email)}` + `&customfield_reference=${orderId}` + `&lang=${customer.language}`; ``` ### Invoice Links Add direct payment links to your invoices: ``` https://payrequest.me/yourhandle?amount={{invoice_total}}&name={{customer_name}}&email={{customer_email}}¬es=Invoice%20{{invoice_number}} ``` ## URL Encoding Always encode special characters in URLs: | Character | Encoded | Example | | - | - | - | | Space | `%20` | `John Doe` → `John%20Doe` | | @ | `%40` | `user@example.com` → `user%40example.com` | | & | `%26` | `Smith & Co` → `Smith%20%26%20Co` | | # | `%23` | `Apt #5` → `Apt%20%23%5` | > [!TIP] > > Most programming languages have built-in URL encoding functions (`encodeURIComponent` in JavaScript, `urlencode` in PHP, `urllib.parse.quote` in Python). ## Security & Best Practices ### ✅ Do's * **URL encode all parameters** to prevent formatting issues * **Use HTTPS** for secure payment page access * **Enable read-only fields** for personalized payment requests * **Test links** before sending to customers * **Use product links** for fixed-price items * **Add language parameter** for international customers ### ❌ Don'ts * **Don't include sensitive data** like passwords or credit card numbers * **Don't rely on URL parameters for security** (use proper authentication instead) * **Don't exceed URL length limits** (keep under 2000 characters) * **Don't hardcode customer data** without proper consent ## Troubleshooting ### Link doesn't work **Check:** 1. Payment page is active (Settings → Payment Page) 2. Product ID exists and belongs to your account 3. URL parameters are properly encoded 4. Handle is correct (case-sensitive) ### Pre-filled data not showing **Causes:** 1. Parameter names must be exact (lowercase) 2. Special characters need URL encoding 3. Product parameter overrides amount parameter ### Customer can edit locked fields **Solution:** Enable "Readonly dynamic fields" in Settings → Payment Page → Options ### Wrong language displays **Fix:** Add `?lang=nl` or `?lang=en` parameter to URL. Default is English. ## Examples Library ### Basic Product Payment ``` https://payrequest.me/yourhandle?product=1814 ``` ### Dutch Product Payment ``` https://payrequest.me/yourhandle?product=1814&lang=nl ``` ### Pre-filled Customer Data ``` https://payrequest.me/yourhandle?product=1814&name=John%20Doe&email=john@example.com ``` ### Custom Amount with iDEAL ``` https://payrequest.me/yourhandle?amount=99.50&method=ideal&name=Jane%20Smith&email=jane@example.com ``` ### Complete Address Information ``` https://payrequest.me/yourhandle?product=1814&name=John%20Doe&email=john@example.com&address=Main%20Street%20123&city=Amsterdam&postal=1012AB ``` ### Subscription with Custom Fields ``` https://payrequest.me/yourhandle?product=1859&name=Business%20Corp&email=billing@business.com&customfield_company_id=BC-2024&lang=nl ``` ### Per-Unit Pricing (Rental Days) ``` https://payrequest.me/yourhandle?product=1880&customfield_days=3&disabled=true ``` ### Locked Custom Fields Quote ``` https://payrequest.me/yourhandle?product=1880&customfield_size=large&customfield_quantity=10&disabled=true&name=Customer%20Name&email=customer@example.com ``` ### Payment Recovery Link ``` https://payrequest.me/yourhandle?invoice=2358 ``` ## Need Help? > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > Configure accepted payment methods > [card] [Products](/products-and-pricing/creating-products) > > Create products with dynamic pricing > [card] [Subscriptions](/subscriptions/subscription-lifecycle) > > Manage recurring subscriptions > [card] [Custom Fields](/products-and-pricing/custom-fields) > > Add custom fields to products > [card] [Share Your Crypto Address](/payment-processing/share-wallet-address) > > Branded wallet address links with QR code and copy button # Payment Pages Source: https://docs.payreque.st/payment-processing/payment-pages Create flexible, branded payment pages for collecting payments, donations, and custom amounts with ease # Payment Pages 💰 PayRequest Payment Pages are powerful, customizable payment collection tools that enable you to receive payments for any purpose without requiring customers to browse your shop. Perfect for invoicing, donations, service fees, deposits, or any custom payment scenario. > [!NOTE] > > **Flexible Payment Collection**: Payment Pages work independently of your product catalog, allowing customers to pay custom amounts or predefined fees with a clean, professional interface. ## AI Name Suggestions With an active **Premium or Business** subscription, you can enable **AI Name Suggestions** in **PayRequest Page → Settings → Options**. It works on payment and product pages. The switch saves automatically and is off by default for each Page. Visitors receive an optional name suggestion based on their email address. They choose whether to use it, and existing or manually entered names are preserved. Read the [AI Name Suggestions guide](/payment-processing/ai-name-suggestions) for setup instructions, examples and privacy details. ## 🎯 What are Payment Pages? Payment Pages are standalone payment collection forms that you can customize and share with customers: > [card] 💳 Custom Payment Forms > > **Flexible Collection** > > * Custom amount entry > * Predefined payment amounts > * Minimum and maximum limits > * Optional customer information > * Multiple payment methods > [card] 🔗 Easy Sharing > > **Simple Distribution** > > * Clean, branded URLs (payrequest.me/yourhandle) > * QR codes for in-person payments > * Email integration > * Social media sharing > * Website embedding > [card] 🎨 Full Customization > > **Brand Integration** > > * Custom page titles and descriptions > * Your business branding > * Personalized success messages > * Responsive mobile design > * Professional appearance > [card] 📊 Payment Tracking > > **Complete Analytics** > > * Real-time payment monitoring > * Customer information capture > * Payment history and reporting > * Revenue tracking > * Export capabilities ## 🚀 Payment Page Features ### Flexible Amount Configuration > [tab] Custom Amount Entry > > **Customer-Defined Amounts:** > > * Allow customers to enter any amount > * Set minimum payment thresholds (e.g., €0.01+) > * Configure maximum payment limits > * Default amount suggestions > * Real-time validation and formatting > > **Use Cases:** > > * Donations and fundraising > * Service fees and consultations > * Invoice payments > * Tip collection > * Flexible billing scenarios > [tab] Predefined Amounts > > **Fixed Payment Options:** > > * Set specific payment amounts > * Multiple amount choices > * Quick-select buttons > * Subscription-style pricing > * Package deal options > > **Applications:** > > * Membership fees > * Event tickets > * Standard service charges > * Product deposits > * License fees > [tab] Amount Validation > > **Smart Controls:** > > * Minimum amount enforcement (€0.01 minimum) > * Maximum payment limits > * Currency formatting (EUR default) > * Real-time validation feedback > * Error prevention and guidance > > **Business Protection:** > > * Prevent micro-payments > * Set reasonable payment limits > * Ensure payment viability > * Reduce processing issues > * Maintain profit margins ### Customer Information Collection **📝 Flexible Form Fields** **Optional Customer Data:** * Customer name (optional/required) * Email address for receipts * Order notes and descriptions * Custom reference information * Contact details when needed **Smart Defaults:** * Auto-fill for logged-in users * Magic link authentication * Minimal required information * Progressive data collection * GDPR-compliant handling **🔐 Customer Authentication** **Login Options:** * "Login to auto-fill" feature * Magic link authentication * Guest payment capability * Account creation optional * Streamlined user experience **Benefits:** * Faster checkout for returning customers * Automatic information population * Payment history tracking * Customer portal access * Relationship building ### Multi-Language Support > [!NOTE] > > **Sell internationally without extra setup**: every Payment Page (`payrequest.me/yourhandle`) automatically shows in your customer's own language — no translation work required on your end. **🌍 21 Supported Languages** English 🇬🇧, Dutch 🇳🇱, German 🇩🇪, French 🇫🇷, Spanish 🇪🇸, Italian 🇮🇹, Portuguese 🇵🇹, Polish 🇵🇱, Swedish 🇸🇪, Danish 🇩🇰, Norwegian 🇳🇴, Finnish 🇫🇮, Greek 🇬🇷, Czech 🇨🇿, Romanian 🇷🇴, Hungarian 🇭🇺, Turkish 🇹🇷, Russian 🇷🇺, Chinese 🇨🇳, Japanese 🇯🇵, and Ukrainian 🇺🇦. Core checkout fields and labels — name, email, address, order notes, totals, payment method, and more — are translated for every language above, so customers always understand what they're filling in and paying. **🎯 Automatic Detection** **Language is chosen automatically, in this order:** 1. A saved language preference for returning/logged-in customers 2. Their browser's language setting 3. Their country (detected via IP), for visitors whose browser language isn't one of the 21 supported **Manual override:** * A language switcher (flag icon) in the top-right corner of every Payment Page lets customers pick a different language at any time * Business owners can also share a direct link with a fixed language, e.g. `payrequest.me/yourhandle?lang=it` ### Payment Method Integration **1. European Payment Methods** **Optimized for EU Markets:** * iDEAL (Netherlands) * Bancontact (Belgium) * SEPA Direct Debit * Credit/Debit Cards * Bank transfers **2. International Options** **Global Payment Support:** * Visa and Mastercard * American Express * PayPal integration * Apple Pay and Google Pay * Local payment methods **3. Smart Method Selection** **Intelligent Defaults:** * Geographic payment preferences * Amount-based recommendations * Customer history integration * Mobile-optimized selection * One-click payment options ## 🛠️ Setting Up Your Payment Page ### Configuration Process **1. Access Payment Page Settings** Navigate to **Payment Pages** in your PayRequest dashboard or go directly to `/paymentpage` **2. Configure Basic Settings** **Essential Configuration:** * **Custom Handle**: Create a memorable URL (e.g., `payrequest.me/yourhandle`) * **Page Title**: Professional heading (e.g., "Pay YourBusiness") * **Description**: Clear payment instructions * **Amount Settings**: Default, minimum, and maximum amounts **3. Customize Payment Options** **Advanced Settings:** * Enable/disable custom amount entry * Require customer descriptions * Set success messages * Configure redirect URLs * Enable dynamic field controls **4. Test and Activate** **Go Live Process:** * Test with small amounts * Verify payment processing * Check email notifications * Confirm mobile experience * Activate for public use ### Configuration Options **⚙️ Basic Settings** **Core Configuration:** **Custom Handle:** * Create memorable URLs (letters, numbers, hyphens only) * Example: `payrequest.me/consultation` or `payrequest.me/donate` * Auto-converts to lowercase * Must be unique across PayRequest * Falls back to business name if not set **Page Content:** * **Title**: Main heading (e.g., "Pay for Services") * **Description**: Instructions or context for payment * **Success Message**: Custom thank-you message after payment * All text supports your brand voice and tone **💰 Amount Configuration** **Payment Amount Controls:** **Default Amount:** * Pre-fill amount field with suggested value * Customers can modify if custom amounts enabled * Useful for standard fees or donations * Leave blank for completely open amounts **Amount Limits:** * **Minimum**: Prevent micro-payments (default €0.01) * **Maximum**: Set upper payment limits * **Custom Amounts**: Allow/disable customer amount entry * Real-time validation and error messages **Amount Display:** * Euro (EUR) currency formatting * Automatic decimal handling * Clear visual feedback * Mobile-friendly input **📋 Form Behavior** **Customer Experience Controls:** **Information Requirements:** * **Name**: Optional or required customer name * **Email**: For receipt delivery * **Description**: Allow customers to add payment notes * **Readonly Fields**: Lock specific form elements **Advanced Options:** * **Require Description**: Force customers to add payment context * **Dynamic Field Control**: Enable/disable field modifications * **Guest Payments**: Allow payments without account creation * **Auto-fill Integration**: Support logged-in user data ## 🎨 Customization and Branding ### Visual Customization > [card] 🏪 Brand Integration > > **Professional Appearance:** > > * Your business logo display > * Consistent color scheme > * Custom domain support > * Professional typography > * Mobile-responsive design > [card] 📱 Mobile Optimization > > **Mobile-First Design:** > > * Touch-friendly interface > * Responsive layouts > * Fast loading times > * Thumb-friendly buttons > * Optimized form fields ### Content Personalization > [tab] Messaging Customization > > **Branded Communication:** > > * Welcome messages and instructions > * Payment confirmation text > * Success page content > * Error message customization > * Email receipt branding > > **Tone and Voice:** > > * Professional service language > * Friendly donation appeals > * Clear payment instructions > * Reassuring security messages > * Brand-consistent communication > [tab] URL Customization > > **Professional URLs:** > > * Custom handles for memorable links > * Business name integration > * Service-specific naming > * Campaign-focused URLs > * Easy sharing and marketing > > **Examples:** > > * `payrequest.me/consultation` > * `payrequest.me/donate` > * `payrequest.me/membership` > * `payrequest.me/invoice` > * `payrequest.me/deposit` ## Customer instructions you can share Use [Paying a business](/customer-guide/payments) to explain the checkout to customers, and [Your customer account](/customer-guide/customer-account) for login help. The guides cover payment pages as well as the shop portal. For an authorization hold, share [Security deposits for customers](/customer-guide/security-deposits) alongside the original deposit link. ## 👤 Customer Login & Account Area Customers can log in and manage their own account **directly from your payment page** — no separate shop portal required. > [!NOTE] > > This is a lighter-weight account area built into the payment page itself, separate from the full [Customer Portal](/customer-management/customer-portal) available under your shop URL. Both share the same customer session, but the payment page account area is scoped to a few essential self-service tabs. ### Passwordless Magic Link Login Customers log in with just their email — no password to remember or reset: **1. Customer clicks Login** From your payment page, the customer clicks the account menu and enters their email address. **2. Magic link is emailed** PayRequest emails a one-time login link. If no customer record exists yet for that email, one is created automatically. **3. Customer clicks the link** Clicking the link logs them in and starts a session — no password required. ### Account Tabs Once logged in, customers can switch between tabs using the `?tab=` parameter (e.g. `?tab=settings`): | Tab | What Customers Can Do | | - | - | | **Settings** | Manage notification preferences (invoice created/paid/reminder, subscription renewal/status, order confirmation) | | **Contacts** | Add up to 10 contact persons from their organization, each with a role and their own notification preferences | | **Payment Methods** | View and revoke saved SEPA mandates | | **Subscriptions** | View their active subscriptions (read-only) | | **Support** | Submit a support request directly to your business, which notifies you by email | > [!TIP] > > Every account action is scoped to the correct business — a customer logged in on one business's payment page can never see or modify data belonging to another business, even though the underlying `customer` session key is shared site-wide. ## 📊 Payment Page Analytics ### Performance Tracking > [card] 💳 Payment Metrics > > **Transaction Analytics:** > > * Total payments received > * Revenue generated > * Average payment amount > * Payment success rates > * Method preferences > [card] 👥 Customer Insights > > **User Behavior:** > > * Visitor conversion rates > * Customer information completion > * Return visitor tracking > * Geographic distribution > * Device usage patterns > [card] 📈 Optimization Data > > **Performance Optimization:** > > * Form completion rates > * Payment method effectiveness > * Mobile vs desktop usage > * Time-to-payment analysis > * Error and abandonment tracking ### Recent Payment History **1. Real-Time Monitoring** View payments as they happen with instant dashboard updates **2. Customer Information** Track customer details, payment amounts, and transaction status **3. Payment Methods** Analyze which payment methods customers prefer **4. Export and Reporting** Download payment data for accounting and analysis ## 🌟 Use Cases and Applications ### Business Applications **💼 Professional Services** **Service-Based Businesses:** * Consultation fees and hourly billing * Project deposits and milestones * Retainer payments * Invoice settlements * Expense reimbursements **Configuration Example:** * Handle: `consultation` * Title: "Professional Consultation Payment" * Description: "Pay for your consultation session" * Default Amount: €150.00 * Allow Custom: Yes (for variable session lengths) **🎗️ Fundraising and Donations** **Non-Profit and Fundraising:** * Charity donations * Crowdfunding campaigns * Event sponsorships * Membership contributions * Emergency fundraising **Configuration Example:** * Handle: `donate` * Title: "Support Our Cause" * Description: "Your donation makes a difference" * Minimum Amount: €5.00 * Allow Custom: Yes * Success Message: "Thank you for your generous support!" **🎫 Events and Memberships** **Event and Membership Management:** * Event ticket sales * Membership fee collection * Workshop registrations * Conference payments * Annual dues collection **Configuration Example:** * Handle: `membership` * Title: "Annual Membership Payment" * Description: "Join our community for exclusive benefits" * Default Amount: €99.00 * Allow Custom: No * Require Description: Yes (for member information) **🏠 Rental and Deposits** **Property and Rental Payments:** * Security deposits * Rental payments * Booking fees * Damage deposits * Utility payments **Configuration Example:** * Handle: `deposit` * Title: "Security Deposit Payment" * Description: "Required deposit for rental agreement" * Default Amount: €500.00 * Allow Custom: No * Maximum Amount: €2000.00 ### Integration Scenarios > [card] 📧 Email Integration > > **Email Marketing:** > > * Newsletter payment links > * Invoice payment buttons > * Campaign-specific URLs > * Automated follow-ups > * Receipt customization > [card] 🌐 Website Integration > > **Web Integration:** > > * Direct website links > * Payment page embedding > * QR code generation > * Social media sharing > * SEO-friendly URLs ## 🔒 Security and Compliance ### Payment Security > [card] 🛡️ PCI Compliance > > **Industry Standards:** > > * PCI DSS Level 1 certification > * Secure card processing > * Encrypted data transmission > * Tokenized payment storage > * Regular security audits > [card] 🔐 Data Protection > > **Privacy Safeguards:** > > * GDPR compliance > * Data minimization > * Secure data storage > * Customer consent management > * Right to deletion > [card] ⚡ Fraud Prevention > > **Risk Management:** > > * Real-time fraud detection > * Velocity checks > * Geographic validation > * Device fingerprinting > * Risk scoring algorithms ### Compliance Features **📋 GDPR Compliance** **Data Protection:** * Minimal data collection * Clear consent mechanisms * Data portability options * Deletion requests handling * Privacy policy integration * Cookie consent management **💳 PCI DSS Standards** **Payment Card Security:** * Secure cardholder data handling * Strong access controls * Regular security monitoring * Vulnerability management * Secure network architecture * Information security policies ## 📱 Mobile Experience ### Mobile-First Design **1. Responsive Layout** Automatically adapts to all screen sizes with touch-friendly interfaces **2. Fast Loading** Optimized for mobile networks with compressed assets and smart caching **3. Touch Optimization** Large buttons, easy form fields, and thumb-friendly navigation **4. Mobile Payments** Support for Apple Pay, Google Pay, and mobile wallet integration ### Mobile Features > [card] 📲 PWA Support > > **App-Like Experience:** > > * Add to home screen > * Offline functionality > * Push notifications > * Fast loading > * Native feel > [card] 📷 QR Code Integration > > **Contactless Payments:** > > * QR code generation > * In-person payment collection > * Event check-in integration > * Contactless donations > * Physical location payments ## 🔧 Advanced Configuration ### API Integration **🔌 Webhook Integration** **Real-Time Events:** * Payment completion notifications * Failed payment alerts * Customer information updates * Refund processing events * Custom business logic triggers **Webhook Payloads:** * Complete payment details * Customer information * Payment method used * Transaction metadata * Timestamp and reference data **⚙️ API Access** **Programmatic Control:** * Payment page creation via API * Dynamic amount configuration * Customer pre-filling * Payment status monitoring * Bulk payment processing **Use Cases:** * CRM integration * Automated billing systems * Custom payment workflows * Multi-tenant applications * White-label solutions ### Business Intelligence **1. Analytics Integration** Connect Google Analytics and other tracking tools for comprehensive insights **2. Payment Optimization** A/B test different page configurations to maximize conversion rates **3. Customer Journey Tracking** Understand how customers find and complete payments on your pages **4. Revenue Attribution** Track which marketing channels drive the most valuable payments ## 📞 Support and Resources > [card] 🚀 Setup Assistance > > **Implementation Help** > > * Payment page configuration > * Custom integration support > * Best practices guidance > * Optimization recommendations > [card] 📚 Documentation > > **Complete Resources** > > * API documentation > * Integration guides > * Code examples > * Troubleshooting help > [card] 💬 Ongoing Support > > **Continuous Help** > > * Technical support > * Feature requests > * Performance optimization > * Business consultation ## 🎓 Next Steps > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > Understand all available payment methods and optimization strategies > [card] [QR Code Payments](/payment-processing/qr-code-payments) > > Enable contactless payments with QR codes for in-person collection > [card] [Analytics Dashboard](/analytics-and-reporting/insights-dashboard) > > Track payment page performance and optimize conversion rates > [card] [Customer Management](/customer-management/customer-profiles) > > Manage customers who pay through your payment pages *** > [!TIP] > > **Pro Tip**: Start with a simple payment page configuration and gradually add advanced features based on customer feedback and usage analytics. Monitor conversion rates to optimize your page settings for maximum payment completion. # QR Code Payments Source: https://docs.payreque.st/payment-processing/qr-code-payments Accept payments via QR codes on flyers, receipts, table tents, and signage ## Overview Every Smart Link automatically generates a QR code that customers can scan to make a payment. QR codes are perfect for physical locations, printed materials, and anywhere you want to offer contactless payments. ## How It Works 1. **Create a Smart Link** with a fixed amount or product 2. **Open the smart link detail page** and click **Share** 3. **Download or share the QR code** — it encodes the smart link URL 4. **Customer scans** the QR code with their phone camera 5. **Payment page opens** with the correct amount pre-filled > [!NOTE] > > QR codes are generated automatically for every smart link. No additional setup required. ## Getting Your QR Code ### From Smart Link Detail Page 1. Navigate to **Payment Page** → **Smart Links** 2. Click on any smart link to open the detail page 3. Click the **Share** button 4. The QR code is displayed in the share modal 5. Right-click the QR code to save (200x200px PNG) ### Sharing Options The share modal provides: * **QR Code Image** — Right-click to save * **Copy URL** — Copy the smart link URL to clipboard ## Use Cases ### Restaurant Table Payments Place QR codes on table tents or menus: ``` Smart Link: Table Payment Amount: Variable (let customer enter) Path: pay QR Code: Printed on table tent ``` ### Invoice Supplements Add QR code to printed invoices for easy mobile payment: ``` Smart Link: Invoice Payment Amount: €250.00 Path: inv-2025-001 QR Code: Printed on invoice footer ``` ### Retail Deposits Display QR codes at the register for equipment deposits: ``` Smart Link: Equipment Deposit (Security Deposit product) Amount: €500.00 Path: equipment-deposit QR Code: Laminated card at service desk ``` ### Event Entrance Fees Print QR codes on tickets or event posters: ``` Smart Link: Workshop Entry Amount: €35.00 Path: workshop-march QR Code: Event poster, email invitation ``` ## Print Guidelines **Minimum Size:** 2cm x 2cm (0.8 x 0.8 inches) **Best Practices:** * Use high contrast (black QR on white background) * Leave white space (quiet zone) around the QR code * Test the printed QR code before distributing * Include a short text label below the code (e.g., "Scan to pay") **Recommended Sizes by Use:** | Format | Suggested Size | | - | - | | Business card | 2cm x 2cm | | Table tent | 4cm x 4cm | | Flyer / A5 | 5cm x 5cm | | Poster / A3 | 8cm x 8cm | | Banner | 10cm+ x 10cm+ | > [!WARNING] > > Always test QR codes after printing. Some printers may distort the code at very small sizes. Test with at least 3 different phone cameras. ## Tracking QR Code Payments All payments through QR codes are tracked via the Smart Link analytics: * **Views**: Each QR scan counts as a view * **Payments**: Completed payments through the link * **Conversion Rate**: Views vs. payments percentage * **Revenue**: Total collected through this QR code This lets you measure the effectiveness of physical QR code placements. ## Need Help? > [card] [Smart Links](/payment-processing/smart-links) > > Full smart link documentation > [card] [Security Deposits](/payment-processing/security-deposits) > > QR codes for deposit collection # Allocate a bank payment to invoices Source: https://docs.payreque.st/payment-processing/reconcile-bank-payments Review a received Ponto bank payment and assign it to one or more invoices for the same customer. Use **Allocate to invoices** when money has already arrived through your connected bank account, but the correct invoices remain open. This is useful when a customer sends one combined payment for several invoices or an older receipt was booked without settling the invoices. > [!NOTE] > > This records how received money pays invoices. It does not collect money, initiate a transfer or send another payment request. Bookkeeping status and invoice settlement are separate. Looking for ledger postings, partial bank allocations, provider fees or quarter-end reports? See [Bookkeeping](https://docs.payreque.st/analytics-and-reporting/bookkeeping). Matching in that workspace does not change the original invoice payment status. ## Before you start You need access to the relevant Ponto transactions and permission to edit invoices. Team members require invoice-editing permission. * The receipt must be positive, no longer pending and have an execution date. * Select open, positive invoices for **one customer in your own account**. * The invoices must be dated on or before the bank payment date and use its currency. * The selected invoice total must equal the received amount exactly. This flow does not allocate part of a receipt or accept a difference for fees or overpayment. * Payments already linked elsewhere and invoices with other payment activity, credits or certain linked order/collection states require separate review. Use the customer's payment specification or another reliable record to identify the invoices. A matching total or an invoice number in the bank description is not proof of which invoices the customer intended to pay. ## Review and confirm 1. Open [Ponto transactions](https://payrequest.app/ponto/transactions). 2. To find possible older matches, select **Invoice allocation review (all dates)**. This review filter shows candidates; it is not a complete list of every unallocated receipt. You can also open a relevant incoming transaction from the normal list. 3. Open the transaction and choose **Allocate to invoices**. 4. Enter an **Invoice number for this customer**, then choose **Load open invoices**. Check that the displayed customer is correct. 5. Select the invoices that the received payment actually covers and choose **Review allocation**. 6. Check the amount, currency, original payment date and every invoice number. Confirm **I verified that this payment covers these invoices**, then choose **Confirm allocation**. For example, a received EUR 150 payment can settle two eligible EUR 100 and EUR 50 invoices for the same customer when the customer's specification confirms that grouping. PayRequest does not choose a subset of invoices for you. ## What confirmation changes The reviewed invoices are marked paid using the original bank execution date. Their reminders are disabled and obsolete awaiting-bank-transfer instructions are cancelled. The allocation is recorded with the received payment; existing accounting notes are preserved. **No customer email or payment request is sent.** Payment notifications and automatic service provisioning are not replayed. If an associated service needs an operational action, review it separately rather than assuming this bookkeeping action will perform it. ## If confirmation is blocked | Message or situation | Next step | | - | - | | Total or currency does not match | Check the customer's specification. Do not select unrelated invoices to make the sum fit. | | Receipt already linked | Review the existing allocation before attempting anything else. | | Invoice has credits, payment activity or another incompatible state | Review its payment history and settle the discrepancy separately. | | Invoice is missing | Check the customer, invoice status and date. The selection screen lists up to 200 eligible open invoices. | | Preview expired or records changed | Load and review the allocation again. Previews expire after ten minutes. | | Browser response is unclear | Check the transaction and invoices before retrying. The same confirmed operation cannot allocate the receipt twice. | There is no undo step described in this flow. If an allocation appears incorrect, ask for a reviewed correction before editing payment records or marking invoices unpaid. ## Related guides * [Automatic bank-transfer matching](https://docs.payreque.st/payment-processing/bank-transfer) * [Connect and sync a bank account with Ponto](https://docs.payreque.st/payment-processing/bank-sync-ponto) * [Create invoices](https://docs.payreque.st/invoices/creating-invoices) # Saved Payment Methods Source: https://docs.payreque.st/payment-processing/saved-payment-methods Enable customers to reuse SEPA Direct Debit mandates for faster invoice payments ## Overview Saved Payment Methods allow your customers to pay invoices quickly using previously authorized SEPA Direct Debit mandates. Instead of creating a new payment method each time, customers can select from their existing mandates, making repeat payments faster and more convenient. > [!TIP] > > This feature is perfect for recurring customers, subscriptions, and businesses that send frequent invoices to the same clients. It reduces friction and increases payment success rates. ## How It Works ### For Customers 1. **First Payment**: Customer pays an invoice via SEPA Direct Debit 2. **Mandate Created**: Mollie automatically creates and stores a mandate 3. **Future Payments**: Customer sees "Saved Payment Methods" option on invoices 4. **Quick Payment**: Select saved mandate → Confirm → Payment processed instantly ### For Business Owners The system works automatically: * No configuration required * Mandates are created during first SEPA payment * Saved methods appear automatically for returning customers * Full transaction history and audit trail maintained > [!NOTE] > > Saved payment methods only apply to **SEPA Direct Debit** mandates. Credit card and other payment methods do not support saved credentials in the same way. ## Payment Flow ### Step 1: Customer Receives Invoice When a customer views an unpaid invoice in their portal, they see two payment options: * **Pay with New Method**: Standard payment flow with Mollie checkout * **Pay with Saved Method**: Quick payment using existing mandate ### Step 2: Selecting a Saved Method If the customer has active SEPA mandates: 1. Click **"Pay with Saved Payment Method"** button 2. Modal appears showing all available mandates 3. Each mandate displays: * Mandate ID (e.g., `mdt_abc123xyz`) * Bank account details (masked: `NL**ABNA0123456789`) * Creation date * Status (Active/Pending/Expired) ### Step 3: Confirming Payment 1. Customer selects a mandate from the list 2. Clicks **"Confirm Payment"** 3. System creates payment using selected mandate 4. Invoice status updates to "Pending" immediately 5. Payment processes through Mollie ### Step 4: Payment Confirmation **Successful Payment:** * Invoice marked as "Paid" * Transaction recorded in payment history * Email notification sent (if configured) * Customer redirected to invoice overview **Failed Payment:** * Error message displayed * Invoice remains "Open" or "Pending" * Customer can retry with different mandate or new payment method ## Customer Experience ### Customer Portal Interface **Invoice Detail Page** (`/shop/{handle}/portal/invoices/{id}`): > [card] Payment Button States > > **Available** (Blue) > > * Default state > * Clickable and ready > * Shows "Pay with Saved Payment Method" > > **Processing** (Gray) > > * Payment in progress > * Button disabled > * Shows "Processing..." > > **Completed** (Green) > > * Payment succeeded > * Invoice marked as paid > * Button hidden > [card] Payment Method Modal > > **Modal Contents:** > > * List of active mandates > * Mandate details (ID, bank, date) > * "Cancel" button to close > * "Confirm Payment" button > > **Real-time Updates:** > > * Loading states during fetch > * Error messages inline > * Success confirmation ### Mobile-Friendly Design The saved payment method interface is fully responsive: * Touch-friendly buttons (minimum 44px tap target) * Modal adapts to screen size * Clear visual feedback for all actions * Works on iOS, Android, and desktop browsers ## Mandate Management ### What is a Mandate? A **SEPA mandate** is an authorization from a customer allowing you to automatically debit their bank account. It's created during the first SEPA Direct Debit payment and can be reused for future payments. > [!NOTE] > > Mandates are regulated by SEPA (Single Euro Payments Area) regulations and must comply with EU banking standards. ### Mandate Statuses | Status | Description | Can Use for Payment? | | - | - | - | | **Valid** | Active and ready to use | ✅ Yes | | **Pending** | Awaiting bank verification | ❌ No (use after verification) | | **Expired** | No longer valid | ❌ No | | **Canceled** | Revoked by customer or business | ❌ No | ### How Mandates Are Created **Automatic Creation via Mollie:** 1. Customer selects SEPA Direct Debit at checkout 2. Mollie redirects to bank for authorization 3. Customer authorizes direct debit 4. Mollie creates mandate and links to customer 5. Mandate becomes available for future payments **When are Mandates Created?** * First SEPA payment for subscription * SEPA invoice payment * SEPA order payment in shop * Manual SEPA setup (via Mollie dashboard) ### Viewing Active Mandates **For Business Owners:** Navigate to **Settings** → **Payment Providers** → **Mollie** → **Mandates** View all mandates including: * Customer name and email * Mandate ID * Bank account (masked) * Status and creation date * Linked subscriptions/invoices **For Customers:** Mandates appear automatically when viewing unpaid invoices in the customer portal. No separate mandate management page needed. ## Technical Details ### System Architecture **Key Components:** * **ShopCustomerInvoiceDetail Component**: Livewire component handling UI and payment processing * **MollieService**: Handles API communication with Mollie * **Mandate Loading**: Fetches active mandates via Mollie API * **Payment Creation**: Creates payments using mandate ID * **Duplicate Prevention**: Ensures no concurrent payments for same invoice ### Payment Processing Flow ```mermaid theme={null} sequenceDiagram Customer->>Portal: Clicks "Pay with Saved Method" Portal->>MollieService: loadAvailableMandates() MollieService->>Mollie API: GET /mandates Mollie API-->>MollieService: Returns active mandates MollieService-->>Portal: Display mandate list Customer->>Portal: Selects mandate & confirms Portal->>MollieService: payWithSavedMethod(mandateId) MollieService->>Mollie API: POST /payments (with mandateId) Mollie API-->>MollieService: Payment created MollieService->>Database: Update invoice status Database-->>Portal: Payment pending Portal-->>Customer: Success confirmation ``` ### API Integration PayRequest integrates with Mollie's Customers API to manage mandates: **Endpoints Used:** * `GET /v2/customers/{customerId}/mandates` - Fetch customer mandates * `POST /v2/payments` - Create payment with mandate ID * `GET /v2/mandates/{mandateId}` - Verify mandate status **Authentication:** * OAuth 2.0 access tokens (auto-refreshed) * API keys stored encrypted in database * Per-business provider credentials ### Security Features > [card] Duplicate Prevention > > * Prevents multiple simultaneous payments > * Checks invoice payment status before creating payment > * Validates mandate belongs to customer > * Ensures mandate is active and valid > [card] Error Handling > > * Comprehensive error catching > * User-friendly error messages > * Automatic retry suggestions > * Logs all failed attempts > [card] Audit Trail > > * All payments logged in transactions table > * Activity log tracks payment attempts > * Mandate usage tracked per invoice > * Full transaction history maintained > [card] Data Privacy > > * Bank account numbers masked in UI > * Mandate IDs encrypted in database > * GDPR-compliant data handling > * Secure communication with Mollie ## Use Cases ### 1. Recurring Service Providers **Scenario:** Monthly consulting services with variable amounts **Benefit:** * Customers pay new invoices with one click * No need to re-enter bank details each month * Faster payment processing * Reduced payment failures **Example:** ``` Business: Web Development Agency Customer: SaaS Startup Invoice: €2,500 for March development work Payment: Customer uses saved mandate from previous month Result: Payment processed same day ``` ### 2. Subscription Businesses **Scenario:** Annual subscriptions with add-on purchases **Benefit:** * Main subscription uses mandate automatically * Add-on invoices can reuse same mandate * Consistent payment method across all charges * Higher payment success rate **Example:** ``` Business: SaaS Platform (€20/month) Customer: Small Business Invoice: €50 for additional user licenses Payment: Uses subscription mandate Result: Instant payment confirmation ``` ### 3. Service Businesses with Deposits **Scenario:** Project-based work with upfront deposits **Benefit:** * Initial deposit creates mandate * Final invoice uses same mandate * No payment friction at project completion * Professional client experience **Example:** ``` Business: Design Studio Customer: E-commerce Company Invoice 1: €1,000 deposit (creates mandate) Invoice 2: €4,000 final payment (uses saved mandate) Result: Smooth payment experience ``` ## Troubleshooting ### Customer Can't See Saved Payment Methods **Possible Causes:** 1. **No Active Mandates** * Customer has never paid via SEPA * Previous mandates expired or canceled * Mandates belong to different Mollie customer 2. **Wrong Customer Account** * Customer logged into wrong portal * Email mismatch between PayRequest and Mollie * Multiple customer accounts exist 3. **Mollie Connection Issue** * Mollie provider inactive * OAuth token expired (auto-refresh failed) * API credentials invalid **Solutions:** > [accordion] Verify Mandate Exists in Mollie > > 1. Log into Mollie dashboard > 2. Navigate to Customers > 3. Search for customer email > 4. Check Mandates tab > 5. Verify status is "Valid" > [accordion] Check PayRequest-Mollie Customer Sync > > 1. Go to Settings → Payment Providers → Mollie > 2. Ensure "Sync Customers" is enabled > 3. Click "Test Connection" to verify > 4. Check customer record in PayRequest dashboard > 5. Verify `mollie_customer_id` field is populated > [accordion] Refresh Mollie Connection > > 1. Navigate to Settings → App Store → Mollie > 2. Click "Test Connection" > 3. If failed, click "Reconnect" > 4. Complete OAuth flow > 5. Retry payment ### Payment Fails with Saved Mandate **Common Error Messages:** **"Mandate is no longer valid"** * Mandate expired or revoked by bank * Customer needs to create new mandate * Solution: Pay with new payment method **"Insufficient funds"** * Customer's bank account balance too low * SEPA direct debit declined by bank * Solution: Customer should check bank account **"Payment already exists for this invoice"** * Duplicate payment attempted * System prevented double-charging * Solution: Refresh page, check invoice status **"Unable to create payment"** * Mollie API error or timeout * Temporary service disruption * Solution: Wait 5 minutes and retry ### Mandate Shows as "Pending" **What it means:** * Bank hasn't confirmed authorization yet * Usually takes 1-3 business days * Customer can use mandate after confirmation **Next steps:** * Wait for bank verification * Use alternative payment method meanwhile * Check Mollie dashboard for status updates > [!WARNING] > > Never manually mark invoices as paid while using saved payment methods. Always wait for Mollie webhook confirmation to ensure payment actually succeeded. ## Best Practices ### For Business Owners > [card] Enable Customer Sync > > Turn on Mollie customer sync to automatically link customers between PayRequest and Mollie. This ensures mandates appear correctly. > [card] Test Before Going Live > > Use Mollie test mode to verify saved payment methods work correctly before processing real payments. > [card] Monitor Mandate Health > > Regularly check mandate statuses in Mollie dashboard. Replace expired mandates before they cause payment failures. > [card] Educate Customers > > Inform customers about saved payment methods in onboarding emails. Explain the convenience and security benefits. ### For Customers * **Keep bank details current**: Update mandate if you change banks * **Monitor email notifications**: Check for payment confirmations * **Contact business if issues**: Don't repeatedly retry failed payments * **Understand processing time**: SEPA payments take 1-3 business days ## Security & Compliance ### SEPA Regulations PayRequest complies with SEPA mandate regulations: * ✅ **Pre-notification**: Customers receive advance notice of charges * ✅ **Mandate Reference**: Unique ID for each authorization * ✅ **Revocation Rights**: Customers can cancel mandates anytime * ✅ **Dispute Process**: SEPA chargeback rights preserved ### Data Protection **Data Storage:** * Mandate IDs are provider-issued references, not raw payment credentials — the full card/IBAN number is never stored by PayRequest * Bank account numbers masked in all interfaces * Connected provider API credentials (Mollie, Stripe, PayPal, Payoneer) are stored encrypted **Access Control:** * Only customer can use their own mandates * Business owners see aggregated data only * Multi-tenant isolation enforced **Audit Logging:** * All payment attempts logged * Mandate usage tracked * Failed payments recorded with reasons ### PCI Compliance PayRequest **never stores** sensitive bank account details: * Bank data stays with Mollie (PCI-DSS Level 1 certified) * Only mandate IDs stored in PayRequest * No direct access to customer bank accounts * All payment processing handled by Mollie > [!NOTE] > > By using Mollie mandates, PayRequest maintains PCI compliance without needing to store sensitive payment information. ## Frequently Asked Questions > [accordion] Can customers use saved methods for subscriptions? > > Yes! Subscriptions automatically create and use mandates for recurring payments. The same mandate can be used for both subscription charges and one-off invoice payments. > [accordion] What happens if a customer cancels their mandate? > > The mandate will no longer appear in saved payment methods. The customer will need to create a new mandate by making a new SEPA payment, or use a different payment method. > [accordion] How long do mandates remain active? > > SEPA mandates remain valid indefinitely unless: > > * Customer revokes the mandate > * Bank account is closed > * 36 months pass without any payments (dormancy) > * Business manually cancels the mandate > [accordion] Can I manually create mandates for customers? > > No. Mandates must be created through the standard SEPA Direct Debit payment flow via Mollie. This ensures proper authorization and compliance with SEPA regulations. > [accordion] Do saved payment methods work with other payment types? > > Currently, only SEPA Direct Debit mandates support saved payment methods. Credit cards, iDEAL, and other payment methods do not offer saved credentials in the same way. > [accordion] Can customers have multiple saved mandates? > > Yes! Customers can have multiple mandates (e.g., personal and business bank accounts). They can choose which mandate to use for each payment. > [accordion] What's the difference between saved mandates and subscriptions? > > **Subscriptions** are recurring payments that automatically charge on schedule. **Saved mandates** allow one-click manual payments on individual invoices. Both use SEPA mandates but serve different purposes. ## Related Documentation > [card] [SEPA Mandates](/subscriptions/managing-mandates) > > Learn more about mandate management > [card] [Mollie Integration](/payment-processing/setting-up-payment-providers) > > Set up Mollie for your business > [card] [Customer Portal](/customer-management/customer-portal) > > Configure customer portal settings > [card] [Invoice Payments](/invoices/creating-invoices) > > Create and manage invoices > [card] [Subscriptions](/subscriptions/creating-subscriptions) > > Set up recurring billing > [card] [App Store](/business-settings/app-store) > > Manage payment provider integrations *** > [!NOTE] > > **Need Help?** If you're experiencing issues with saved payment methods, contact [support@payrequest.io](mailto:support@payrequest.io) with the invoice ID and customer email for assistance. # Security Deposits Source: https://docs.payreque.st/payment-processing/security-deposits Collect authorization holds on credit cards for hotels, car rentals, equipment, and Airbnb. Capture or release funds after inspection. ## Overview Security Deposits let you place a temporary hold on a supported payment method without collecting the amount immediately. The reservation reduces the customer's available balance or credit until it is captured, released or expires. After the service is completed — a hotel stay, car rental return, or equipment inspection — you can either **capture** (charge) all or part of the hold, or **release** it back to the customer. > [!TIP] > > Security Deposits are perfect for any business that needs a guarantee before delivering a service: hotels, Airbnb hosts, car rental companies, equipment rental, event venues, and more. ## How It Works Security Deposits use your connected payment provider, such as Stripe, Mollie, or PayPal, to create authorization holds on supported cards: 1. **Customer authorizes** → An amount is temporarily reserved (not collected) 2. **You inspect** → Check the property, vehicle, or equipment after use 3. **You decide** → Capture the hold (charge for damages) or release it (no charge) ``` Customer authorizes €500 deposit ↓ Hotel stay / Rental period ↓ Inspection after checkout ↓ ├─ No damage → Release full €500 (bank restores available funds) ├─ Minor damage → Capture €75 (charge only what's needed) └─ Major damage → Capture full €500 ``` > [!WARNING] > > Use the authorization methods offered by the connected provider in this deposit checkout. Stripe deposits use supported cards; iDEAL, SEPA Direct Debit and ordinary bank transfers do not create card authorization holds. Direct PayPal deposits follow a separate PayPal approval flow. ## Key Features * **Authorization Hold**: Amount reserved on card, not charged * **Full or Partial Capture**: Charge the exact amount needed for damages * **Release Hold**: Release the remaining reservation after confirmation * **Authorization Deadline**: Check the provider-confirmed deadline; a configured duration does not guarantee that the bank will reserve funds for that long. See [hold durations](/payment-processing/deposit-hold-duration). * **Customer Status Page**: Branded page where customers can track their deposit * **Progress Tracking**: Visual countdown showing remaining hold days * **Capture History**: Full audit trail of all captures * **Email Notifications**: Confirmations for tracked reservations, charges and releases when a recipient email is available ## Finish a request or resolve a blocked allowance Open **Security Deposits** to see which requests still need attention: | Status | What to do | | - | - | | Waiting for customer | Open the request and share its existing authorization link. **Copy reminder text** prepares a message you can review and send yourself. Creating another request is usually unnecessary. | | Processing authorization | Wait for the payment provider to confirm the result. Do not ask the customer to authorize a second deposit while the first attempt is processing. | | Authorization attempt expired | That checkout expired. Check the exact provider records and any other attempts before considering a replacement; an expired checkout does not rule out another hold. Contact support if the existing Stripe request cannot continue. | | Funds reserved | Inspect the rental and release the hold, or capture the amount agreed with the customer before the displayed deadline. | | Request closed | The unused request's authorization link has been disabled. It cannot reserve funds. | If a booking was canceled or you made a duplicate request, its detail page offers **Close unused request** only when PayRequest can confirm that authorization has never started. Confirming this action frees the active deposit allowance. The request stays in the history and still counts toward the monthly allowance. No message is sent to the customer and the booking itself is unchanged. Requests with a provider attempt, an uncertain result, or an existing hold cannot be closed this way. Older requests may also lack the evidence needed to offer this action. Contact PayRequest support if one of these requests is blocking your allowance; do not create or authorize another deposit just to work around it. > [!TIP] > > ### Plan limits > > | Plan | New requests per calendar month | Open requests at a time | > | - | -: | -: | > | Free | 3 | 1 | > | Premium (€5/month) | 15 | 5 | > | Business (€20/month) and Growth | Unlimited | Unlimited | > > Pending requests, authorized holds, and partially captured deposits count as open. The monthly allowance resets on the first day of each month. Closing an eligible unused request frees an open slot, but does not restore the monthly allowance. > > View your current usage under **Security Deposits** or **Settings → PayRequest Plan**. Premium's higher allowance applies to your existing active or trial Premium subscription; you do not need to subscribe again. Business is available [on request through support](/business-settings/payrequest-plans#requesting-the-business-plan). > > Existing eligible Premium subscriptions retain unlimited access while that same subscription remains active or in trial and stays on Premium. Existing holds can still be managed, captured, and released after a plan change. See [PayRequest Plans](/business-settings/payrequest-plans#security-deposit-allowances) for the plan comparison. ## Verify reserved funds at Stripe For a connected Stripe account, **Security Deposits → Stripe card reservations** shows provider records separately from your PayRequest requests. Choose **Check Stripe** to refresh the overview. Older or other payment links can have a real card hold even when a newer checkout has expired. The overview separates the original amount, funds still reserved, funds charged and funds released. Each record shows when it was checked. Provider discovery may be delayed. A missing row, an expired checkout or an incomplete check does **not** prove that no funds are held. Records are linked to a PayRequest deposit only by an exact, verified payment reference. Names and email addresses are never used to guess this link. For an unlinked reservation, **Open in Stripe** lets you inspect the payment in your own Stripe account; contact PayRequest support if you need help. Refreshing the overview does not charge or release funds. On an individual Stripe deposit, **Check linked authorization** checks its exact reference. PayRequest rechecks the provider amount and status before a charge or release. If the check fails, the action stops. A release is recorded only after Stripe confirms it. ## Confirmation emails After a confirmed reservation, charge or release, PayRequest sends a confirmation to the business and the customer email on the deposit. A quick deposit does not need a separate customer profile for this confirmation. Duplicate webhook deliveries do not generate another confirmation for the same event. A release confirmation states the amount released and explains that the cardholder's bank determines when the pending reservation disappears. Previously charged amounts are not refunded by releasing the remaining hold. Provider searches and migration of this overview do not send historical customer confirmations. ## Renew a Stripe deposit on Business For new Stripe deposits, customers can optionally agree to save their card and permit replacement holds for the **same amount and booking**, for up to **30 days from the first authorization**. This option is available on the direct deposit authorization page and deposit product or Smart Link checkout. Leaving it unchecked does not prevent the original authorization. Existing holds without that prior consent cannot use saved-card renewal. During the final 48 hours of an eligible hold, open **Security Deposits → the deposit → Renew deposit authorization**. This is a merchant-requested action, not automatic renewal. A merchant expiry email is queued when the opted-in hold enters its final 48 hours; delivery depends on the queue and email provider. PayRequest requests a new reservation using the saved card. The original reservation remains until Stripe confirms the replacement and confirms cancellation of the old hold. Both reservations may briefly appear on the customer's card. A declined replacement leaves the original hold and deadline in place. No funds are captured by renewal. If the bank requests verification, the business and customer receive a confirmation notice. The customer follows the confirmation link to the secure PayRequest payment page and chooses **Confirm deposit renewal**. If they start on an app or custom-domain page, **Open secure bank confirmation** takes them to that page. They do not need to enter their card again, but the bank may still decline the request. Confirmation is available for up to 23 hours after the renewal request and only while enough time remains within the agreed limit. Without confirmation, the original hold is not extended. While an attempt is unresolved, capture and release pause to prevent acting on the wrong reservation. **Check renewal status** checks the existing attempt; **Cancel renewal attempt** cancels the replacement only and keeps the original hold when it is still valid. If an uncertain attempt has no saved provider reference, contact support; do not create another deposit to retry it. The provider-confirmed deadline always applies. PayRequest conservatively requires at least seven days remaining within the 30-day agreement before requesting another authorization. A final short extension may therefore be unavailable. A replacement that does not extend the original deadline or would exceed the agreement is canceled. If the customer withdraws permission, use **Withdraw permission for further renewals**. This also cancels an unresolved replacement when its exact provider reference is available. It does not refund a charge or release a previously completed hold. Existing holds remain manageable after a plan change; new renewals require Business. ## Repeated clicks, uncertain attempts and expired checkout links For the same tracked Stripe deposit, opening authorization again reuses its existing **open** session after checking the merchant, request, amount and currency. It does not intentionally create a second session for the same request. If a previous provider request has no confirmed response, PayRequest blocks another start and asks the customer to contact support. Expired or completed sessions are not automatically replaced. This avoids a new reservation while an earlier result is still uncertain. Contact PayRequest support to verify the provider records before arranging any new authorization. A **different request or another payment link** must be checked separately; this protection does not prove that no other hold exists. ## When a customer says the hold is still there 1. Find the exact reservation and check its latest provider status, original amount, remaining reservation, charged amount and release time. 2. If release is not confirmed, investigate the provider result before telling the customer it is released. For Stripe, use **Check Stripe** and **Check linked authorization** as appropriate. 3. If release is confirmed, give the customer the released amount, confirmation time with timezone and payment reference. Explain that the bank controls when its display and available funds update. 4. If they report a second hold, investigate **both** entries. Compare amounts, currencies, dates, card last four digits and authorization references. A different displayed date alone does not prove a new authorization; it also does not prove ordinary bank delay. 5. Ask for a cropped screenshot if needed, with unrelated transactions and sensitive details hidden. Never request a full card number, security code or login code. > [!WARNING] > > Do not capture and refund a reservation merely to make it disappear from a bank app. Releasing the remaining hold does not refund a previously captured payment. Treat any refund request separately. ## Share instructions with your customer Send the [customer security-deposit guide](/customer-guide/security-deposits) alongside the original deposit link. It explains authorization, pending bank entries, releases, partial charges and how to get help. The [Customer Guide](/customer-guide/overview) also covers payment pages and customer accounts. You can adapt this release message after checking the provider result: > We have confirmed the release of your \[amount and currency] card reservation on \[date, time and timezone]. Your bank controls when the pending entry disappears and your available funds update. Because this was a reservation, you may not see a separate refund. If it remains visible, we can provide the payment reference for your card issuer to investigate. Use the **remaining released amount**, not the original deposit amount, if part was charged. Do not send a release confirmation while the provider result is still uncertain. ## Creating a Deposit Product ### Step 1: Create a New Product Navigate to **Products** in your dashboard and click **New Product**. 1. In the product type step, select **Security Deposit** 2. Give your product a descriptive name (e.g., "Airbnb Deposit", "Car Rental Borg") ### Step 2: Configure Deposit Settings In the pricing step, configure the deposit-specific settings: **Hold Duration** (Required) * How many days the authorization hold remains active * Options: 1 to 28 days * This setting is not a promise of the bank authorization window or an automatic release appointment * Check the provider-confirmed deadline after authorization and release explicitly after inspection * For a longer rental, confirm provider eligibility before relying on a longer hold **Allow Partial Capture** (Optional) * Enable to charge only part of the deposit * Example: €500 deposit, charge €75 for a broken item * When disabled, you can only capture the full amount **Deposit Instructions** (Optional) * Custom instructions shown to customers * Explain what the deposit covers * Example: "This deposit covers potential damages during your stay" > [!NOTE] > > The deposit amount is set as the regular product price. Set it to the maximum amount you want to hold (e.g., €500 for a hotel deposit). ### Step 3: Save and Share After saving your deposit product, you can share it via: * **Smart Links** (recommended) — Create a branded payment link * **Payment Page** — Send customers directly to your payment page ## Using Deposits with Smart Links The recommended way to collect security deposits is through **Smart Links**. This gives you a branded URL, analytics tracking, and a centralized management interface. You can also open **Security Deposits → Create Deposit Link** in the dashboard. A deposit collected through a payment link is managed in the same Security Deposits list, even when it has no linked product. ### Creating a Deposit Smart Link 1. Go to **Payment Page** → **Smart Links** tab 2. Click **Create Smart Link** 3. Select **Product Link** as the type 4. Choose your deposit product 5. Give it a descriptive name (e.g., "Airbnb Borg 2025") 6. Optionally add a description explaining the deposit 7. Click **Create** ### Managing Deposits in Smart Links All deposits collected through a smart link appear in the **Deposits tab** on the smart link detail page. For each deposit, you can see: **Deposit Information:** * Customer name and email * Amount held * Authorization status with colored badge * Authorization date * Mollie payment ID * Customer-facing status page URL **Hold Duration Progress:** * Visual progress bar showing elapsed vs. remaining time * Days remaining counter * Start and end dates * Turns red when nearing expiration (2 days or less) **Capture History:** * Table of all captures with amounts * Capture status (Succeeded/Failed) * Timestamps and descriptions ## Find a Deposit and Capture an Amount **1. Open Security Deposits** Sign in to the business account that collected the deposit and open [Security Deposits](https://payrequest.app/deposits) in the dashboard sidebar. You do not need to open Customers first. **2. Open the customer's deposit** Search by customer name, email, or booking reference. Click the **underlined customer name**, or **View** in the Actions column on the right. On a narrow screen, scroll the table horizontally to reach Actions. **3. Check the reservation** **Funds reserved** means the card authorization has been confirmed. Check the capture deadline. A waiting, processing, failed, or expired authorization cannot be captured. **4. Choose full or partial capture** At the top of the detail page, select **Capture Full Amount** or **Partial Capture**. Partial Capture appears when partial capture is enabled in the deposit's product or payment-link settings. Enter the amount to charge and optionally describe the reason. **5. Review and confirm** For Stripe deposits, the confirmation shows the amount charged, the amount released, the PayRequest platform fee, and the notice about separate Stripe fees. Opening this window does not charge the customer. The final **Capture** button charges the displayed amount. ### One final capture with Stripe > [!WARNING] > > The current Stripe deposit flow supports **one capture**, whether full or partial. When you capture part of a deposit, Stripe releases the unused amount. You cannot make a second capture from that authorization. Decide the total amount you need before confirming. For example, from a **€350** Stripe deposit: | Action | Charged | Released | Available for another capture | | - | - | - | - | | Capture €150 | €150 | €200 | €0 | | Capture the full €350 | €350 | €0 | €0 | After a successful partial Stripe capture, the deposit is marked **Captured**. The detail page explains the charged and released amounts, the Captures tab records the charge, and the capture buttons disappear. Captured means the capture is complete; it does not necessarily mean the original deposit was charged in full. Stripe Multicapture is **not enabled in PayRequest**. It would require Stripe eligibility and approval for the merchant's business and use case, as well as integration support. It cannot restore funds already released from an existing deposit. Other providers have their own capture restrictions; do not assume that enabling partial capture also enables multiple captures. ### Fees on Stripe deposit captures PayRequest charges **0% platform fees on Stripe security-deposit captures**. Stripe processing fees remain separate and are deducted from the captured amount. Their exact amount depends on the card and your Stripe pricing. If you capture **€100**, the PayRequest platform fee is **€0**. Your net payout is €100 minus Stripe's fees. The capture window does not promise a net payout or automatically increase the charge to cover processing costs. Your Business subscription price is separate from these payment-processing fees. ### Releasing a Deposit When no charges are needed (e.g., property returned in perfect condition): 1. Open the deposit detail page and click **Release Hold** 2. Confirm the release action 3. Check that the provider confirms the release. The bank determines when the pending entry disappears and the available balance or credit updates. > [!WARNING] > > Releasing a deposit cannot be undone. Once released, the authorization hold is permanently voided and you cannot capture any amount from it. ## Customer Status Page Customers should keep the exact status link generated for their request. Payment-page deposits can use a branded URL such as: ``` https://payrequest.me/[your-handle]/deposit/[token] ``` ### What Customers See The branded payment-page status view can show the following details. A standalone quick-deposit link may use a simpler authorization/status view; do not promise all fields on every link: * **Status Badge** — Color-coded indicator in the top-right corner (Hold Active, Partially Charged, Released, etc.) * **Smart Link Title & Description** — Your custom title and description from the smart link * **Amount** — The held amount with a status-appropriate icon * **Details** — Booking reference, authorization date, hold expiry with countdown * **Hold Duration Progress Bar** — Visual indicator of remaining hold time * **Capture History** — All captures with amounts, descriptions, and timestamps * **Info Callout** — Status-specific explanation of what happens next > [!NOTE] > > The branded status view refreshes periodically. Provider updates can arrive later; reopening a page does not create or confirm a new reservation. A separate quick-deposit page may need to be reopened to show an updated status. ### Status States | Status | Badge Color | Description | | - | - | - | | Awaiting Authorization | Amber | A successful card authorization has not yet been confirmed | | Hold Active | Blue | Amount held on card, awaiting capture or release | | Partially Charged | Indigo | Part of the hold has been captured | | Deposit Charged | Amber | Capture completed; check the actual captured amount | | Deposit Released | Green | Remaining hold released; any previous captured amount is separate | | Hold Expired | Red | Authorization hold expired | ## Dashboard Statuses and Next Steps The dashboard uses clear authorization labels instead of a single Pending label. Use the matching filters in the Security Deposits list to find deposits that need attention. | Dashboard status | Meaning | What to do | | - | - | - | | **Waiting for customer** | No successful authorization has been confirmed. The customer may still need to enter card details or finish their bank verification. | Ask the customer to complete the authorization. | | **Processing authorization** | The provider confirms it is processing the authorization; the reservation is not confirmed yet. | Wait for confirmation. Do not ask the customer to pay again yet. | | **Authorization attempt expired** | The checkout attempt has expired. This does not rule out another authorization. | Check Stripe reservations and exact references. Do not automatically ask the customer to authorize again. | | **Funds reserved** | The card authorization is confirmed and the amount is held. | Capture or release before the displayed deadline. | | **Captured** | The capture has completed. A Stripe partial capture also closes the authorization and releases the unused amount. | Review the charged and released amounts and capture history. | | **Partially Captured** | A provider-specific partial capture is recorded. This does not guarantee another capture is possible. | Check the remaining capturable amount and available actions. | | **Released** | The remaining reservation has been released. | No further capture is available. | | **Expired** | A previously reserved hold has reached its expiry. | A new authorization is required to reserve funds again. | | **Failed** | The authorization or payment attempt failed. | Check the deposit details before asking the customer to retry. | > [!NOTE] > > **Authorization attempt expired** and **Expired** are different: one concerns a checkout attempt and the other an existing authorization. Neither is evidence about a different payment reference. Creating or opening a link alone does not reserve money. Stripe attempt status is updated from provider-confirmed information, not simply from the age of the deposit. The [API](/api/security-deposits) retains its existing machine-readable status values. Dashboard labels do not introduce new API status values. ## Use Cases ### Hotel / Airbnb Deposit ``` Product: Room Deposit Amount: €250 Hold Duration: 14 days Partial Capture: Enabled Scenario: 1. Guest authorizes €250 at check-in 2. Guest checks out after 5 nights 3. Inspection reveals a stained carpet 4. Host captures €60 for cleaning fee 5. With Stripe, the remaining €190 is released automatically when the capture completes ``` ### Car Rental Deposit ``` Product: Vehicle Deposit Amount: €1,000 Hold Duration: 7 days Partial Capture: Enabled Scenario: 1. Customer authorizes €1,000 when picking up the car 2. Customer returns car after 3 days 3. Inspection shows a scratch on the bumper 4. Agency captures €350 for repair 5. Remaining €650 is released ``` ### Equipment Rental ``` Product: Camera Equipment Deposit Amount: €500 Hold Duration: 3 days Partial Capture: Disabled Scenario: 1. Customer authorizes €500 for a camera rental 2. Customer returns equipment in perfect condition 3. Business releases the full €500 hold ``` ### Event Venue Deposit ``` Product: Venue Deposit Amount: €2,000 Hold Duration: 7 days Partial Capture: Enabled Scenario: 1. Client authorizes €2,000 for venue rental 2. Event concludes, venue inspection done 3. Minor cleanup needed beyond agreement 4. Venue captures €150 for extra cleaning 5. Remaining €1,850 is released ``` ## Email Notifications For tracked deposits, PayRequest sends confirmations after a confirmed reservation, charge or release to the business and the available customer email. The message identifies the business, deposit and amount, explains the recorded action and includes the customer status link when available. Reservation messages include the authorization deadline when known. Confirm the customer email before sharing a request. A missing email does not prove that no hold exists. Status checks do not send historical confirmations for unlinked provider records. ## Best Practices ### Setting Hold Duration * Plan authorization close enough to the rental that inspection can occur before the provider deadline. * Check the exact deadline once funds are reserved; eligibility for longer holds varies. * Release explicitly after inspection when no charge is needed. * Do not rely on the product duration to extend an authorization or arrange an automatic release. ### Communication * Use the **Deposit Instructions** field to clearly explain what the deposit covers * Add a descriptive **Smart Link description** so customers understand the purpose * When capturing, always add a description explaining the charge reason ### Amount Guidelines * Set deposits proportional to potential damage costs * Don't set deposits unreasonably high — it ties up customer funds * Consider your industry standards and customer expectations ## Frequently Asked Questions > [accordion] Why can customers only pay with credit card? > > Security deposits require a payment method that supports authorization holds. The deposit checkout uses supported cards; payment methods such as iDEAL and SEPA do not provide this card-authorization flow. > [accordion] What happens if I don't capture or release before the hold expires? > > The payment provider and card issuer determine authorization expiry. Check the exact deadline on the deposit; the product duration alone does not release funds. Once the actual authorization expires it cannot be captured, and the bank controls when available funds update. > [accordion] What if I need more than seven days? > > Eligible Stripe accounts and cards may receive a longer hold at the first authorization. If the deadline is still too short, Business can request a replacement near expiry when the customer agreed to saved-card renewal beforehand. The merchant receives an expiry warning around 48 hours before the current deadline. The customer usually does not need to enter their card again, but the bank can require confirmation or decline. Replacements must stay within 30 days of the first authorization; a final short extension is not guaranteed. See [Stripe deposit renewal](#renew-a-stripe-deposit-on-business) for the steps and limits. > [accordion] Can I capture more than the original hold amount? > > No. You can only capture up to the original authorized amount. If damage costs exceed the deposit, you'll need to invoice the customer separately for the difference. > [accordion] How quickly do released funds appear in the customer's account? > > The card issuer controls this. Updating the pending entry and available funds may take several days; do not promise a universal number of business days. Give the customer the confirmed release time and payment reference if their bank needs to investigate. An uncaptured reservation usually does not produce a separate incoming refund. > [accordion] Can I make multiple partial captures? > > Not with the current Stripe deposit flow. A €150 capture from a €350 deposit releases the remaining €200, so you cannot capture another €50 later. Partial capture means choosing a smaller amount for the final capture, not splitting the authorization into multiple charges. Other providers have their own restrictions. > [accordion] Why can I not find the capture button? > > Open Security Deposits in the dashboard, then click the underlined customer name or View. Capture buttons appear on the deposit detail page when there is a confirmed, unexpired reservation. A waiting, processing, expired, released, or already finalized Stripe deposit cannot be captured. Partial Capture also requires partial capture to be enabled in the deposit settings. > [accordion] How much does PayRequest charge if I capture €100 with Stripe? > > The PayRequest platform fee for a Stripe security-deposit capture is €0 (0%). Stripe's own processing fees still apply, so the net payout depends on the card and your Stripe pricing. > [accordion] Is there a minimum capture amount? > > The capture amount must be greater than zero. There is no other minimum — you can capture as little as €0.01 if needed. > [accordion] Can customers see their deposit status? > > Yes. Every deposit has a unique status page URL that customers can visit to see the current status, amount held, hold duration progress, and capture history. The URL is visible in the smart link deposits tab. > [accordion] What's the maximum hold duration? > > The product offers a duration setting, but the actual authorization window depends on the payment provider, payment method and account eligibility. Use the provider-confirmed deadline, not a duration selected in advance. See [Deposit Hold Duration](/payment-processing/deposit-hold-duration). > [accordion] Do I need a Business plan for security deposits? > > Free includes 3 new security deposit requests per calendar month, with at most 1 open request at a time. Premium (€5/month) includes 15 new requests per calendar month and at most 5 open requests at a time. Business (€20/month) and Growth include unlimited security deposits. Payment-provider fees remain separate. Existing eligible Premium subscriptions retain unlimited access while that same subscription remains active. These limits apply to creating new deposits; you can still manage, capture, and release existing deposits. ## Need Help? > [card] [Smart Links](/payment-processing/smart-links) > > Create branded payment links for deposits > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > Understanding payment methods > [card] [Handling Chargebacks](/payment-processing/handling-chargebacks) > > Managing payment disputes # Set up your payment provider Source: https://docs.payreque.st/payment-processing/setting-up-payment-providers Connect an eligible payment account, check payment readiness and request another provider. Your payment provider processes customer payments through your own merchant account. PayRequest supplies the payment and billing workflow. Creating a PayRequest account or selecting a paid plan does not approve your business with a payment provider. ## Choose an available connection During onboarding, the main connections are **Stripe, Mollie and PayPal**, subject to your legal account country, provider availability and receiving permissions. Choose from the connections actually offered in your account. | Provider | Check before connecting | | - | - | | Stripe | You need an eligible Stripe account that can accept payments. A Paystack account is separate and cannot be connected as Stripe. | | Mollie | You need an eligible business account that can receive payments. Authorization may be followed by further business verification. | | PayPal | Use a PayPal Business account approved to receive payments. A send-only account is insufficient. | The methods available to a buyer depend on the provider, merchant approval, payment flow, amount and currency. Connecting a provider does not enable every payment method or every recurring-billing feature. ## Connect your account 1. [Open onboarding](https://payrequest.app/onboarding). If setup is already complete, open **Provider Settings** in your account. 2. In onboarding, confirm the country where your business or payment account is legally registered. Your detected location is only a suggestion. 3. Select **Connect** for an available provider. Your saved Stripe, Mollie or PayPal choice appears first in onboarding. 4. Sign in on the provider's own page and authorize PayRequest. Complete any provider verification that remains. 5. Return to PayRequest and check the connection status before sharing a payment link. > [!NOTE] > > Returning from the provider, or seeing an account linked, does not by itself confirm that payments can be received. Payment readiness is checked separately. For a connection that is incomplete, cancelled or awaiting verification, follow the [onboarding troubleshooting steps](https://docs.payreque.st/getting-started/onboarding#payment-connection-not-complete). **I'm stuck** opens a draft email with your account and connection status; review and send it yourself. Do not email passwords or API keys. ## Request a different provider Onboarding offers **Square, Paystack, Razorpay, Payfast and Payoneer** as integration requests for review. Choose **My payment provider is not listed** for another name and describe your needs before submitting. A provider in the intake list records what you use or want to use. It is not a list of live integrations. Requests do not connect an account, grant access or promise availability or a delivery date. See [requesting a provider](https://docs.payreque.st/getting-started/onboarding#request-another-payment-provider). **Payoneer is currently an onboarding request option.** Do not assume a normal Payoneer account can be connected for Checkout. See [Payoneer availability](https://docs.payreque.st/payment-processing/connect-payoneer). ## Existing connections and billing You can manage the providers offered in your account from Provider Settings. Check each connection's receiving status and the payment methods enabled for the flow you use. Before disabling or replacing a provider, review active subscriptions, stored payment agreements, pending payments and refunds. Connecting another provider does not automatically move those agreements or historical payments. A default provider setting does not override payment-method eligibility or an existing payment agreement. For automatic recurring billing, follow the setup for your provider and subscription type. Some flows require a customer mandate or additional provider permissions. See [subscription payment methods](https://docs.payreque.st/subscriptions/payment-methods). ## Mollie Apple Pay and Klarna You can offer Apple Pay and Klarna on your existing PayRequest Page and payment links when your Mollie profile is approved for them. Enable cards and Apple Pay together in Mollie, enable Klarna if available, and include the methods in any custom PayRequest method selection. Apple Pay appears only in supported browsers. Klarna asks the buyer for name, email and a full billing address; its available options and approval are decided by Klarna. Follow the separate setup guides for [Apple Pay](https://docs.payreque.st/payment-methods/apple-pay) and [Klarna](https://docs.payreque.st/payment-methods/klarna). ## Mollie Pay by Bank If available for your account, activate Pay by Bank on your Mollie website profile and include it in your PayRequest payment-method selection. Automatic EUR subscription collection also requires the appropriate SEPA Direct Debit setup: the first bank payment establishes the mandate and later payments use SEPA. See [Pay by Bank](https://docs.payreque.st/payment-processing/pay-by-bank). This is different from reconciling a transfer received in your bank account through Ponto. ## Fees and next steps PayRequest plan fees and provider processing fees are separate. Review your current [PayRequest plan](https://docs.payreque.st/business-settings/payrequest-plans) and your provider agreement rather than assuming that a method or plan removes all fees. * [Stripe](https://docs.payreque.st/payment-processing/connect-stripe) * [PayPal](https://docs.payreque.st/payment-processing/connect-paypal) * [Create a payment link](https://docs.payreque.st/payment-processing/smart-links) * [Receive and reconcile bank transfers](https://docs.payreque.st/payment-processing/bank-transfer) # Share Your Crypto Address Source: https://docs.payreque.st/payment-processing/share-wallet-address Get a branded link with your wallet address, QR code, and copy button — perfect for X giveaways, donations, and tip jars # Share Your Crypto Address Every connected crypto wallet automatically gets its own shareable link on your `payrequest.me` page — a clean, branded card with a QR code and a one-tap **copy address** button. Drop the link anywhere you'd normally paste a wallet address: X/Twitter giveaways, Discord, a tip jar, or a "buy me a coffee" post. > [!NOTE] > > No setup needed beyond connecting the wallet itself (Provider Settings or Business Details). Once a wallet address is saved, its share link works immediately. ## Your Address Links | Asset | Link | Requires | | - | - | - | | Solana (SOL) | `payrequest.me/{yourname}/sol` | `solana_wallet_address` connected | | Bitcoin (BTC) | `payrequest.me/{yourname}/btc` | BTC address set in Business Details | | Base / Ethereum (ETH) | `payrequest.me/{yourname}/eth` | EVM wallet connected | Replace `{yourname}` with your PayRequest handle — the same one used in your main payment page URL (`payrequest.me/{yourname}`). > [!TIP] > > Don't have a wallet connected for an asset yet? Visiting that link returns a friendly "not configured" message instead of an error — connect the wallet first, then the link goes live instantly. ## What Visitors See The address page uses the **same branding as your main payment page**: * Your avatar, name, and tagline (or logo + business name) * Your social links (X, LinkedIn, GitHub, website) * Your accent color and page theme (Solana / Crypto Native, if set) * A QR code for the address * The address itself in a copy-to-clipboard field * The "Secure · Encrypted · Powered by PayRequest" trust footer Visitors can scan the QR code with any wallet app, or tap the copy icon to grab the address as text — no account or login required. ## Requesting a Specific Amount You can also pre-fill an amount by adding it to the link: ``` payrequest.me/{yourname}/10usd/sol payrequest.me/{yourname}/25eur/btc payrequest.me/{yourname}/5gbp/eth ``` This shows the same branded card, plus the equivalent amount in crypto (converted at the current exchange rate) and a countdown showing when the rate will refresh. Useful for invoicing a specific person a round amount without creating a full invoice. > [!WARNING] > > Supported fiat codes are `usd`, `eur`, and `gbp`. The amount is informational only — the page does not verify or track payments. For payments you need confirmed and reconciled automatically, use your full [payment page](/payment-processing/payment-methods-overview) or [Smart Links](/payment-processing/smart-links) instead. ## Use Cases > [card] Social giveaways > > Drop your `/sol` link in a giveaway post — entrants get a clean page with your address and a QR code, with your branding front and center. > [card] Tip jar / donations > > Add the link to your bio or stream overlay so people can quickly tip you in BTC, SOL, or USDC on Base. > [card] Quick one-off requests > > Send a friend or client `payrequest.me/{yourname}/25eur/sol` instead of typing out an address and amount in chat. > [card] Print or QR display > > Print the QR code on a flyer, business card, or table tent for in-person crypto tips and donations. ## Frequently Asked Questions > [accordion] Do I need to enable anything to use this? > > No. As soon as a wallet address is saved on your account (Solana, Base/ETH, or BTC), its share link is live at `payrequest.me/{yourname}/{asset}`. > [accordion] Does this page track or confirm payments? > > No. It's a static "here's my address" page — a QR code and a copy button. To accept and automatically reconcile payments, use your [payment page](/payment-processing/payment-methods-overview) or a [Smart Link](/payment-processing/smart-links). > [accordion] Can I change how the page looks? > > Yes — it inherits your PayRequest Page styling: avatar, tagline, social links, accent color, and [crypto page theme](/shop-and-checkout/crypto-page-themes) all carry over automatically. > [accordion] What happens if I haven't connected a wallet for that asset? > > The link returns a "this merchant has not configured a wallet" message. Connect the wallet in Provider Settings or Business Details and the link starts working right away. ## Next Steps > [card] [Solana USDC Payments](/payment-processing/solana-pay) > > Accept full checkout payments via Solana Pay QR codes. > [card] [Crypto Page Themes](/shop-and-checkout/crypto-page-themes) > > Give your page a Solana or Crypto Native look. > [card] [Supported Crypto Wallets](/payment-processing/crypto-supported-wallets) > > Connect a Base/EVM wallet to receive USDC. > [card] [Smart Links](/payment-processing/smart-links) > > Create shareable payment links with fixed amounts. # Smart Links Source: https://docs.payreque.st/payment-processing/smart-links Create branded payment links, request another payment from an existing customer, and manage payment status, sharing, and reminders ## Overview Smart Links are reusable, branded payment URLs designed for marketing campaigns, social media sharing, QR code payments, and flexible payment options such as partial payments. Unlike dynamic payment page links that need to be generated each time, Smart Links provide a permanent, memorable URL that you can share anywhere. > [!TIP] > > Smart Links are perfect for social media campaigns, QR codes on flyers, email signatures, or any situation where you want a clean, memorable payment URL with analytics tracking. ### Partial Payments PayRequest supports split payment Smart Links that collect payments in multiple sequential stages. Each customer can pay the upfront amount first, then complete the remaining balance later through the same Smart Link URL. * The payment page shows a payment progress visualizer with the number of confirmed payment stages out of the total requested. * Customers see the current due amount and payment method options for installment payments. * Sellers can track partial payment status and use payment reminders for outstanding stages. This capability complements invoice partial refunds and separate debt collection payment plans by offering flexible, staged payment requests before invoice completion. See the sections below for details on how partial payments appear and behave for customers. ## Key Features * **Pretty URLs**: `https://payrequest.me/[businessname]/[path]` * **Embed Button Snippet**: Copy a styled HTML button (Blue / Dark / Outline) and paste it on any website or WordPress page * **QR Code Generation**: Automatic QR code for every smart link * **Analytics Tracking**: View counts, payment counts, revenue, and conversion rates * **Four Link Types**: Product checkout, fixed amount, security deposit, or invoice bundle * **Payment Limits**: One-time, multiple, or unlimited payment options * **SMS & Email Delivery**: Send links directly to customers via SMS or email * **Payment Reminders**: Automatic follow-up reminders for unpaid links * **Tag Support**: Organize smart links with tags for easy management * **Repeat Customer Payments**: Start an editable one-time Amount Link from a customer's previous payment without creating a product * **Payment Status Filters**: Find links with paid transactions or no linked payments, and search by customer * **Active/Inactive Toggle**: Quickly enable or disable links * **After-Payment Actions**: Redirect customers or update tags after successful payment * **Access Code Protection**: Require a code before visitors can pay, ideal for links shared publicly but meant for a specific audience * **Renewable Timed Access**: Sell a fixed number of access days through the same reusable Amount Link * **Telegram Delivery**: Give each paying customer a personal invite to a private group or channel ## Accessing Smart Links Navigate to **Payment Page** in your dashboard sidebar, then click the **Smart Links** tab. > [!NOTE] > > Smart Links are available for all PayRequest accounts. The feature integrates seamlessly with your existing payment page setup. ## URL Structure Every smart link follows this format: ``` https://payrequest.me/[your-handle]/[path] ``` **Example:** ``` https://payrequest.me/acme-corp/summer-sale ``` * **`[your-handle]`**: Your payment page handle or business name * **`[path]`**: Custom URL path (auto-generated from link name) > [!NOTE] > > The path is automatically generated from your link name, but you can customize it when editing the smart link. ## Creating a Smart Link ### Step 1: Choose Link Type When creating a new smart link, first select the type: **Product Link** * Links directly to a specific product * Redirects to your shop's product page * Best for: Product promotions, catalog links, shop items **Amount Link** * Fixed payment amount * Renders directly on payment page (keeps smart link URL visible) * Best for: Donations, event tickets, service fees **Deposit Link** (Product Link with a Deposit product) * When you select a Security Deposit product, the smart link becomes a deposit link * Customers pay via credit card authorization hold (amount is held, not charged) * Deposits tab appears on the smart link detail page for capture/release management * Best for: Hotel deposits, car rental holds, equipment guarantees **Invoice Bundle Link** * Bundles multiple open invoices into a single, one-click payment link * Customer sees all invoices with invoice numbers, amounts, and due dates — plus a total * One Mollie payment covers all selected invoices; all invoices are marked paid automatically when payment succeeds * Best for: Collecting multiple overdue invoices in one go, end-of-month payment consolidation > [!TIP] > > Choose "Amount Link" for marketing campaigns where you want the branded URL to remain visible during checkout. For security deposits, create a [Deposit product](/payment-processing/security-deposits) and use a Product Link. For collecting multiple outstanding invoices from a single customer at once, use an Invoice Bundle Link. ### Step 2: Configure Link Details **Required Fields:** * **Name**: Descriptive name for the link (e.g., "Summer Sale Promotion") * **Type**: Product, Amount, or Invoice Bundle * **Product** (for product links): Select from your product catalog * **Amount & Currency** (for amount links): Set fixed payment amount * **Customer + Invoices** (for invoice bundle links): Select the customer, then tick the open invoices to include — the total is calculated automatically **Optional Fields:** * **Description**: Public description shown to customers (supports rich text — this is displayed on the payment page and in the email) * **Tags**: Organize links by campaign, category, or purpose > [!NOTE] > > Invoice Bundle links require selecting a **customer** first. Only invoices with status **open**, **sent**, or **overdue** are shown for selection — already-paid invoices are excluded automatically. ### Step 3: Set Payment Limit (Optional) Control how many times your smart link can be used for payments: **Unlimited** (Default) * Link stays active indefinitely * Accepts unlimited payments * Best for: Ongoing campaigns, permanent donation links **One-time** * Link automatically disables after the first successful payment * Prevents multiple uses * Best for: Individual invoices, one-time offers, exclusive deals **Multiple times** * Set a custom limit (1-1000 payments) * Link disables when limit is reached * Shows remaining payment count in analytics * Best for: Limited inventory, early bird tickets, capacity-limited events > [!TIP] > > Payment limits are perfect for scarcity marketing. Show "Only 50 spots left!" and the link automatically disables at the limit. **How it works:** 1. Select payment limit type when creating the link 2. For "Multiple times", enter the maximum number of payments (1-1000) 3. Smart link tracks successful payments automatically 4. When limit is reached, customers see "Payment limit reached" message 5. You can view remaining payments in the analytics dashboard > [!NOTE] > > Payment limits only count successful (paid) transactions. Failed or pending payments don't count toward the limit. ### Step 3b: Protect with an Access Code (Optional) Require visitors to enter a code before they can see and use the payment page. This is useful when a link is shared in a public or semi-public place (a newsletter, a social post, a community channel) but should only work for a specific group of people. **How to enable it:** 1. While creating or editing the smart link, check **Protect with access code** 2. Enter a code, or click **Generate** to get a random 6-character code 3. Save the smart link **What customers see:** * Opening the URL shows a branded "Access code required" page asking for the code * After entering the correct code once, the link works normally for the rest of that browser session * An incorrect code shows an error message; repeated wrong attempts are temporarily rate-limited > [!TIP] > > Use access codes for invite-only pre-orders, community discounts, B2B pricing shared with a specific client, or any "amount" or "deposit" link you don't want to be fully public even though the URL itself isn't secret. > [!NOTE] > > The code is stored securely (hashed) and is never shown again after saving — when editing a protected link, leave the access code field blank to keep the existing code, or type a new one to replace it. > [!WARNING] > > Access code protection adds friction for legitimate customers too. For one-off payment requests sent directly to a single customer, the link itself is already private — an access code is usually unnecessary there. ### Step 3c: Grant Renewable Timed Access (Optional) An Amount Link can grant a customer access for a fixed number of days after a successful payment. This is useful for paid signal groups, coaching communities, premium newsletters, temporary support access, and other offers where customers renew by paying again. 1. Create or edit an **Amount Link** 2. Enable **Grant time-limited access after payment** 3. Enter the number of access days, such as `30` 4. Optionally select a connected **Telegram community** 5. Keep the payment limit set to **Unlimited** when customers should be able to renew 6. Save and share the Smart Link The public URL remains the same for every buyer and every renewal. PayRequest records access separately for each customer: * A first payment starts access from the payment time * A renewal made while access is active adds the new period to the existing expiry date * A renewal made after access expired starts a new period from the new payment time * Repeated payment notifications cannot accidentally add the same period twice > [!NOTE] > > For example, a customer with access through June 30 who pays again for a 30-day link receives access through July 30. Other customers using that same Smart Link retain their own independent access dates. > [!WARNING] > > Timed-access fulfillment is currently available for **PayPal Amount Links**. Do not promise automatic access delivery for another payment provider until that provider is listed here as supported. #### Deliver Access Through Telegram PayRequest treats Telegram as an optional delivery destination, not as a separate product type. The same timed-access link can therefore represent trading signals, a membership, a course community, or another paid service. **1. Connect your Telegram account** Open `@payrequestme_bot` in a private chat and send `/start`. Follow the secure connection link to sign in to your PayRequest account. **2. Add the bot to your community** Add `@payrequestme_bot` as an administrator of the private Telegram group or channel. The community is then registered automatically with the PayRequest account connected to your bot chat. **3. Select the community** Return to the Amount Link create or edit screen, enable timed access, and choose the community under **Telegram community**. **4. Share the payment link** After payment, the customer sees a personal Telegram join button on the PayRequest success page. Each invitation is valid for 24 hours and can be used by one person. PayRequest links the joined Telegram member to that customer's access period. When access expires, the bot removes the member automatically; after a renewal, the customer can receive a new invitation. > [!NOTE] > > The bot must remain an administrator with permission to create invite links and manage members. Removing the bot or its administrator permissions stops automatic invitations and expiration handling. > [!TIP] > > Connect and select the Telegram community before taking payments. Existing access grants do not automatically receive an invitation when a community is linked later. ### Step 4: Send to Customer (Optional) Send the smart link directly to a customer via email or SMS: **Delivery Options:** 1. **Select Customer**: Choose from your customer list 2. **Choose Delivery Method**: * **Email**: Send to customer's email address * **SMS**: Send to customer's phone number (requires valid international format) * **Both**: Send via both email and SMS simultaneously **Email Delivery:** * Uses your configured email template * Includes smart link URL * Professional branded message * Sent immediately upon creation **SMS Delivery:** * Requires valid phone number (international format: +31612345678) * Costs 1 SMS credit per message — every account starts with 1 free credit and earns 1 new credit for every payment received * Personalized message with customer name * Includes the payment link * Sent from your business name > [!WARNING] > > SMS delivery requires the customer to have a valid phone number in international format (starting with country code). Invalid numbers will disable the SMS option, and so will an empty SMS credit balance. > [!NOTE] > > Curious how SMS credits work? See the dedicated [SMS Payment Links](/payment-processing/sms-payment-links) guide. **Tracking:** * Delivery status shown on smart link detail page * Timestamp of when link was sent * Delivery method badges (Email/SMS) > [!TIP] > > Combine SMS and email delivery for important payment requests to ensure customers receive the link through their preferred channel. ### Step 4b: Enable Payment Reminders (Optional) Automatically send follow-up reminders to customers who haven't paid yet. This feature appears when you select a delivery method (Email or SMS). **Enabling Reminders:** 1. Select a customer and delivery method (Step 4) 2. Check **Enable Payment Reminders** 3. Configure reminder settings **Reminder Frequency Options:** * **Daily**: Send a reminder every day * **Every 2 days**: Send reminder every other day * **Every 3 days**: Send reminder every third day * **Weekly**: Send one reminder per week * **Monthly**: Send one reminder per month **Maximum Reminders:** * Set how many reminders to send (1-50) * Use the slider or input field to select * Reminders stop automatically when limit is reached * Reminders also stop when payment is completed > [!NOTE] > > Payment reminders use the same delivery method(s) you selected for the initial send. If you chose Email + SMS, reminders will be sent via both channels. **How Reminders Work:** 1. Initial smart link is sent to customer 2. If no payment received, first reminder sent based on frequency 3. Reminders continue until: * Customer completes payment, OR * Maximum reminder limit is reached **Example Configuration:** ``` Delivery Method: Email + SMS Reminder Frequency: Every 2 days Maximum Reminders: 5 Timeline: Day 0: Initial link sent Day 2: Reminder 1 (if unpaid) Day 4: Reminder 2 (if unpaid) Day 6: Reminder 3 (if unpaid) Day 8: Reminder 4 (if unpaid) Day 10: Reminder 5 (final reminder) ``` > [!TIP] > > For urgent invoices, use "Daily" frequency with 3-5 reminders. For less urgent requests, use "Weekly" or "Monthly" with more reminders. **Tracking Reminders:** When editing a smart link with reminders enabled, you'll see: * Number of reminders sent vs. limit * Next scheduled reminder date * Reminder status > [!WARNING] > > Reminders are only available when sending to a specific customer via delivery methods. They cannot be enabled for links shared publicly without a customer association. ### Step 5: Save and Share After creating your smart link: 1. Copy the generated URL 2. Download the QR code 3. Share via social media, email, or print materials ## Use Cases ### 1. Marketing Campaign Create an amount link for a limited-time promotion: ``` https://payrequest.me/fitnessstudio/early-bird-2025 ``` **Setup:** * **Type**: Amount Link * **Name**: Early Bird Registration 2025 * **Amount**: €49.00 * **Description**: Special early bird discount - Register before December 31st! **Where to share:** * Social media posts * Email newsletters * WhatsApp messages * Website banners ### 2. Event Registration Fixed-price event ticket payment: ``` https://payrequest.me/techconference/ticket ``` **Benefits:** * Clean, memorable URL * Track registrations in real-time * See conversion rate from social media * QR code for physical posters ### 3. Donation Link Permanent donation link for non-profit: ``` https://payrequest.me/charity/donate ``` **Features:** * Fixed suggested amount (customers can change if payment page allows) * Track total donations * Calculate average donation size * Share QR code in physical locations ### 4. Product Promotion Direct link to specific product with tracking: ``` https://payrequest.me/webshop/premium-bundle ``` **Advantages:** * Shorter than dynamic product links * Track which campaigns drive sales * Measure conversion from different channels * Professional branded URL ### 5. QR Code Payments Print QR code on invoices, receipts, or signage: **Use cases:** * Restaurant table payments * Service provider invoices * Retail store deposits * Event entrance fees ### 6. Limited Early Bird Campaign with SMS Create scarcity with payment limits and instant SMS delivery: ``` https://payrequest.me/gym/early-bird-50 ``` **Setup:** * **Type**: Amount Link * **Amount**: €39.00 (normal price €59) * **Payment Limit**: Multiple times - 50 payments * **Delivery**: Send to existing customers via SMS * **Message**: "🎉 Early bird special! Only 50 spots at €39. Link: \[URL]" **Benefits:** * Creates urgency with visible limit counter * Instant SMS delivery to customer database * Automatic deactivation at 50 payments * Track conversion rate by delivery method * Shows "X payments remaining" in real-time **Marketing Strategy:** 1. Send initial batch via SMS to VIP customers 2. Share link on social media once SMS customers claim spots 3. Monitor analytics to see SMS vs social media conversion 4. Link automatically closes when limit reached ### 7. Invoice Bundle — Collect Multiple Overdue Invoices Send a client a single link covering all their outstanding invoices: ``` https://payrequest.me/hostingwalk/openstaande-facturen-maart ``` **Setup:** * **Type**: Invoice Bundle Link * **Customer**: Select the customer (e.g., Acme BV) * **Invoices**: Tick all open/overdue invoices (e.g., INV-2025-041, INV-2025-042, INV-2025-043) * **Total**: Calculated automatically (€ 1.850,00) * **Delivery**: Email + SMS * **Description**: Optional message explaining the situation **What the customer sees:** * A dark-themed payment page listing all their open invoices with invoice numbers, amounts, and due dates * An "Overdue" badge on invoices past their due date * A clear total and a single **Pay** button * After payment, a confirmation page with processing status **After payment:** * All bundled invoices are automatically marked **paid** in PayRequest * Each invoice records the Mollie payment ID for audit trail * The smart link's analytics increment (views + payments) > [!TIP] > > Add a description like "Your hosting has been suspended. Please settle all outstanding invoices below to restore service." — it appears above the invoice list on the payment page and in the email. ## Analytics Dashboard Every smart link tracks comprehensive analytics: ### Key Metrics **Views** * Total number of link visits * Tracks every time someone opens the URL * Blue icon with eye symbol * **Detailed view tracking**: IP address (masked), browser/OS, referer, timestamp **Payments** * Successful payments through this link * Green icon with credit card symbol * Shows conversion percentage: `(payments / views) × 100` **Revenue** * Total amount collected via this smart link * Purple icon with euro symbol * Shows average payment value: `revenue / payments` ### Payment Limit Tracking For smart links with payment limits, the detail page shows: **Remaining Payments Badge:** * Color-coded status indicator * Green: 4+ payments remaining * Orange: 1-3 payments remaining * Red: Limit reached **Payment Limit Card:** * Current limit type (One-time, Multiple, Unlimited) * Total limit (for multiple payment links) * Remaining payment count * Percentage of limit used > [!NOTE] > > When a payment limit is reached, the smart link automatically becomes inactive and displays a "Payment limit reached" message to customers. ### Delivery Information If you sent the smart link to a customer, the detail page displays: **Delivery Card:** * Delivery methods used (Email/SMS badges) * Timestamp of when link was sent * Relative time (e.g., "2 hours ago") ### Activity Log (Tabbed Interface) The smart link detail page shows a comprehensive activity dashboard with four tabs: #### All Tab Overview of all activity combined, sorted by date (newest first): * Payment events * View events * Link sent events * Reminder events #### Views Tab Detailed view analytics with pagination (10 per page): **Information tracked per view:** * Timestamp (e.g., "Dec 14, 2025 17:47") * Browser & OS (e.g., "Chrome / Mac", "Safari / iOS") * IP address (masked for privacy: "192.168.1.xxx") * Referer URL (where visitor came from) * Relative time (e.g., "2 hours ago") > [!NOTE] > > Detailed view tracking records every visit with analytics data. IP addresses are automatically masked (last octet hidden) for visitor privacy. #### Payments Tab All payments through this smart link with pagination: * Customer name * Payment date and time * Invoice number (if applicable) * Amount paid * Payment status badge #### Reminders Tab Reminder status and history: **Settings Summary:** * Frequency (Daily, Every 2 days, etc.) * Sent count vs. limit (e.g., "1 / 3") * Remaining reminders **Reminder Events:** * Sent reminders with timestamp * Scheduled reminders showing "Upcoming" status **Activity Timeline Features:** * Tab-based organization for easy navigation * Pagination for large datasets * All events sorted by date (newest first) * Different colored icons for quick identification * Amount displayed for payment events * Status badges for each activity type > [!NOTE] > > Activity data updates in real-time. New payments, views, and reminders appear immediately across all tabs. ## Managing Smart Links ### Payment Links Overview The **Payment Links** overview shows each request's name, linked customer, requested amount, payment status, last activity, revenue, and active/inactive switch. | Column | What it shows | | - | - | | Name | Link name and URL path, with any assigned tags | | Customer | Linked customer, with a shortcut to their profile; otherwise **No customer linked** | | Requested amount | Amount and currency for Amount Links; other link types show **See checkout** | | Payment status | **Paid** when the link has a positive paid transaction, or **No linked payments yet**; also shows the latest payment date and any expiry date | | Last activity | Latest linked payment date, otherwise the recorded last-used or sent date | | Revenue | Positive paid amounts linked to this request in the link's currency, with a payment count | Use **All payment statuses**, **Paid**, or **No linked payments yet** to filter the list. Search by customer name, company, link name, description, or path. Type and tag filters can narrow the results further; **Clear** removes the filters. > [!NOTE] > > Payment status, payment count, and revenue in this overview come from recorded paid transactions. Revenue is shown in the link's currency; different currencies are not added together. **Paid** means the link has received a payment, not that an unlimited reusable link is closed. #### Payments Without a Link Connection Some historical payments or payments collected directly through your PayRequest Page are not connected to a specific Smart Link. They remain in the customer's payment history but do not count toward that link's status or revenue. A matching description alone does not connect a payment to a link. **No linked payments yet** therefore means no positive paid transaction is connected to this request. It does not prove that the customer has never paid you. Check their payment history before following up. #### Quick Actions * **Copy payment link** copies the checkout URL. A **Copied** confirmation appears when copying succeeds. If your browser blocks clipboard access, open the link details to copy it there. * **Request again** appears on Amount Links with a linked customer and an eligible linked payment. It opens a new editable request using a previous payment associated with that link and customer. * **Set up reminders** appears for active, unexpired links with a linked customer and no linked paid transactions. It opens the existing reminder settings; opening them does not send a message. * **View**, **Edit**, **Duplicate**, and **Delete** remain available. From a [customer profile](/customer-management/customer-profiles#request-payment-again), **View unpaid payment requests** opens this overview with that customer's filter and **No linked payments yet** selected. You can also choose one of the customer's five most recent eligible payments to request another payment. ### Editing Smart Links Click **Edit** on any smart link to modify: **Editable after creation:** * Path (URL slug) * Description * Internal notes (private) * Tags * After-payment redirect URL * Active/inactive status * Access code protection (on/off and the code itself) **Cannot change:** * Type (product vs amount) * The smart link will keep its analytics history ### Duplicating Links Create a copy of an existing smart link: 1. Find the link in the **Payment Links** overview. 2. Click **Duplicate** in its actions. 3. Modify the duplicated link as needed. To ask an existing customer for another payment, use **Request payment again** on their profile instead. That opens a draft based on a paid transaction; duplicating a link creates a copy of the existing link configuration. **Use cases:** * Create similar campaigns for different time periods * Test different amounts with same description * Duplicate successful campaigns ### Deactivating Links Toggle a smart link active/inactive: **When inactive:** * URL returns 404 error * Link no longer accepts payments * Analytics history is preserved * Can be reactivated anytime **Use cases:** * End limited-time campaigns * Pause seasonal promotions * Disable outdated links ## QR Code Integration Every smart link automatically generates a QR code. ### Downloading QR Codes 1. Open smart link detail page 2. Right-click QR code image 3. Save image (200x200px PNG) ### QR Code Best Practices **Print Quality:** * Use vector format for large prints * Minimum size: 2cm × 2cm * Ensure high contrast (black on white) **Placement Ideas:** * Business cards * Flyers and posters * Table tents * Product packaging * Email signatures * Invoice footers > [!WARNING] > > Always test QR codes after printing to ensure they scan correctly on different devices. ## After-Payment Actions Configure what happens after customers complete payment. Smart Links support three types of after-payment actions that can be combined: ### 1. Redirect Option **Setting Location:** Smart Link Edit → After Payment Actions → Redirect Action **Redirect URL:** Enter a full URL to redirect customers after successful payment. **Common redirect destinations:** * Thank you page: `https://yourdomain.com/thank-you` * Discount code page: `https://yourdomain.com/special-offer` * Download link: `https://yourdomain.com/download/guide.pdf` * Member portal: `https://yourdomain.com/welcome` **Example:** ``` After payment redirect: https://fitnessstudio.com/welcome?promo=early-bird ``` > [!TIP] > > Use redirect URLs to provide immediate value: discount codes, exclusive content, or onboarding instructions. ### 2. Apply Tag to Customer Automatically add a tag to the customer when they complete payment through this smart link. **Setting Location:** Smart Link Create/Edit → After Payment Actions → Apply Tag to Customer > [!NOTE] > > This option only appears when you select a customer in "Send smart payment link to customer". Customer tags are designed for targeted customer-specific smart links. **How it works:** 1. Select a customer to send the smart link to 2. Choose a Customer-type tag from the "Apply Tag to Customer" dropdown 3. When the customer completes payment, the tag is automatically added to their profile **Use cases:** | Scenario | Tag to Apply | Result | | - | - | - | | Promotion payment | "2025 Promo Buyer" | Track who bought via promotions | | VIP upgrade offer | "VIP Customer" | Auto-upgrade customer status | | Loyalty program | "Loyalty Member" | Enroll in loyalty program | | Course purchase | "Course Participant" | Grant course access | | Event registration | "Event Attendee 2025" | Track event participants | **Example Workflow:** ``` Smart Link: Early Bird Conference Ticket Customer: john@company.com Apply Tag: "Conference 2025 Attendee" → John pays via the smart link → "Conference 2025 Attendee" tag automatically added to his profile → Filter all attendees by this tag for event communications ``` > [!TIP] > > Combine "Apply Tag" with email automations to trigger welcome sequences when customers receive specific tags. ### 3. Remove Tag from Customer Automatically remove a tag from the customer when they complete payment. The dropdown shows only tags that the customer currently has. **Setting Location:** Smart Link Create/Edit → After Payment Actions → Remove Tag from Customer > [!NOTE] > > The "Remove Tag" dropdown dynamically shows: > > * Tags the customer currently has > * Plus: any tag selected in "Apply Tag" (since it will be added) > > If the customer has no tags, you'll see "This customer has no tags to remove". **How it works:** 1. Select a customer to send the smart link to 2. Choose a tag from "Remove Tag from Customer" (shows only customer's existing tags) 3. When payment completes, the tag is automatically removed from their profile **Use cases:** | Scenario | Tag to Remove | Result | | - | - | - | | Payment reminder | "Overdue Payment" | Clear overdue status | | Trial conversion | "Trial User" | Remove trial status | | Upgrade payment | "Basic Plan" | Remove old plan tag | | Renewal | "Renewal Due" | Clear renewal reminder | | Debt collection | "Payment Pending" | Mark as paid | **Example Workflow:** ``` Smart Link: Outstanding Invoice Payment Customer: sarah@business.nl Remove Tag: "Overdue Payment" Apply Tag: "Paid Customer" → Sarah pays her overdue invoice via the smart link → "Overdue Payment" tag automatically removed → "Paid Customer" tag automatically added → Customer status updated in one action ``` > [!WARNING] > > The "Remove Tag" dropdown only shows tags the customer actually has. If you don't see a tag, the customer doesn't have it assigned. ### Combining All Three Actions You can use all three after-payment actions together for powerful automation: **Complete Example:** ``` Smart Link: VIP Membership Upgrade Customer: existing-customer@email.com Redirect: https://yourdomain.com/vip-welcome Apply Tag: "VIP Member" Remove Tag: "Standard Member" Result after payment: ✅ Customer redirected to VIP welcome page ✅ "VIP Member" tag added to profile ✅ "Standard Member" tag removed from profile ``` > [!TIP] > > This combination is perfect for upgrade flows, trial conversions, and membership tier changes where you need to update customer status and provide immediate next steps. ## Tags and Organization Organize smart links using the tag system. Smart Links support two types of tags: 1. **Smart Link Tags**: Organize your smart links by campaign, channel, or purpose 2. **Customer Tags**: Automatically applied/removed from customers after payment (see After-Payment Actions) ### Creating Tags Inline When creating or editing a smart link, you can create new tags directly without leaving the form: 1. Scroll to the **Smart Link Tags** section 2. Click **Create New Tag** 3. Enter a tag name 4. Select a color from the color picker 5. Click **Create Tag** The new tag is immediately available and selected. > [!TIP] > > Inline tag creation saves time when setting up campaigns. No need to navigate to the Tags page first. ### Managing Tags on Smart Links From the smart link detail page: 1. Click the **pencil icon** next to "Tags" in the sidebar 2. The tag management modal opens 3. Select or deselect tags using the searchable dropdown 4. Create new tags inline if needed 5. Click **Save Tags** ### Tag Use Cases **By Campaign:** * "Summer 2025" * "Black Friday" * "Newsletter Campaign" **By Channel:** * "Social Media" * "Email" * "Print Materials" **By Purpose:** * "Donations" * "Event Tickets" * "Product Sales" ### Filtering by Tags In the Smart Links list: 1. Click **Tag Filter** dropdown 2. Select one or more tags 3. View only matching smart links ## Technical Details ### URL Routing Smart links use intelligent routing: 1. **Amount routes** match numeric values: `/[handle]/12.50` 2. **Smart link routes** match alphabetic paths: `/[handle]/campaign-name` 3. **Default payment page**: `/[handle]` > [!NOTE] > > Smart link paths must start with a letter (not a number) to avoid conflicts with amount-based payment links. ### Payment Page Customization When accessed via smart link, the payment page shows: **Custom Content:** * **Title**: Smart link name (instead of payment page title) * **Description**: Smart link description (instead of default) * **Amount**: Pre-filled and disabled (amount links only) **Hidden Elements:** * Minimum/maximum amount text * Amount field editing (for amount links) ### Session Tracking Smart links use session-based tracking: **Data stored:** * Smart link ID * Link name and description * Fixed amount (for amount links) * Original path **Payment attribution:** * Session persists through checkout * Payment webhook links transaction to smart link * Analytics update automatically ## Advanced Integration ### Email Campaign Integration Include smart links in marketing emails: ```html theme={null} Claim Your Discount - Pay Now ``` **Benefits:** * Track email campaign conversion * Shorter, cleaner URLs than dynamic links * Professional branding ### Social Media Campaigns Share smart links on social platforms: **Twitter/X:** ``` Early bird discount ends midnight! 🎟️ Get your ticket: payrequest.me/event/ticket-2025 ``` **Instagram Bio:** ``` 💳 Pay tuition: payrequest.me/school/tuition ``` **Facebook Post:** ``` Donate to our cause: payrequest.me/charity/donate Track: Total donations and supporter count via analytics ``` ### Embed Button on Your Website Every Smart Link includes a ready-to-paste **payment button snippet** so you can drop a styled "Pay" button onto your own website, blog, landing page, or WordPress post — without writing any code yourself. > [!TIP] > > The embedded button is a simple link, not an iframe or popup. Customers click and are taken to your branded PayRequest checkout. It works in **any** website builder: WordPress, Squarespace, Wix, Webflow, plain HTML, or even an email signature. #### How to Get the Snippet **1. Open the Smart Link** Go to **Payment Page → Smart Links** and click the link you want to embed. **2. Click Share** Press the **Share** button at the top right. The share dialog opens with the URL, QR code, and embed options. **3. Pick a Button Style** Choose between three styles in the **Embed button on your website** section: * **Blue** — PayRequest's default primary button, works on most sites * **Dark** — Black button, ideal for light backgrounds * **Outline** — Minimal transparent button with a border, blends into any design **4. Copy the Snippet** Click **Copy snippet**. The full HTML is now on your clipboard. **5. Paste It Into Your Site** Paste the snippet into any HTML block — WordPress' **Custom HTML** Gutenberg block, a Squarespace **Code** block, or directly in your theme files. The button appears instantly with the correct styling. #### What the Snippet Looks Like ```html theme={null} Pay €4.50 ``` The first line loads the PayRequest button stylesheet (one-time include — paste it once and reuse the button as often as you like). The second line is the actual button. > [!NOTE] > > The button label defaults to the Smart Link's amount (e.g. **Pay €4.50**) or its name. You can edit the text inside the snippet after pasting — change it to "Buy now", "Donate", "Subscribe", or any language you prefer. #### WordPress 1. Edit the post or page where you want the button 2. Add a **Custom HTML** block (Gutenberg) or a **Code Snippet** widget (Classic editor) 3. Paste the snippet 4. Update/publish — the button appears with full styling #### Style Variants | Variant | Class | Best For | | - | - | - | | Blue | `pr-btn pr-btn--default` | Most sites, primary CTA | | Dark | `pr-btn pr-btn--dark` | Light backgrounds, minimal designs | | Outline | `pr-btn pr-btn--outline` | Already-styled pages, secondary CTAs | You can also add the `pr-btn--secure` modifier (e.g. `class="pr-btn pr-btn--default pr-btn--secure"`) to prefix the button with a small lock icon — useful for emphasising the secure-checkout cue. #### Tracking Still Works Buttons embedded on third-party sites continue to feed your **Smart Link analytics**: every click increments the view count, and every successful payment increments revenue and conversion rate, exactly as it would on a direct payment URL. ### QR Code Embed ```html theme={null} Scan to donate ``` ## 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 > [accordion] What's the difference between Smart Links and Dynamic Payment Links? > > **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. > [accordion] Can I change the smart link path after creation? > > 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. > [accordion] How long are analytics stored? > > Analytics are stored permanently for the lifetime of your smart link. Even if you deactivate a link, historical data remains accessible. > [accordion] Can I use custom domains with Smart Links? > > 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. > [accordion] What happens if I delete a smart link? > > 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. > [accordion] Can customers change the amount in amount-based smart links? > > 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. > [accordion] How do payment limits work? > > 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. > [accordion] Can I send smart links via SMS? > > 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. > [accordion] What happens when a payment limit is reached? > > 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. > [accordion] Can I change the payment limit after creating a smart link? > > 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". > [accordion] How do customer tag actions work? > > 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. > [accordion] Why don't I see the Apply/Remove Tag options? > > 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. > [accordion] Why doesn't the Remove Tag dropdown show all customer tags? > > 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". > [accordion] Can I create tags while creating a smart link? > > 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. > [accordion] How do payment reminders work? > > 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. > [accordion] Can I change reminder settings after creating a smart link? > > 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. > [accordion] Why don't I see the reminder options? > > 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. > [accordion] What happens to reminders when a customer pays? > > 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. > [accordion] What information is tracked for each view? > > 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. > [accordion] How do the activity tabs work? > > 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). > [accordion] What is a Deposit Link? > > 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. > [accordion] How does access code protection work? > > 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. > [accordion] I forgot the access code I set — how do I see or reset it? > > 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. > [accordion] What is an Invoice Bundle 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. > [accordion] Which invoices can I include in a bundle? > > 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. > [accordion] Can I include invoices from different customers in one bundle? > > 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. > [accordion] Can I add or remove invoices from an existing bundle? > > 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. > [accordion] What does the customer see on an Invoice Bundle payment page? > > 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? > [card] [Security Deposits](/payment-processing/security-deposits) > > Collect authorization holds for rentals and services > [card] [Payment Page Setup](/payment-processing/payment-page-dynamic-links) > > Configure your payment page settings > [card] [Products](/products-and-pricing/creating-products) > > Create products for product links > [card] [Tags System](/organization-and-automation/tags-system) > > Organize with tags > [card] [Invoices](/invoices/creating-invoices) > > Create and manage invoices to bundle into payment links > [card] [SMS Payment Links](/payment-processing/sms-payment-links) > > Send payment links directly via SMS > [card] [PayRequest Upload](/products-and-pricing/quick-upload) > > 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. > [!NOTE] > > 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? > [card] Gets Seen Fast > > Text messages are typically read within minutes — much faster than email. > [card] Your Name as Sender > > The SMS arrives with your business name as the sender, so customers know it's you. > [card] One Tap to Pay > > The message contains your payment link — customers tap it and pay on their phone. > [card] Fair for Everyone > > The credit system keeps SMS free to use while preventing abuse. ## How It Works **1. Create a smart link** Go to **Payment Page → Smart Links** and create a new link, just like you normally would. **2. Select a customer** 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`). **3. Choose SMS as delivery method** Tick the **SMS** option. You'll see the phone number it will be sent to, plus how many SMS credits you have left. **4. Save — and it's sent** As soon as you save the smart link, the SMS goes out. Your customer receives a short personal message with the payment link. > [!TIP] > > 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. > [!NOTE] > > 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 > [accordion] Why do SMS messages cost credits while email is free? > > 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. > [accordion] Which payments earn me a credit? > > 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. > [accordion] Do my credits expire? > > No. Credits stay on your account until you use them. > [accordion] Can I buy extra credits? > > Not at the moment — credits are earned through payments only. Since every payment earns a credit back, active businesses naturally keep a positive balance. > [accordion] Why is the SMS option greyed out? > > 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. > [accordion] My customer didn't receive the SMS — what now? > > 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 > [card] [Smart Links](/payment-processing/smart-links) > > Everything about creating reusable, branded payment links > [card] [Payment Reminders](/invoices/payment-reminders) > > Automatically follow up on unpaid links > [card] [Customer Profiles](/customer-management/customer-profiles) > > Keep phone numbers and contact details up to date > [card] [Payment Methods](/payment-processing/payment-methods-overview) > > 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. > [!NOTE] > > 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 > [card] Scan & pay in seconds > > 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. > [card] Works with any Solana wallet > > 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. > [card] Instant settlement > > Solana confirms in under a second. The USDC is in your wallet almost immediately after the customer approves. > [card] Open standard > > 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. **1. Open Provider Settings** In your PayRequest dashboard, go to **Settings → Provider Settings**. **2. Connect your Solana wallet** Scroll to **Solana Wallet (P2P)** and click **Connect Solana Wallet**. Approve in Phantom, Solflare, or any compatible wallet. Your address is saved. **3. Done — Solana Pay appears on your page** 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. > [!TIP] > > 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: **1. QR code appears** 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. **2. Customer scans with their wallet** 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. **3. Customer approves — payment sent** One tap in the wallet sends the USDC. The transaction is signed and broadcast to the Solana network. **4. Checkout page confirms** Within 1–2 seconds the checkout page shows a green confirmation. The invoice is marked paid in your PayRequest dashboard. > [!NOTE] > > 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 | > [!TIP] > > 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 > [accordion] What does it cost? > > 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). > [accordion] Are there hidden fees? > > 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 > [accordion] What is USDC? > > 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. > [accordion] Does the customer need a PayRequest account? > > No. Any customer with a Solana wallet and USDC can pay — no account, no signup, no email required. > [accordion] What if the customer doesn't have USDC? > > 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. > [accordion] Do I need to worry about exchange rates? > > 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. > [accordion] Can I refund a Solana Pay payment? > > 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. > [accordion] Does Solana Pay work on my payment page automatically? > > 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. > [accordion] Can I use Solana Pay alongside iDEAL or credit card? > > Yes. PayRequest shows all your enabled payment methods as cards on one checkout page. The customer picks the one that works for them. > [accordion] How do I convert received USDC to euros? > > 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 > [card] [Connect Your Solana Wallet](/business-settings/business-details) > > Set up your Solana wallet in Provider Settings to activate Solana Pay on your checkout. > [card] [P2P Wallet Payments](/payment-processing/p2p-wallet-payments) > > The same Solana wallet also powers instant P2P payments from your payrequest.me page — no invoice needed. > [card] [USDC on Base](/payment-processing/crypto-payments) > > Accept USDC on the Base network via WalletConnect — another crypto option alongside Solana Pay. > [card] [Share Your Crypto Address](/payment-processing/share-wallet-address) > > Get a branded link with your SOL address, QR code, and copy button — great for giveaways and tips. > [card] [Payment Methods Overview](/payment-processing/payment-methods-overview) > > See all payment methods PayRequest supports and how they compare. # Split a payment into two links Source: https://docs.payreque.st/payment-processing/split-payments Collect an upfront payment and the balance in two steps, and track what remains outstanding. Use **Split payment** under **Payment Links** to collect an upfront amount and the balance for a project. You need an active Payment Page and at least one connected Mollie, Stripe or PayPal account that can accept payments. Split payments are in EUR, with a minimum of €1 per payment. ## Example: 30% upfront, 70% on delivery **1. Create the two payment links** In **Payment Links**, select **Create Link**, then **Split payment**. Enter a description, a total of **€1,000**, and an upfront percentage of **30**. PayRequest creates an upfront link for **€300** and a balance link for **€700**. **2. Share the upfront link** Copy the €300 link from the split payment overview and send it to your customer. The customer opens the link and chooses an available payment option and pays the fixed amount through that provider. After approving a PayPal payment, return to the Payment Page and select **Confirm payment**. **3. Check the outstanding balance** Open either link in **Payment Links**. The **Split payment** panel shows the total, the amount received, and the outstanding balance. After the provider confirms the €300 payment, the outstanding balance is **€700**. **4. Share the balance link on delivery** Copy the separate €700 link and send it when the work is ready. After the provider confirms the second payment, the outstanding balance is **€0**. You choose when to share each link. Each link opens a separate one-time checkout. Sharing both links lets the customer pay either amount immediately. The feature collects payments separately from your invoices. Send any required invoice through your usual invoicing workflow. If a checkout is still open, reopening the link lets the customer continue the same payment. Check the original payment with its provider if the overview says a payment could not be verified. The balance reflects confirmed refunds where PayRequest can verify the refunded amount. Use a new payment request to collect a refunded amount. For a refundable card hold on a rental booking, see [Security Deposits](/payment-processing/security-deposits). # Tourist Tax Source: https://docs.payreque.st/payment-processing/tourist-tax Calculate tourist tax for a stay, collect the remaining amount with a one-time payment link, and export payment and nightly records Tourist Tax helps accommodation owners calculate the levy for a booking, account for tax already collected elsewhere, and request the remaining amount from the guest. Each saved stay keeps its original inputs, calculation and tariff version. Open **Collect → Tourist Tax** in your dashboard, or go directly to [Tourist Tax](https://payrequest.app/tourist-tax). The interface is available in English, Dutch, Spanish and French. > [!NOTE] > > You can try the [public calculator](https://payrequest.io/free-tools/tourist-tax-calculator) without an account. Create a PayRequest account to save accommodation and stay records or collect payment. Dashboard actions currently require the account owner; team-member sessions cannot manage Tourist Tax. ## Before collecting payment You need: * A completed PayRequest account setup. * An active **Mollie** connection belonging to your account. * An active payment page with a handle and **EUR** as its currency. * A verified accommodation address, category and applicable local rules. * Confirmation that no additional VAT needs to be charged on this separate tourist-tax payment. Connect your provider through [Payment Providers](/payment-processing/setting-up-payment-providers). This Tourist Tax workflow currently collects through **Mollie only**; Stripe and PayPal are not supported for these links. > [!NOTE] > > PayRequest calculates and collects the payment. The host remains responsible for checking exemptions, filing declarations and remitting tax. It does not register guest identities, scan passports, import PMS bookings automatically, or submit municipal returns. ## Supported tariffs and periods The preset applies to the accommodation's actual municipality and the nights of the stay, not simply the country or booking date. The departure day is not an overnight stay. | Preset | Covered nights | Calculation | | - | - | - | | Amsterdam city | January 1–December 31, 2026 | 12.5% of the host-confirmed taxable stay price excluding VAT and tourist tax. Guest counts do not apportion that price automatically. | | Barcelona city | April 1, 2026–March 31, 2027 | Regional category tariff plus the municipal surcharge, per taxable guest and taxable night; maximum seven nights. | | Paris city, France pilot | January 1–December 31, 2026 | Fixed classified tariffs, or the capped proportional formula for unclassified accommodation, with separately calculated additional taxes. Taxe de séjour **au réel** only. | | Your own verified local rule | Dates and applicability verified by the host | Simple per-guest/night, per-accommodation/night or percentage formulas. These are not automatically maintained local tariffs. | A stay outside a preset's verified period is rejected. An arrival on December 31, 2026 with departure on January 1, 2027 has one overnight stay in 2026; departure on January 2 adds a night outside the Paris and Amsterdam coverage. Use an official accommodation classification where required. Platform review scores and star ratings are not a substitute. Surrounding municipalities can have different rates. ### Barcelona exemptions and prepaid bookings The host enters the exempt guest count. Guests aged **16 or under** are exempt in Barcelona. Verify other applicable exemptions separately. Occupancy and eligibility must remain unchanged throughout a stay calculated with this preset. Fully prepaid Barcelona bookings are rejected because the tariff applicable at reservation can differ. Check the applicable rule before using a verified custom calculation. Do not split a booking into artificial stays to restart the seven-night limit. ### Paris: classification, exemptions and collection timing The French pilot covers **Paris municipality, INSEE 75056**, not all of Île-de-France or France. It does not cover the **forfait** regime. * Guests under **18** are exempt. Verify other exemptions, including relevant resident and seasonal-worker cases. * Include exempt people in the **total occupant count** for the unclassified price calculation. * Confirm unchanged accommodation-only net nightly price, occupancy and exemptions throughout the stay. If any change, verify the nights separately; the preset does not calculate changing nightly conditions. * Collect during the stay, as specified by the [Paris tax portal](https://taxedesejour.paris.fr/). PayRequest prevents creating a Paris tax link before the saved arrival date and checks the date again when checkout starts. For an unclassified or classification-pending property, the communal rate is **5% of the accommodation-only price excluding VAT, per occupant per night**, capped at **€4.90** before additions. The calculation divides the full accommodation price by the number of nights and **all occupants**, including exempt people. Round the communal amount to cents, then calculate and round each addition separately: | Part | Basis | | - | - | | Communal | Fixed category rate, or the capped 5% unclassified calculation | | Departmental | 10% of the communal part | | SGP regional | 15% of the communal part | | IDFM regional | 200% of the communal part | Multiply the resulting per-person/night amounts by taxable guests and nights. The maximum combined unclassified tariff is **€15.93 per taxable guest per night** under this Paris 2026 preset. Check the [official Paris 2026 tariff sheet](https://taxedesejour.paris.fr/includes/download/rv3R1V-Les-tarifs-en-vigueur-a-partir-du-1er-janvier-2026.pdf). A simple percentage custom rule does not replace this capped formula with separately rounded additions. ## Add an accommodation **1. Enter the accommodation** Enter the name and **Address and municipality**, then choose the tax jurisdiction. Confirm that the address lies inside the selected municipality. **2. Select the category or custom formula** Choose the official category for Barcelona or Paris. For a custom rule, select the calculation method and enter your verified rate with a decimal point. **3. Verify the VAT treatment** Confirm that no additional VAT is due on this separate payment, then click **Save accommodation**. Tourist Tax does not determine accommodation VAT or automatically add VAT to the levy. If an accommodation was saved without VAT confirmation, use **Accommodation settings → Confirm VAT treatment** after completing the check. You can save calculations before confirming this; collection remains unavailable until confirmation. ## Calculate and save a stay 1. Select the accommodation and enter a recognizable **Booking reference**. A reference must be unique for that accommodation in your account. 2. Enter arrival and departure dates, **Total guests** and **Exempt guests**. 3. Enter the taxable price when required. Amsterdam and custom percentages use the complete applicable taxable basis. Unclassified Paris uses accommodation-only price excluding VAT and tourist tax. 4. Select the booking channel and enter **Tourist tax already collected elsewhere**. 5. For Paris, confirm unchanged nightly price, occupancy and exemptions. Check the preview and each tax part. 6. Confirm that you verified the jurisdiction, exemptions, basis and previous collection, then click **Save stay**. > [!WARNING] > > Check the booking statement before recording external collection. Airbnb collects tourist tax for relevant bookings in France, but the channel name alone does not prove collection for every location or booking. Request only the remaining amount. An externally collected amount greater than the calculated tax is rejected. Saving a stay records the calculation. It does not collect payment or send the guest a message. ### Worked Paris example Assume an unclassified property in Paris, three nights in 2026, four occupants including two exempt minors, and **€600** of accommodation-only price excluding VAT. Price, occupancy and exemptions remain constant. The price per occupant per night is `€600 ÷ 3 ÷ 4 = €50`. The communal part is `5% × €50 = €2.50`, below the cap. | Part | Per taxable guest per night | Two taxable guests × three nights | | - | - | - | | Communal | €2.50 | €15.00 | | Departmental | €0.25 | €1.50 | | SGP regional | €0.38 | €2.28 | | IDFM regional | €5.00 | €30.00 | | **Calculated tax** | **€8.13** | **€48.78** | If **€10** was already collected by another party, the saved stay has **€38.78 remaining to collect**. This example is specific to the supported Paris 2026 tariff, not a France-wide formula. ## Create and share the payment link Find the saved stay under **Collect and report**, then click **Create payment link**. For Paris, do this on or after arrival, during the stay. Copy the guest link and send it through an appropriate channel. The link uses the remaining amount from the saved calculation and accepts one successful payment. Repeating the create action returns the same link. An entirely covered stay shows **Nothing to collect** and needs no new request. The guest page shows the accommodation, booking reference, stay dates, tax breakdown, externally collected amount and remaining amount. The guest enters their name and email, chooses an available Mollie payment method and completes payment. A tourist-tax payment charges money; it is separate from a [security-deposit authorization](/payment-processing/security-deposits). > [!NOTE] > > The booking platform's terms still apply. Creating a PayRequest link does not make an external payment request permitted or necessary for an Airbnb, Booking.com or other platform booking. ### Guest message template > Hello \[name], the tourist tax for \[accommodation], booking \[reference], from \[arrival] to \[departure] is \[total]. We have recorded \[already collected] collected by another party, leaving \[remaining amount]. Please pay that remaining amount through \[secure link] at \[permitted collection time]. This is tourist tax, separate from any security deposit. Contact \[host contact] before paying if the dates, guest count or amount need correction. Replace every field and verify the permitted collection time. For the Paris example, total is €48.78 and remaining amount is €38.78. ## Check payment and handle retries Use the linked **Paid transactions** amount and the underlying transaction records. A saved calculation, sent link or pending payment is not proof of payment. Paid summaries count positive linked EUR transactions with confirmed paid status and a payment timestamp. If a payment has already been prepared, the existing provider payment is reused when available. If preparation is uncertain, checkout asks the guest to contact the host. Review the existing invoice and transaction before agreeing another collection attempt. Provider and platform fees do not reduce the tax owed to the authority. Reconcile tax collected, fees, refunds and remittance separately. ## Export records The **Arrival month** selector controls the report period. The two exports apply that period differently: | Export | Included records | Purpose | | - | - | - | | **Export CSV** | Stays whose arrival falls in the selected month, including cancelled stays | Original calculation, external collection, requested amount, gross linked paid transactions and rule version | | **Paris register CSV** | Nights falling in the selected month for saved Paris stays, including stays arriving in a previous month and cancelled stays | An aid for reviewing nightly records and the four calculated tax parts | The Paris register aid includes accommodation and address, INSEE code, booking reference, night and stay dates, category, occupants, exemptions, taxable guests, entered whole-stay accommodation price, each tax part, rule version and cancellation information. > [!WARNING] > > The register contains **calculated tax**, not a certified record of tax actually collected. External collection and paid-transaction values refer to the **whole stay** and repeat on each nightly row. Do not sum those repeated values as monthly collection totals. Check actual collection dates, refunds and corrections before declaring or remitting. For example, a stay arriving September 29 and departing October 3 is absent from the standard October arrival export. The October Paris register contains the nights of October 1 and October 2. Neither export is an automatic municipal return, an approved import format for every tax portal, or a net-remittance statement. ## Cancel a stay Choose **Cancel stay** to retain the calculation and disable its payment link. Cancellation does not delete the assessment and does not refund existing payments. Cancelled stays remain in exports so you can review the history. For incorrect dates, amounts or exemptions, stop further collection and review any existing payment before preparing a corrected calculation. Handle refunds and adjustments separately through the relevant payment records and local declaration procedure. ## Fees and limits Tourist Tax currently has no additional feature-specific plan gate. Normal payment pricing applies: * **Free:** 2% standard platform fee, capped at €25 per successful payment. * **Premium:** €5/month with 0% standard platform fees while the plan is active. * **Business:** €20/month with 0% standard platform fees while the plan is active. Provider fees and commission-payment exceptions remain separate. See [PayRequest Plans](/business-settings/payrequest-plans). ## Official sources Rates were checked on **October 12, 2026**. Saved calculations keep their tariff version; a later rule update does not rewrite a previous stay. * [Amsterdam tourist tax](https://www.amsterdam.nl/belastingen/toeristenbelasting/) * [Catalan Tax Agency: tourist-tax rates](https://atc.gencat.cat/ca/tributs/ieet/quota-tributaria/) * [Paris 2026 tariff sheet](https://taxedesejour.paris.fr/includes/download/rv3R1V-Les-tarifs-en-vigueur-a-partir-du-1er-janvier-2026.pdf) * [Paris declaration and collection portal](https://taxedesejour.paris.fr/) * [French government: tourist-tax obligations](https://entreprendre.service-public.gouv.fr/vosdroits/F743) * [Airbnb: collection and remittance in France](https://www.airbnb.fr/help/article/2284) > [card] [Open Tourist Tax](https://payrequest.app/tourist-tax) > > Save an accommodation and calculate a stay. > [card] [Free calculator](https://payrequest.io/free-tools/tourist-tax-calculator) > > Review a supported calculation without an account. # Messages After Payment Source: https://docs.payreque.st/products-and-pricing/after-payment Add a thank-you message, buyer instructions and an optional action button without creating a PDF # Messages After Payment Tell buyers what happens next with a message and an optional button, such as **Book your consultation** or **Open your resources**. You can add these instructions to a product without creating a separate thank-you PDF. The message accompanies your product's delivery method. A downloadable file, an external resource and a personally delivered service can each have their own next steps. ## Add a Message and Button **1. Open After payment** For an existing product, go to **Products**, edit the product and open the **After payment** tab. When creating a product in the full product wizard, find **After payment** on the **Review** step. **2. Write the buyer message** Enter a **Message for the buyer**. Explain what they receive, what they should do next and any agreed delivery timeframe. The limit is **5,000 characters**. Keep the public product description clear too: buyers should understand the offer before paying. **3. Add an optional action button** Enter **Button text (optional)** and a **Button link (HTTPS)**. Both fields are needed to show a button. Use a clear label such as **Book your consultation**, rather than **Click here**. Button text can contain up to **80 characters**; the link can contain up to **2,048 characters**. Use a public HTTPS address without a username or password in the URL. Leave both button fields empty for a message on its own. **4. Preview and save** Check **Buyer preview**, then save the product or finish creating it. The preview button does not open the destination. The purchase email uses the same message and button within your existing email branding. ## Where Buyers See the Message After confirmed payment, the message can appear: * On the payment confirmation page for the buyer who started checkout in that browser, or the signed-in customer who owns the purchase. * In the existing order confirmation or completion email, when that email is sent for a paid order. * In the customer's shop order details, and in **My downloads** on your Payment Page—even when personal delivery has no downloadable file. Your existing email settings still apply. Saving a message does not send an email or resend an earlier receipt. An ordinary public invoice link does not grant access to the private instructions. ## Choose How You Deliver For a digital product, choose the delivery method that matches the actual offer: | Delivery method | Use it for | What to provide | | - | - | - | | **File download** | Finished notes, books, templates or other files | Upload the actual files the buyer purchases. Add optional reading or setup instructions under **After payment**. | | **External link** | Resources hosted elsewhere | Add the HTTPS delivery link. Buyers receive it through the private download flow after payment. | | **Manual delivery** | Consultations, personalized material or work delivered later | No file is required. Use the buyer message to explain the next step, and manage delivery through the order. | > [!TIP] > > If you are selling a consultation, choose **Service**, or use **Manual delivery** for a digital product delivered personally. You do not need to upload a placeholder PDF just to say thank you. ## Example: A Study Consultation For a consultation arranged through an external booking page, an example message is: > Thank you for your purchase! Use the button below to choose your consultation time. Please have your course topics and questions ready for the session. Set the button text to **Book your consultation** and enter your own booking page's HTTPS URL. Only use this wording if it matches how you actually arrange appointments. If study notes are also included, explain how and when the buyer receives them. A thank-you message alone does not deliver those notes. > [!NOTE] > > An action button opens the destination when the buyer selects it. It does not automatically book an appointment, create an external account or grant access on another website. Configure any required access with that service separately. ## Messages and Delivery Status Showing the message does **not** mark an order as delivered. For personal delivery, open the paid order, review the customer's requirements and use the existing **Order delivery** controls to start work and mark the actual delivery complete. Messages and buttons for new orders are saved with the purchase. Later product edits do not change those saved instructions, and adding a message does not add it to historical orders that had no saved message. Subscription payments without an associated order use the product's current message. Private instructions are checked against the current purchase and access status. An unpaid or authorization-only payment does not unlock them. Refunds, chargebacks and access restrictions can prevent them from being shown again. An external service controls access to its own content; changing PayRequest's message does not revoke a link already received by a buyer. ## Related Guides > [card] [Creating Products](https://docs.payreque.st/products-and-pricing/creating-products) > > Set up services, digital products and personal delivery. > [card] [Digital Products](https://docs.payreque.st/products-and-pricing/digital-products) > > Prepare the actual files and configure secure downloads. # AI Product Websites Source: https://docs.payreque.st/products-and-pricing/ai-product-websites Create and publish a hosted sales website from an existing product with Premium, Business or Growth Turn an existing PayRequest product into a sales website with AI-assisted text, a choice of three styles and a hosted PayRequest address. Visitors can learn about your offer, then select **View price and buy** to open your existing product checkout. > [!NOTE] > > AI product websites are included with an **active paid Premium, Business or Growth subscription**. Free accounts see an **Upgrade to Premium** callout on product detail pages. Trial, pending or expired subscriptions do not unlock this feature. ## Before you start * Create a product with a clear name, public description and, optionally, product features and a cover image. * Use the main account owner's login to open the website editor. * Activate your product and your Payment Page before publishing. A paused product cannot be published as a website. * Complete the payment-provider setup required for your existing checkout to accept payments. You can prepare a private draft while your product or Payment Page is inactive. Creating a website does not publish your product, connect a payment provider or change its payment eligibility. ## Create your website **1. Open your product** In the web dashboard, open **Products** and select an existing product. Select **Create website with AI** in the website callout. If you see **Upgrade to Premium**, open the plan settings and complete a qualifying paid subscription first. Business and Growth subscribers can use the same website button. **2. Choose the website language** Select English, Dutch, German, French, Spanish or Portuguese under **Website language**. **3. Generate a private draft** Select **Create website with AI** in the editor. PayRequest uses the product's public name, description and features to prepare editable website text. The website uses your existing product cover when available; this action does not generate a new image. **4. Review and personalize** Check the headline, introduction, product story, audience and highlights. Choose a style, then adjust the search title and description. Confirm that every claim accurately describes your product. **5. Save and preview** Select **Save draft**, then **Preview saved draft**. The preview is private and its purchase buttons are disabled. Unsaved changes are not included in the preview. **6. Publish and share** Select **Publish website** when your product and Payment Page are active. Copy the address shown under **Ready to share**, or select **Open website** to view the published page. > [!TIP] > > A specific product description gives AI more useful facts to work with. Describe what the buyer receives and who it is for before generating the website. AI text still needs your review. ## Choose a style and edit your content | Setting | What you can change | | - | - | | Website style | **Studio** for a clean, colorful design; **Editorial** for a warm, elegant design; **Midnight** for a bold, dark design | | Headline | Your main sales heading, up to 140 characters | | Introduction | A short opening description, up to 350 characters | | Product story | More detail about your offer, up to 3,500 characters | | Who is this for? | A short audience description, up to 250 characters | | Highlights | Up to six short points, one per line | | Search title | Up to 70 characters | | Search description | Up to 170 characters | The layouts adapt to mobile and desktop screens. You edit the content and choose a style; this is not a free-form HTML editor or a multi-page website builder. ## Your hosted website address Published websites use an address such as: ```text theme={null} https://photography-course-123.payrequest.me ``` The address combines a product-based name with its product ID. Copy the exact address from the editor. Once saved, the website address stays the same when you rename the product; there is no custom subdomain-name field in this release. Hosting and HTTPS are included. You do not need to create DNS records, buy hosting or install a certificate for your PayRequest website address. > [!NOTE] > > **Connecting your own domain to an AI product website is not available yet.** Use the generated PayRequest address. Existing [shop custom-domain settings](https://docs.payreque.st/shop-and-checkout/custom-domains) remain separate and do not connect an AI product website automatically. ## How checkout and delivery work Your website presents the product. Its **View price and buy** buttons open the existing product checkout on your Payment Page, where buyers see the current price, currency, taxes and any recurring or additional charges before paying. Your product's existing payment methods, checkout requirements and delivery settings continue to apply. A generated page does not create a second product or change its price, subscriptions, private files, download rules or membership access. Creating or publishing a website does not send an email. For example, a website promoting a PDF sends buyers to the existing PDF checkout. Confirmed payment uses the product's existing download delivery. A video-series website similarly sends viewers to the existing series product page and checkout; it does not create a new video player or unlock paid episodes. ## Update or unpublish a website After publication, edit and save a new draft without changing the live website. Select **Publish changes** to replace the published website with the saved changes, including its selected language. **Generate a fresh draft** replaces the draft's text and resets its style. It does not replace your published website until you publish again. Review and save your preferred style before publishing. Product prices and purchase terms continue to come from checkout. If you change the product description, regenerate or edit the website copy when you want that change reflected in the website text. Select **Unpublish website** to take the website offline while retaining its draft. This does not unpublish the product or disable its existing checkout link. Hidden, inactive or paused products, an inactive Payment Page, or a suspended seller account can also make the website unavailable. > [!NOTE] > > If your qualifying paid subscription expires, access to the website editor stops and published websites become unavailable. Saved drafts and published content are retained. Restore qualifying paid access to use the feature again, provided the product and Payment Page are still available. ## AI availability and usage limits AI generation has usage limits. Identical product details and the same language may reuse a previous result. If AI is unavailable or a limit is reached, PayRequest prepares an editable template from your product details and tells you that a template was used. You can review, edit and publish that template. Only the public product name, description, features and selected language are used for website text generation. Private delivery files, customer records and payment configuration are not included. ## Troubleshooting > [accordion] Why do I see Upgrade to Premium when I have Business? > > An active paid Business subscription qualifies. Open your plan settings and check that the subscription is current. An unpaid checkout, expired term or trial does not qualify. If your current paid subscription is not recognized, contact support. > [accordion] Why is Publish website unavailable? > > Generate a draft first. Make sure the product is active, visible and unpaused, your Payment Page is active, and your qualifying paid subscription is current. You can keep working on a private draft while preparing an inactive product or Payment Page. > [accordion] Why does my preview show older text? > > The preview displays the saved draft. Select Save draft before opening it. The public website displays the last published version until you select Publish changes. > [accordion] Why am I asked to reload before saving? > > The website changed in another tab. Reload the editor to load the latest saved version before making further changes. > [accordion] Does publishing guarantee visitors or sales? > > No. Share the website with your audience through your own channels. Search titles and descriptions help describe the page; they do not guarantee indexing, rankings, traffic or sales. ## Related guides * [Create products](https://docs.payreque.st/products-and-pricing/creating-products) * [Product sharing](https://docs.payreque.st/products-and-pricing/product-sharing) * [PayRequest plans](https://docs.payreque.st/business-settings/payrequest-plans) * [Set up payment providers](https://docs.payreque.st/payment-processing/setting-up-payment-providers) # 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. > [!NOTE] > > AI Prompts are available on all plans. They work for prompts written for text, image, audio, or video AI tools. > [card] Sell Any AI Prompt > > Works for ChatGPT, Claude, Gemini, Midjourney, Stable Diffusion, DALL·E, Suno, Runway, and more > [card] A Teaser, Not a Leak > > 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 > [card] Instant Unlock > > 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 > [card] Optional Marketplace Listing > > 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 **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **AI Prompt** as the product type. **2. Choose the Target AI Model** 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. **3. Pick a Category** 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. **4. Write Your Teaser** 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. **5. Paste the Full Prompt** Paste the exact prompt text customers will receive after payment. This is stored privately and never shown to anyone who hasn't paid. **6. Set Your Price and Save** Enter your price and save. The product is ready to sell immediately from your shop, your PayRequest Page, or a Smart Link. > [!TIP] > > 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. > [!WARNING] > > 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. **1. Open Your Product** Edit the AI Prompt product you want to list. **2. Turn On List on Marketplace** Enable the **List on Marketplace** toggle. **3. Choose a Marketplace Category** 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. > [!NOTE] > > 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 > [accordion] Can I sell a prompt without writing a teaser? > > 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. > [accordion] What happens if I edit the prompt text after someone already bought it? > > 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. > [accordion] Can I sell prompts for tools that aren't in the dropdown? > > Yes — each media type (Text, Image, Audio/Music, Video) includes an "Other" option for tools not listed by name. > [accordion] Does listing on the marketplace cost extra? > > No. Marketplace listing uses the same pricing and fees as selling directly from your own shop or PayRequest Page. > [accordion] Do AI Prompt products support custom fields or multiple quantities? > > 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 > [card] [Digital Products](/products-and-pricing/digital-products) > > Sell downloadable files with the same secure delivery system AI Prompts are built on > [card] [Pay to Unlock](/products-and-pricing/pay-to-unlock) > > A similar teaser-then-unlock model for photos and audio tracks > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [Customer Portal](/customer-management/customer-portal) > > 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. > [!WARNING] > > 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 ``` > [!TIP] > > **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 > [card] Set Realistic Lead Time > > Give yourself enough notice to prepare for appointments > [card] Use Buffer Time > > Add buffer between bookings for breaks and prep work > [card] Limit Advance Booking > > Don't allow bookings too far ahead if your schedule changes > [card] Enable Reminders > > 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 > [!WARNING] > > **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 > [card] [Creating Products](/products-and-pricing/creating-products) > > Set up different product types > [card] [Order Management](/shop-and-checkout/order-management) > > Manage orders and bookings > [card] [Payment Page](/payment-processing/payment-forms) > > Accept bookings via payment links > [card] [Email Templates](/invoices/email-templates) > > Customize booking confirmations ## Private tours for independent guides Create a **Booking** product and enable **Private tour** in Booking Settings. Enter a fixed price for the entire group, the maximum guest count, comma-separated languages and a meeting point. Use the slot duration for the tour length, and set your working days, hours and travel buffer. All private-tour products belonging to the same business share one guide calendar; use this mode for a single guide. Select the tour products on your Page. Visitors see **Book this tour** and can choose a date, language and number of guests. Guest count does not multiply the group price. Choose full payment or a fixed/percentage deposit using the existing booking payment settings. The remaining balance follows the existing booking flow; it is not automatically charged. Enable **Accept quote requests** on your Page to show **Request a private tour**. Guests provide a date, group size, preferred language, pickup location and wishes. Custom requests may exceed a package's group limit or request another language, so the guide can assess feasibility. These requests appear under **Requests**. Open a request and choose **Prepare proposal with deposit** to prefill a new quote. Review the price, tax, availability and deposit percentage before saving/sending. The default suggested deposit is 25%, and the guide can change it. Approved quotes use the existing quote-to-invoice flow. A custom request or quote does not reserve a time slot or create a booking. The guide must manage the agreed date separately. Confirmed and pending booking records block overlapping private tours, including travel buffers and timezones. Checkout rechecks availability before starting payment, but the existing booking flow does not hold slots during payment: simultaneous or delayed payments still require guide review. Per-person seat sales, variable hourly tour pricing, multiple guides and automatic quote-to-calendar reservation are outside this version. # 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. > [!NOTE] > > 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 > [card] Starting Price > > The price you set is shown to customers as "From €X" — not a fixed, final amount > [card] Commission Badge > > Listings are automatically marked with a pink "Commission" badge on your storefront > [card] Typical Turnaround > > Optionally show customers how long the work usually takes > [card] Capped Platform Fee > > A flat 2% fee, capped at €25, applies to commission sales — regardless of your plan ## How It Works **1. Create a Commission product** Go to **Products → New Product** and select **Commission** as the product type. **2. Set your starting price** Enter the **Starting Price** — the amount you'd typically charge for a simple version of the work. Customers will see this as "From €X". **3. Add turnaround (optional)** 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. **4. Publish and share** The commission appears on your PayRequest Page with a pink "Commission" badge, the "From €X" price, and your turnaround note underneath. **5. Scope the work after purchase** 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 | > [!WARNING] > > 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) | > [!TIP] > > 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 > [card] Price the Simple Version > > Set your starting price for the simplest version of the work, not the average > [card] Set Turnaround Expectations > > Always fill in typical turnaround so customers know what they're waiting for > [card] Follow Up Fast > > Reach out to scope the work as soon as a commission is purchased > [card] Invoice for Extras > > Use a separate invoice for anything beyond the starting price once scope is confirmed ## FAQ > [accordion] Can I offer a fixed-price commission with no variation? > > Yes — just treat the starting price as the final price and don't invoice for anything extra. > [accordion] What if a customer wants a custom quote before paying anything? > > 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. > [accordion] Does the capped fee apply to Stripe, Mollie, and PayPal? > > Yes — the 2%-capped-at-€25 fee applies the same way across all connected payment providers. > [accordion] Can I limit how many commissions I take on at once? > > Not yet as a dedicated feature — for now, unpublish or archive the product once you're at capacity. ## Related Topics > [card] [Creating Products](/products-and-pricing/creating-products) > > Set up different product types > [card] [Booking Calendar](/products-and-pricing/booking-calendar) > > Sell time-based appointments and services > [card] [PayRequest Page](/shop-and-checkout/sales-page-styling) > > Your public storefront where commissions are listed > [card] [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) > > 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. > [!TIP] > > 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. ## AI product websites With an **active paid Premium, Business or Growth subscription**, open an existing product and select **Create website with AI**. Generate a private draft, choose one of three styles, review the text and explicitly publish a hosted website at a product-based `payrequest.me` subdomain. Free accounts see an upgrade callout instead. Your existing checkout and delivery remain connected. Own-domain connections for AI product websites are not available yet. See [AI Product Websites](https://docs.payreque.st/products-and-pricing/ai-product-websites) for setup, previews, publishing and subscription requirements. ## Messages After Payment Add a buyer message and optional HTTPS action button under **After payment** on the **Review** step, or in the **After payment** tab when editing a product. Preview the message before saving. For example, thank the buyer and provide a **Book your consultation** button. For a digital product delivered personally, choose **Manual delivery**: no placeholder PDF is required. The message does not mark the order as delivered, and saving it does not send an email. See [Messages After Payment](https://docs.payreque.st/products-and-pricing/after-payment) for setup, buyer access and delivery behavior. ## Choosing a Product Currency Select the product's currency when creating or editing it. PayRequest's selectors offer 139 Stripe presentment currencies, including AUD, CAD, USD, GBP, EUR, and JPY. The saved product price and currency determine the starting amount for Stripe product checkout: **9 AUD** means nine Australian dollars. Changing a currency is not an exchange-rate conversion. Review the price before saving. Your payment provider must support the selected currency for your account and payment method; Stripe currency availability does not extend Mollie or PayPal support. Use whole amounts for JPY and KRW. For Stripe's special currency rules, refunds, and the distinction between product currency and Adaptive Pricing, see [Choosing your Stripe currency](/payment-processing/connect-stripe#choosing-your-currency). ## 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 the selected currency * **Currency**: Select the currency for this product ### 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 > [!TIP] > > **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 > [!TIP] > > **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. > [!NOTE] > > 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 > [card] [Digital Products](/products-and-pricing/digital-products) > > Sell downloadable files with automatic delivery > [card] [Pay to Unlock](/products-and-pricing/pay-to-unlock) > > Sell photos and tracks behind a free preview > [card] [AI Prompts](/products-and-pricing/ai-prompts) > > Sell prompts for ChatGPT, Midjourney, Suno, and more > [card] [PayRequest Upload](/products-and-pricing/quick-upload) > > Skip this wizard — drop a file and get a link in seconds > [card] [Custom Fields](/products-and-pricing/custom-fields) > > Add custom fields with markup pricing > [card] [Product FAQs](/products-and-pricing/product-faqs) > > Answer common questions directly on a product page > [card] [Setup Fees](/products-and-pricing/setup-fees) > > Configure one-time setup charges > [card] [Product Sharing](/products-and-pricing/product-sharing) > > Share product links with QR codes > [card] [Commissions](/products-and-pricing/commissions) > > Sell custom-scoped creative and freelance work ## Tips & Tricks > [!TIP] > > **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. > [!TIP] > > **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". > [!WARNING] > > **Pricing Changes**: Modifying a product's price doesn't affect existing subscriptions. Existing customers continue paying their original price. > [!NOTE] > > **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. > [!NOTE] > > 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 > [card] Text > > A single-line text input. Good for names, references, or short notes. > [card] Email > > A single-line input validated as an email address. > [card] URL > > A single-line input validated as a URL. > [card] Number > > A numeric input. Supports **per-unit pricing** — see below. > [card] Textarea > > A multi-line text input for longer notes or instructions. > [card] Dropdown (Select) > > A list of options you define. Each option can have its own price markup. > [card] Toggle > > An on/off switch — useful for optional add-ons. Can add a fixed markup when enabled. ## Adding a Custom Field **1. Open the Custom Fields step** In the product wizard (or the product editor's **Custom Fields** tab), click **Add Field**. **2. Set the internal name and label** * **Field Name** — internal identifier (letters, numbers, underscores, hyphens only — no spaces) * **Display Label** — what the customer sees on the payment page **3. Choose a field type** Pick one of the seven types above. The configuration options below change depending on the type you pick. **4. Configure visibility and requirement** * **Show in Shop** — toggle whether the field is visible to customers * **Required Field** — toggle whether customers must fill it in before paying **5. Save the product** 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). > [!TIP] > > 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. > [!NOTE] > > 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 > [accordion] Can I reorder custom fields? > > 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. > [accordion] Can I make a field required? > > Yes. Toggle **Required Field** when configuring the field. Customers can't complete payment without filling it in. > [accordion] Do custom field markups apply to setup fees too? > > No, markups from custom fields apply to the product price. Setup fees are configured separately — see [Setup Fees](/products-and-pricing/setup-fees). > [accordion] Can I hide a field from the shop but still use it? > > 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 > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [Payment Page Dynamic Links](/payment-processing/payment-page-dynamic-links) > > Pre-fill and lock custom field values via URL > [card] [Quantity-Based Pricing](/products-and-pricing/quantity-based-pricing) > > Let customers buy multiple units of a product > [card] [Setup Fees](/products-and-pricing/setup-fees) > > 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. > [!NOTE] > > 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. > [!NOTE] > > 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. > [card] Automatic Delivery > > Customers receive download links instantly after payment — on the success page and in their email > [card] Secure Downloads > > Unique tokens per purchase with configurable download limits and expiry dates > [card] Download Tracking > > See how many times each file was downloaded, with per-token and per-product statistics > [card] Multi-Channel Access > > Downloads accessible from success page, order email, customer portal, and direct link ## Upload progress Digital uploads use a single-file queue. Wait for the upload to finish before saving or continuing. To replace a delivery file, select the complete replacement and wait for its upload to complete before saving the edit. ## PDF covers and browser reading Single-PDF digital products can receive an automatically generated cover from the first page. Cover generation runs after the upload is saved and preserves your manually selected cover and gallery. If the PDF cannot be rendered, the product upload remains saved; you can add your own cover. Automatic covers support source PDFs up to 100 MB, within the normal upload limit. After payment, buyers can select **Read edition** on supported purchase, download and order screens to open the original PDF in their browser. **Download** remains available. Reading uses one of the purchase’s existing download allowances and requires valid, unexpired paid access. Opening the download landing page alone does not use an allowance. This applies to a single PDF, rather than an EPUB or a ZIP bundle. The PDF stays private until access is checked. Buyers can save the purchased file; browser reading is not copy protection. [Step-by-step PDF selling guide](/products-and-pricing/selling-pdfs) Want shoppers to discover your download in a public catalog? [Apply to sell on PayRequest Marketplace](/products-and-pricing/payrequest-marketplace). ## Creating a Digital Product ### Quick route for a workbook or PDF In **Products**, choose **Sell a workbook / PDF**. Upload your PDF (up to 500 MB), confirm the name, enter the total customer price and check the included VAT rate. The currency follows your account settings. PayRequest creates a digital product and a reusable payment link. Copy the link, or choose your button text and style and copy the website code into an HTML block. You can also use the link with an existing website button. Customers receive secure downloads only after successful payment, using the existing delivery flow (five downloads, available for 30 days). Your payment provider must be ready to receive payments. Available methods, including iDEAL, depend on the connected provider. Your plan fees and payment provider fees apply. For other file types or more settings, use the full product wizard below. **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **Digital** as the product type. **2. Choose What You Sell** 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. **3. Prepare the Delivery** 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. **4. Set Your Price** Enter the price, currency, and applicable tax rate for the digital product. **5. Configure Download Settings** 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) **6. Save and Publish** Save the product and make it visible in your shop. Customers can now purchase and receive the file automatically. ## Buyer Messages and Personal Delivery Use **After payment** to add a thank-you message, next steps and an optional HTTPS button. Find it on the **Review** step when creating a product, or in its own tab when editing. Paid buyers can see the instructions on their confirmation page, in existing purchase emails and in their customer portal. If you deliver material personally or arrange a consultation after purchase, choose **Manual delivery**. You do not need to create a thank-you PDF. Upload the real study notes, book or other content when selling an instant file download; a thank-you message does not replace that content. Read [Messages After Payment](https://docs.payreque.st/products-and-pricing/after-payment) for the full setup and how messages relate to order delivery. ## 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. > [!NOTE] > > 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. > [!NOTE] > > 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, m4b, ogg, midi, mid | | Video | mp4, mov, webm | | 3D & CAD | fbx, obj, glb, gltf, blend, stl, dwg | | Fonts | ttf, otf, woff, woff2 | > [!NOTE] > > 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 > [!TIP] > > 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. > [!WARNING] > > 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. > [!TIP] > > 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. > [!NOTE] > > 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 > [accordion] Can I sell multiple digital files in one product? > > Currently, each digital product supports one file. To bundle multiple files, create a ZIP archive containing all files and upload that. > [accordion] What happens if a customer needs more downloads? > > 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. > [accordion] Are files stored securely? > > 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. > [accordion] Can I change download limits after creating a product? > > Yes. Changes to download settings apply to all future purchases. Existing tokens keep the limits they were created with. > [accordion] Do digital products work with custom domains? > > Yes. Download links work on all domains — your PayRequest dashboard, payrequest.me PayRequest Pages, and custom domains. ## Next Steps > [card] [Pay to Unlock](/products-and-pricing/pay-to-unlock) > > Sell photos and tracks behind a free preview > [card] [AI Prompts](/products-and-pricing/ai-prompts) > > Sell prompts for ChatGPT, Midjourney, Suno, and more > [card] [PayRequest Upload](/products-and-pricing/quick-upload) > > Drop a file and get a payment link in seconds, no wizard needed > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [Shop Setup](/shop-and-checkout/shop-setup) > > Configure your shop to showcase digital products > [card] [Email Automations](/organization-and-automation/email-automations) > > Customize order confirmation emails > [card] [Customer Portal](/customer-management/customer-portal) > > How customers access their downloads ### M4B audiobooks Upload an M4B audiobook as a digital download. Add your book cover as the product image and use the description for the author, narrator, listening time and synopsis. The product page shows an audiobook card with an M4B label and download information. Buyers receive the original file through the existing protected download flow after confirmed payment. The file is not converted: embedded chapters, cover and metadata stay intact. Buyers listen in an M4B-compatible audiobook app; chapter navigation and saved listening position depend on the file and app. There is no public full-book player. The existing per-file upload limit and your account storage quota apply. You must own the rights to sell the audiobook. Try the [M4B audiobook demo](https://payrequest.me/payrequest/p/aesops-fables-audiobook-demo) on the PayRequest Payment Page. It uses Aesop’s Fables from LibriVox and costs €1 including VAT through the real checkout. The product description also links to the free original and its public-domain reuse policy. ### Audiobook listening previews For an M4B digital product, enable **Enable audiobook listening preview** in the product editor. Choose 30, 45 or 60 seconds and save. The preview starts at the beginning of your file; choose a length at least two seconds shorter than the audiobook. PayRequest creates a separate short MP3 with a fade-out. Buyers can use **Listen to preview** on your product page before purchasing. The original M4B stays private and continues through the normal paid download flow. Previews are optional and off by default. Disable the option and save to remove the player. Replacing your file or changing the preview length generates a new fragment. The [Aesop’s Fables demo](https://payrequest.me/payrequest/p/aesops-fables-audiobook-demo) includes a 30-second listening preview. The audiobook card labels the format **M4B-compatible audiobook** and shows the complete listening time beside the preview when it has been measured. The player’s timer applies only to the short sample. Full duration is read from the original file when generating the preview; unknown durations are omitted. # Software license keys Source: https://docs.payreque.st/products-and-pricing/license-keys Sell software with unique license keys, installation limits and a license validation API. License keys let your software check whether a buyer has paid for access. Your application must integrate the License API to enforce access. ## Set up a product 1. Create a paid, one-time **License** or **Digital Product**. 2. Open its product detail page and find **Software license keys**. 3. Enable **Generate license keys**, choose the maximum active installations, and optionally enter validity in days. Leave validity empty for lifetime access. 4. Save before the first order is created. One key is issued per purchased unit after confirmed payment. A digital product can deliver both its download and a license key. Keys appear in the order completion email and the primary buyer's order detail in the customer portal. Contact users cannot view keys. License terms are fixed once the product has any order, including an unpaid checkout. Create a new product for different terms. Existing orders never acquire licenses retroactively. ## Connect your software Send HTTPS POST requests to `https://payrequest.app/api/v1/licenses/activate`, `/validate` or `/deactivate`. Send credentials in the request body and use `Accept: application/json`. Do not put keys in URLs or logs. Each request requires `seller_id`, `product_id`, and `license_key`. Copy the seller and product IDs from the product's license settings. Pin those IDs in your integration: a license for another seller or product must never unlock your software. There is no merchant API secret to embed in your application; the buyer's key is a bearer credential. ### Activate an installation ```bash theme={null} curl https://payrequest.app/api/v1/licenses/activate \ -H 'Accept: application/json' \ --data-urlencode 'seller_id=YOUR_SELLER_ID' \ --data-urlencode 'product_id=YOUR_PRODUCT_ID' \ --data-urlencode 'license_key=YOUR_LICENSE_KEY' \ --data-urlencode 'installation_id=YOUR_STABLE_RANDOM_INSTALLATION_ID' \ --data-urlencode 'instance_name=My laptop' ``` Generate a random installation ID of 16–200 characters once and persist it locally. Do not use a hardware fingerprint or personal information. Repeating activation with the same installation ID returns the existing active instance without using another slot. Store the returned `instance.id` for validation and deactivation. A successful response contains `valid: true`, `activated: true`, an `instance` with its ID and name, and a `license` object with seller/product IDs, activation limit, current usage and expiry (`null` for lifetime). ### Validate access POST to `/api/v1/licenses/validate` with `seller_id`, `product_id`, `license_key` and `instance_id`. A successful response has `valid: true` and `validated: true`. Checking only a key is also supported by omitting `instance_id`; this checks the license, without proving an installation is activated. Applications enforcing installation limits must always pass the instance ID. Treat `valid: false`, network failures, malformed responses and unexpected seller/product IDs as no confirmed access. Any optional offline grace period must be explicitly implemented in your software; it delays enforcement of refunds and revocation. ### Deactivate an installation POST to `/api/v1/licenses/deactivate` with the same seller/product/key fields and `instance_id`. Success returns `deactivated: true` and frees that slot. Reactivating a released installation returns a new instance ID; the previous proof remains invalid. ## Manage licenses Open the product detail page to disable or re-enable a license and release individual installations. Re-enabling does not override expiry, payment reversal or seller suspension. Validation freshly checks paid ledger coverage, order/customer ownership, refunds, credit notes, chargebacks and disputes. A refund or dispute blocks all licenses on the affected order; partial refunds do not automatically allocate access between individual units. Invalid licenses and full activation limits return `valid: false` with an error. Invalid input returns HTTP 422; throttling returns HTTP 429. The three API operations share limits of 60 requests per minute per IP and per key. Back off on HTTP 429; do not call on every UI render. ## Current scope This version supports one-time purchases, 1–100 installations per key, up to 100 purchased units per order line, and lifetime or fixed validity. Subscription licenses, imports of existing Lemon Squeezy keys, automatic software updates and offline signed licenses are not included. Existing Lemon Squeezy integrations require an API integration change; this is not a drop-in replacement. # 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. > [!NOTE] > > Pay to Access is available on all plans. Product type: `pay_to_access`. > [card] No File Involved > > Unlike Digital Products or Pay to Unlock, nothing is uploaded or stored — PayRequest only issues and tracks the access code > [card] You Own the Gate > > Your app decides what "access" means (a login, an API call, a page view) — PayRequest just answers "is this code still valid?" > [card] Usage-Limited, Not Time-Limited > > Caps the *number of uses*, not just a subscription window — "paid for 5 logins" locks after the 5th, however many people share the code > [card] Revocable > > 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 **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **Pay to Access** as the product type. **2. Set Max Uses and Expiry** 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). **3. Set Your Price and Save** Enter the price and save. No file upload is required — there's nothing to store. **4. Integrate the API** 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). > [!WARNING] > > 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 ``` **token** `string` *required* 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 ``` **token** `string` *required* 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 } ``` > [!TIP] > > 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 > [accordion] What happens if the customer shares the code with other people? > > 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." > [accordion] Do I need an API key to call verify/consume? > > 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. > [accordion] What's the difference between verify and consume? > > `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. > [accordion] Can I change Max Uses after the code has already been issued? > > 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. > [accordion] Does Pay to Access support custom fields or multiple quantities? > > 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 > [card] [Digital Products](/products-and-pricing/digital-products) > > For selling files instead of metered access > [card] [Pay to Unlock](/products-and-pricing/pay-to-unlock) > > For blurred-photo/audio-preview style unlocks > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [API Overview](/api/overview) > > 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 photos, photo galleries, audio, and video behind a free preview — customers pay to unlock the full content # 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. > [!NOTE] > > Pay to Unlock is available on all plans. Three content types are supported: **Images and photo galleries** (`unlockable`), **Audio Tracks** (`unlockable_audio`), and **Videos** (`unlockable_video`). > [card] Free Preview, Real Teaser > > 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 > [card] Server-Generated, Irreversible > > Previews are generated on PayRequest's servers from the original file. The original detail is never recoverable from the preview > [card] Automatic Delivery > > Built on the same secure delivery system as Digital Products — the full file unlocks instantly after payment > [card] One Price, One Purchase > > No custom fields or quantity selection — sell one file or a complete photo gallery 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. **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Image)** as the product type. **2. Upload the Photo** Upload the original photo (JPG, PNG, WebP, or GIF, up to 25MB). This file is stored privately — it is never served directly. **3. Choose a Blur Level** Use the **Blur Level** slider (1–10) to control how much detail is hidden in the public preview. Higher levels hide more. **4. Set Your Price and Save** Enter the unlock price and save. The blurred preview is generated immediately and appears wherever the product is shown. > [!TIP] > > 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: Photo Galleries Choose **Pay to Unlock (Image)**, then select **Photo gallery** to sell a complete collection for one price. Buyers preview blurred photos and unlock the gallery after confirmed payment. 1. Add **2–50 photos**, one upload at a time. Supported formats are JPG, PNG, WebP and GIF, up to **25 MB per photo**, **24 megapixels**, and **500 MB for the collection**. 2. Move photos earlier or later to set the viewing order. The first photo supplies the blurred product cover. 3. Set one positive, one-time price. Use **Download Settings** to choose the access-link expiry and ZIP download allowance. 4. Optionally enable **Offer a ZIP download after payment**. Without that option, buyers receive gallery viewing access. 5. Save and share the product link. Visitors can browse the blurred previews. After payment, the existing purchase link opens the unlocked viewer on your Payment Page. > [!NOTE] > > Gallery contents, order and download availability are fixed when created. You can edit the product title, description and price for future purchases. Create a new gallery to sell a different collection. Existing single-photo products keep their current behavior. Originals and the collection manifest remain private. Every photo request checks the purchase, seller, link expiry and current refund/dispute status. Viewing does not consume ZIP downloads, and exhausting the ZIP allowance does not end viewing access before the link expires. > [!WARNING] > > Viewing access is not copy protection: buyers can save images they can view or take screenshots. Only publish content you have the rights to sell and that your payment provider permits. A payment-provider connection does not establish approval for every content category. ## 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. **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Audio)** as the product type. **2. Upload the Track** Upload the full track (MP3, WAV, or FLAC, up to 100MB). It's stored privately, the same way Digital Product files are. **3. Set the Preview Length** Use the **Free preview length** slider (5–60 seconds, default 25s) to choose how much of the track plays for free. **4. Add Cover Art (Optional)** Upload a **Cover Image** separately from the track itself — this is the artwork shown on your shop and product pages. **5. Set Your Price and Save** 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"). > [!WARNING] > > 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. **1. Start a New Product** Navigate to **Products** and click **New Product**. Select **Pay to Unlock (Video)** as the product type. **2. Upload the Full Video** 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. **3. Set the Teaser Length** 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. **4. Add Cover Art (Optional)** Upload a cover image for product cards and listings. The playable teaser appears on the product and checkout pages. **5. Set Your Price and Save** PayRequest generates a browser-friendly MP4 teaser. Customers can watch it immediately and pay to unlock the original video. > [!WARNING] > > 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 > [accordion] Can I use both a blurred photo and a cover image? > > 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. > [accordion] Can customers download the preview clip and get the full song that way? > > 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. > [accordion] Can customers retrieve the full video from the teaser player? > > No. The player receives only the separately generated teaser MP4. The private original is delivered through a secure download token after successful payment. > [accordion] What file types are supported? > > Images: JPG, PNG, WebP, GIF (up to 25MB). Audio: MP3, WAV, FLAC (up to 100MB). Video: MP4, MOV, WebM, M4V (up to 500MB). > [accordion] Can I change the blur level or preview length after publishing? > > For single images, audio and video, changing the blur level or preview length regenerates the public preview from the original file. Photo gallery contents, order, blur previews and download availability are fixed when created; create a new gallery for a different collection. > [accordion] Do Pay to Unlock products support custom fields or multiple quantities? > > No. Each Pay to Unlock product is a single image, photo gallery, track, or video sold as one item, so the custom fields step and quantity selection are skipped automatically. ## Next Steps > [card] [Digital Products](/products-and-pricing/digital-products) > > The delivery system Pay to Unlock is built on > [card] [PayRequest Upload](/products-and-pricing/quick-upload) > > The fastest way to create a Pay to Unlock link — just drop the file > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [Shop Setup](/shop-and-checkout/shop-setup) > > Configure your shop to showcase Pay to Unlock products > [card] [Customer Portal](/customer-management/customer-portal) > > How customers access their unlocked files # PayRequest Marketplace Source: https://docs.payreque.st/products-and-pricing/payrequest-marketplace Find digital downloads from independent creators or apply to sell eBooks, templates, workbooks, and design assets on PayRequest Marketplace. [PayRequest Marketplace](https://payrequest.me/) is a public catalog for buying and selling digital products. Buyers can browse by category or search for a specific download. Creators can submit a product for review before connecting a payment provider. ## Buy a digital product [Explore the Marketplace](https://payrequest.me/) and open a listing to see its price, what is included, and any software requirements or usage license supplied by the seller. Complete payment on the product page to get access to the digital files. ## Apply to sell a digital product 1. Open [Sell your product](https://payrequest.me/sell) with your own verified PayRequest account. If you are signed in on payrequest.app and arrive directly from there, the Marketplace can carry over your session. If prompted, choose **Continue with PayRequest**. 2. Add a title, category, description, proposed price and currency, seller country, cover, and product file. Confirm that you have permission to sell the content. You can save a text draft and return to it later. 3. Submit the product for review. Your application and files stay private while PayRequest reviews them. Check [My products and sales](https://payrequest.me/seller) for the review status and feedback. 4. After approval, choose the buyer usage license and accept the Marketplace selling terms. PayRequest verifies payment and settlement arrangements before activating sales. 5. When the product is live, copy its public link and share it with your audience. Use the **Profile** tab to update the name, avatar, and bio shown on your live listings. Submit a revision when you need to change a product's reviewed contents. Good candidates include original eBooks, workbooks, spreadsheets, printable planners, templates, design assets, and other downloadable content. Describe the files and formats buyers receive, which apps they need, and what the license allows. ## Commission, sales, and payouts The Marketplace commission is **10% per sale**. The **Sales and earnings** tab shows eligible sales and indicative earnings. Your final settlement accounts for applicable tax, payment processing costs, and reversals. During the pilot, payouts are reconciled manually. The **Payouts** tab shows statements once prepared and records when a transfer has been completed. The review decision and the sales activation status are shown separately in the seller dashboard. ## Marketplace or your own storefront? Use a marketplace when people should be able to discover your product by searching or browsing a public catalog. Use your own storefront or a direct payment link when most buyers already find you through your website, newsletter, or social accounts and you want more control over the purchase experience. Compare the full costs, including listing, platform, and processing fees, alongside licensing, delivery, and payout terms. | What you sell or need | Platforms to compare | | - | - | | Printables, planners, patterns, and templates | [Etsy digital listings](https://www.etsy.com/seller-handbook/article/how-to-sell-digital-downloads-on-etsy/47330319230) | | Graphics, fonts, and other design assets | [Creative Market](https://creativemarket.com/about) | | eBooks for the Kindle Store | [Amazon Kindle Direct Publishing](https://kdp.amazon.com/en_US/publish) | | Direct links alongside marketplace discovery | [Gumroad direct sales and Discover](https://gumroad.com/pricing) | | A hosted store for digital downloads or courses | [Payhip](https://payhip.com/features/sell-online) | With PayRequest you can [submit a Marketplace listing](https://payrequest.me/sell) for discovery or [sell digital products through your own PayRequest page](/products-and-pricing/digital-products) with a connected payment provider. Marketplace publication depends on review and sales activation. Discovery depends on what buyers search for. # Private tours Source: https://docs.payreque.st/products-and-pricing/private-tours Sell private group tours and receive custom tour requests on your own Page. Offer a fixed-price private tour to customers who find you through Instagram, hotels, WhatsApp or recommendations. Customers can book an available time or ask you to prepare a custom proposal. ## Set up a private tour 1. Open **Products → New Product** and choose **Booking**. 2. Enter the tour name, description, image, currency, tax settings and price. The price covers **one entire group**, rather than each guest. 3. In **Booking Settings**, enable **Private tour**. 4. Enter the maximum number of guests, available languages separated by commas, and the meeting point. 5. Set the tour duration, working days, available hours, advance notice and travel buffer. 6. Choose full payment or a fixed/percentage deposit under **No-show protection**. 7. Save the product and select it among the products displayed on your **Page**. For example, offer a two-hour city walk for €240 per group with up to six guests. With a 25% deposit, the payment split is €60 now and €180 remaining, before any additional tax required by your tax settings. Set and check your tax settings before publishing. ## Let guests book a package Your Page displays **Private tours** with **Book this tour** buttons. Guests choose a date, time, guest count and an offered language. PayRequest checks the guest limit and language again during checkout. Changing the number of guests does not multiply the group price. Your opted-in private tours share one calendar for your business. An existing pending or confirmed booking blocks overlapping private tours, including travel buffers. This mode assumes one guide; ordinary booking products keep their own availability. > [!WARNING] > > A time slot is checked before payment starts, but is not held during payment. Simultaneous or delayed payments can still need manual review. Review your bookings before confirming travel arrangements with guests. ## Receive custom tour requests Enable **Accept quote requests** in your Page settings. Guests can then choose **Request a private tour** and enter their preferred tour, date, language, group size, pickup location and wishes. Custom requests may ask for more guests than the package permits or for another language. You decide whether you can accommodate the request. A request does not confirm availability or reserve a time slot. ## Prepare a proposal with an advance payment 1. Open **Requests** and select the custom tour request. 2. Choose **Prepare proposal with deposit**. 3. Review the prefilled customer and tour details. 4. Enter your agreed price, tax and terms, and confirm availability separately. 5. Adjust the suggested 25% deposit as needed, then save and send the quote through the existing quote flow. 6. After the customer approves, use the existing quote-to-invoice flow for the deposit invoice. Opening the proposal form does not save or send a quote. Quotes do not create a calendar booking automatically. Agree and record the date separately. Remaining balances are not automatically charged by the private-tour feature. ## Current scope This version supports fixed group packages and custom requests with proposals. Variable hourly prices, per-person seat inventory, multiple guides and automatic calendar reservations from accepted quotes are not included. See [Booking Calendar](/products-and-pricing/booking-calendar) for availability and deposit settings, and [Quotes to Invoices](/invoices/quotes-to-invoices) for invoicing an approved proposal. # 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. > [!NOTE] > > 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 **1. Open the product** Go to **Products**, then create a new product or open an existing product and choose **Edit**. **2. Find Frequently asked questions** In the product details section, find **Frequently asked questions** and click **Add question**. **3. Write the question and answer** Enter a short customer-facing question. Use the rich-text editor to format the answer with headings, emphasis, lists, and links when helpful. **4. Add or reorder questions** Add up to 20 questions. Use the up and down arrows to control their order, or use the delete button to remove one. **5. Save the product** 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. > [card] Delivery > > Explain what the customer receives, how it is delivered, and when it becomes available. > [card] Usage and licensing > > State whether personal use, commercial use, redistribution, or client work is permitted. > [card] Compatibility > > List supported file formats, software versions, devices, or other requirements. > [card] Refunds and support > > Set expectations about refunds, replacements, updates, and how customers can get help. > [!TIP] > > 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 > [accordion] What do I receive after purchasing? > > List the exact files, service, access, or other deliverables included with the purchase. > [accordion] How will my purchase be delivered? > > Explain whether delivery is immediate, sent by email, available as a secure download, or arranged manually. > [accordion] Can I use this commercially? > > Summarize the licence and link to the complete terms when applicable. > [accordion] What happens if I need help? > > Tell customers how to contact you and what information they should include in their request. ## Next Steps > [card] [Creating Products](/products-and-pricing/creating-products) > > Configure product details, pricing, images, and visibility > [card] [Product Sharing](/products-and-pricing/product-sharing) > > 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 > [!NOTE] > > 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 | > [!TIP] > > 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. ## Share a dedicated product website Want a fuller presentation before checkout? Active paid **Premium, Business and Growth** subscribers can [create an AI product website](https://docs.payreque.st/products-and-pricing/ai-product-websites) from an existing product. Publish the reviewed draft and copy its hosted `payrequest.me` website address from the website editor. Visitors select **View price and buy** to open the existing product checkout. This website address is separate from the product's usual **Share** link. Existing product links keep working independently. ## Need Help? > [card] [Smart Links](/payment-processing/smart-links) > > Branded links with analytics > [card] [Creating Products](/products-and-pricing/creating-products) > > 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. > [!NOTE] > > 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 **1. Open your product's pricing settings** In the product wizard or editor, find the **Allow customers to select quantity** toggle. **2. Turn it on (or off)** For eligible product types, this defaults to on. Turn it off if you want customers to only ever buy one at a time. **3. Save the product** 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. > [!TIP] > > 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 > [accordion] Which product types support quantity selection? > > 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. > [accordion] Does quantity affect setup fees? > > No. Setup fees are charged once per order regardless of the quantity selected. > [accordion] Can I set a minimum or maximum quantity? > > 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). > [accordion] Does this work with dynamic payment links? > > 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 > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings > [card] [Custom Fields](/products-and-pricing/custom-fields) > > Add per-unit pricing with Number fields > [card] [Setup Fees](/products-and-pricing/setup-fees) > > Configure one-time setup charges > [card] [Payment Page Dynamic Links](/payment-processing/payment-page-dynamic-links) > > 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 ## Uploading Audiobooks You can now upload M4B audiobook files as digital downloads using PayRequest Upload. This format is recognized separately from regular audio files and treated as an audiobook product type. ### What to Expect * M4B files are validated with special MIME type checks to ensure compatibility. * When generating a payment link with an M4B file, the product uses the dedicated Audiobook type. * On payment pages, an Audiobook card is shown with details and an M4B format label. * Buyers receive the original file for download after payment via the secure download flow. ### How to Upload 1. Go to [payrequest.me/upload](https://payrequest.me/upload). 2. Drag or select an M4B audiobook file. 3. Confirm or edit the title. 4. Set your price. 5. Generate the payment link. ### Buyer Experience Buyers see the audio format labeled as "Audiobook" with an M4B tag. After payment, they receive the full audiobook file via a secure download link. The file contains embedded chapters and metadata; playback features such as chapter navigation and position saving depend on the buyer's audiobook app. > [!NOTE] > > The uploaded audiobook file is delivered unchanged; PayRequest does not convert or stream the book. Be sure you have the rights to distribute the audiobook. **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. > [!NOTE] > > 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. > [card] Any File, Instantly > > Drag and drop almost any file type — audio, video, images, ZIPs, 3D models, fonts, design files — up to 250MB > [card] Auto-Detected Details > > The title is pre-filled from your filename and the file category is detected automatically — both editable > [card] Pay to Unlock, Optional > > For photos and audio tracks, flip on Pay to Unlock to sell behind a free preview instead of an instant download > [card] No Setup Required > > Behind the scenes it creates a normal product and a Smart Link for you — nothing to configure first ## How It Works **1. Drop your file** 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. **2. Check the details** 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. **3. Set a price** Enter what you want to charge. Your account's currency symbol is shown automatically. **4. Optional: Pay to Unlock** 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. **5. Generate your link** 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. > [!NOTE] > > 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. > [!TIP] > > 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 > [accordion] Do I need an account to try it? > > 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. > [accordion] What file types are supported? > > 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. > [accordion] Can I turn a regular upload into a Pay to Unlock product later? > > Yes — open the product from your dashboard and change its type, the same as any product created through the full product wizard. > [accordion] Is the generated link any different from one I create manually? > > 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 > [card] [Digital Products](/products-and-pricing/digital-products) > > The delivery system behind every PayRequest Upload link > [card] [Pay to Unlock](/products-and-pricing/pay-to-unlock) > > Sell photos and tracks behind a free preview > [card] [Smart Links](/payment-processing/smart-links) > > Manage, track, and customize the link PayRequest Upload created > [card] [Creating Products](/products-and-pricing/creating-products) > > The full product wizard, for more control # Sell PDFs and let buyers read online Source: https://docs.payreque.st/products-and-pricing/selling-pdfs Sell a PDF, workbook or edition with a first-page cover and private browser reading after payment. Sell a PDF as a [digital product](/products-and-pricing/digital-products). Buyers receive private access after successful payment and can choose to read in their browser or download the original file. ## Prepare and publish 1. Open **Products → New Product** and select **Digital**. 2. Choose **E-book / PDF** and the PDF format, then upload the finished file. 3. Enter the name, description, price, currency and applicable tax. 4. Review the download allowance and link expiry. These also apply to browser reading. 5. Save the product and make it visible when you are ready to sell. ## Check the cover PayRequest can generate a public cover image from page one of a single PDF. Use a first page suitable for a public product listing. An existing manual cover or gallery is preserved. Generation happens in the background and supports PDFs up to 100 MB. An encrypted, corrupt or unsupported PDF may not generate a cover. The saved upload remains available; add your own cover if needed. Replacing the source file may require a new cover to finish processing. ## What buyers see After payment, **Read edition** is available on supported success, download and order screens. It opens the original PDF in the browser’s PDF reader. Buyers can also choose **Download**. Each explicit reading action uses one remaining download allowance. The link must still be valid and the purchase must retain paid access. Refunds, reversed payments or exhausted access can block reading. Opening the landing page alone does not consume an allowance. Browser controls depend on the buyer’s device. If inline reading is unavailable, use Download and open the file in a PDF app. EPUB files and ZIP bundles use ordinary download delivery. > [!NOTE] > > The public cover is an image, not a public link to the full PDF. Authorized buyers can save their purchased file; this feature does not provide DRM. # 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. > [!TIP] > > 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" > [!NOTE] > > 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. > [!NOTE] > > 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 > [accordion] Can I add a setup fee to an existing product? > > Yes. Edit the product, enable the setup fee toggle, and set the amount. New purchases will include the fee. Existing subscriptions are not affected. > [accordion] Is the setup fee included in the product price display? > > 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. > [accordion] Can I make the setup fee name different per product? > > Yes. Each product has its own setup fee name and description fields. You can call it "Borg" on one product and "Installation" on another. > [accordion] Does the setup fee appear on invoices? > > Yes. The setup fee appears as a separate line item on the invoice with your custom name and description. ## Need Help? > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product configuration options > [card] [Quantity Pricing](/products-and-pricing/quantity-based-pricing) > > Seat-based and quantity pricing # File storage Source: https://docs.payreque.st/products-and-pricing/storage Storage allowances for product files, images and previews. Your storage meter appears on **Products**, in the product editor and on the upload page. It counts original product files, product images and generated audio/video previews. GB means 1,000,000,000 bytes. | Plan | Storage | | - | - | | Free | 1 GB | | Free with the platform-fee reward | 10 GB | | Premium (€5/month) | 10 GB | | Business | 50 GB | | Growth | 50 GB | ## Earn more storage on Free Once PayRequest has verified **€5 in total lifetime platform fees** from your successful payments, your Free account permanently unlocks 10 GB. There is no monthly reset. This increases storage only; your account remains on Free with its usual transaction fees. At a 2% platform fee, €250 in successful EUR payments would generate €5 in fees. Only actual recorded platform fees count. Payment-provider processing charges, test payments, unpaid requests and estimated fees do not count. Verification runs automatically in the background. Foreign-currency fees are converted to EUR using the available exchange rate when first verified; that conversion rate is saved. Missing provider information or an unavailable exchange rate delays credit until verification succeeds. Existing verified payment history is included when available. Solana direct wallet payments have no recorded platform-fee amount and therefore do not earn storage credit. Confirmed Base USDC fees count once the merchant payout has been recorded. The reward stays available once unlocked. Premium provides 10 GB immediately without waiting for fee income; Business and Growth provide 50 GB. ## When you reach your limit New permanent uploads are blocked if the file or its generated preview would exceed your allowance. Existing product files and customer downloads remain available. You can still edit product details. Replacing a file also requires available space for the new upload; a refused replacement preserves the previous file. Remove files you no longer need, upgrade your plan or earn the Free storage reward. Canceling a paid plan does not delete existing files, but new uploads use your current plan's allowance or your unlocked reward, whichever is greater. Temporary upload transport is separate from your permanent product storage. Failed uploads that leave stored objects can still use space until cleaned up; contact support if your meter appears incorrect. # 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. > [!NOTE] > > Trial periods are only available for **recurring (subscription) products**. ## Enabling a Trial **1. Set your product to recurring** In the product wizard's pricing step, enable **Is Recurring** and configure your billing interval. **2. Turn on Enable Free Trial** A new section appears with trial settings. **3. Set the trial duration** **Trial Duration (days)** — how many days the trial lasts, from 1 to 365 days. **4. Add a trial description (optional)** **Trial Description** — a short line explaining what's included, shown to the customer (e.g. "Full access for 14 days"). **5. Save the product** 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 > [!WARNING] > > 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 > [accordion] Can I offer trials on one-time products? > > No. Trials only apply to recurring/subscription products, since they work by delaying the first automatic charge. > [accordion] What happens if the customer cancels during the trial? > > 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. > [accordion] Does the trial apply to existing subscribers if I enable it later? > > No. Trial settings only apply to new subscriptions created after you enable and configure the trial — existing subscriptions keep their original terms. > [accordion] Can I change the trial length after customers have already started their trial? > > 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 > [card] [Creating Subscriptions](/subscriptions/creating-subscriptions) > > Set up recurring billing for your products > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > Understand every subscription status, including Trial > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > What happens if the trial-to-paid charge fails > [card] [Creating Products](/products-and-pricing/creating-products) > > Learn about all product types and settings # Video Series Source: https://docs.payreque.st/products-and-pricing/video-series Sell a video season with free opening episodes, a paywall and one-time access after payment Video Series lets you sell a season of videos from your PayRequest Payment Page. Arrange your episodes, make the opening episodes free, and charge one price to unlock the rest. Viewers watch and buy on the same product page, with a mobile-friendly player and no app installation. Use it for short dramas, original AI-assisted stories, animation, tutorials or other episodic content you have permission to sell. PayRequest handles the series page, checkout and purchase-bound watch link; you supply the videos. > [!NOTE] > > Video Series currently supports **one-time season purchases**. A recurring subscription to a video library, coins and per-view credits are not included. ## Try the live example > [card] [Watch and unlock the demo](https://payrequest.me/payrequest/p/sintel-video-series-demo) > > Watch the first Sintel trailer fragment for free, then select episode two to see the paywall and checkout on the same page. > [card] [View the PayRequest Page](https://payrequest.me/payrequest) > > Find the real season product alongside PayRequest’s other products. The demo titles, descriptions, video labels and default checkout language are English. The example has three short episodes and one free opening episode. Unlocking the season costs **€1.00 including VAT, paid once**. You can inspect the free episode and paywall without buying. Completing checkout is a real purchase. The example uses the official **Sintel** trailer by the Blender Foundation, split into three consecutive fragments with a portrait background and demo labels. It is an existing animated film trailer, not an AI-generated PayRequest production. The original trailer remains [freely available from its creator](https://durian.blender.org/download/). ## How the sales flow works 1. Share a trailer or opening episode on TikTok, Instagram, YouTube or another channel. 2. Link viewers directly to the series product on your PayRequest Payment Page. 3. Viewers watch the configured free episodes, choose another episode, and unlock the season on that same product page. 4. Your existing payment provider processes the purchase through PayRequest checkout. 5. After confirmed payment, the buyer receives a private **Watch season** link. PayRequest does not automatically publish to your social accounts, generate episodes or transfer access from TikTok's own paid Series feature. ## Prepare your episodes First create each episode as a [Pay to Unlock (Video) product](/products-and-pricing/pay-to-unlock#pay-to-unlock-video). Choose a clear episode title and upload the full video. | Setting | Requirement | | - | - | | Series size | Between 2 and 50 episodes | | Video format | MP4 or WebM | | File size | Up to 500 MB per episode | | Ownership | Every episode belongs to the same merchant account | | Currency | Every selected video uses the series currency | | Availability for selection | The video product is active and has an uploaded private file | | Free episodes | At least one opening episode, with at least one episode remaining paid | | Season price | A positive, one-time price | The uploaded originals remain private. Any individual product teaser is a separate file; PayRequest does not reveal a full paid video and limit its playback only in the browser. Originals, covers and generated previews count toward your [storage allowance](/products-and-pricing/storage). Video products remain individual products too. Select only the season on your Payment Page if you want the Page catalogue to promote the season rather than each episode separately. Active videos may also appear in your shop's normal product catalogue. > [!TIP] > > Use a consistent title format, such as “Episode 1 — The invitation”, so customers can recognize the viewing order. ## Create and publish a season **1. Choose Video Series** Open **Products → New Product → Video Series** in the web dashboard. **2. Add the season details** Enter a name, description and optional cover. Explain what is included and whether the season is complete. **3. Select your episodes in viewing order** Select the video products in the order you want viewers to watch them. The first selected video becomes episode one. To move an episode to the end, deselect it and select it again. **4. Choose the free opening episodes** Set **Free episodes at the start**. For a three-episode season, setting this to one makes episode one free and keeps episodes two and three paid. **5. Set the price and publish** Enter the one-time season price and review the currency and tax setting. Save the active season, then add it to the products shown on your Payment Page or use its direct product link. **6. Share the viewing link** Share the product URL from your Payment Page, for example `payrequest.me/yourname/p/your-series`. The video player, episode list, description and checkout are all on this page. Older `/series/...` viewing links redirect to the product page. Your existing merchant-access, payment-provider, country, tax and checkout requirements still apply. The checkout shows the final amount, including applicable tax. Creating a series does not connect a provider or grant payment eligibility. ## What viewers see The product page displays your cover before playback, an ordered episode list, the season description and a next-episode button. On desktop, the player appears next to the product details and checkout; on mobile, it appears above them. Free and locked episodes are labeled separately. The player supports normal browser controls and mobile inline playback. When an episode ends, the player opens the next episode on the same product page. If that episode is locked, viewers see the paywall; its video does not play until the season is purchased. If a viewer pauses a video, the browser can remember its playback position on that device. This is local browser storage, not cross-device watch history. Selecting a locked episode keeps you on the same product page and shows the **Unlock the full season** action, which leads to the checkout form on that page. Directly requesting a paid episode's playback URL without a valid purchase does not unlock it. ## What buyers receive After confirmed payment, the order success page and customer order detail provide a **Watch season** link. The season link is also included through the existing digital-delivery section of the order email. Keep that link private: anyone who has it can use it. Opening it returns the buyer to the same product page with the purchased episodes unlocked for that browser session. The watch code is kept on the server and is not added to the product-page URL or HTML. If the session expires, the buyer can reopen the original private link. This does not sign the buyer into a customer account or replace an existing customer session. PayRequest checks the current order and merchant state whenever a new playback URL is requested. Series watch links have no download counter or automatic expiry. A reversed payment, active dispute, refund being processed, credit note or suspended merchant can block access. Media playback URLs already issued expire after five minutes. ## Editing a published series The episode IDs and their order are saved when the order item is created. Adding another episode later does not automatically add it to previous purchases. Each saved episode still uses the current video file for that product. Replacing or deleting the underlying video can change or remove its availability to existing buyers. Keep purchased episode products and files available; create a new season when you want to sell a different collection. ## Content rights and the demo source Upload videos you own or have explicit permission to distribute and sell. Finding a video on TikTok, YouTube or another website is not by itself permission to copy it into a paid product. For third-party footage, follow the license and attribution requirements of the specific work. The live example uses this creator-provided source: * **Work:** Sintel official trailer, by the Blender Foundation / Durian Open Movie Project. * **Attribution:** © copyright Blender Foundation | [durian.blender.org](https://durian.blender.org/). * **License:** [Creative Commons Attribution 3.0](https://creativecommons.org/licenses/by/3.0/), as described on the creator's [sharing and attribution page](https://durian.blender.org/sharing/). * **Changes:** the trailer is divided into three consecutive excerpts, re-encoded and presented with a blurred portrait background, PayRequest demo labels and visible credit. The original footage remains visible without cropping in the foreground. The demo does not claim ownership of Sintel or endorsement by the Blender Foundation. ## Limitations * The player uses browser video playback and short-lived storage URLs. It does not provide DRM or prevent screen recording. * MOV and M4V remain available for individual video products, but must be converted to MP4 or WebM for use in a series. * Streaming uses storage and transfer resources. Large audiences and long videos need an appropriate storage plan and delivery setup. * There is no automatic recurring library subscription, credit balance, social publishing or external streaming-platform entitlement in this release. ## Related guides * [Create products](/products-and-pricing/creating-products) * [Pay to Unlock video](/products-and-pricing/pay-to-unlock) * [Storage allowance](/products-and-pricing/storage) * [Payment Page product display](/shop-and-checkout/product-display) # 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. > [!NOTE] > > 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 > [accordion] Is there a dedicated compliance export for auditors? > > Not a one-click export today. The Activity Log is view-only in the dashboard — for a formatted compliance export, contact support. > [accordion] Are logs retained forever? > > Yes, activity logs are retained indefinitely with no automatic deletion. ## Next Steps > [card] [Billing Activity Log](/organization-and-automation/activity-tracking) > > Full reference: event types, filtering, and examples > [card] [Two-Factor Authentication](/security-and-compliance/two-factor-authentication) > > 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. > [!WARNING] > > 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 **1. Export your business data** 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). **2. Archive a customer** 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. **3. Delete your own account** 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. **4. Two-factor authentication** 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 > [accordion] Can I fulfill a single customer's 'right to erasure' request today? > > 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. > [accordion] Can a customer export their own data from the customer portal? > > 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. > [accordion] Does deleting my PayRequest account delete my customers' data too? > > 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. > [accordion] Does PayRequest have a Data Processing Agreement (DPA)? > > Contact support directly for DPA requests — this isn't something documented as a self-serve download at this time. > [accordion] Is my customers' data stored in the EU? > > PayRequest's database runs on a Hetzner server in the EU. For specifics relevant to your compliance obligations, contact support. ## Next Steps > [card] [PCI Compliance](/security-and-compliance/pci-compliance) > > How card payment data is handled > [card] [Audit Logs](/security-and-compliance/audit-logs) > > Track who accessed or changed what > [card] [Two-Factor Authentication](/security-and-compliance/two-factor-authentication) > > Add a second login factor > [card] [Support Requests](/customer-management/support-requests) > > 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. > [!WARNING] > > 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 **1. Customer initiates payment** 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. **2. PayRequest redirects to the processor** 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. **3. The provider notifies PayRequest by webhook** 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. **4. PayRequest stores only the masked reference** 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 > [card] [Two-Factor Authentication](/security-and-compliance/two-factor-authentication) > > Add 2FA to your dashboard login to protect access to payment settings and customer data. > [card] [Audit Logs](/security-and-compliance/audit-logs) > > Every account and payment-related action is logged with who, what, and when. ## FAQ > [accordion] Is PayRequest itself PCI DSS certified? > > 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. > [accordion] What card data does PayRequest store for saved payment methods? > > 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. > [accordion] If I connect Stripe instead of Mollie, does the same apply? > > 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. > [accordion] Where can I read more about how saved cards (mandates) work? > > See [Saved Payment Methods](/payment-processing/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. > [!NOTE] > > 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 **1. Open Security settings** Go to **Settings → Security** (`/settings?tab=2fa`). **2. Click Enable** PayRequest generates a TOTP secret and shows a QR code plus a manual setup key. **3. Scan with an authenticator app** Scan the QR code with Google Authenticator (or any TOTP-compatible app) — or enter the setup key manually if you can't scan. **4. Confirm with a code** Enter the 6-digit code your authenticator app generates to confirm setup. Until you confirm, 2FA isn't actually active on your account. **5. Save your recovery codes** 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. > [!TIP] > > 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. | > [!NOTE] > > 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 > [accordion] Which authenticator apps work? > > Any standard TOTP app — Google Authenticator, Authy, 1Password, and similar all work since PayRequest uses the standard TOTP protocol. > [accordion] What happens if I lose my phone and my recovery codes? > > You won't be able to complete the 2FA challenge yourself. Contact support to regain access to your account. > [accordion] Is 2FA required? > > No, it's optional but strongly recommended, especially since your dashboard has access to customer data and payment configuration. > [accordion] Does 2FA apply to my customers logging into the customer portal? > > No — 2FA in PayRequest is for your own dashboard login. The customer-facing portal uses its own separate, session-based login. > [accordion] Do I need to re-enter my password to enable or disable 2FA? > > No. PayRequest uses magic-link (passwordless) authentication, so enabling/disabling 2FA is confirmed with an authenticator code rather than a password. ## Next Steps > [card] [Audit Logs](/security-and-compliance/audit-logs) > > See every login and account change > [card] [GDPR Compliance](/security-and-compliance/gdpr-compliance) > > 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. > [!NOTE] > > Apple Wallet Card is available on iPhone. Android/Google Wallet support is planned for a future release. > [card] One tap to add > > Add your page to Wallet directly from your PayRequest Page settings — no app to install > [card] Built-in QR > > The card includes a scannable QR that opens your PayRequest Page, just like your existing QR code > [card] On-brand > > Shows your business name, handle, and tagline in PayRequest's signature blue ## How It Works **1. Open your PayRequest Page settings** Go to **PayRequest Page** from the main menu. **2. Find the Apple Wallet card** Next to your QR code, click **Add to Apple Wallet**. **3. Confirm in Wallet** On iPhone, this opens the standard Apple Wallet "Add" screen. Tap **Add** to save the card. **4. Show it to customers** 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 | > [!TIP] > > 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 > [accordion] Does the card update automatically if I change my handle or branding? > > 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. > [accordion] Can my customers add my card to their own Wallet? > > 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). > [accordion] Is this available on Android? > > 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. > [accordion] Do I need an Apple ID or special app to use this? > > 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 > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize the name, tagline, and accent color shown on your page > [card] [QR Code Payments](/payment-processing/qr-code-payments) > > 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. ## 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** > [!TIP] > > 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 > [!NOTE] > > 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 > [accordion] Match your brand personality > > 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. > [accordion] Keep it short and looping > > The best GIFs are short (2–4 seconds) and loop cleanly. Long GIFs can feel distracting after the third replay. > [accordion] Avoid anything jarring > > 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 > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize your avatar, colors, and layout > [card] [Checkout Customization](/shop-and-checkout/checkout-customization) > > 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. > [!NOTE] > > 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 **1. Billing information** 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. **2. Payment method selection adapts to the cart** * **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). **3. Available payment methods come from your Mollie settings** 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. **4. Submit** 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 | > [!WARNING] > > 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 > [accordion] Can I make address fields optional? > > 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. > [accordion] Can I offer a discount code at checkout? > > Not currently — the cart checkout doesn't have a coupon/discount code field. > [accordion] Why does checkout only offer credit card for one of my products? > > 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. > [accordion] Do URL parameters override a logged-in customer's saved details? > > Yes — URL parameters take priority and pre-fill over the customer's saved profile data. ## Next Steps > [card] [Shopping Cart](/shop-and-checkout/shopping-cart) > > How products get added and priced > [card] [Spam Protection](/shop-and-checkout/spam-protection) > > Block bots and unwanted traffic > [card] [Checkout Recovery](/shop-and-checkout/checkout-recovery) > > Win back abandoned checkouts > [card] [Setting Up Payment Providers](/payment-processing/setting-up-payment-providers) > > 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. > [!TIP] > > 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 > [!NOTE] > > 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. > [!NOTE] > > 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) > [!WARNING] > > 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 | > [!TIP] > > 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. > [!NOTE] > > 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 > [!WARNING] > > 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 > [accordion] How long are checkout attempts stored? > > Checkout attempts are stored indefinitely so you can track historical patterns and analytics. You can manually delete individual attempts if needed. > [accordion] Can I customize the recovery email template? > > 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. > [accordion] Does this work with guest checkouts? > > Yes, as long as the customer enters their email address during checkout. The email address is required to send recovery emails. > [accordion] Will customers receive automatic 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. > [accordion] What happens if the recovery link expires? > > 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. > [accordion] Can I see what products were in the abandoned cart? > > Yes, the checkout attempt record includes the product name and amount. For shop checkouts with multiple items, the full cart contents are preserved. > [accordion] Is checkout tracking GDPR compliant? > > 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. > [accordion] How do I measure recovery success? > > 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? > [card] [Smart Links](/payment-processing/smart-links) > > Create branded payment links > [card] [Shop Setup](/shop-and-checkout/shop-setup) > > Configure your online shop > [card] [Payment Forms](/payment-processing/payment-forms) > > Set up payment pages > [card] [Email Configuration](/business-settings/email-configuration) > > 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"**. > [!NOTE] > > 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 > [card] A Real Drinks Menu > > 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. > [card] Donor Messages & GIFs > > Supporters can leave a short thank-you note and pick a GIF to go with it, straight from a built-in GIF search. > [card] Automatic X Profile Pictures > > If a supporter shares their X (Twitter) link, their real name, profile photo, and verified badge appear automatically — no upload needed. > [card] Privacy by Default-On > > 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 **1. Switch to Donation mode** Open **PayRequest Page** from the dashboard, scroll to **What to show on your page**, and click the **Donation goal** tab. **2. Choose the Coffee style** 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!"). **3. Build your drinks menu** 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. **4. Name your goal (optional)** Give the goal a title like "Help keep the servers running" or "Coffee fund for late-night updates" — it appears above the progress bar. **5. Set your goal amount and reset period** Same as regular Donation Mode: pick a target amount and choose **Monthly** (auto-resets on the 1st) or **One-time**. **6. Save and share** 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. > [!TIP] > > 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 > [!TIP] > > **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. > [!TIP] > > **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. > [!TIP] > > **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. > [!TIP] > > **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 > [accordion] Can I set my own drink names and prices? > > 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. > [accordion] Do supporters need an X account to tip? > > 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. > [accordion] What happens if I turn off the donor feed? > > 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. > [accordion] Can a supporter hide their message but still appear in the feed? > > 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. > [accordion] Can I switch from Coffee style back to a plain donation ask? > > 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. > [accordion] Which social platforms show an avatar automatically? > > 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 > [card] [Donation Mode](/shop-and-checkout/donation-mode) > > The base fundraising goal, progress bar, and donor feed that Coffee Tips builds on. > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Brand your coffee page with an avatar, tagline, and accent color. > [card] [Celebration GIF](/shop-and-checkout/celebration-gif) > > See how PayRequest's built-in GIF search works elsewhere in the checkout flow. > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > 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`. > [!NOTE] > > 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 > [card] Welcome page > > Introduce new members with formatted text and an optional YouTube or Vimeo video. > [card] Content sections > > Organize posts into topics such as Breakfast, Lunch, Dinner, Tutorials, or Tips & tricks. > [card] Members-only posts > > Publish protected articles with text, images, links, and supported video embeds. > [card] Free members > > Let visitors join with verified email access before they decide to purchase the paid membership. > [card] Pinned post > > Keep one important announcement, challenge, or start-here post at the top of the Community. > [card] Automatic access > > Unlock content after successful membership payment and lock it when membership access ends. ## Set Up Your Community **1. Open Community** Go to **Community** in the dashboard. This feature is available on Premium and higher plans. **2. Configure the membership plan** Create or connect the membership customers buy. Its name, description, image, price, interval, and benefits form the public Community offer. **3. Write the welcome page** Add a welcome heading, formatted introduction, instructions, and optionally a YouTube or Vimeo URL. **4. Configure the public landing page** 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/`. **5. Create sections** Add sections to keep a growing content library easy to browse. You can edit, reorder, or remove sections without deleting their posts. **6. Publish the Community** Turn on **Published** and save. Customer login stays enabled automatically while the Community is published. **7. Choose whether to show the tab** 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. **8. Preview the member experience** 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. > [!NOTE] > > 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: **1. Create a post** Open **Posts** and start a new post. **2. Protect the content** Choose **Everyone**, **Free and paid members**, or **Active members only**. **3. Choose a Community section** Assign the post to a section. Leave it unassigned if it should appear without a category. **4. Publish** 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. > [!NOTE] > > 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 > [accordion] Can I create several pages inside Community? > > Community provides a welcome page plus sections that organize your posts. This creates a simple mini-site structure without requiring a separate website builder. > [accordion] Does Community use my Page design? > > Yes. It reuses the same banner, avatar, theme, profile, and navigation as your normal PayRequest Page. > [accordion] Can non-members see my private posts? > > 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. > [accordion] Can free members comment? > > Yes. Signed-in free members can comment on posts they may read. They cannot open or comment on paid members-only posts. > [accordion] Can someone who bought an e-book enter Community? > > 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. > [accordion] What happens when a member cancels? > > Access normally continues through the paid period and ends when the subscription becomes inactive. ## Next Steps > [card] [Memberships](/shop-and-checkout/memberships) > > Configure pricing, billing, benefits, and access rules. > [card] [Posts](/shop-and-checkout/posts) > > Create and organize protected content. > [card] [Digital Products](/products-and-pricing/digital-products) > > Sell files customers retrieve from their download library. > [card] [Customer Portal](/customer-management/customer-portal) > > 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. > [!NOTE] > > 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 > [card] Solana > > 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. > [card] Crypto Native > > 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 **1. Open your PayRequest Page editor** From the main dashboard, go to **PayRequest Page** and click the **Styling** tab. **2. Find the Page Theme card** 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. **3. Click to select** Click any theme card to select it instantly. The mini-preview shows a thumbnail of what the background and card will look like. **4. Save** 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 | > [!TIP] > > 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 > [accordion] Can I preview the theme before saving? > > 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. > [accordion] Does the theme affect my payment page on a custom domain? > > Yes. If you've connected a custom domain to your PayRequest Page, the theme applies there too. > [accordion] Will visitors see the animated background on mobile? > > 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. > [accordion] Can I use a theme without connecting a crypto wallet? > > Absolutely. Themes are purely visual — they don't require a connected wallet or any crypto features to be enabled. > [accordion] Will more themes be added? > > 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 > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Full guide to avatar, tagline, accent color, and social links on your PayRequest Page. > [card] [P2P Wallet Payments](/payment-processing/p2p-wallet-payments) > > Let other PayRequest users send USDC directly to your wallet from your page. > [card] [Solana USDC Payments](/payment-processing/crypto-payments) > > Accept USDC payments from any Phantom or Solflare wallet on your page. > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > 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. > [!NOTE] > > **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: > [card] 🏪 Brand Consistency > > **Professional Appearance** > > * Match your main website branding > * Consistent customer experience > * Enhanced brand recognition > * Improved customer trust > [card] 📈 SEO Benefits > > **Search Engine Optimization** > > * Better search rankings > * Domain authority building > * Improved click-through rates > * Enhanced local SEO > [card] 🔒 Customer Trust > > **Security & Credibility** > > * SSL certificate included > * Professional appearance > * Reduced cart abandonment > * Higher conversion rates > [card] 📊 Analytics Integration > > **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: **1. Choose Your Domain Strategy** **Subdomain Approach (Recommended)** * `shop.yourbusiness.com` * `store.yourbusiness.com` * `buy.yourbusiness.com` **Subdirectory Alternative** * `yourbusiness.com/shop` * `yourbusiness.com/store` * Requires additional DNS configuration **2. Configure Domain in PayRequest** 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) **3. DNS Configuration** Add DNS records with your domain provider (detailed instructions below) **4. Verification & Testing** * 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: > [tab] Subdomain Setup (Recommended) > > **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 > > > [!WARNING] > > > > **Important**: Ensure proxy/CDN features are disabled initially. You can enable them after verifying the basic setup works. > [tab] Root Domain Setup > > **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] > > > > **Note**: Root domain setup requires additional coordination with PayRequest support for proper routing configuration. > [tab] Advanced DNS Setup > > **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: > [accordion] > > **🎛️ Domain Settings** > > **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 Configuration** > > **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 > > **📧 Email Integration** > > **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 > [card] 🔍 DNS Verification > > **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 > [card] 🔐 SSL Certificate > > **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 **1. Basic Connectivity** * Access shop homepage via custom domain * Navigate through product categories * Test search functionality * Verify responsive design on mobile **2. Product & Cart Testing** * View individual product pages * Add products to cart * Modify cart quantities * Test custom field inputs **3. Checkout Process** * Complete checkout flow * Test payment processing * Verify order confirmation * Check automated emails **4. SEO & Analytics** * Verify meta tags and structured data * Test Google Analytics tracking * Check social media sharing * Validate sitemap.xml accessibility ## 🚨 Common Issues & Troubleshooting ### DNS Propagation Issues > [accordion] > > **🕐 Slow DNS Propagation** > > **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 > ``` > > **🔧 Incorrect DNS Configuration** > > **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 > [accordion] > > **🔐 Certificate Issues** > > **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 > [card] 🌍 International Domains > > **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 > [card] 🏢 Brand Variations > > **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 > [accordion] > > **🎨 Domain-Specific Theming** > > **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 > > **📊 Domain Analytics** > > **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 > [!NOTE] > > **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. > [card] Domain Registration > > **Annual Costs:** > > * .com domains: \$10-15/year > * .org/.net domains: \$12-18/year > * Country TLDs: \$15-50/year > * Premium domains: \$50-500+/year > [card] SSL Certificates > > **Included Free:** > > * Let's Encrypt certificates > * Automatic renewal > * Wildcard support available > * Multi-domain certificates > [card] Performance Impact > > **Optimization:** > > * CDN integration supported > * Caching configuration > * Global edge locations > * Sub-100ms response times ### Performance Optimization **1. CDN Configuration** Enable content delivery network for faster global performance **2. Caching Strategy** Configure appropriate cache headers for static resources **3. Image Optimization** Use WebP format and responsive images for faster loading **4. Monitoring Setup** Implement uptime monitoring and performance tracking ## 📞 Support & Resources Need help with custom domain setup? > [card] DNS Support > > **Technical Assistance** > > * DNS configuration help > * Propagation troubleshooting > * Record verification > * Provider-specific guidance > [card] Domain Migration > > **Migration Services** > > * Existing domain transfer > * Zero-downtime migration > * SEO preservation > * Redirect management > [card] Performance Optimization > > **Speed & SEO** > > * CDN configuration > * Performance auditing > * SEO optimization > * Analytics setup ## 🎓 Next Steps > [card] [Shop Setup](/shop-and-checkout/shop-setup) > > Complete your shop configuration and customize the customer experience > [card] [Product Display](/shop-and-checkout/product-display) > > Optimize how your products are presented to customers > [card] [Checkout Customization](/shop-and-checkout/checkout-customization) > > Customize the checkout flow for better conversion rates > [card] [Analytics Setup](/analytics-and-reporting/insights-dashboard) > > Set up comprehensive analytics and tracking for your custom domain *** > [!TIP] > > **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. > [!NOTE] > > 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 > [card] Live Progress Bar > > Shows total raised vs. your goal in real time, with a percentage and remaining-to-go amount. > [card] Monthly Auto-Reset > > A monthly goal resets on the 1st of each month — no manual reset, no cron jobs. > [card] Public Donor Feed > > Recent donations appear below the bar with name, amount, and relative time. > [card] Pay Any Amount > > Donors can give exactly what they want. Optional preset amounts (€2, €5, €10…) appear as one-click buttons. ## How It Works **1. Switch to Donation mode** Open **PayRequest Page** from the dashboard, scroll to **What to show on your page**, and click the **Donation goal** tab. **2. Set your goal amount** Enter the amount you want to raise (e.g. `10.00`, `100.00`, `2500.00`). Use the currency configured on your business profile. **3. Pick a reset period** 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). **4. Toggle the donor feed** 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). **5. Add suggested amounts (optional)** 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. **6. Save and share** 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 > [!TIP] > > 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 | > [!NOTE] > > 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 > [!TIP] > > 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 > [!TIP] > > **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. > [!TIP] > > **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. > [!TIP] > > **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. > [!TIP] > > **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 > [accordion] Does the goal reset automatically? > > 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. > [accordion] What happens to past donations after a monthly reset? > > 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**. > [accordion] Can donors stay anonymous? > > 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. > [accordion] Can I see who donated what privately? > > 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. > [accordion] Do refunds affect the progress total? > > 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. > [accordion] Can I switch back to Products mode later? > > 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). > [accordion] What currency does the goal use? > > The currency configured on your business profile. All donations are recorded in the same currency for clean totals. ## Next Steps > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Brand your donation page with an avatar, tagline, and accent color. > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > Use your own domain for your donation page instead of payrequest.me. > [card] [Payment Providers](/payment-processing/setting-up-payment-providers) > > Connect Mollie, Stripe, or PayPal so donors can pay through their preferred method. > [card] [Smart Links](/payment-processing/smart-links) > > Build pre-filled donation links for specific tiers or campaigns. > [card] [Coffee Tips](/shop-and-checkout/coffee-tips) > > A friendlier "Buy Me a Coffee"-style version of Donation Mode with a drinks menu, GIFs, and X profile pictures. > [card] [README Badge](/shop-and-checkout/readme-badge) > > 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. > [!NOTE] > > 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 | > [card] [Community](/shop-and-checkout/community) > > 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. > [!WARNING] > > PayPal does not currently support PayRequest Page memberships. It can still process supported one-time purchases. ## Create or Connect a Membership **1. Open Community** In the PayRequest dashboard, go to **Community**. **2. Create or select the plan** 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. **3. Describe the membership** Add the name and description customers should see. The membership name also labels the Community tab on your public Page. **4. Set price and billing interval** Choose a daily, weekly, monthly, or yearly recurring price. Price changes apply to new members; existing subscriptions retain their current price. **5. Add benefits and an image** Enter one benefit per line and optionally upload an image or reuse your Page avatar. **6. Save the plan** 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 > [accordion] Can I create multiple membership tiers? > > Not currently. Each PayRequest Page connects to one membership product, keeping the offer and access rules simple. > [accordion] Where do I edit my membership? > > Use **Community** in the dashboard. Membership products remain visible under Products, but Community is the central setup screen. > [accordion] Can I change the membership price? > > Yes. The new price applies to future members. Existing subscriptions keep the price already attached to them. > [accordion] What can free members read? > > 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**. > [accordion] Can I use PayPal for memberships? > > Not yet. Use Mollie, Stripe Connect, or PayRequest Merchant of Record. ## Next Steps > [card] [Community](/shop-and-checkout/community) > > Create the private welcome page and organize members-only content. > [card] [Posts](/shop-and-checkout/posts) > > Write public or members-only posts. > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize the shared banner, avatar, colors, and Page profile. > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > 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 > [!NOTE] > > **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 > [!NOTE] > > 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) | > [!TIP] > > **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** > [!NOTE] > > 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 | > [!TIP] > > **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 > [card] Monitor Abandonment > > Track checkout-to-payment conversion rates to identify issues > [card] Use Paid-Only Wisely > > Enable for high-volume products to reduce noise, keep default for premium products > [card] Link to Invoices > > Always create invoices for paid orders to maintain financial records > [card] Tag Orders > > 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 > [card] [Creating Products](/products-and-pricing/creating-products) > > Set up products with order creation modes > [card] [Tags System](/organization-and-automation/tags-system) > > Learn about organizing with tags > [card] [Checkout Customization](/shop-and-checkout/checkout-customization) > > Customize your checkout experience > [card] [Smart Links](/payment-processing/smart-links) > > 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. > [!NOTE] > > 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. > [card] News > > Share general announcements, business updates, launch notes, or important changes. > [card] Update > > Tell customers what improved, what changed, or what is coming next. > [card] Changelog > > Keep a simple history of product improvements, fixes, and new features. > [card] Sale > > Promote limited-time offers, discounts, bundles, or seasonal campaigns. > [card] Membership > > Share updates for supporters, subscribers, members, or private communities. > [card] Product Embeds > > Add a product to a post so readers can view it and buy directly from the update. ## Create a Post **1. Open Posts** From your PayRequest dashboard, go to **Posts**. **2. Click New Post** Start a new update and give it a clear title. **3. Choose a type** Pick the type that best matches the post: **News**, **Update**, **Changelog**, **Sale**, or **Membership**. **4. Write your content** Use the editor to format text, add headings, create lists, insert links, add emoji, or embed a YouTube video. **5. Optionally attach a product** 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. **6. Publish or save as draft** 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. > [card] [Memberships](/shop-and-checkout/memberships) > > Set up your recurring plan, benefits, payment provider, member login, and protected content. > [card] [Community](/shop-and-checkout/community) > > 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`. > [!TIP] > > 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 > [!TIP] > > **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". > [!TIP] > > **Keep the first paragraph useful.** Visitors often skim. Start with the main point before adding details. > [!TIP] > > **Use the right post type.** Sales, changelogs, and membership posts feel different to readers. The type helps set expectations. > [!TIP] > > **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 > [accordion] Can I save a post without publishing it? > > Yes. Set the post status to **Draft**. Draft posts stay private until you change them to **Public**. > [accordion] Can I link directly to the Posts tab? > > Yes. Share `payrequest.me//posts` to send visitors directly to your public posts. > [accordion] Can I share one specific post? > > Yes. Open the post from your dashboard and copy its public URL. > [accordion] Can I attach more than one product to a post? > > Currently, a post can show one embedded product. If you want to mention more products, add normal links in the post text. > [accordion] What is the difference between free and paid member posts? > > Free-member posts require a confirmed free signup or paid membership. Paid members-only posts additionally require an active or trial paid subscription. > [accordion] How many posts can I pin? > > One per account. Pinning a different post replaces the current pinned post. > [accordion] Do posts replace my products or payment page? > > No. Posts and Community are built into your PayRequest Page. Your home page, products, Community, and payment options remain available. ## Next Steps > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize the profile, description, color, and social links shown above your posts. > [card] [Product Display](/shop-and-checkout/product-display) > > Learn how products appear on your public page and checkout flow. > [card] [Coffee Tips](/shop-and-checkout/coffee-tips) > > Create a Buy Me a Coffee-style support page with messages and public activity. > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > 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. > [!NOTE] > > 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 > [card] Carousel > > 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. > [card] Grid > > 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 **1. Open your PayRequest Page settings** Go to **PayRequest Page** in the main menu, then click the **Settings** tab. **2. Find the Product Layout section** Scroll down to the **Products** block. Below the product checkboxes you'll see a **Product layout** picker with two buttons: **Grid** and **Carousel**. **3. Select your layout** Click **Carousel** or **Grid** — the button highlights instantly to confirm your selection. **4. Save** 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 > [!TIP] > > 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 > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Customize your avatar, tagline, accent color, and social links > [card] [Category Display Types](/categories/display-types) > > Cards, List, and Price Table layouts for product categories in your shop > [card] [Creating Products](/products-and-pricing/creating-products) > > Add images, descriptions, and pricing to your products > [card] [Apple Wallet Card](/shop-and-checkout/apple-wallet-card) > > 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. > [!NOTE] > > 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 > [card] One-Click Copy > > Grab a ready-made snippet from your dashboard — nothing to write or format yourself. > [card] Works Anywhere Markdown Does > > GitHub, GitLab, npm packages, blogs, forums — anywhere that renders Markdown or plain images and links. > [card] Always Current > > The badge reflects your page live — if you're running a donation goal, it shows the amount raised right now. > [card] Matches Your Page Mode > > The wording adapts automatically depending on whether your page is set to Products, Amounts, or Donation mode. ## How to Get Your Badge **1. Open PayRequest Page** Go to **PayRequest Page** from the main menu — you'll land on the **Overview** tab by default. **2. Find the README badge card** 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. **3. Copy the snippet** 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. **4. Paste it wherever you like** Drop it into your GitHub README, your website, or anywhere else — see below for specific examples. ## Adding It to GitHub **1. Open your repository's README.md** On GitHub, click the pencil (edit) icon on your `README.md` file, or edit it locally and push the change. **2. Paste the snippet** Paste the copied snippet near the top of the file, or under a **Support** / **Sponsor** heading further down — both are common conventions. **3. Commit the change** Commit directly to your default branch, or open a pull request if that's your project's convention. **4. Check it renders** Open the repository page on GitHub — your badge should appear as a small clickable image. Clicking it takes visitors straight to your PayRequest Page. > [!TIP] > > 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 | > [!TIP] > > 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 | > [!NOTE] > > 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 > [accordion] Do I need a handle to use the badge? > > 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. > [accordion] Can I change the badge's color or text? > > 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. > [accordion] Does the badge slow down my README or website? > > No. It's a tiny image, similar in size to any other status badge you might already be using. > [accordion] What happens if I rename my handle later? > > 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. > [accordion] Does it work in GitHub's dark mode? > > Yes — the badge has its own fixed background color, so it stays legible in both GitHub's light and dark themes. ## Next Steps > [card] [Donation Mode](/shop-and-checkout/donation-mode) > > Turn your page into a fundraising goal with a live progress bar and donor feed — your badge shows the running total. > [card] [PayRequest Page Styling](/shop-and-checkout/sales-page-styling) > > Brand your page with an avatar, tagline, accent color, and social links. > [card] [Coffee Tips](/shop-and-checkout/coffee-tips) > > A friendlier "Buy Me a Coffee"-style version of Donation Mode with a drinks menu and GIFs. > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > 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. This now includes a **Profile Banner** — a wide cover image displayed at the top of your PayRequest Page and payment pages, with adjustable crop positions for desktop and mobile. You can customize these branding elements: * **Profile Avatar** - Your photo or logo, with options for object-fit styles (`contain`, `fill`, or `cover`) * **Profile Banner** - A branded cover image with separate desktop and mobile crops and position controls * **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, avatar border, and highlights * **Social Links** - Connect up to 25 social platforms and contact options > [!TIP] > > 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 > [!NOTE] > > 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) > [!TIP] > > 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. > [!NOTE] > > 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. > [!TIP] > > 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**. > [!NOTE] > > 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" > [!NOTE] > > 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. > [!TIP] > > 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 > [!TIP] > > 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. > [!NOTE] > > 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 | > [!TIP] > > The **Add More** section includes a search field — start typing a platform name to filter the list instantly instead of scrolling. ### Adding Social Links **1. Open the Add More section** 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. **2. Enter your profile URL** Paste the full URL (e.g., `https://instagram.com/username`) or just type the address without `https://` — PayRequest adds it automatically. **3. Add contact options** 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. **4. Check the live preview** Every link you add appears instantly in the preview with its brand icon, exactly as visitors will see it. > [!WARNING] > > 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. > [!TIP] > > 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 > [accordion] Use a professional, high-quality avatar > > 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. > [accordion] Keep your tagline focused > > Your tagline should instantly communicate what you do. Avoid jargon or overly clever phrases. Clear and simple wins. > [accordion] Only include active social profiles > > Quality over quantity. It's better to have 2-3 active profiles than 8 dormant ones. Remove links to profiles you no longer use. > [accordion] Write your description for your audience > > Think about who visits your PayRequest Page. What do they need to know? Focus on benefits and outcomes, not just features. > [accordion] Test on mobile > > After saving, visit your PayRequest Page on your phone to ensure everything looks good on smaller screens. ## Frequently Asked Questions > [accordion] Why can't I see some avatar options? > > 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. > [accordion] How do I change my PayRequest Page URL? > > The URL handle is configured in the **Settings** tab, not the Styling tab. Go to Settings and update the "PayRequest Page Handle" field. > [accordion] Can I use custom colors or fonts? > > 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). > [accordion] Why doesn't my avatar update immediately on the live page? > > The preview updates in real-time, but the actual live page only updates after you click **Save Styling**. Make sure to save your changes. > [accordion] What size should my avatar be? > > Avatars are displayed at 96x96 pixels on desktop. Upload an image at least 200x200 pixels for crisp display on high-resolution screens. > [accordion] Do email and phone links expose my contact details? > > 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. > [accordion] Can I link my OnlyFans, Twitch, or other creator profiles? > > 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 > [card] [Crypto Page Themes](/shop-and-checkout/crypto-page-themes) > > Solana and Crypto Native themes for your payrequest.me page > [card] [Apple Wallet Card](/shop-and-checkout/apple-wallet-card) > > Carry your PayRequest Page as a card in Apple Wallet > [card] [P2P Wallet Payments](/payment-processing/p2p-wallet-payments) > > Let visitors send USDC directly to your wallet from your page > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > Use your own domain for your PayRequest Page > [card] [Business Details](/business-settings/business-details) > > Configure your business information > [card] [Product Display Layout](/shop-and-checkout/product-display) > > Switch between carousel and grid for your product showcase > [card] [Visitor Analytics](/analytics-and-reporting/payrequest-page-visitors) > > 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. > [!NOTE] > > 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 **1. Choose a shop name** 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. **2. Add a description and default language** Set a shop description and pick a default language (English, Dutch, French, or Spanish). **3. Go live** New shops are created offline by default. Flip the **Shop Status** toggle to make it publicly visible and start accepting orders. **4. Configure branding** In the **Branding** tab, upload a logo and set a portal accent color (hex code) that's used across your shop and customer portal. **5. Set up a custom domain (optional)** In the **Custom Domain** tab, point your own domain at the shop. See [Custom Domains](/shop-and-checkout/custom-domains) for DNS steps. **6. Review shop settings and legal pages** 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. | > [!NOTE] > > 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 > [accordion] Can I change my shop name after creating it? > > Yes, from the same **Shop** page — just note the URL changes with it, so update any shared links. > [accordion] Can I run more than one shop? > > 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. > [accordion] What happens to existing orders if I turn the shop offline? > > Existing orders, invoices, and subscriptions are unaffected — offline only blocks new visitors from reaching the storefront and starting a new checkout. > [accordion] Does disabling signup log out existing customers? > > No. It only hides the option for new customers to register; customers who already have portal accounts can still log in. ## Next Steps > [card] [Checkout Customization](/shop-and-checkout/checkout-customization) > > See what customers experience at checkout > [card] [Shopping Cart](/shop-and-checkout/shopping-cart) > > How multi-product carts work > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > Put your shop on your own domain > [card] [Vacation Mode](/shop-and-checkout/vacation-mode) > > 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. > [!NOTE] > > 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 **1. Add a product** 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. **2. Quantity behavior depends on the product** 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. **3. Review and edit in checkout** On the checkout page, customers can edit quantity and custom fields per line, or remove an item entirely, before paying. **4. Checkout** 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)). > [!TIP] > > 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 > [accordion] Can customers mix one-time and recurring products in the same cart? > > 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). > [accordion] What happens if a product in the cart becomes unavailable? > > 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. > [accordion] Does the cart apply the customer's tax-exempt status? > > Yes — if a logged-in customer is marked tax-exempt, tax is excluded from every line and the setup fee for that cart. > [accordion] Can a customer buy the same product with different custom field choices as two separate lines? > > 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 > [card] [Checkout Customization](/shop-and-checkout/checkout-customization) > > What happens after "Checkout" > [card] [Checkout Recovery](/shop-and-checkout/checkout-recovery) > > Recover abandoned carts automatically > [card] [Quantity-Based Pricing](/products-and-pricing/quantity-based-pricing) > > Configure per-product quantity selection > [card] [Custom Fields](/products-and-pricing/custom-fields) > > Add priced options to products # Checkout spam protection Source: https://docs.payreque.st/shop-and-checkout/spam-protection Understand automatic checks on public checkout and what to do when a legitimate submission is blocked. PayRequest applies shared protection to public checkout starts and other public submissions before creating records or starting mail delivery. These baseline checks are always active; you do not need to enable them in shop settings. ## Automatic checks * **Submission limits** restrict repeated attempts from an IP address and email address, including attempts across different public routes. * **Checkout cooldowns** slow repeated checkout starts. * **Hidden-field checks** reject submissions that fill fields intended to remain empty. * **Name and email validation** reject invalid or suspicious entries. * **Session protection** requires valid browser requests for protected actions. Public checkout does not require the former Cap challenge. These checks reduce abuse; a customer record or order notification does not confirm payment or ownership of the submitted mailbox. Check the recorded payment status before delivering goods or services. ## If a real customer is blocked 1. Ask the customer to check their name and email address for mistakes. 2. If the message says there have been too many attempts, wait before submitting again. Repeated retries can prolong the problem. 3. Reopen checkout in a current browser session if the session has expired. 4. If the problem continues, contact [PayRequest support](mailto:support@payrequest.io) with the page address, time and error message. Do not include card details, passwords or login links. ## Payment verification stays separate A checkout submission, invoice creation or email notification does not prove payment. Payment-provider confirmation and the normal fulfillment checks determine whether access or delivery is available. [Payment failures](/troubleshooting/payment-failures) · [Order management](/shop-and-checkout/order-management) # 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 > [!NOTE] > > 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. > [!TIP] > > 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 > [accordion] Notify customers in advance > > If possible, announce your vacation period through email or social media before enabling Vacation Mode. > [accordion] Set clear expectations > > Use the custom message to tell customers exactly when you'll be back and accepting orders again. > [accordion] Check pending orders first > > Before enabling Vacation Mode, make sure you've fulfilled or addressed any pending orders. > [accordion] Use automatic end dates > > Set an end date so you don't forget to re-enable orders when you return. ## Frequently Asked Questions > [accordion] Are existing subscriptions affected? > > No. Active subscriptions continue to bill normally. Vacation Mode only prevents new orders and subscriptions from being created. > [accordion] Can customers still pay invoices? > > Yes. Existing invoices can still be paid during Vacation Mode. Only new product purchases are blocked. > [accordion] What happens to my shop visibility? > > Your shop remains fully visible. Customers can browse products and view prices - they just can't complete checkout. > [accordion] Can I enable Vacation Mode for specific products only? > > Currently, Vacation Mode applies to your entire shop. To disable individual products, set their status to "Archived" or toggle "Show in shop" off. > [accordion] What timezone is used for the end date? > > 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. > [!NOTE] > > 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. > [card] Customer Switched Plans > > 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. > [card] Former Customer > > 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. > [card] Completed Project > > 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. > [card] Merged or Restructured > > 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. > [!WARNING] > > 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 **1. Open the subscription** Go to **Subscriptions**, find the subscription, and open its detail page. **2. Cancel first (if still active)** A subscription must be **canceled** before it can be archived. If it's still active, cancel it first. **3. Click Archive** On a canceled subscription, click the **Archive Subscription** button below the Reactivate button. **4. Confirm** A confirmation dialog explains what archiving does. Click **Archive Subscription** to confirm. > [!TIP] > > 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 > [!TIP] > > Reactivation is the only action available on archived subscriptions. This prevents accidental status changes on subscriptions that should stay shelved. ## Best Practices > [accordion] Archive after the dust settles > > 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. > [accordion] Use tags before archiving > > 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. > [accordion] Review your Archived tab periodically > > 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. > [accordion] Archive in batches when discontinuing a product > > 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 > [accordion] Can customers see archived subscriptions? > > No. Archived subscriptions are completely hidden from the customer portal. > [accordion] Are archived subscriptions included in MRR calculations? > > No. Only active subscriptions are counted in MRR and revenue reports. > [accordion] Will archiving delete any invoices or transactions? > > 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. > [accordion] Can I archive an active subscription directly? > > No. You need to cancel it first, then archive. This two-step process prevents accidentally hiding a subscription that's still billing. > [accordion] What's the difference between archiving and soft-deleting? > > 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. > [accordion] Can I search for archived subscriptions? > > Yes. Use the **Archived** tab in the subscription list, or search by customer name — archived subscriptions appear when you're on the Archived tab. > [accordion] What happens to open invoices when I archive? > > 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 > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > Understand all subscription statuses and transitions > [card] [Tags System](/organization-and-automation/tags-system) > > Tag subscriptions for easy filtering and organization > [card] [Cancellation Requests](/subscriptions/cancellation-requests) > > Structured cancellation with notice periods > [card] [Suspending Subscriptions](/subscriptions/suspending-subscriptions) > > 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. > [!TIP] > > 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 | > [!NOTE] > > 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 > [!NOTE] > > 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 | > [!WARNING] > > 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 > [!NOTE] > > 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) ``` > [!NOTE] > > 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) > [!TIP] > > 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 > [!NOTE] > > 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 ``` > [!TIP] > > 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) > [!WARNING] > > 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 | > [!NOTE] > > 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 > [card] [Creating Subscriptions](/subscriptions/creating-subscriptions) > > Set up new subscriptions > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > Configure dunning and retries > [card] [Pausing & Resuming](/subscriptions/pausing-and-resuming) > > Temporary subscription stops > [card] [Trial Periods](/products-and-pricing/trial-periods) > > Configure free trials ## Frequently Asked Questions > [accordion] Can I bill on a specific day of the month? > > 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. > [accordion] What happens if a customer's billing date falls on the 31st? > > 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. > [accordion] Can I change the interval of an existing subscription? > > Currently, you cannot change the interval of an existing subscription. You would need to cancel and create a new subscription with the desired interval. > [accordion] When exactly does billing run? > > The billing job runs daily at 03:00 Europe/Amsterdam timezone. Subscriptions with `next_billing_at` in the past are processed. > [accordion] Do weekends or holidays affect billing? > > 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. > [accordion] How do I give a customer a billing grace period? > > 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 cancellation dates, customer decisions, alternative proposals and confirmations without losing the original request. In **request mode**, a customer submits a reason and PayRequest records an effective cancellation date. A support request keeps the discussion and any proposals together. The subscription remains active pending that date unless an agreed earlier end is confirmed. In **immediate mode**, the customer's confirmed cancellation ends the subscription immediately. Product settings and service restrictions determine which actions are available. See [Customer self-service](/subscriptions/customer-self-service). ## Calculate the effective date The product can use a notice period in **calendar months** or **days**. When calendar months are configured, they take precedence over days. Calendar-month calculations keep the same day where possible and use the last valid day when needed. The effective date is the latest of: * The request date plus the configured notice period. * A later next billing date. * A later explicit contract end on the subscription. For example, one calendar month from October 15 is November 15; this is not an instruction to add 30 days. Check the actual calculated date in the portal and request rather than promising an end date from the product setting alone. The default day-based notice is 30 days when no overriding setting applies. An end date can affect future billing; it does not settle or cancel invoices already issued. ## Review a pending request 1. Open the cancellation in **Requests** and inspect the linked subscription, reason, requested date and effective date. 2. Check existing unpaid invoices, pending collections, paid access and any external service or domain linked to it. 3. Reply to the customer to explain the end date and any separate invoice or service work. 4. Use **Confirm scheduled cancellation** to confirm the agreed date, or prepare an eligible alternative proposal if the customer might prefer one. **Confirm scheduled cancellation** does not cancel a future-dated subscription immediately. The business cannot use the former reject action to withdraw a customer's cancellation. Only the customer can withdraw it, including through explicit acceptance of an eligible alternative. ## Offer an alternative Eligible active, single-quantity subscriptions billed by PayRequest can support these proposals: | Proposal | What the customer reviews | | - | - | | **End earlier** | An earlier agreed end date and consequences for future renewals, service access and any export. | | **Temporary discount** | Discounted price, number of billing periods, first renewal date, VAT basis and the regular price afterwards. | | **Cheaper subscription** | A compatible product, the service change and when the new price begins. | The current discount range is 1–80% for 1–12 billing periods. Product switches require compatible currency, interval and VAT basis. Provisioned services, provider-managed schedules and subscriptions with an active payment retry are excluded from these offers. Other eligibility checks can also hide unavailable options. **1. Prepare terms** Select an available offer, enter its terms and expiry, and add a message if helpful. Its expiry must precede the relevant billing, cancellation and proposed end dates. **2. Preview** Choose **Preview proposal** and review the dates, amounts and future consequences. Previewing does not publish or send the offer. **3. Publish** **Publish proposal and notify customer** makes the offer available in the portal and queues the support notification. A new published offer replaces a previous pending offer. **4. Wait for an explicit decision** The primary customer or an enabled customer administrator reviews the terms, confirms agreement and accepts or declines. The original cancellation remains until the relevant alternative is accepted. Ignoring, declining, withdrawing or letting a proposal expire preserves the original cancellation date. Acceptance of a discount or eligible product switch withdraws the pending cancellation without adding a new minimum term. Changed subscription terms require a new preview and offer. A cheaper product is not an automatic migration for a VPS, domain, VPN or other provisioned service. Arrange external-service changes separately. ## Confirm an already-agreed earlier end If the customer already agreed directly to stop sooner, the account owner can use **End immediately**, enter a reason and review the previous end date and access consequences. Confirm that shutdown and any data export have been agreed, then use **End now and send confirmation**. This is separate from publishing a proposal for the customer to consider. It ends the native subscription and disables future billing/retries; it does not delete an external server. Existing invoices and payments remain unchanged. Review unpaid invoices and pending consolidated items first, and use the separate [credit-note flow](/invoices/credit-notes) for applicable invoice corrections or refunds. ## Automatic processing and confirmations Scheduled cancellations are checked **every five minutes**. Provider and external-service updates may have their own processing times; do not promise an exact second of shutdown. Scheduled and immediate confirmations generate a customer email with the subscription and end date. A later status confirmation is generated when scheduled cancellation takes effect. Inspect the request's email status if the customer has not received it: queued or provider-accepted does not prove inbox delivery. Check the final subscription status and effective date before telling a customer cancellation has completed. A missing email alone is not a reason to submit a second cancellation. ## Domains, access and existing invoices A request can initiate disabling auto-renew on a linked domain registration. Check the registrar result separately; cancellation does not itself delete or transfer the domain. If the customer later stays, review whether renewal needs to be re-enabled. Canceling a subscription or accepting an offer does not erase existing invoices, reverse a settled payment or automatically issue a refund. Agree on export and access for any external service before ending it. ## Share the customer instructions Send [Cancel or pause your subscription](/customer-guide/manage-subscription) so the customer can find their service, review the end date and understand any proposal. > [card] [Customer self-service](/subscriptions/customer-self-service) > > Configure the available customer actions. > [card] [Pausing and resuming](/subscriptions/pausing-and-resuming) > > Manage a temporary pause separately from cancellation. # 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. > [!TIP] > > 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 > [!NOTE] > > 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) ``` > [!NOTE] > > 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 > [!WARNING] > > 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 > [!TIP] > > 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 | > [!NOTE] > > 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 > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > Understand status transitions > [card] [Managing Mandates](/subscriptions/managing-mandates) > > SEPA authorization management > [card] [Billing Cycles](/subscriptions/billing-cycles) > > Configure payment intervals > [card] [Failed Payments](/subscriptions/failed-payment-handling) > > Handle payment failures ## Frequently Asked Questions > [accordion] Can I change the price of an existing subscription? > > 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. > [accordion] What happens if a customer's mandate expires? > > 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. > [accordion] Can customers have multiple active subscriptions? > > Yes, customers can have unlimited active subscriptions. Common scenarios include multiple products, different billing entities, or separate projects. > [accordion] How do I migrate existing customers to subscriptions? > > 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. > [accordion] Can I link an existing subscription to an order? > > 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. > [accordion] Can I offer different prices to different customers? > > Yes! Use the "Custom price" option when creating each subscription. This lets you offer promotional pricing, grandfathered rates, or negotiated enterprise pricing. > [accordion] What's the difference between pausing and canceling? > > **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? > [card] [Products Setup](/products-and-pricing/creating-products) > > Create recurring products > [card] [Trial Periods](/products-and-pricing/trial-periods) > > Configure free trials > [card] [Order Management](/shop-and-checkout/order-management) > > Link subscriptions to orders > [card] [Payment Providers](/payment-processing/setting-up-payment-providers) > > 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. > [!NOTE] > > 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 > [card] No chargebacks > > USDC payments are irreversible once confirmed on-chain. No disputes, no chargeback fees, no refund fraud — even for recurring billing. > [card] Worldwide reach > > Crypto works everywhere. No country restrictions, no currency conversion. Anyone with USDC on Base can subscribe — even without a bank account or credit card. > [card] Funds go directly to you > > The smart contract sends 98% directly to your wallet in the same on-chain transaction. PayRequest never holds your subscription revenue. > [card] No mandate needed > > 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 **1. Create or edit a subscription** 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. **2. Invoices are generated each billing cycle** 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. **3. Customer pays with USDC** 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. **4. Funds arrive in your wallet instantly** 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. > [!TIP] > > **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 > [!NOTE] > > 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: > [card] Invoice with crypto option > > The invoice email includes a **Pay with Crypto** button alongside any other active payment methods. > [card] Scan with their wallet > > A WalletConnect QR code appears on the invoice payment page. Customers scan it with MetaMask, Coinbase Wallet, or any WalletConnect-compatible wallet. > [card] Confirm in their 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). > [card] Instant confirmation > > 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 > [!NOTE] > > 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 > [accordion] Is crypto fully automatic like a SEPA mandate? > > 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. > [accordion] Does the customer need a crypto wallet? > > 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. > [accordion] Can I use crypto for the trial-to-paid conversion? > > 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. > [accordion] What happens if the customer doesn't pay the crypto invoice? > > 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. > [accordion] Are there additional fees for crypto subscriptions? > > 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. > [accordion] Can the customer set up a recurring automatic payment from their wallet? > > 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. > [accordion] What if the USDC amount changes between invoice and payment? > > 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. > [accordion] Can I mix crypto and other payment methods across subscriptions? > > 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 > [card] [Crypto Payments (USDC)](/payment-processing/crypto-payments) > > Full guide to USDC payments on Base — wallet setup, smart contract details, and supported wallets. > [card] [Payment Methods for Subscriptions](/subscriptions/payment-methods) > > Overview of all subscription payment methods — automatic, manual, and crypto. > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > How subscriptions work from creation to cancellation. > [card] [Supported Wallets](/payment-processing/crypto-supported-wallets) > > 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. > [!NOTE] > > Self-service settings are configured per product. Go to **Products** > edit a product > **Customer Portal Actions** to manage these settings. ## Portal Actions > [card] Pause Subscription > > Customers can pause eligible subscriptions where supported. Review future billing and service access; existing invoices remain separate. > [card] Cancel Subscription > > 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. > [!TIP] > > Choose the available actions to match your service and agreed terms. If an action is unavailable, give customers a clear support route and explain how requests are handled. ## Cancellation Modes > [!NOTE] > > [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. A notice period can be configured in calendar months or days. Calendar months use the same day of the following month, or its last day when that day does not exist. The portal shows the calculated end date; an explicit minimum contract term can extend it. ## Proposals during cancellation An account owner can offer an alternative from the cancellation request in **Requests**: * **End earlier:** agree to stop immediately upon acceptance, or on an earlier date on or before the next renewal. Future renewal invoices are waived. Agree on any data export and service shutdown before sending this offer. * **Temporary discount:** offer 1–80% off for 1–12 billing periods, starting with the next renewal. The preview shows the discounted price, VAT basis, first renewal date and regular price after the discount. Accepting withdraws the pending cancellation without adding a new minimum term. * **Cheaper subscription:** switch to a compatible product in the same currency, billing interval and VAT basis. The product changes on acceptance; the new price starts at the next renewal. This option is available for simple recurring services, without a setup fee, trial, new minimum term or linked delivery. A VPS, domain, VPN or other provisioned service needs a separate migration and is not automatically switched. Choose an expiry date, add an optional message and select **Preview proposal**. The preview does not save or send an offer. **Publish proposal and notify customer** makes the offer available in the portal and queues the existing support email notification. Publishing a new offer replaces the previous pending offer; you can also withdraw it. The customer reviews the proposal in the portal, checks the agreement checkbox and explicitly accepts. Only the primary customer or an enabled customer administrator can accept or decline. Ignoring, declining, withdrawing or letting an offer expire preserves the original cancellation date and notice period. Changed subscription or product terms require a new offer. The request retains the offer terms, status, acceptance time and conversation history. These offers currently support active subscriptions billed by PayRequest, with quantity one, a future renewal/cancellation date and no payment retry in progress. Subscriptions billed on an external provider schedule are excluded. Existing invoices and payments remain unchanged; an early-stop offer includes no refund. Review unpaid invoices and pending consolidated invoice items first, and use the existing invoice credit flow when needed. **Confirm scheduled cancellation** confirms the agreed date; it does not stop a future-dated subscription immediately. A business cannot withdraw the customer's cancellation through the former reject action. Scheduled cancellations are checked every five minutes. Proposals do not delete external servers or migrate services automatically. ### Confirming an earlier end as the business If the customer has already agreed to stop sooner, the account owner can select **End immediately** in the cancellation request. Enter a reason and review the subscription and previous end date. Confirm that the earlier service shutdown, any data export and paid access have been agreed with the customer, then select **End now and send confirmation**. This ends the native PayRequest subscription, disables billing/retries and withdraws pending proposals. It does not delete a VPS or other external service. Existing invoices and payments stay unchanged; refunds require the separate invoice credit flow. Unpaid invoices or pending consolidated items must be reviewed first. This business confirmation is separate from an offer: use a proposal when the customer has not yet agreed to the alternative. The original cancellation remains valid until either an agreed earlier end is explicitly confirmed or the customer accepts a proposal. Both scheduled and immediate confirmations generate a customer email using the customer's saved language, with the subscription name, end date, renewal consequences, portal link and the business as reply contact. A second status confirmation is generated when a scheduled cancellation actually takes effect. The request shows whether the email is queued, submitted to the email provider, suppressed or needs verification. Provider acceptance is not proof of inbox delivery. Repeated confirmation does not create duplicate emails, and an outdated scheduled confirmation is not sent after the end date changes. ## Share customer instructions Send [Cancel or pause your subscription](/customer-guide/manage-subscription) to explain the available actions, end date, existing invoices and alternative offers. Portal access depends on the customer or contact role; see [Contact persons and portal access](/customer-management/contact-persons). ## Next Steps > [card] [Cancellation Requests](/subscriptions/cancellation-requests) > > Set up notice periods and reason collection for cancellations > [card] [Pausing & Resuming](/subscriptions/pausing-and-resuming) > > Learn how subscription pausing works > [card] [Customer Portal](/customer-management/customer-portal) > > Overview of the full customer portal experience > [card] [Support Requests](/customer-management/support-requests) > > Manage customer communications and cancellation requests ## Hetzner server subscriptions For [Hetzner Cloud subscriptions](/integrations/hetzner-cloud), the customer’s **Server** tab shows server details and permitted controls. Existing servers can be manually linked, with customer reboot and console access enabled separately. Automatically delivered servers require valid paid access for customer controls. Cancelling a subscription does not automatically stop or delete its server, or revoke Linux/SSH access. Hetzner continues charging while the server exists. Review termination, backups and remaining paid access separately. # 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) > [!NOTE] > > 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 > [!WARNING] > > 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** > [!TIP] > > 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 > [!WARNING] > > 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 > [!NOTE] > > 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 > [accordion] Set Appropriate Retry Limits > > * **Standard subscriptions**: 2 retries > * **High-value subscriptions**: 3-4 retries > * **Annual subscriptions**: 4-5 retries > [accordion] Monitor Retry Status Regularly > > 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 > [accordion] Contact Customers Between Retries > > If the first retry fails, consider: > > * Sending a friendly reminder email > * Asking them to update their payment method > * Offering alternative payment options > [accordion] Review Failed Subscriptions Monthly > > For subscriptions that exhausted all retries: > > * Contact the customer directly > * Offer a manual payment link > * Consider pausing instead of canceling ## FAQs > [accordion] Will retry attempts charge the customer multiple times? > > No. Each retry is a separate payment attempt. The customer is only charged once when a payment succeeds. > [accordion] Can I manually trigger a retry? > > Yes. Go to the subscription detail page and click "Process Payment" to create an immediate payment attempt. > [accordion] What if the customer updates their payment method? > > The next scheduled retry will automatically use the updated payment method. > [accordion] Do retries cost extra? > > No. Retry attempts are included in PayRequest at no additional cost. > [accordion] Can I disable automatic retries? > > Yes. Set "Max Retry Attempts" to 0 in the subscription settings to disable automatic retries. > [accordion] What happens if a retry succeeds after I've canceled the subscription? > > 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. > [!TIP] > > 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 | > [!NOTE] > > 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** > [!NOTE] > > 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 | > [!NOTE] > > 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 > [card] [Payment Methods](/subscriptions/payment-methods) > > Switch between automatic and manual payment > [card] [Creating Subscriptions](/subscriptions/creating-subscriptions) > > Set up subscriptions with mandates > [card] [Failed Payments](/subscriptions/failed-payment-handling) > > Handle payment failures > [card] [Payment Providers](/payment-processing/setting-up-payment-providers) > > Configure Mollie integration ## Frequently Asked Questions > [accordion] How long does a mandate last? > > 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. > [accordion] Can a customer have multiple mandates? > > 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. > [accordion] What happens if a mandate is revoked during an active subscription? > > 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. > [accordion] Can I transfer a mandate to a different subscription? > > 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. > [accordion] Why did my customer's mandate fail even though they just authorized it? > > 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. > [accordion] Can customers in other countries use SEPA mandates? > > 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. > [accordion] How do I know if a mandate is about to be revoked? > > 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. > [accordion] What's the difference between a mandate and a payment method? > > 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? > [card] [Saved Payment Methods](/payment-processing/saved-payment-methods) > > Customer payment method management > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > Understand subscription states > [card] [Mollie Setup](/payment-processing/setting-up-payment-providers) > > Configure your payment provider > [card] [Troubleshooting](/troubleshooting/payment-failures) > > 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. > [!TIP] > > **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** > [!NOTE] > > 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 > [!NOTE] > > 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 > [!TIP] > > 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 > [!NOTE] > > 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 > [accordion] Does switching to manual payment cancel the customer's mandate? > > 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. > [accordion] What happens if I switch during a billing cycle? > > 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. > [accordion] Can I use different payment methods for different subscriptions of the same customer? > > Yes! Each subscription has its own payment method setting. A customer could have one subscription on automatic payment and another on manual payment. > [accordion] Will the customer be notified when I switch their payment method? > > 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. > [accordion] What if the customer has no mandates available? > > 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 > [accordion] I manually marked an invoice as paid — was a subscription created? > > 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 > [card] [Managing Mandates](/subscriptions/managing-mandates) > > Set up and manage SEPA mandates > [card] [Billing Cycles](/subscriptions/billing-cycles) > > Configure billing intervals and timing > [card] [Bank Transfer Payments](/payment-processing/bank-transfer) > > Accept bank transfer payments > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > 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. > [!NOTE] > > Bulk price adjustments are available from the **Bulk Actions** page at **Dashboard > Bulk Actions > Subscriptions > Apply Inflation Adjustment**. > [card] Multiple Methods > > Increase by percentage, fixed amount, or set a specific new price > [card] Smart Rounding > > Round results to the nearest EUR 0.50, EUR 1.00, or EUR 5.00 > [card] Schedule Changes > > Apply immediately, on a specific date, or at each subscription's next renewal > [card] Legal Compliance > > Built-in Dutch law compliance with 30-day notice and cancellation rights ## How It Works **1. Select Subscriptions** 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. **2. Configure the Increase** 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 **3. Preview the Impact** Review the price change preview showing each subscription's current and new price, plus MRR impact cards showing total revenue change. **4. Confirm and Execute** 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 | > [!TIP] > > 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 | > [!NOTE] > > 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 > [!WARNING] > > 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. > [!TIP] > > 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 > [accordion] Can I undo a price increase? > > 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. > [accordion] What happens to scheduled increases if a subscription is canceled? > > Scheduled increases are automatically skipped for subscriptions that are no longer active. The increase status is set to "cancelled" and no change is applied. > [accordion] Can I apply different rates to different subscriptions? > > 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. > [accordion] Does the price change sync to Mollie? > > 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 > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > Learn about all available bulk actions > [card] [Billing Cycles](/subscriptions/billing-cycles) > > Understand how billing intervals work > [card] [Email Templates](/invoices/email-templates) > > Customize the price increase notification email > [card] [Tags System](/organization-and-automation/tags-system) > > 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. > [!NOTE] > > 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. > [!WARNING] > > 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 > [!TIP] > > 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**. > [!NOTE] > > 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 > [accordion] Include Invoice Reference in Reason > > 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. > [accordion] Send Invoice Before Suspending > > 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. > [accordion] Use with Debt Collection > > 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. > [accordion] Check Insights Dashboard Regularly > > The Action Required section shows suspended subscriptions. Review these weekly to follow up with customers or decide whether to cancel. ## FAQs > [accordion] Can the customer unsuspend their own subscription? > > No. Suspension is admin-only. The customer can only resolve it by paying the overdue invoice, which triggers automatic reactivation. > [accordion] Will the customer still be billed while suspended? > > No. Suspended subscriptions are excluded from billing. Billing resumes only after reactivation. > [accordion] What if I want to suspend multiple subscriptions for the same customer? > > You'll need to suspend each subscription individually from its detail page. > [accordion] Is the suspension email customizable? > > Yes. Go to **Settings > Email Templates** and edit the "Subscription Suspended" template to match your tone and branding. > [accordion] Does suspending affect the customer portal? > > 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. > [!WARNING] > > 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 > [card] Price > > 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. > [card] Custom Fields > > 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. **1. Open the subscription** 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. **2. Review the differences** 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 **3. Select which changes to apply** 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. **4. Confirm** Click to sync the selected fields. Only this subscription is updated. > [!WARNING] > > 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 > [accordion] If I change a product's price, does it update existing subscriptions? > > No. The new price only applies to subscriptions created after the change. To update existing subscriptions, use [Bulk Price Adjustments](/subscriptions/price-adjustments). > [accordion] If I add a new custom field to a product, do existing subscriptions get it automatically? > > No. Use the **Sync with Product** tool on each subscription's detail page to add it manually. > [accordion] Can I sync custom fields for many subscriptions at once? > > Not currently — the Sync with Product tool works one subscription at a time from that subscription's detail page. > [accordion] What happens to a field's stored value if I sync a removed field? > > 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 > [card] [Bulk Price Adjustments](/subscriptions/price-adjustments) > > Push price changes to existing subscriptions in bulk > [card] [Custom Fields](/products-and-pricing/custom-fields) > > Learn how custom fields work on products > [card] [Subscription Lifecycle](/subscriptions/subscription-lifecycle) > > 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 > [accordion] I made a change but don't see it reflected yet. > > 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. > [accordion] Where do I report a bug or something not covered here? > > 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 > [card] [Sync Problems](/troubleshooting/sync-problems) > > Fix provider data that looks out of date > [card] [Payment Failures](/troubleshooting/payment-failures) > > Diagnose declined or stuck payments > [card] [Email Delivery Issues](/troubleshooting/email-delivery-issues) > > Fix bounced or undelivered customer emails > [card] [Custom Domains](/shop-and-checkout/custom-domains) > > 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. > [!NOTE] > > 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 **1. Go to the customer profile** Navigate to **Customers** and click the affected customer. A red **Email Delivery Blocked** warning appears at the top. **2. Check the bounce details** The warning shows the bounce type, date, and SMTP error message. Use this to determine whether the email is permanently invalid or temporarily unreachable. **3. Fix the email address** If the address is wrong, click **Edit Customer** and enter the correct email. This automatically clears the suppression and removes any "Invalid Email" tags. **4. Or clear the suppression manually** 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 > [!TIP] > > 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 > [card] [Email Health & Suppression](/customer-management/customer-health) > > Full guide to the bounce suppression system > [card] [Payment Reminders](/invoices/payment-reminders) > > 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. > [!NOTE] > > 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 | > [!NOTE] > > **Failed**, **Canceled**, and **Expired** describe different outcomes for a particular attempt. They do not prove that no other payment or reservation exists: 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 **1. Open the transaction** Find it under **Transactions**, or from the related customer/invoice/order. **2. Check the status and timestamps** The detail view shows `Failed Date` or `Canceled Date` where applicable, alongside the payment method used. **3. Sync with the provider if the status looks stale** 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. **4. Look for a pattern** 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. ## Stripe Currency or Amount Errors If checkout reports an unsupported currency, check the product's saved currency and your connected Stripe account. PayRequest supports 139 Stripe presentment currencies, including AUD; availability still depends on Stripe's account-country and payment-method rules. Reconnecting an otherwise active Stripe account is not the first troubleshooting step. Check these details before retrying: * **Currency:** confirm the product uses the intended currency. Changing the currency does not convert its numeric price. * **Amount precision:** JPY and KRW require whole amounts. Stripe also requires whole amounts for ISK and UGX. PayRequest rejects unsupported fractions rather than silently changing the charge. * **Payment method and minimum amount:** a method may require a particular currency or a minimum charge. Check the specific error in Stripe before changing the price. If the customer may already have paid, verify the exact payment first. A checkout error alone does not prove that no other payment succeeded. See [Stripe currency guidance](/payment-processing/connect-stripe#choosing-your-currency). ## 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). ## When the customer has already paid Share [I paid, but my invoice is still open](/customer-guide/invoice-still-open). Check the exact invoice and payment references before retrying or asking for another transfer. A failed or expired attempt does not rule out a different successful payment or authorization. An **I have paid** confirmation for an external method needs receipt verification by the business. ## FAQ > [accordion] A payment shows as Failed but the customer says they were charged. What do I do? > > 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 that attempt failed, check whether another payment or reservation exists before drawing a conclusion. Compare the exact references and ask the customer for the relevant pending/completed bank entry if needed. > [accordion] Can I manually mark a failed payment as paid? > > 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. > [accordion] Does a Failed payment retry automatically? > > 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 > [card] [Failed Payment Handling](/subscriptions/failed-payment-handling) > > Automatic retries and chargeback handling for subscriptions > [card] [Checkout Recovery](/shop-and-checkout/checkout-recovery) > > Recover abandoned checkouts before they become failed payments > [card] [Sync Problems](/troubleshooting/sync-problems) > > When transaction data looks out of date ## Invoice payment history shows a pending entry A pending transaction entry does not by itself mean the invoice is unpaid. Check the invoice’s current status, amount paid and remaining balance alongside its transaction history. Older pending attempts can remain visible after another attempt has paid the invoice. Do not ask the customer to pay again solely because one history entry is pending. # 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 > [accordion] Why does a page with a lot of transactions take longer to load? > > 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. > [accordion] Is there a limit to how many customers/products/subscriptions I can have? > > 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. > [accordion] Does having many tags slow anything down? > > 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 > [card] [Bulk Operations](/organization-and-automation/bulk-operations) > > Make mass changes instead of editing records one at a time > [card] [Tags System](/organization-and-automation/tags-system) > > Organize large datasets for faster filtering > [card] [Export Functions](/analytics-and-reporting/export-functions) > > 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. > [!NOTE] > > 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 | > [!TIP] > > 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 > [accordion] I clicked a sync button and nothing changed. What now? > > 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. > [accordion] Should I use Fill Gap or Reset Sync? > > 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. > [accordion] Does a sync problem mean I lost data? > > 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 > [card] [Payment Failures](/troubleshooting/payment-failures) > > Diagnose a specific declined or stuck payment > [card] [Webhook Configuration](/organization-and-automation/webhook-configuration) > > Your own outgoing payment notifications, separate from provider sync