Toss intake and payment integration

Look up customers and reservations in the Toss Front plugin and record payments initiated by the plugin as purchases.

Acceptance

Test customer lookup, payment approval, cancellation of the payment flow, timeouts, purchase persistence and restart recovery on the target device.

Boundary

Limited to payments initiated by this plugin. It does not collect all POS transactions, automate refunds or partial cancellations, or retract ad conversions. Confirm rollout after device testing.

Check in a customer and verify Toss payment

[blocked]

Prepare an available test terminal and a transaction approved for testing.

Starting conditions and inputs

Confirm merchant connection and the test-payment operator. This procedure can create a real charge.

Connect a Toss store and plugin

Values for this task

entry_url, terminal_id, customer_id, amount, purchase_id, transaction_url

Command sequence

text

open "$entry_url" && snapshot -i
# Outside browser: The on-site operator confirms the customer and performs one agreed test reception and payment. Obtain reception and transaction IDs.
snapshot -i
click "$purchase_row" && snapshot -i
get text body
open "$transaction_url" && snapshot -i
get text body

open "$entry_url" && snapshot -i
# Outside browser: The on-site operator confirms the customer and performs one agreed test reception and payment. Obtain reception and transaction IDs.
snapshot -i
click "$purchase_row" && snapshot -i
get text body
open "$transaction_url" && snapshot -i
get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	Outside browser	The on-site operator confirms the customer and performs one agreed test reception and payment. Obtain reception and transaction IDs.
2	`click` `$purchase_row`	Purchase linked to the test transaction
3	`get text`	Read customer, purchase amount and payment state.
4	`open`	Confirmation for the original terminal transaction
5	`get text`	Compare purchase and transaction amounts and identifiers.

Check the result

Customer, transaction ID, amount and approval outcome match.

Resuming after interruption

Check the original request ID and outcome first. Do not resubmit while its result remains unknown.

[blocked]

Prepare a test transaction

Prepare an available test terminal and a transaction approved for testing. Agree on product, quantity, amount, and cancellation handling. If recording only the UI, state that no payment approval is performed.

[blocked]

Confirm the customer

Find the customer in the plugin and check an identifier beyond the name. Confirm the reservation or check-in details. Resolve duplicate names against the source customer before continuing.

[blocked]

Request and approve payment

Check the product and amount, then request payment on the terminal. Do not repeat the request while approval is pending. On failure, record the transaction identifier and time before checking approval.

[blocked]

Match the purchase record

Compare the Laney customer, product, amount, and status with terminal approval. Use the recovery guide when they differ. If the test is cancelled, verify both the actual cancellation and the purchase record.

Connect a Toss store and plugin

[blocked]

Compare the Toss store identifier with the Laney organization.

Starting conditions and inputs

Identify the terminal merchant and destination Laney organization.

Values for this task

entry_url, organization_id, merchant_id, terminal_id, reception_url

Command sequence

text

open "$entry_url" && snapshot -i
# Outside browser: The installation operator links the merchant and physical terminal. Obtain merchant and terminal identifiers.
snapshot -i
click "$toss_account" && snapshot -i
get text body
# Outside browser: Create a test reception on the terminal and record its time and identifier.
open "$reception_url" && snapshot -i
get text body

open "$entry_url" && snapshot -i
# Outside browser: The installation operator links the merchant and physical terminal. Obtain merchant and terminal identifiers.
snapshot -i
click "$toss_account" && snapshot -i
get text body
# Outside browser: Create a test reception on the terminal and record its time and identifier.
open "$reception_url" && snapshot -i
get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	Outside browser	The installation operator links the merchant and physical terminal. Obtain merchant and terminal identifiers.
2	`click` `$toss_account`	Toss connection account record
3	`get text`	Compare organization, merchant and terminal IDs with the installation result.
4	Outside browser	Create a test reception on the terminal and record its time and identifier.
5	`open`	Matching reception record
6	`get text`	Compare the customer and terminal for the same reception.

Check the result

Reception targets the intended organization. Payment testing remains a separate task.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

[blocked]

Match store and organization

Compare the Toss store identifier with the Laney organization. Map each branch separately. Terminal installation and plugin account connection are separate completion checks.

[blocked]

Complete plugin setup

Open the installed Laney plugin and follow the supplied connection procedure. Check the displayed store and organization before saving. Correct a wrong branch before accepting customers or payments.

[blocked]

Check staff access

Check the staff member’s organization access. Grant the required customer and purchase access. Access to the physical terminal does not grant access to other branches’ customer records.

[blocked]

Verify the connection

Find a test customer and verify the plugin’s check-in and payment entry points. This integration covers transactions initiated by the plugin. It does not establish automatic synchronization of every POS transaction.

Resolve mismatched Toss payment results

[blocked]

Collect the store, customer, time, amount, terminal transaction identifier, and Laney purchase ID.

Starting conditions and inputs

Keep the original transaction identifiers; do not start another charge.

Values for this task

entry_url, merchant_id, transaction_id, purchase_id, amount, transaction_url

Command sequence

text

open "$entry_url" && snapshot -i
get text body
open "$transaction_url" && snapshot -i
get text body
# Outside browser: After confirming the original outcome, the recovery operator handles that reception. Do not request another payment while the result is unknown.
snapshot -i
reload && snapshot -i
get text body

open "$entry_url" && snapshot -i
get text body
open "$transaction_url" && snapshot -i
get text body
# Outside browser: After confirming the original outcome, the recovery operator handles that reception. Do not request another payment while the result is unknown.
snapshot -i
reload && snapshot -i
get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	`get text`	Read the original reception ID, transaction ID and outcome.
2	`open`	Toss confirmation for the same transaction
3	`get text`	Compare approved, cancelled or unresolved state and amount.
4	Outside browser	After confirming the original outcome, the recovery operator handles that reception. Do not request another payment while the result is unknown.
5	`reload`	Reload the same reception record.
6	`get text`	Compare the original reception and transaction with the recovered purchase.

Check the result

The same transaction is recorded without another charge, or explicitly handed over as unresolved.

Resuming after interruption

Check the original request ID and outcome first. Do not resubmit while its result remains unknown.

[blocked]

Identify the transaction

Collect the store, customer, time, amount, terminal transaction identifier, and Laney purchase ID. Distinguish nearby transactions. Confirm that the transaction originated in the plugin.

[blocked]

Compare approval and storage

Check the original approval result at the terminal or provider. Compare it with the Laney purchase amount and status. A stalled screen does not prove payment failure. Distinguish approved, rejected, and unknown results.

[blocked]

Recover without duplicating payment

If approval exists but storage is missing, do not charge the same amount again. Give the transaction identifiers to your connection contact for reconciliation. Retry only after checking the original state and duplicate prevention.

[blocked]

Check cancellation limits

Changing a purchase to voided does not execute a card refund. Confirm refunds and partial cancellations at the provider, then reconcile records. Do not assume every terminal cancellation is synchronized automatically.

Related tasks

Request technical support and verify resolution