> 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/payment-standalone-mode/transactions/force-post.md).
# Force Post
### Force Post
There may be situations where you need to obtain an authorization for a credit card sale directly from the card issuer. In such a case, you must manually enter the authorization code provided by the issuer into the terminal to complete the transaction.
#### **To enter the authorization code for a force post transaction:**
1. Touch **Operations** and touch **Force post** from the menu.
2. Enter the Merchant password and then touch **Confirm**.
{% hint style="info" %}
NOTE: If you have previously disabled password protection for force post transactions, the terminal will not ask for the password.
{% endhint %}
3. Using the number pad, enter the Authorization code provided by the card issuer and touch **Confirm**.
4. Tap, insert, or swipe the payment card.
5. After confirming the force post transaction, the terminal prints the merchant copy of the transaction receipt. To print the customer copy, touch **Print receipt** or touch **No receipt** if no customer copy is requested.
---
# 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/payment-standalone-mode/transactions/force-post.md?ask=&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.
