# Overview

# Introduction & Prerequisites

The Gift Cards use case is meant for companies who wish to distribute gift cards to their customers or employees.

In this specific case, the cardholders are not KYC-validated. It may be applied to:

  • Single-merchant gift cards – Cards that may only be used in one merchant’s point of sale.
  • Special events gift cards – Usually specific to your country's legislation, these are cards allocated by a company on special occasions such as marriages and children’s births.

We propose two guides to help you through the Gift Cards use case: No-code or API.

# No-code guide

Recommended for people who wish to get started with no development effort.

Once you’ve gone through the prerequisites listed below and have access to your Dashboard, you’re good to go!

Start your no-code implementation →

# API guide

Recommended for people with experience working with APIs.

Once you’ve completed the prerequisites and got your credentials, you’re good to set up your favorite development and testing tools (e.g., set up our Postman Collection).

Start integrating Treezor API →

Paperclip icon

Prerequisites – Before starting this use case, make sure that you’ve:

  • Created your company, its legal representatives, shareholders and its Master Wallet (see Creating your company guides)
  • Gone through the KYC validation process for your legal entity
  • Set up a Card Program with Treezor (it may be a default one provided with your Sandbox)

# Functional architecture

The use case relies on the following actors and objects:

  • Your company – The legal entity (corporate user, legal representatives and ultimate beneficial owners).
  • End users – Physical persons (not KYC-validated) who will use the gift cards.
  • Master Wallet – The wallet attached to the legal entity (your company), and through which all the funds are going to transit.
  • Cards – The final gift cards, which may be physical or virtual. They are attached to both your Master Wallet and the end users they are allocated to.
functional architecture diagram

# Financial flows

The following money flows will occur in this use case:

  1. SEPA Credit Transfers – Your company wires the necessary amount into its Master Wallet. (Usually to cover about 3 to 4 days of expenses, hence avoiding being short on funds).
  2. Card transactions – Your end users pay in the approved merchants' point of sale (POS) with the cards (attached to the company’s Master Wallet).
functional architecture diagram
Thumbs icon

Best practice – Develop alerting for your Master Wallet

To ensure your transactions never fail due to insufficient funds, we recommend you develop an alerting system to be notified when your Master Wallet is low on funds.

# Keywords

Find below a few terms specific to the use case.

If you have any doubts, you may find more definitions in the Glossary.

# Master Wallet

The Master Wallet refers to the single wallet attached to a company through which all the funds transit.

You may also find the term Titres Spéciaux de Paiements.

# Card Program

The Card Program covers everything regarding the final issued card, from its design and packaging to the features the card provides (i.e., limits, restrictions, etc.).

When creating your cards, you'll need the Id of your Card Program which has been communicated to you by Treezor. This Id is usually referred to as the cardPrintId, card print reference or GPS Id.

Updated on: 6/4/2024, 11:38:32 AM