#381 — Design user flow to have multiple PayEngine merchants on the same tenant.

Repo: Twill-AI/twill-ai-ui State: closed | Status: done Assignee: Unassigned

Created: 2025-05-29 · Updated: 2025-09-11

Description

AC:

User flow for adding multiple integrations is described with details:
- Steps to create the first PayEngine/Payments integration. How to handle “not completed application” situation (allow start new? what to show on “Twill Payments” tile?)?
- Steps to create second PayEngine/Payments integration. How to generate a name of new integration? How to handle “not completed application” situation (allow start new? what to show on “Twill Payments” tile?)?
Have a control to rename integration on any Integration popup.
Decide which icon to show PayEngine/Payments integrations (https://www.figma.com/design/ZUrZatocX5Vs79IBNqzGke/Twill-UI?node-id=11445-26004&t=BHcTHz9f6dQTE2cZ-4). Think about PayEngine/Payments “Connect” button on Integrations page - for “Payments V0” we would connect existing PayEngine accounts via direct API call (therefore need to remove this button from UI), but for “Payments V1” we want it to exist and be marked by “gateway/processor” icon (nmi | sierra | viaconex | stripe | elavon | payrix | etc.). While we don’t know which merchant/gateway user would choose eventually.
Solve ambiguity with 3 “Create new” buttons doing the same on Integrations page (https://www.figma.com/design/ZUrZatocX5Vs79IBNqzGke/Twill-UI?node-id=11445-26004&t=BHcTHz9f6dQTE2cZ-4).

Designs:

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets