> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-wholesale-b2b/add-on-features/create-payment-term-for-your-b2b-customers.md).
# Payment Term and Payment Invoice
Let B2B customers pay for their order later or on a specific date, instead of paying immediately at checkout.
Payment Term lets your B2B customers pay later — either by a specific date or within a set number of days — instead of paying immediately at checkout.
Once enabled, a **Pay Later** button appears on your cart page. Clicking it creates a draft order and clears the cart.
{% hint style="info" %}
The draft order created this way already has the discounted price applied when you view it in Shopify **Draft Orders**.
{% endhint %}
## Steps to manage
{% stepper %}
{% step %}
### Open Payment term
Open the app, go to **Add-on Features**, then click **Payment term > Setup payment term**.
{% endstep %}
{% step %}
### Start a new payment term
Click **Add new payment term**.
{% endstep %}
{% step %}
### Configure the term
* **Status** and **Title** — enable the payment term and give it a name (only visible to you).
* **Payment term** — choose when the customer must pay: **Due on receipt**, **Due on fulfillment**, a fixed number of days (**Within 7/15/30/45/60/90 days**), a **Fixed date**, or **After checkout**.
* **Customer targeting** — choose **Logged in customers**, **Specific customers**, or **Customer tags**. Tick **Exclude customers** to hide it from certain customers.
* **Apply to Markets** — choose **All markets** or **Specific markets**.
* **Product targeting** — choose **All products**, **Specific products**, **Specific collections**, or **Product tags**, and optionally **Exclude products**.
* **Apply payment terms based on cart contents** — choose **Only if all items qualify** or **If any item qualifies**.
* **Order conditions** — choose **No restriction**, or set a minimum/maximum order amount or quantity that triggers this term.
* **Order tagging** — search for a tag to automatically apply to orders that use this payment term. Create the tag in Shopify first, and it'll appear in this list.
{% endstep %}
{% step %}
### Save
Click **Save**.
{% endstep %}
{% endstepper %}
You can also style the **Pay Later** button — see [Customize Payment term button](/samita-wholesale-b2b/add-on-features/create-payment-term-for-your-b2b-customers/customize-payment-term-button.md).
> ### **Need support?**
>
> If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://help.samita.io/support@samita.io)
---
# 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.samita.io/samita-wholesale-b2b/add-on-features/create-payment-term-for-your-b2b-customers.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.
.png?alt=media)
