Securely process online payments with a variety of popular payment options across 9+ countries.

Checkout services

Services allow a business to separate revenue streams by location, target market, etc.

Services are pre-configured with some settings for the payment process that apply to the majority of the business cases. To customize them, please see the options available here

After successful registration, every business gets a default service. You can create more services as your business needs change over time.

The checkout platform allows multiple services to co-exist under a single business name.

Most businesses ONLY NEED ONE SERVICE (the default service) and no further configuration is required.

Below is the path to a list of all services and it's also where you'll find a button to create a new service:

Dashboard > Service List

---

Configure payment options

What are payment options?

These are channels from payment providers through which customers are able to pay for your services and products on your online stores.

Payment options DO NOT belong to a business. Each service MUST have it's own set payment options configured.

Below is the path to a list of all available payment options which you can activate or deactivate:

Dashboard > Service list > Select a service > Configurations > Payment options

Supported payment options

Here is a list of all supported payment options across available countries. The list of payment methods available for your service depends on the configured countries for your business.

The above list is not final, as we continue to expand our operations, more countries will be added.

Payment Options

Supported Countries

Get your API keys

Each service has a set of API keys used in our integrations and issue resolution. These can be found in the navigation below:

Dashboard > Service list > Select a service > Configurations > API keys

There are grouped into 3 categories:

Application keys

Client Code

Each business (client account) is assigned a unique reference when onboarding. This identifier (id) is primarily important when reporting & resolving issues with our support team.

It's mostly used with a Service Code for troubleshooting.

Service Code

A tag that uniquely identifies your service on the Tingg checkout platform. Enabling you to search and find operations tied to a specific service.

Encryption Keys

These are keys used to securely encrypt your checkout request form field values using AES-256-CBC.

AES-256-CBC is a highly secure encryption algorithm that uses a 256-bit key and operates on data blocks of size 128 bits, making it one of the most secure encryption algorithms available.

IV key

(aka initialization vector) is the information used to ensure that encrypted data is unique and not predictable by adding extra randomisation to the encryption output.

Secret key

aka symmetric key is used together with the IV key to encrypt your data.

Access key

A unique token that's used to double-check your identity when you send a checkout request using Express Checkout. It's usually passed in the URL as query parameters.

OAuth keys

These are keys used to authenticate your application when using the Tingg checkout API, to create a customised payment flow for your business.

Client ID

The client ID is a 32-character hex string public identifier for your Tingg service.

Even though it’s public, it’s best that it isn’t guessable by third parties. By exposing it, makes it slightly easier to craft phishing attacks against your checkout applications.

Client secret

This corresponding pair of the above client ID which is synonymous to a password in the Authentication process when using the custom API.

🚧

API keys gives access to important account functions.

To keep it secure:

• ONLY grant access to necessary parties.
• Avoid storing it in version control services i.e GitHub
• Use a password manager or secret vault in CI/CD pipelines.
• NEVER embed it in mobile apps or browser storage i.e local storage

Simulate visits

Go to the simulate visit page in your service.

Dashboard > Service list > Select a service > Dashboard > Simulate visit

On clicking the **Simulate visit** button, a pop-up will appear to the right on the page, where you fill in the following fields:

These are the same details your customer will be required to provide except for the Amount & Account Number which should be generated by your system.

And click on the Simulate visit button.

You will be redirected to a checkout page listing all your configured payment options. For card payments use one of the following test cards

Click on the payment option you wish to test and fill in the details as required.

Simulate payments

You can then simulate a payment for a checkout visit. Make sure to use the SAME Account number as the one used in the checkout visit simulation.

To do this, you'll need to navigate to:

Dashboard > Service list > Select a service > Configuration > Payment methods

Click on the Simulate payment button and a pop-up will appear to the right on the page, where you fill in the following fields:

Fill in the required fields and click on Pay. Your test payment will be recorded and the balances updated