Adding custom fields to capture more payment information
Custom fields is a paid add-on. Once it's on you can capture extra values through Agent Capture Assist or the API, store them in the transaction log, and pass them to your gateway as metadata.
How do I add fields to send additional custom values to Paytia and a payment gateway?
Note: Custom fields is an additional licence. If you require this please contact sales@paytia.com
Custom fields are stored in Paytia transaction logs and where possible sent as additional metadata fields to the associated payment gateway.
Adding Custom fields

From the merchant portal find the Configure user screen menu and then the Data-capture sub-menu, from there you will be able to see the Custom field section.

Using the Add button
Agent form settings you can create your own custom fields that are accessible to use over Paytia API services and also from inside the agent ACA screen.
Add

Description of how the fields work
| Field Name * | This is a required value. It allows you to add a text label to your new field |
| Placeholder Name * | This is a required field. It allows you to write the text form users will see when they use the field in the Paytia Agent Capture Assist interface. |
| Required/Not Required | It allows you to set if this field must be completed or not by your form users |
| Hide/Show | Controls if the field is hidden from the user form. Hidden fields can still be passed to logs and the payment gateway (where supported) |
| Data type | It allows you to set the expected data type so data is rejected if it is not found to be entered in the correct data format |
| Maxlength | Sets the maximum number of characters (including spaces) the field can hold |
| Field control | Controls if the data captured is retained in Paytia logs only, sent to the payment gateway or stored in both locations |
| Payment gateway field | Shows the field on the payment gateway this value will be sent into |
Once you have created a new field Paytia will automatically create a 'slug'. The slug is the field name as it would be sent to Paytia over an API post.
Example showing 'slug' value

API posting
From the API you would add the slug as a body field name.
Postman example

Agent Capture Assist form use
Your new custom fields will be added to the form view below the last system field of 'Account number' and before the system field of 'Payment type' selection.

Once you have all your fields added you are ready to start using the enhanced form service.
More in Payment rules
Can I have more than one merchant ID?
Yes. You can run several Merchant IDs under one gateway and pick between them at the point of payment. Here's how to add the second one.
Can I send my customer a payment receipt?
Yes. Paytia can email a receipt to your customer as soon as their payment goes through. There's a one-off setup step, then your team can send receipts straight from the payment screen.
Can we add account numbers?
Account numbers can be built in two parts, a fixed prefix and a per-customer suffix, then linked to a gateway. It cuts typing errors and speeds up entry on the call.
Controlling Card Brand and Card Type Acceptance with Paytia
You can decide which card brands and card types your business accepts over the phone. Here's the difference between the two, and how to set your rules.
Controlling the International dial prefix on Paytia telephone numbers
Add the countries you actually dial and they appear in the international dial code dropdown. You can pick them one at a time or a whole region at once.
Create and manage Campaign eForms
Campaign eForms let you run targeted donation and payment collections. Here's how to build one, manage it, and what the single- and multiple-campaign licences each allow.
Still need help?
Our support team is here to help. Submit a ticket and we'll get back to you within one business day.