#195 — UI support Rutter Commerce and PayEngine integrations

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

Created: 2025-01-09 · Updated: 2025-09-11

Description

Now we support only Rutter Accounting integrations:

For payments we need to support integrations of 2 new categories:

Rutter Commerce (Clover, Amazon, etc.) - the same UX as with Rutter Accounting, just more options and restructured categories.
PayEngine merchant. Which may be implemented for 2 cases:
- Full PayEngine embedded on-boarding form UI (see https://docs.payengine.co/developer-docs/merchant-onboarding/embedded-onboarding-ui and try it for yourself; it is ~50 questions form asking for detailed financial information, SSN/TIN, documents, etc.). For showing this PayEngine’s UI we need to ask Legal Name and Email first.
- TwillAI page asking for already on-boarded and approved MerchantID (will be implemented as pure back-end functionality, to be executed via TwillAI support). Here need only in MerchantID.

Note that process of on-boarding merchant for PayEngine looks like:

Merchant is provided with link to branded for TwillAI PayEngine Onboarding UI where merchant should fill quite long form.
Next PayEngine verifies merchant. It may take up to few days. Status of approval is received by back-end via MERCHANT_STATUS_CHANGED webhook event and passed to relevant Integration entity.
Once the merchant is approved (status=ready in Integration), we can use . This indicates the merchant is fully on-boarded and ready to process transactions.

Payengine Application Icon in

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets