A payment page is a hosted page you create for customers to pay. Attempts and fraud analysis are on the page record.
Who can use this. You need payment_pages.index, or super admin.
Before you start. Prepare the amount or the fields the page asks for. The customer page can ask for a full name or company name and a note to the merchant. It can also say: Please verify your identity in order to continue to payment.
Steps
- Open Payment Pages.
- Choose Create Payment Page.
- Complete the page fields, including Enable 3D Secure and Enable Fraud Prevention when those options are available.
- Save. The toast says Payment page created successfully.
- Send the page URL to the customer.
- Open the page record and its attempts to see Fraud Analysis.
- If the list is empty, the text is No payment pages found.
| What you see | Meaning | What happens next |
|---|---|---|
| Create Payment Page | Starts a new page. | Does not charge a card. |
| Payment page attempts | The tries for that page. | Use them when Transaction History has no row. |
| Surcharge | Shown on the page flow when surcharge applies. | The amount the customer pays is on the page, not in this article. |
| Delete | Asks: Are you sure you want to delete this payment page? | Does not refund an earlier approval. |
After you save or submit. A paid page has a transaction. Confirm APPROVAL before you fulfill the order.
Example. Example only: Example Cafe publishes a page for a 30.00 class fee. Fictional customer Avery Patel pays. Attempts shows Allowed, and Transaction History shows Payment Page and APPROVAL.
Troubleshooting
- No payment pages found. You have not created one, or the filter excludes it.
- Identity prompt blocks the customer. The customer must finish that verification step. It is not an approval.
- You wanted the page to renew every month. Use Recurring Payments. A payment page is not the subscription record.
Related
Found this helpful?
( 0 out of 1 found helpful )
