Twill Brain

#299 Facade supports PayEngine merchants on-boarding

2 min read

#299 — Facade supports PayEngine merchants on-boarding

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

Created: 2025-03-06 · Updated: 2025-09-15

Description

Request

To support PayEngine merchants need to:

  • extend Integration entity,
  • extend POST /integrations API-s,
  • extend “bdstate” handling logic (new parameters?)

See https://twillpayments.atlassian.net/wiki/spaces/TD/pages/249331714/Payments+PayEngine+data+location+evaluation for explanation.

Acceptance criteria

  • Facade Integration entity contains PayEngine merchant-related information.
  • Facade POST /integrations API-s supports Payengine/Payengine integration type for 2 cases:
    • User doesn’t have PayEngine’s merchant and UI need to provide PayEngine’s UI. For this need to provide merchantID. It may be obtained by calling https://docs.payengine.co/api-reference/onboarding/create-a-merchant with legal name and email. Also need proxy request to create integration to BD with just received merchantID.
    • User has merchantID and need to create in Facade and proxy request to create Integration to BD.
  • Facade “bdstate” handling logic may understand that BD passed information about changes in Integration PayEngine merchant-related information.
  • Logic above is covered with unit tests.

Implementation details

Looks like we don’t need to store extra information for PayEngine in Facade’s Integration. Current fields may be reused:

  • name to get legal name of the merchant to create Merchant on PayEngine side.
  • access_token can carry merchantId for existing PayEngine’s Merchant. API now doesn’t hide it.
  • state can have new more st

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View