All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Click & Collect System
  2. Features
  3. Payment and pricing
Feature · Payment and pricing

Payment and pricing

Follow payment and pricing through the records and decisions your team uses each day.

OverviewOrders under fraud review
Click & Collect System · Payment and pricing

Orders under fraud review

Customer orders

New
Record numberPlaced atFraud statusFinancial statusStatus
CO-2699125 OctUnder reviewPendingOpen
CO-4254023 OctUnder reviewAuthorizedFulfilled
CO-9138108 OctUnder reviewPaidArchived
CO-8576307 OctUnder reviewPartially paidOpen
CO-6105021 OctUnder reviewRefundedFulfilled
6 of 6 records
CO-26991Customer orders · CO-26991
Under review
Placed at25 Oct
Financial statusPending
StatusOpen
Example screen with sample data

What you can do

Start with the operating record

The merchant owner sets the payment choices, tax rates, discount rules and shipping charges used for order pricing. A payment evidence record identifies an authorization, capture, sale or void, its amount and outcome. Use the order’s currency and totals to frame the payment check. Payment evidence records an authorization, capture, sale, or void with an amount and status; its provider reference supports reconciliation. Payment methods, tax rates, discount rules, and shipping methods carry the choices the Merchant Owner maintains.

How the work is organized

  • Checkout choices. Check active payment and shipping methods for the order’s catalog.
  • Price evidence. Compare the order discount with applied discounts and its discount rules record.
  • Payment result. Compare a payment evidence amount and status with the order’s paid amount and the provider result.

What to agree during setup

The owner agrees which payment methods are active for each catalog, when discounts apply, and which tax rate covers an order address. Review of risk and financial status stays with the owner before fulfillment proceeds. Merchant Owner chooses the active payment methods and discount periods for each catalog. Agree how staff select the applicable tax rate for an address and who resolves an order marked under review for fraud. Rehearse a failed payment as well as a successful one. Keep the provider result available for reconciliation before treating a local payment record as money received.

Check the handoff on an actual case

A paid order shows a discount and a tax charge. The owner checks the applied discount and its rule, then checks the applicable tax rate and payment evidence amount. If the fraud status is under review, the owner resolves that decision through the operating process before the warehouse acts on the order. Ask the next role to find the same case from its linked record and explain the current decision. Keep the order number or catalog code visible in the handoff so a change is applied to the intended transaction.

Repeat the check with a second case whose status or linked record differs. Have the responsible role explain the correction and confirm that the next person can see the result in the same records.

What your team sees

  • Orders under fraud review — Orders whose fraud status needs the Merchant Owner’s attention.
  • Promotion calendar — Discount rules with start and end dates for checking active offers.

Follow the work through

See the storefront order cycle and implementation for a pilot that connects this work to the rest of the order.

What it keeps track of

Data model
Payment methods
Each record is a way customers can pay, used to configure which payment options are offered.
Payment evidence
Each record is a captured payment attempt or charge, used to confirm and audit how an order was paid.
Tax rates
Each record is a tax rate for a region, used to charge the correct tax on orders.
Discount rules
Each record is a discount or promotion, used to define how and when customers get a price break.
Applied discounts
Each record is a discount actually applied to an order, used to track savings given to customers.
Config validation runs
Checkout configuration validation runs produced by the Pricing, tax, shipping, payment workflow. One row per validated configuration set; validation never mutates the merchant configuration.

Who uses it

Permissions
Merchant Owner
Maintains checkout settings and reviews fraud exceptions.
Customer Service Rep
Reads payment evidence to explain an order while leaving provider reconciliation to the responsible owner.

Set up Click & Collect System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started