Confirmations

PayCertify provides you different ways to get confirmed about the authenticity of your customer’s information. Currently we offer six different strategies that are detailed below. The procedure used to trigger a confirmation process is the same for all strategies.

Before starting to use one of the confirmation strategies available, you must create an initial template for it. This will provide you an initial set of default messages that will be used in the interaction with the end-users that will receive confirmation messages. These messages will appear in the email and sms bodies, web interfaces and into all communication steps. The template creation process is described here.

Each template contains a set of messages that will be displayed to your customer in a given moment of the confirmation process. When a confirmation template is created, these messages are scaffolded with default contents, and they can be modified/customized by using this same API in order to achieve the desired look-and-feel and branding. Also, by customizing these messages you’re allowed to add any particular information that you expect to be shown to your customer into the messages.

It worths to say that once a template is created and customized for a given confirmation strategy, it can be used to trigger many confirmation processes. Of course you can have more than one template for each confirmation strategy, and this will make total sense when a merchant have more than one portal or ecommerce store.

For each confirmation strategy we’ll show you how to create a template and how to use it to dispatch a confirmation for your customer. Below we will show you the six strategies currently implemented in our API: email_ecommerce, email_moto, phone_ecommerce and phone_moto, email_moto_secure, phone_moto_secure.

For each action taken in a confirmation process, the API composes a complete log that provides you a detailed view of the customer’s behavior in this process. Also, whenever the customer interacts with the process, navigation-specific data (IP location, browser details) is gathered and stored with the related actions.

Moreover, you can provide a callback URL in order to receive updates of confirmation process statuses in your own system. This allow you to have a full-automated process integrated with your system’s workflow.