Sending Payments via TrekkSoft API

To maintain PCI compliance, we are updating the process Merchants send credit card payments to TrekkSoft via the API.

Previously payments are sent by the Merchant to TrekkSoft using our Public API (‘Add credit card payment’ method or ‘Create a Booking’ method).

The new process is:

1. Merchant tokenizes a credit card using Payyo Vault. It receives Alias (Token) as a result of the process.
2. Merchant uses alias instead of credit card data in ‘Create a Booking’ method or in newly created ‘Add credit card alias payment’ method.

We appreciate you updating this process to increase security for your customers.

This document guides users on the steps needed to make this change:

Credit card tokenization.

Please follow this guide to tokenize a credit card (vault.storeCreditCard method). If you are not integrated to Payyo directly please contact us for your Payyo:
Public Key
Secret Key
Merchant ID (it is Payyo internal merchant id)

Public Key and Secret Key are necessary to pass authentication during the vault.storeCreditCard method call.

Example Request:

You will receive an ‘alias’/token from Payyo:

Sending Alias to TrekkSoft.

Next you will need to Send the Alias received from Payyo to confirm or create the booking.

We have updated our guide to do this under ‘Add credit card alias payment’ and ‘Create a Booking’.

The alias/CVC entered under the card> alias, CVC.

Please consider that the CVC may only be stored until the first authorization. If you want to make multiple charges to the same credit card you should use Payment Plans.

It is however also possible to use the credit card alias funding instrument and provide the CVC explicitly.   

Payments send directly to TrekkSoft Public API will fail soon.

Soon we will retire the ability to receive payments via our Public API using Add credit card payment or Create a Booking in favour of this new, more secure payment method.