Payment requests are containers for a range of settings that are experienced by a Customer via a payment page, and the data generated through the lifecycle of a real world payment:
- Customer details - the Customer receiving the payment request (name, email, mobile)
- Contact details - Merchant contact details for Customer queries (name, email, phone)
- Custom fields - configured per request or request template, custom data fields the Merchant wishes to collect/display through the payment process
- Payment options - the type of payment request, and options presented to the Customer for payment
- Pay now (recurring) schedule settings
- Pay later product enabled on the payment request
- Product fields required to be completed by the Merchant and/or Customer (FlipPay defined)
- Payment page - the settings to be applied to the payment page presented to the Customer
- Bank account to direct funds to
- Page branding (logo, company details - name, email, web, phone, etc)
- Redirection settings after successful/failed payment attempts
- Notifications - notifications configured to be sent on status changes
- PR - payment request statuses
- TX - transaction statuses
- Transactions - the transactions generated on the payment request