Offline Transactions

Offline Scenarios

There are several offline scenarios including:

1. The Simphony workstation is offline from CAPS and the payment terminal itself is online.

2. The Simphony workstation is online and the payment terminal is offline from the payment host.

In scenario 1, the data looks like the simple payment transaction example above, however the Payment Transaction Detail result set is only available once Simphony is back online. If Simphony is offline for more than three days, downstream systems may get Payment Settlement Details or even Payment Payout Details without previously getting Payment Transaction Details. 

In scenario 2, once the terminal gets back online two possible options exist:

• Option 1: The payment completes successfully. Within the data structures this looks like the simple payment example (with the exception of "offline type" being 1), settlement and payout occur as usual with T0 being the time when the terminal comes back online. 

• Option 2: Once the terminal comes online, it forwards the stored payments to the payment processor and the card issuer subsequently refuses the payment. This creates:

  • One row in Payment Transaction Details with the original payment amount, which becomes available after the transaction happened in the POS (independent from how long the terminal is offline).

  • Another row in Payment Transaction Details once the terminal is back online with 0 transaction amount and a negative cancelled amount of the original payment amount.

  • A row in Payment Settlement Details with a Journal Type of "REFUSED" and a settlement amount of 0.

Use Case Description

• A guest check is paid in full by credit card using an offline terminal, on day 0 (Monday 08/05/2024) at 8:00 a.m. EST.

  • Check Total: 45.00

  • Tip Total: 5.00

  • Payment Total: 50.00

• The check is paid and closed in Simphony.

• The terminal gets back online on day 2 (Wednesday 08/07/2024 at 2:00 p.m.).

  • Once the terminal comes online, it forwards the stored payments to the payment processor and the card issuer subsequently refuses the payment.

Export or BI API Results

• Results when collected on Tuesday 08/06/2024.

  Table 10-5 Payment Transaction Details

  Payment ID

  Payment Detail ID

  Business Date

  Adjustment Business Date

  Transaction Date and Time

  PSP Reference

  Check Number

  Guest Check Line Item ID

  Payment Type

  Transaction Amount

  Tip Amount

  Offline Type

  Cancel Amount

  123450

  123456780

  08/05/2024

  <null>

  08/05/2024 8:00AM

  AB88000000CD000001

  1234

  1234567890

  PAY

  50.00

  5.00

  1

  0.00

• Export results when collected on Thursday 08/08/2024.

  Table 10-6 Payment Transaction Details

  Payment ID

  Payment Detail ID

  Business Date

  Adjustment Business Date

  Transaction Date and Time

  PSP Reference

  Check Number

  Guest Check Line Item ID

  Payment Type

  Transaction Amount

  Tip Amount

  Offline Type

  Cancel Amount

  123450

  123456780

  08/05/2024

  <null>

  08/05/2024 8:00AM

  AB88000000CD000001

  1234

  1234567890

  PAY

  50.00

  5.00

  1

  -50.00

  Table 10-7 Payment Settlement Details

  Payment ID	Payment Detail ID	PSP Reference	Business Date	Settlement Date	Journal Type	Card Present Fee	Card Present Rate	Settlement Amount
  123450	123456780	AB88000000CD000001	08/05/2024	08/08/2024	REFUSED	0.00	0.00	0.00

  No Payment Payout Details are produced for this transaction.

Payment Tracking Report

• Payment Tracking Report run on Monday 08/05/2024 at 8:05 a.m. for business date 08/05/2024.

  • Tender Amount: 50.00

  • Everything else is empty or 0 (also pending amount)

• Payment Tracking Report run on Thursday 08/08/2024 at 2:00 p.m. for business date 08/05/2024.

  • Tender Amount: 0.00

  • Settled Amount: 0.00

  • Variance Settled to Tender: 0.00

  • Fee Amount: 0.00 

  • Expected Payout: 0.00

  • Payout Amount: empty

  • Variance Payout to Expected: empty

• Payout Amount and Variance Payout to Expected stay empty because there is no payout for the refused transaction.