Skip to main content

In Person Payments with Payment Terminals

Learn how Pepper enables distributors to accept in-person card payments at pickup and delivery, manage invoices and credits in a single workflow, and collect payment securely at the moment orders are fulfilled.

Written by Grace Pepetone
Updated this week

Pepper supports in-person card payments using payment terminals, allowing distributors to collect payment directly from PMC at the time of delivery or pickup. By combining customer selection, invoice management, and terminal checkout into a single workflow, teams can eliminate manual payment follow-ups and close out orders faster.

Note: Payment Terminals are available for anyone with Finance Hub enabled - contact your customer success rep to learn how to get started.

Key Benefits

  • Collect payments on the spot: Initiate and complete card payments directly from PMC using a connected payment terminal.

  • Reduce manual reconciliation: Payments are tied to customers and invoices, minimizing errors and back-and-forth after delivery.

  • Flexible invoice management: Review open invoices, add new charges, or apply credits before sending the total to the terminal.

  • Clear, customer-friendly checkout: Customers see the final amount (and any applicable card fees) directly on the terminal before confirming.

  • Centralized receipt access: Receipts are available both physically (if enabled) and digitally within PMC.

Accessing Payment Terminals

  1. Navigate to PMC

  2. Go to the Payments tab

  3. Select the Terminals flow

Step-by-Step Payment Workflow

Step 1: Select a customer

Search for and select the customer you want to charge.

Once selected, all existing open invoices for that customer automatically populate in the payment flow.

Step 2: Review or modify invoices

Before sending the payment to a terminal, you can:

  • Select from existing open invoices

  • Add a new invoice

  • Add a credit to adjust the total

The net total is automatically calculated based on:

  • Open invoices

  • Newly added invoices

  • Credits applied

Click the Add charge button to add credits and charges.

Step 3: Select a payment terminal

Choose a terminal from the Payment method list.

Each terminal represents a physical device connected to the system. Select the terminal where the customer will complete payment, then click Send to push the payment request to the device.

Select a terminal under 'Payment method', review the subtotal and add a memo in the 'Notes' box, then click 'Send to terminal'.

Step 4: Complete payment on the terminal

Once the payment is sent:

  • The terminal displays the total charge amount

  • The customer can tap, insert, or swipe their card

Credit card fees (if enabled):

  • Fees are calculated and displayed on the terminal, not in PMC

  • The customer sees the fee breakdown before confirming

  • The customer must confirm the fee and complete the transaction on the device

Step 5: Access receipts and finalize

After a successful payment:

  • A physical receipt is printed (if enabled)

  • The payment is recorded in PMC

  • A digital receipt is available in the History section by clicking on an invoice number. It can also be accessed in the Transaction History section of the Payments tab.

Key Behavior Notes

  • Open invoices automatically populate when a customer is selected

  • Manual invoices and credits can be added before sending the total to the terminal

  • Credit card fees (if enabled) are handled and confirmed on the terminal

  • Receipts are available both physically and digitally

  • The terminal manages all customer-facing fee confirmations

Permissions and Access

Access to in-person payments with payment terminals is controlled by user permissions in PMC.

  • Only users with Payments access can view the Payments tab and access the Terminals flow.

  • Users must have permission to initiate payments in order to send charges to a payment terminal.

  • Users without the required permissions will not see the Terminals option in PMC.

If you’re unsure whether a user should have access to this feature, review their role and permissions in the User Config tool.

Did this answer your question?