> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/canada-doc-center/applications/secure-payment/application-securetable-module/payment-process/gift-card-transactions/gift-card-processing-workflow.md).

# Gift Card Processing Workflow

## Gift Card Processing Workflow

When processing a transaction (sale or refund) using a gift card, the workflow a terminal operator will use depends on the Secure Payment module they are using.

If you are using Secure Payment's **Gateway** module, the gift card is recognized as soon as the operator swipes the card and the appropriate gift card application is launched (DataCandy or Freebees).

If you are using any other Secure Payment module (**App to App**, **SecurePay**, **SecureTable**, or **Standalone Payment**), the operator (or customer) must indicate that the card being used is a gift card by tapping the **Gift card** button.

![Gift card button](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/assets/images/Gift/GiftCardButton_Sale.png)

If the terminal operator or customer do not tap the **Gift card** button before swiping the card, the terminal displays a screen asking if a gift card is being used.

![Gift card terminal question](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/assets/images/Gift/GiftCardButton_Sale_GiftCardQuestion.png)

When you tap the **Gift card** button or answer **Yes** to the gift card question, the Secure Payment application launches the appropriate gift card application (DataCandy or Freebees) to process the sale or refund. When the gift card transaction is complete, the terminal returns to the Secure Payment application.


---

# 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.payfacto.com/payfacto-knowledge/canada-doc-center/applications/secure-payment/application-securetable-module/payment-process/gift-card-transactions/gift-card-processing-workflow.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.