Payments Portal User Guide
Version 1.0 | 01-MAR-2023
Available service actions are dependent on your account configuration.
RequesterRefNo – The merchant’s unique payment reference is available on payments reporting.
UserData – These fields can provide additional merchant reference data.
Template – This identifies which template is used to process the payment. The default value should be
used; available templates depend on your account configuration.
OptionFlags – Reserved for future use; your integration manager will let you know if this field is required.
Username – The user that created/modified the Pay By Link.
Active – Ensure that the box is checked for Active. Otherwise, the recurring payment will not be active, and
the transactions will not be created.
3.4.3 Pay By Link optional detail fields
These fields are optional and are dependent on your account configuration. These values can default
as part of the template.
post_url_success, post_url_fail The URL Planet invokes success/failure; this is a Host to Host message the
customer browser is not involved.
redirect_approved, redirect_declined, redirect_error The URL Planet redirects the customer’s browser to.
merchant_script_data[n] These values can be used to customize what is displayed to the customer. Values
entered here in conjunction with the template configuration transform the payment page displayed to the
customer.
Use an easily identifiable
to allow you to keep track of your Pay by Links.
User Data (1-5) are reference fields. For example,
can be used for a facility or other
reference parameter. Data entered in these fields will be included in each transaction and are
essential for data mining. This must also be kept consistent for all entries.
If you only expect one payment, always select
; the status can always be set back to
active to allow future payments.