Payment Capture Page
Ezypay’s Payment Capture Page (PCP) let you easily embed and customise the payment capture step in your onboarding flow. With flexible configuration options, you can tailor the experience to match your brand and user journey — all while reducing the complexity of handling sensitive payment data.
What does the Payment Capture Page looks like?
🔍 What’s New in Payment Capture Page?
| Feature | HPP | PCP |
|---|---|---|
| Link the new payment method token to a specific customer | No | Yes |
| Provide multiple payment options for customer to choose to create? | Yes | Yes |
| Display the dynamic customer paid fees as part of the Payment method creation form | No | Yes |
| Allow automated validation check on accepted payment method type based on the merchant setting in Ezypay? | No | Yes |
| Allow integrators/merchant to include their own T&C? | No | Yes |
| Allow styling of the Payment method creation form? | No | Yes |
| Provide a submit button within the payment method creation form to reduce HTTP window listener? | No | Yes |
Example:
Embed the PCP using the following sample URL in an iframe:
{{Ezypay Secure domain}}/embed?customerId=50d5b1b7-93f0-4b52-8a1f-a5d5278acb46&paymentMethods=VISA,MASTERCARD,BANK&feepricing=true
Key specification details
Required Parameters:
| Parameter | Example | Mandatory | Description |
|---|---|---|---|
| paymentMethods | paymentMethods=VISA, MASTERCARD,BANK,PAYTO | Yes | Available payment methods. See supported methods. |
Optional Parameters:
| Parameter | Value Type | Mandatory | Description |
|---|---|---|---|
| customerId | UUID | No | Auto-links the new payment method to a specific customer |
| feePricing | boolean | No | Displays dynamic customer-paid fees for different payment methods. |
| setasprimary1 | boolean | No | Sets this payment method as primary |
| setasprimary2 | boolean | No | Allows the customer to set the newly created payment method as the default option. |
| submitbutton | boolean | No | Use Ezypay’s built-in button or replace it with your own for a fully branded experience |
| termsandconditions | string URL | No | Display your custom Terms & Conditions from a secure URL |
Custom Styling
You can style the embedded form to match your app’s look and feel. You can use CSS to modify input fields and layout.
| Category | Property | Description |
|---|---|---|
| Typography | font-family | Set the font used in input fields |
| font-size | Control text size | |
| font-weight | Adjust text boldness | |
| line-height | Manage line spacing | |
| Spacing & Borders | padding/margin | Set space around elements |
| border-radius | Round input field corners | |
| Colors | color | Text colour |
| background-color | Page and field backgrounds | |
| border-color | Input field border colour | |
| danger-color | Colour for alerts of errors |
What do integrators need to do?
For existing HPP users:
- No customer–payment method linking required
- You no longer need to call the Create Payment Method API separately.
- No need to show customer-paid fees manually
- Fee information is now built-in. No need to call the Retrieve Customer Paid Fees API.
- Use Ezypay’s built-in submit button
- You can remove external submit buttons and rely on the one provided by the form.
- Apply your own style.
- Customise the PCP to match your app branding and layout.
Updated 3 days ago