Skip to main content
The link is a standard HTTPS URL, returned as dropInLinkUrl. Share it through whichever channel fits the interaction:
  • Email
  • SMS or WhatsApp
  • Live chat or a support tool
  • Attached to or embedded in an invoice
  • Sent by an agent during a call
Your customer needs no account, no app, and no login. The link opens in any modern browser on desktop or mobile.

​
Customer communications are yours to send

Payrails does not email or message your customers about Payment Links. You are responsible for:
  • Sending the link itself
  • Payment confirmations and receipts
  • Reminders and follow-ups on unpaid or partially paid links
  • Telling the customer about refunds or reversals
Drive all of these from webhook events. See Track and reconcile.

​
What the payer sees

Example of a Payrails-hosted payment page using Payrails branding, showing the amount due and a payment form The example above uses the Payrails branding. The logo and colors are configurable for your brand.
  1. Payrails validates that the link is enabled and not expired
  2. The page loads your branding, the description you set, and the amount due
  3. The payer enters their details, if payer information collection is enabled
  4. The payer submits payment, and 3-D Secure runs if required
  5. A confirmation or failure screen is shown
The payer interacts only with the Payrails-hosted page. There is no direct connection between your customer and your backend, which is what keeps card data out of your systems.
The confirmation screen is for the payer, not for your systems. Confirm the outcome from the webhook instead.

​
Information collected from the payer

Whether the page asks for payer details at all depends on your configuration.
  • If payer information collection is enabled, the page collects name, email address, and phone number before payment.
  • If it is disabled, none of those are collected and the payer goes straight to paying.
Where payer information is collected, it is included in webhook payloads so you can reconcile and follow up. If collection is disabled, do not build reconciliation or customer contact logic that depends on those fields being present. Payer information collection is set as part of your configuration. See Overview for what to agree at onboarding.

​
Page branding

The hosted page applies your logo, colors, and font, configured by Payrails during onboarding. See Overview for what to supply. Merchant-configurable branding and theming are not yet released. Until it ships, all brand changes go through your Payrails contact.

​
Payment methods

The payer sees the payment methods enabled in the workflow behind the link, set by workflowCode. 3-D Secure and capture behavior follow that same workflow configuration. Apple Pay and Google Pay are available on the hosted payment page. If payment is still required, create a new link and share it.

​
Language

The hosted page is available in English. Localization and right-to-left support are not currently available.

​
Next steps

Last modified on September 28, 2026