#578 — Update Merchant Onboarding flow to new back-end API

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

Created: 2025-08-05 · Updated: 2025-08-15

Description

Changes list:

“Update merchant”/“Save draft” API HTTP method is PUT now (was PATCH).
“Submit merchant” API HTTP method is POST now (was PUT).
“Submit merchant” API now returns merchant field of MerchantPersisted type with the result of saving and (probably) submission of merchant entity. Need to apply it to the UI app state because it may change ID-s for bank accounts.
MerchantPersisted.approved_stock_change is removed.
BankAccountPersisted.merchant_id is removed.
BankAccountPersisted.mutabel field is added - UI need to disable ability to remove or edit bank accounts with mutable=false.
DocumentPersisted.merchant_id is removed.
MerchantUpdate.cc_amex_processing is removed.
(probably no change needed) MerchantCreate.name is optional
(probably no change needed) OfficerUpdate all fields are optional
(probably no change needed) BankAccountUpdate all fields are optional
MerchantUpdate following fields are removed: cc_amex_monthly_card_sales, cc_accepted_before, active_bank_account_name, active_bank_account_last_5, year_to_date_settled_amount.

AC:

UI uses updated API-s and back-end entities, there are no 422 errors from back-end and other integration problems.
@AlexanderMakarov is notified when updates are done to deploy new UI app version to Azure FrontDoor.
Functionality of submitting merchant is tested (Raymond and Aleksandr)

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets