Start nowContact sales

Developer tools

Coming soon

Create a payment request using the tools enabled for your merchant account.

Etail APIs and tools are not available yet. This guidance is for existing merchant connections.

On this page

Payment requests

Create a hosted payment request, share it with the customer and match the result to the sale.

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

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

  1. Create the request

    Enter the purchase, total, currency and reference. Check tax, shipping, delivery, expiry and reuse settings available in your account.

  2. Review the checkout page

    Confirm the business identity, purchase details, total and payment methods on the payment page. Check the mobile view and customer terms.

  3. Share the payment request

    Use the link, QR code or button supplied by the request tool. Keep it tied to the purchase; never include card details or credentials in 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. Match the transaction’s merchant, amount, currency and verified state to the order before fulfillment or reminders.

One request can receive several payments
Shared payment requestOne offer or destination
First purchaseOrder and payment

Its own transaction reference and verified result

Next purchaseSeparate order and payment

A different transaction reference and verified result

The request identifies the offer. Each transaction identifies a payment against a purchase.
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.

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.