Integrated payments can pass the amount to a supported terminal or payment service. The provider, account, approval, fees and supported actions are separate from the website design.
Sam’s Town Pizza, MoeFrabPOS & Order Eats archive ↗
Historical FrabPOS material—not a One product screenshot.
PAYMENTS & EFTPOS / PRACTICAL FUNCTIONS
What it does. Why you’ll use it.
Keep the sale and its payment in agreement. Choose a function, see the example, and check the detail with your business.
01 / AT PAYMENT
Sale totalTerminalResult
Send the sale amount to EFTPOS
Pass the agreed total to a compatible terminal connection.
WHY IT HELPSLess typing the amount a second time.
See an example +
Try this: Pay a sale containing the approved surcharge or adjustment.
Check in your setup: Provider, device and production-approved integration must be confirmed.
02 / AT PAYMENT
ApprovedDeclinedCancelled
Approved, declined or cancelled
Handle the actual transaction response instead of assuming success.
WHY IT HELPSA declined payment should not mark the sale paid.
See an example +
Try this: Run each outcome and check the sale’s paid state.
Check in your setup: Payment-state behaviour needs provider sandbox and production acceptance tests.
03 / RECOVERY
PendingStatus checkSafe next step
Delayed-payment recovery
Find out whether the original attempt completed before trying again.
WHY IT HELPSLess risk of charging twice during a connection problem.
See an example +
Try this: Simulate a delayed response and recover the original attempt.
Check in your setup: The provider’s query and retry rules must be respected.
04 / RECOVERY
PermissionProvider refundReceipt
Permission-controlled refunds
Refund using the right provider path and record the result.
WHY IT HELPSA traceable refund, not just a negative amount.
See an example +
Try this: Refund part of an original transaction where supported.
Check in your setup: Refund limits, settlement timing and provider fees vary.
05 / AT PAYMENT
PrintEmailReprint
Receipt choices
Provide the supported printed or digital receipt after a confirmed sale.
WHY IT HELPSThe customer receives the right record.
See an example +
Try this: Finish a purchase, then reprint its receipt from sales history.
Check in your setup: Printer/email configuration and refund-receipt formats need checking.
06 / RECOVERY
CashCardSettlement check
Payments in end-of-day reporting
Compare recorded payment methods with your closing records.
WHY IT HELPSMake differences easier to identify.
See an example +
Try this: Match known test transactions and refunds to the daily totals.
Check in your setup: Provider settlement and business reports can use different periods; reconcile them explicitly.
01 / 06
Swipe, or use the arrows
About these functions and your One setup
These cards describe the supplied One project and the published FrabPOS service range. They are not screenshots or certification of every function in a live One release. Your demonstration and quote confirm the exact menu rules, hardware, connections and service scope before you commit.
No. Your provider’s pricing and terms apply separately.
Can I use any terminal or provider?
Do not assume universal compatibility. The specific provider, device and production-approved connection must be confirmed.
About these examples & product scope
These are illustrative business situations, not attributed customer complaints. The explanations use the agreed One project scope and FrabPOS’s published service range. Older FrabPOS or Order Eats material does not certify every function in One. Your demonstration and quote confirm the released setup.