# Payments

The block that collects payment for an order. It loads available payment methods from the subsidiary settings, shows tender buttons, integrates with the Registers block for terminal-level orchestration, and supports refund and adjustment flows.

When Payments is on the page, **Submit Button** hides itself automatically — Payments drives the submission once payment is collected.

![Payments block showing tender buttons (Cash / Card / Gift Card), an amount field, and a confirm button at the bottom](/files/3AnakrwPAkJe6NnqfjDD)

## Available in

* Order Form modules **only**

## When to use

* Every POS workflow that takes payment at time-of-sale.
* Cashier registers, retail POS pages, walk-in service order pages.
* Anywhere the order should be tendered before submission rather than invoiced for later payment.

For order forms where the order is invoiced rather than paid in full at submit, skip Payments and use Submit Button alone.

## Settings

| Setting                   | Description                                                                                                                                          |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Payment Configuration** | Opens the configuration modal — payment method selection, processor mapping, and additional options. All Payments configuration lives in this modal. |

The configuration modal covers:

* **Payment methods** — which tenders to surface: Cash, Card, Gift Card, Credit Memo, Check, Payment Instruments (saved cards), Terms, and split. The methods available depend on your subsidiary settings.
* **Card Present processors** — Fortis, 8Q, and Datacap. For each, map to a NetSuite payment method record written on completion.
* **Card Not Present processors** — Accept Blue (saved cards and bank payments) and PayStand (bank payments).
* **Payment Instruments** — when on, cashiers can save and reuse a customer's stored cards and bank accounts across orders.
* **Terms** — lets cashiers place an order on payment terms, capturing the due date and early-pay discount.
* **Receipt and invoice templates** — assign a custom template, enable auto-print on completion, or allow download and email.
* **Email Settings** — shows a *Send Invoice by Email* checkbox on the order completion screen.
* **Stock validation** — optionally blocks payment if line item quantities exceed available stock.
* **Click-to-pay** — when on, selecting a tender jumps straight to the payment flow, skipping the amount entry step.
* **Print before payment** — optionally prints a receipt or invoice preview before the cashier collects payment.
* **Visible order types** — limit the block to specific order types; it hides for all others.
* **Allow zero-dollar orders** — lets a $0 order submit without requiring payment.
* **Allow partial payment** — lets an order complete before the full balance is collected.
* **Keyboard shortcut** — assign a hotkey (e.g. Ctrl+P) to open the payment modal.

## How it works

1. Loads payment methods from the subsidiary's Card Present + Card Not Present processor configuration.
2. Reads the order total from the Summary block.
3. Renders tender buttons for the available methods.
4. For card payments, communicates with the configured terminal or processor (often via the Registers block, which manages the active terminal).
5. For cash, shows a change calculator.
6. For gift card and credit memo, validates the available balance.
7. When the collected total meets the order amount, shows an order completion screen. Payment submits after the cashier confirms.
8. If **Email Settings** is enabled and the cashier opts in, emails a PDF invoice to the configured recipient.

PIN entry is supported when the processor requires it. Refunds and adjustments use the same payment flow.

{% hint style="info" %}
**Standalone payment mode** — when configured as standalone, the block takes a payment against a customer's account without an active order. It requires customer selection and records the payment immediately on confirmation. Use this for taking ad-hoc payments outside of an open cart.
{% endhint %}

{% hint style="warning" %}
Payment methods come from the subsidiary settings configured by your NetSuite Admin. If a method you expect isn't showing, check the subsidiary's Card Present / Card Not Present payment processor configuration first.
{% endhint %}

## Examples

**Standard POS register.** Customer/Vendor Selection at top, Order Lines, Summary, Payments at bottom. Cashier scans items, taps Cash or Card, takes payment, confirms on the order completion screen, transaction submits.

**Card-only terminal.** Subsidiary configured with only card processors. Payments shows the Card tender and integrates with the in-store payment terminal.

**Multi-tender split.** Customer pays partly cash, partly card. Payments handles the split flow, accumulates the collected total, and submits when the full balance is met.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Submit Button</strong></td><td>Hides automatically when Payments is present.</td><td><a href="/pages/PhZ3dkc4a1LxD8vQ0aja">/pages/PhZ3dkc4a1LxD8vQ0aja</a></td></tr><tr><td><strong>Registers</strong></td><td>Manages the active register and cash drawer that Payments works with.</td><td><a href="/pages/M0pXygmWQ0wWJr2z5pUD">/pages/M0pXygmWQ0wWJr2z5pUD</a></td></tr><tr><td><strong>Summary</strong></td><td>The block that calculates the total Payments collects against.</td><td><a href="/pages/kclyuiviMjm8L7MhEpoq">/pages/kclyuiviMjm8L7MhEpoq</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/payments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.