#331 — Facade extra payments (PayEngine) info API with Gateways, ACH on/off settings
Repo: Twill-AI/facade State: closed | Status: done Assignee: sparsh-twillpayments
Created: 2025-04-21 · Updated: 2025-07-04
Description
Request
Caused by:
- Michael’s 2025/04/17 Prod sync request - we need to provide information about PE Merchant gateway to our P0 user.
- https://www.figma.com/design/ZUrZatocX5Vs79IBNqzGke?node-id=12796-31613#1259309442 - we need to provide information about whether ACH is enabled for PE Merchant or not.
Notes:
- In P0 we would support only “one gateway per merchant” scenario. See https://www.figma.com/design/ZUrZatocX5Vs79IBNqzGke?node-id=12552-26243#1259300460.
- https://github.com/Twill-AI/business-data/issues/189 is in another (next) epic.
- If we would add gateway ID into existing GET
/integrationsthen it would mean extra queries for all (even not PayEngine) integrations and would trigger changes in UI. So instead better to add specific API for “payment actions capable” integrations which may be found by source_type/mediator_type fields.
Acceptance criteria
- Facade has new API GET
/integrations/{integration_id}/payments/infowhich returns body:
{
"gateways": [ // UI may check here that it is only one, otherwise show error "Merchant is unsupported because has multiple gateways.".
"id": str, // Gateway ID in PayEngine.
"nickname": str, // Nickname given to the gateway.
"capabilities": object // Capabilities enabled for the gateway (no idea what is inside).
],
"achEnabled": boolean // Whether ACH is enabled or not.
}
This API is implemented by making requests to PayEngine API-s described in https://docs.payengine.co/api-ref
Notes
Add implementation notes, blockers, and context here
Related
Add wikilinks to related people, meetings, or other tickets