> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/ce/extensibility-and-integrations/payments/invoice.md).

# Invoice

Apart from payment gateways, Emporix supports **invoice (post-checkout)** as a payment mode. This is common in B2B flows, for example net terms.

Invoice is configured through the Payment Gateway Service API.

{% hint style="info" %}
Invoice does **not** collect the actual funds. You invoice the customer outside of Emporix.
{% endhint %}

### Create the invoice payment mode

Create an `invoice` payment mode with `POST /payment-gateway/{TENANT}/paymentmodes/config`. For the full endpoint reference, see [Payment modes configuration](https://developer.emporix.io/api-references/api-guides/checkout/payment-gateway/api-reference/payment-mode).

#### Example request

```bash
curl --location --request POST 'https://api.emporix.io/payment-gateway/{{TENANT}}/paymentmodes/config' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {EMPORIX_AUTH_TOKEN}' \
--data-raw '{
  "code": "invoice",
  "active": true,
  "provider": "INVOICE",
  "configuration": {}
}'
```

#### Payload notes

* `code`: Your storefront uses this as the method identifier (for example `invoice`).
* `provider`: Must be `INVOICE`.
* `configuration`: Empty for invoice.

### What to do next

After configuration, the mode shows up in `GET /payment-gateway/{TENANT}/paymentmodes/frontend`. Use that list to render available payment options in your storefront.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/ce/extensibility-and-integrations/payments/invoice.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.