> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/extensions-addons/flow-gift-card/physical-vs-digital-gift-cards.md).

# Physical vs digital gift cards

In short, when using the Flow Gift Card service, you are totally free in terms of how you want for the gift 'card' to be.

It can be sent digital, or handed out as something physical.

## Physical vs digital cards?

Digital gift cards are convenient as they can be emailed directly to the customer without any physical handling. However, many stores prefer to provide a tangible 'card' to customers.

You have complete flexibility to decide how it shall be delivered after the order has been created.

There is *no* magnetic strip or NFC chip in use for Flow Gift cards. The only thing on the card that is being used is the 16 digit gift card number displayed on the card (as a barcode for easy registration, alongside the card number, which is the representation of the barcode).

### Option: CVC code for added security

In addition to the card number, a 3-digit Card Verification Code (CVC) can be used to verify ownership. This security feature is optional and can be enabled as a setting on the card brand.

When enabled, customers must provide the CVC together with the card number for each transaction.

The CVC is not visible on the actual card. It is typically sent to customers via SMS immediately after purchase. For physical gift cards distributed in bulk, you may consider pre-printing the CVC directly on the card, concealed beneath a scratch-off layer that customers must remove to view the code.

## What can the physical 'card' be like?

A physical gift 'card' can have any form you prefer: It might be a high-quality plastic credit card, or it can be a custom-designed, professionally-produced paper card, in any layout/format you prefer, from standard card format to squared format.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F8fyD6BcGbUxIgFlXZJpc%2Fflow-giftcard-removebg-preview.png?alt=media&amp;token=70b9cb49-8642-4e19-8d1b-39104b4d1113" alt=""><figcaption></figcaption></figure>

## Who produces the physical gift cards?

### Cards from Flow Retail

We offer delivery of batches of up to a few hundred plastic cards with custom designs in a credit-card format. Contact our customer service for details on delivery and pricing.

### 'Cards' produced by yourself / your agency (recommended)

Our recommendation though is to either simply use your local marketing agency or print agency to design and produce 'cards' in whichever format you want.

In both scenarios the gift card number and barcode is produced as printed labels in your store for each time a customer buy a gift card, and which you simply stick onto the 'card'.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/extensions-addons/flow-gift-card/physical-vs-digital-gift-cards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
