Skip to main content

Implementation Checklist

Implementation Checklist​

Payter test terminals are delivered in a default state. Specifically, they are configured to use the Payter Cloud Payment Service (CPS) integration method with some key configuration values pre-determined. These values represent the most common settings, but one of the key strengths of the Payter solution is the extent to which it can be customized. Whether it is something as simple as extending a timeout value, to wholesale UI and behavior changes, Payter want to track these centrally.

note

For large or complex projects, we will usually start to track these during your Integration Consultation. Where a consultation has not taken place, or for some smaller or simpler solutions, Payter will capture this data towards the end of the Project Delivery phase.

Payter track these changes in a spreadsheet which will be used by our Customer Support teams as needed during the support lifetime of the solution. When Project Delivery is nearing completion, we will seek to ratify the settings.

This might mean:

  • Checking the configured options are all needed
  • Understanding any regional variations
  • Creating Automation to apply settings at key milestones
Important

Payter will use the Implementation Checklist to determine the Protocol Validation tests that are completed.