Full Customization
The complexity of this tool is such that Payter will provide it to licensed partners only. Please contact us if you wish to discuss the terms of using this functionality.
Full Customization Process
There are several steps involved in the process of customizing the layout of a *single screen.
- Design the screen - this can be done on any tool of the licensed partners choice e.g. Figma/Miro/Paper
- Build the screen using the command line interface (CLI) tool
- Test the screen using PSP or CPS
- Submit the screen for approval to Payter's integration team.
Initial Screen Design
Whilst it can be tempting to design a screen from scratch it is recommended that Licensed Partners become familiar with the core Elements that are available. Whilst the choice of possible screens is very large, there remain some limitations in both design and data capture.
Designing a screen outside of the Payter solution is however a key step in ensuring the final screen meets expectations.
Build the Screen
Using the CLI tool, construct, configure and position each Element. The result of each command is instantly viewable on the configured Staging terminal, allowing the designer to trial different settings to achieve their overall goal.
Once saved, it is also possible to replicate elements using the text editor.
For example, a text box is placed at the top of a screen. The same size box is also required at the bottom of the screen. Copying and Pasting the JSON code for the first box and amending the Y value achieved this quicker than redoing all the CLI commands.
Test the Screen
A built screen or element can have it's value and some other key elements amended either by a Cloud Payment Service or Payter Session Protocol command.
Submit the Screen for Approval
Save the template and provide the Hex String to Payter for approval. The Payter team need to ensure that the screen meets payment terminal compliance standards, for example it does not request a PIN is captured.
When approval is completed, Payter can deploy the screen to Staging and Live terminals as a configuration update.