Before you import gift cards, the pools that will store them must already exist on the project. Every card in the file must reference an existing pool.
In this article
- Step 1. Choose the action
- Step 2. Prepare and upload the file
- Step 3. Map the file fields
- Step 4. Review and launch the import
- How to track an import
- Import result
Step 1. Choose the action
- Select the import type — Loyalty → Gift cards.
- Select the action — Add gift cards.
Step 2. Prepare and upload the file
- Decide which fields you need to load. The file must contain every required field.
| Field | Required | Description |
|---|---|---|
| Card number | Yes | Unique number of the gift card. |
| Pool system name | Yes | System name of the pool the card belongs to. The pool must already exist on the project. |
| Gift card CVV | No | Required for pools that have CVV transfer enabled. |
| Card balance | Yes | For cards with a fixed face value, the balance must equal the pool’s face value. |
| Point of contact external ID | No | The point of contact where the card was issued. Used when registering cards that were sold in the past. |
| Card purchase date (UTC) | No | Date and time the card was issued, in UTC. Used when registering cards that were sold in the past. For pools with a fixed validity period, the expiration date is counted from this date. |
| Gift card status | No | Current status of the card. If the field is omitted, the card is assigned the “Inactive” status. |
- CanBeUsed — activated. The card can be used to pay for an order. Cards in this status cannot be sold.
- Inactive — not activated. The card can be sold. Once sold, the card becomes activated and can be used to pay for an order.
- Blocked — blocked. The card cannot be sold or used for payment.
-
Export the data from the external system and prepare the file for upload. Put any column names you like in the first row.
- Format —
.csvor.txt. - Recommended encoding — UTF-8.
- Check that the values match the allowed formats.
- Format —
- Upload the file and click Continue.
Step 3. Map the file fields
The system automatically maps the file’s columns to project fields. Adjust the mapping if needed:- In the Import column, check the fields you want to load. Unchecked columns are skipped.
- In the Maestra field column, match each file column to the corresponding project field. Optional fields without a mapping are skipped.
- Click Continue.
Step 4. Review and launch the import
Before launching, the system shows the first rows of the file with the mapping already applied. Make sure the data looks the way you expect — that the right values landed in the right fields. If everything looks good, click Launch import.How to track an import
Once started, the import appears in the list on the Import page. Each job shows:- the launch date,
- the import type,
- who launched it.