> 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.md).

# Gift Card Transactions

## Processing Gift Cards

If your business uses gift cards as a payment option, your terminal includes an application to process gift card transactions. When working with Secure Payment, gift card transactions are supported when you identify that the payment method is a gift card or the terminal detects that the card used is not a credit or debit card.

For more information on working with gift cards in the Secure Payment application, please refer to the following topics:

* [Supported Gift Card Transactions](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/Gift/Supported_Gift_Card_Transactions.htm)
* [Gift Card Processing Workflow](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/Gift/Gift_Card_Processing_Workflow.htm)
* [Processing a Sale with Gift Cards](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/Gift/Processing_a_Sale_with_Gift_Cards.htm)
* [Processing a Refund with Gift Cards](https://documentation.payfacto.com/SecurePayment/SecureTable/UG/CA-EN/Gift/Processing_a_Refund_with_Gift_Cards.htm)

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td>Supported Gift Card Transactions</td><td></td><td><a href="/payfacto-knowledge/canada-doc-center/applications/secure-payment/application-securetable-module/payment-process/gift-card-transactions/supported-gift-card-transactions.md">Supported Gift Card Transactions</a></td></tr><tr><td></td><td>Gift Card Processing Workflow</td><td></td><td><a href="/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</a></td></tr><tr><td></td><td>Processing a Sale with Gift Cards</td><td></td><td><a href="/payfacto-knowledge/canada-doc-center/applications/secure-payment/application-securetable-module/payment-process/gift-card-transactions/processing-a-sale-with-gift-cards.md">Processing a Sale with Gift Cards</a></td></tr><tr><td></td><td>Processing a Refund with Gift Cards</td><td></td><td><a href="/payfacto-knowledge/canada-doc-center/applications/secure-payment/application-securetable-module/payment-process/gift-card-transactions/processing-a-refund-with-gift-cards.md">Processing a Refund with Gift Cards</a></td></tr></tbody></table>


---

# 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.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.