Skip to main content

Events

Events exposed by wasabi_banking for integration hooks.

danger

The resource folder must be named wasabi_banking.

Client events​

wasabi_banking:uiState​

Fired when the banking UI opens or closes. Useful for HUDs and other resources that should hide while banking is open.

AddEventHandler('wasabi_banking:uiState', function(state)
    if state then
        print('Banking UI is now open')
    else
        print('Banking UI is now closed')
    end
end)

state: true when open, false when closed.

wasabi_banking:openUI​

Opens the banking UI in a specific mode.

TriggerEvent('wasabi_banking:openUI', 'main') -- 'main' | 'atm' | 'admin'

Usually triggered from the server:

TriggerClientEvent('wasabi_banking:openUI', source, 'admin')

wasabi_banking:closeUI​

Closes the banking UI.

TriggerEvent('wasabi_banking:closeUI')
-- or
TriggerClientEvent('wasabi_banking:closeUI', source)

wasabi_banking:refresh​

Refreshes the open banking UI payload from the server.

TriggerClientEvent('wasabi_banking:refresh', source)

wasabi_banking:openAtmCard​

Opens the ATM UI pre-seeded with a single card (item-use / found-card flow). The payload is a card row prepared by the server.

AddEventHandler('wasabi_banking:openAtmCard', function(card)
    -- ATM UI opens with this card seeded for PIN entry
end)
warning

Prefer listening to wasabi_banking:uiState for HUD integrations. openUI, closeUI, refresh, and openAtmCard are intended for controlled integrations. Triggering them from unrelated resources can put the NUI focus and local state out of sync.