> 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/day-to-day-operations/selling/payments/payment-methods/two-invoice.md).
# Two Invoice
Invoice business customers through Two, which credit-checks the buyer and takes the invoice.
## What is this?
Two Invoice hands business invoicing to Two, an external invoice provider. Flow Retail sends the order to Two, Two checks the customer's credit and asks them to approve the purchase, and the invoice is Two's to issue and collect.
Where plain Invoice leaves the credit with you, this puts it with Two.
***
## How does it work?
Two Invoice is for company customers, and it takes the whole order. It cannot share a sale with another payment method — choose it on an order that already has a settlement and the till answers **Can only be used without other settlements**.
The order also needs a named contact person with a mobile number. Both the customer and that contact have to be enrolled with Two first; the till offers to do it on the spot:
> Customer is missing TWO service. Do you want to add?
Enrolling a contact sends them an SMS link, and the till waits on Waiting on activation until they confirm.
When you settle, Flow Retail checks the customer's credit with Two and creates the order there. The till shows **Order sent to Two for approval by customer**, and Two texts the customer a link. The settlement stays in progress until Two reports the customer approved it, then completes on its own.
If Two turns it down, the till says **Order not Approved by Two** with the reason, and the order stays unpaid.
Refunds go back through Two, against the original order.
{% hint style="info" %}
Two sets a maximum single order value per customer. An order at or above that limit is rejected before it reaches approval.
{% endhint %}
Two Invoice cannot be used to pay off an existing invoice.
***
## How do we get started?
Ask us to add the **Two Invoice** extension — that is what makes the payment method available. You then enter the **Two Invoice Merchant ID** and **Two Invoice API Key** you get from Two under **Admin → Settings → Extensions**, and enable the payment method in the stores that should offer it.
Each business customer needs a company name and a VAT number on their record before they can be enrolled with Two, and at least one contact with both an email address and a mobile number.
***
*Last updated 17.09.2026*
---
# 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/day-to-day-operations/selling/payments/payment-methods/two-invoice.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.