Toss intake and payment integration

Task sequences

• Check in a customer and verify Toss payment
• Connect a Toss store and plugin
• Resolve mismatched Toss payment results

Compare shared actions across features in the sequence catalog.

Related guidance

When a customer arrives, staff need to identify the customer and collect payment for the correct item. Looking up the customer in Laney and handling payment separately creates another reconciliation task later.

The Laney plugin on a Toss terminal connects customer identification, payment requests, and approval results with Laney purchase records. Use it to check that the customer you checked in is the customer who paid. Also verify that the selected product and approved amount match.

This article explains the integration’s scope and the order of work. Start with store and organization setup if this is your first connection. Staff who already use the integration can start with the check-in and payment procedure.

How does it work at the counter?

Consider a customer who arrives for a booked consultation and pays for a consultation product. Staff first find the customer in the plugin and check the booking or customer information. If names overlap, use your organization’s identification rules, such as checking the phone number.

After confirming the customer, staff check the product and amount before requesting payment. They then compare the terminal approval with the purchase record in Laney. Matching amounts alone are not enough: both records must refer to the same customer and transaction.

This connection also lets another staff member review the customer, purchase details, and approval evidence later. Installing the integration does not establish that every record is linked correctly. Verify the connection with a test transaction before operational use.

Approval and purchase records answer different questions

The terminal result shows whether the payment was approved. The Laney purchase record shows the customer, selected item, and purchase terms. For a completed transaction, staff must be able to reconcile its identity and amount across both records.

Suppose the terminal shows approval but you cannot find the purchase in Laney. Check the existing approval before requesting another payment. An absent record does not establish payment failure. Repeating the charge can create a duplicate payment. Follow the mismatched payment results procedure.

Changing a purchase to a cancelled state is also different from refunding a card payment. Confirm the provider’s cancellation or refund result, then compare it with the purchase record.

Prepare before first use

First, connect the correct Toss store and Laney organization. For multiple branches, compare the current terminal’s store with the organization that will receive records. Do not proceed with check-in or payment if another branch is connected. The connection contact can use store and plugin setup to review the required checks.

Next, agree on customer identification and selling terms. Use customer and transaction identification rules instead of selecting a customer by name alone. The product, option, and amount must match the actual selling terms. Check purchase record requirements for the customer and selected items to retain.

Finally, give staff access to the records needed for their work. Access to a terminal does not grant access to every branch’s customers. Check organization permissions before assigning check-in and purchase-review tasks.

Which transactions are included?

This integration covers check-in and payment requests initiated in the Laney plugin. It does not automatically collect every transaction made through other POS screens in the same store.

When a Toss approval has no corresponding Laney record, first establish where the transaction began. For a plugin transaction, use the approval time, amount, and transaction identifier to find the record. A transaction from another path requires a different investigation.

This capability is included in the Toss terminal integration product. If you need physical installation, read Toss terminal installation. Verify physical installation separately from the store and organization connection.

Continue with your task