UBIQ Pay - Payment Form Setup

UBIQ Pay supports several form fields that determine how payments are calculated and processed.

1. Product List
2. Recurring Payment
3. Input 

1. Product List Field 

Drop and drag this payment-specific field to offer preset products or fees. 

What you can configure:

• Value: The price of the item.

• Name: What users will see on the form (e.g., Adult Ticket, Student Ticket).

• Limit:  Limit the number of each product available. This prevents the over-selling of an item. 
   

2. Recurring Payment Field

The Recurring Payment field allows users to make payments on a recurring schedule—ideal for donations or ongoing contributions.

Configuration options:

• Set the available billing frequencies (e.g., monthly, quarterly).

• Users choose from the frequency options you enable.

3. Input Field

To use an Input Field as a payment field, you must change the Input Type to Numeric. This field can be used as a free-form custom payment field that allows users to make donations or gifts in the amount of their choosing. 

To use it for payments, you must also map it in the Settings → Form Payments.

Note: Only one Input Field can be mapped to a payment amount.

After adding your payment fields, click BUILD FORM to proceed to payment configuration.

Navigate to Settings → Form Payments to define how payments are processed.

1. Payment Processor

For Ubiq Pay, your Payment Processor should be UBIQPAY.

2. UbiqPay Account

Select which UBIQ Pay account (if you have multiple) should receive payments from this form.

3, 4 & 5. Invoice Settings

These settings generate the invoice number and help track payments:

• Invoice Prefix: A label added to each invoice (e.g., Prom).

• Invoice Index: The starting number for invoices (e.g., 100).

Example:
Prefix: Prom
Index: 100
Generated invoices: Prom100, Prom101, Prom102, etc.

• Invoice Description: Sent to Stripe to describe what the payment is for.

6. Source Fields (Payment Amount Mapping)

This field is required only if you have used a Numeric Input Field for payment in your form. 

Map the Input field to the payment destination, so Stripe knows where the amount originates. See Step 1 above. 

Additional Source Fields can be found under the Form Contact Mapping section. These fields can be mapped and used for personalising your confirmation messages. This is completely optional.

If you send confirmation emails to form submitters, you can also include the tag [TransactionSummary] in the body of the email. This will then display all payment-related information collected through the form in their confirmation email.