All guides
User

Payments

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/packages on your site.

Steps

Use Continue with payment

  1. Open /portal/packages and select the record you want to work with. Its detail/edit address follows /payment/ezone/checkout/{reference}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Find the form containing Payment method, First name, Last name. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Continue with payment. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Payment methodRequired. Enter the payment method for this task, using the help or example shown by the form.
First nameRequired. Enter the first name for this task, using the help or example shown by the form. Maximum 100 characters.
Last nameRequired. Enter the last name for this task, using the help or example shown by the form. Maximum 100 characters.
Customer phone numberRequired. Enter the customer phone number for this task, using the help or example shown by the form. Maximum 30 characters.
Birth yearRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1900.

Use Confirm payment

  1. Open /portal/packages and select the record you want to work with. Its detail/edit address follows /payment/ezone/checkout/{reference}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Find the form containing Confirmation code / Confirmation code (if required). Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Confirm payment. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Confirmation code / Confirmation code (if required)Enter the confirmation code / confirmation code (if required) for this task, using the help or example shown by the form. Maximum 30 characters.

Use Request another OTP

  1. Open /portal/packages and select the record you want to work with. Its detail/edit address follows /payment/ezone/checkout/{reference}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Select Request another OTP. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information
MethodSource-default route
GET/portal/packages
LIVEWIRE/payment/ezone/checkout/{reference}
LIVEWIRE/payment/{plan}
GET/payment/cancel/{gateway}
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
paymentInfomodules/App/AppPayments/Livewire/CheckoutPage.php