#411 — Facade’s merchant on-boarding API-s with proxying data to PayEngine

Repo: Twill-AI/facade State: closed | Status: done Assignee: sparsh-twillpayments

Created: 2025-07-21 · Updated: 2025-08-01

Description

Caused by https://github.com/Twill-AI/facade/issues/397, also see https://twill-network.slack.com/archives/C078KS0R05B/p1753074243447429.

In order to offload front-end (from dealing with PayEngine’s API with separate auth system) and simplify integration with other than PayEngine payment processors later we better to store all “merchant on-boarding” data on Twill back-end (in Facade) and update PayEngine only for it’s portal visibility about merchants.

Twill-partner-portal "Merchant On-boarding" flow

differs from PayEngine’s web-component in many parts:

and we need to map all these 3 things to PayEngine’s docs.

Note that POST /partner/merchants ‘Create Merchant’ API is not in scope, it is in scope of https://github.com/Twill-AI/facade/issues/397.

AC:

• PayEngine’s API and web component are compared with twill-partner-portal’s UI to find:
  • Required fields for PE’s API. It is needed to a) update twill-partner-portal design, b) enhance Facade’s “merchant” table with new fields, c) implement required validation logic for ‘Submit Merchant Application’ API.
  • 2 mappings:
    • “twill-

Notes

Add implementation notes, blockers, and context here

Related

Add wikilinks to related people, meetings, or other tickets