All Collections
POS Configuration
Toast Configuration (LB 2.0)
2e - Create Lunchbox Native, Catering & Aggregation Payment Options (Toast)
2e - Create Lunchbox Native, Catering & Aggregation Payment Options (Toast)
Updated over a week ago

Disclaimer: This article is for Lunchbox 2.0 customers only. If your dashboard header looks the same as below, you are in the right place:


Let’s set up Lunchbox payment options in Toast. Payment Options will need to be built in Toast for each Payment Type that you wish to differentiate for online ordering for reporting purposes.

  • Native & Catering Payment:

    • ‘Lunchmoney’

  • Aggregation:

    • ‘Doordash’

    • ‘Ubereats’

    • ‘Grubhub’

    • “EZCater'

Note: You must set up these payment options at each of your location if you are not using Toast Master Location Management (MLM) each of these will have different GUIDs and it is very important that all of these IDs are communicated to your onboarding manager.


Configuring Your Payment Options

Step 1: From the Toast Admin Dashboard homepage click on Payments > Other Payment Options to create ‘Lunchbox’ payment option.

Step 2: Click Add

Step 3: Enter ‘Lunchbox Payment’ in the Name field.

Note: For MLM Locations make sure that the target and owner are configured to the parent restaurant group.

Note: Some restaurant partners may choose to set the require manager setting on this payment option. This is up to the preference of the restaurant partner. Typically this will be left unchecked in the event that a server needs to make an adjustment to a check in the POS. Please note any order refund or voids need to be applied both on the Lunchbox Admin Dashboard and in Toast.

Step 4: Other mandatory settings include…

Treat as Discount: set to NO

Tax Exempt: set to NO

Tips Enabled: set to Yes, show the tip dialogue and tip receipt line

Step 5: Click Save and then the Publish Now link.

Locating Payment Options GUIDs

Your GUID can be located by clicking the blue name link of your new payment option and is visible under the Name.

Did this answer your question?