Payment requests

Create a request, check the customer’s checkout and follow the payment back to its order. Keep the request reference separate from the transaction reference.

Business owners and operations teams

Before you begin

  • A configured merchant account with access to payment request tools
  • The purchase details, total and currency
  • The order or invoice reference and terms shown to the customer
On this page

Choose a request for the sale

Match the request to the purchase
SaleRequest to use
A shared offerUse a payment link, checkout button or QR code for an offer that several customers can buy. Each purchase still needs its own order and transaction record.
An individual invoiceUse an invoice when you need itemized charges and payment terms for a particular purchase. Keep its reference and current balance with the order.
Scheduled billingIf recurring billing is available for your account, use its separate setup and authorization process. Paying a request once does not establish a recurring agreement.

Create, review and share

One shared request, separate purchases
  1. Define the offer

    Purchase details, total, currency and terms

  2. Share the payment request

    Payment link, button or QR code

  3. Match each purchase separately
    Customer AOrder and payment

    Its own transaction reference and verified result

    Customer BOrder and payment

    A different transaction reference and verified result

Do not use a reusable request as the unique payment identifier. Each buyer’s purchase keeps its own order and transaction records.

  1. Create the request in the account service

    Enter the purchase description, total, currency and reference. Check the available delivery, tax, shipping, expiry and reuse settings before sharing the request.

  2. Review the checkout page

    Open the generated destination and confirm the business identity, purchase details, amount and available payment methods. Check mobile readability and the terms the customer will see.

  3. Share the payment request

    Use the link, QR code or button supplied by your account’s request tool. Keep it tied to the purchase and keep card details and credentials out of its URL.

Use purchase details in request fields

Use descriptions and reference fields for purchase information. Do not put card numbers, verification codes, bank credentials or identity documents into invoice fields that accept free text.

An offer changes after sharing

Review the supported edit, cancellation or replacement process. Confirm what the customer’s existing link now shows. Changing a request does not rewrite a payment already processed.

Match the payment to the order

Opening a link, scanning a QR code or viewing an invoice does not prove payment. Find the resulting transaction in the correct merchant account and compare its amount, currency and verified processing state with the purchase.

One request, several customers
A reusable destination can produce several legitimate transactions. Associate each payment with its buyer and order; the request ID is not a unique payment ID.
One order, several attempts
Keep the attempt references together. Check whether an earlier payment remains unresolved before asking the customer to try again.
Invoice and transaction status
A sent or canceled invoice is an invoice event. Use the payment record to determine what was authorized, captured or refunded, including any pending action.
What to confirm

Fulfillment and reminders follow the verified payment record for that purchase, not the request’s delivery or viewing status.

Follow up on an unpaid or uncertain request

Keep these references connected
RecordWhat to check
Order or invoiceThe purchase, amount owed and current payment terms.
Payment requestThe hosted destination and its expiry, cancellation or reuse settings, where supported.
Payment and operationEach transaction and any related capture, reversal or refund.
Amount, currency and timeThe values needed to match the result and investigate an uncertain attempt.
The customer says they paid

Search using the order or request references, amount and time. Check unresolved attempts before sending a new request or asking for another payment.

The request is unpaid or expired

Verify its current state and any payment already attempted. Use the supported reminder or replacement process, keeping the relationship to the original purchase.

Two payments look like duplicates

Compare the order and transaction references. Determine whether they are separate purchases or an unintended duplicate before taking a refund action.