Add the Event Listener to your Integration
To add the Event Listener to your GEFT widget integration, place the following script on the same page as your GEFT widget:html
Reviewing your Event Listener data
You’ll receive the following types of event data from the GEFT widget:- A JavaScript event, which indicates a user event during the payment flow
- Widget state changes, which indicate progress through the guarantee process
| EVENT NAME | DESCRIPTION | TERMINATING EVENT |
|---|---|---|
APP_MOUNTED | GEFT widget has successfully loaded and is ready for user interaction. | No |
CONSENT_DISABLED | Emitted when using a custom consent screen instead of the Flinks-provided one (optional configuration). | No |
INSTITUTION_SELECTED | The user has selected their financial institution. | No |
SUBMIT_CREDENTIAL | The user has submitted their bank login credentials. | No |
SUBMIT_MFA | The user has submitted multi-factor authentication answers. | No |
ACCOUNT_SELECTED | The user has selected which bank account to use for the payment. | No |
COMPONENT_DEPOSIT_CONTINUE | The user has clicked to continue after entering or confirming the payment amount. | No |
GUARANTEE_OFFERED | Flinks can guarantee the payment and has presented the guarantee offer to the user. | No |
COMPONENT_PAD_DOWNLOADED | The Pre-Authorized Debit (PAD) agreement has been downloaded or signed by the user. | No |
SUCCESS | The user has successfully completed the GEFT payment flow. The iframe should be closed. | Yes |
GUARANTEE_FAILED | Flinks cannot guarantee the transaction. The user should be offered alternative payment methods. | Yes |
COMPONENT_PAD_WARNING_SCREEN_EXIT | The user has opted not to accept the PAD agreement and has chosen to exit the flow. | Yes |
COMPONENT_OTHER_FUNDING_OPTIONS_SELECTED | Flinks cannot guarantee the transaction and the user has selected other funding options. | Yes |
COMPONENT_NBO_RETURN_TO_CLIENT_SELECTED | The user has chosen to return to your application for alternative payment methods. | Yes |
CLOSE | The user has clicked the close button (X) to exit the widget. | Yes |
Event Examples
Flow Events
APP_MOUNTEDGuarantee Events
GUARANTEE_OFFEREDTerminal Events
SUCCESS (Terminating)Implementation Examples
Basic Event Handling
Advanced Event Tracking
Error Handling and Timeouts
Event Flow Examples
Successful Payment Flow
APP_MOUNTED- Widget loads successfullyINSTITUTION_SELECTED- User selects their bankSUBMIT_CREDENTIAL- User enters bank credentialsSUBMIT_MFA- User completes multi-factor authentication (if required)ACCOUNT_SELECTED- User selects the account for paymentCOMPONENT_DEPOSIT_CONTINUE- User confirms payment amountGUARANTEE_OFFERED- Flinks approves the guaranteeCOMPONENT_PAD_DOWNLOADED- User signs PAD agreementSUCCESS- Payment completed successfully
Guarantee Declined Flow
APP_MOUNTED- Widget loads successfullyINSTITUTION_SELECTED- User selects their bankSUBMIT_CREDENTIAL- User enters bank credentialsACCOUNT_SELECTED- User selects accountCOMPONENT_DEPOSIT_CONTINUE- User confirms amountGUARANTEE_FAILED- Flinks cannot guarantee the paymentCOMPONENT_OTHER_FUNDING_OPTIONS_SELECTED- User chooses alternative methods
User Exit Flow
APP_MOUNTED- Widget loads successfullyINSTITUTION_SELECTED- User selects their bankCLOSE- User clicks X to close widget
Testing Event Handling
During development, test event handling with all scenarios in the sandbox environment. Use the test cases provided in the Sandbox Guide to verify proper event handling for both successful and failed flows. Test the following scenarios:- Happy path: Complete successful payment flow
- Guarantee failure: Handle declined guarantees gracefully
- User abandonment: Handle when users close the widget
- Network issues: Handle timeouts and connectivity problems
- PAD decline: Handle when users don’t accept the agreement
Related Documentation
- GEFT Widget: Widget configuration and setup
- Setup Guide: Complete implementation walkthrough
- Sandbox Guide: Testing procedures and test data