Incoming Payments should become tenanted as per the Multi-Tenancy design, and will be logically separated in the backend database by a tenantId row that serves as a foreign key on the tenants table.
[ ] Add tenantId row to incomingPayments table that is required and maps to an id on the tenants table.
[ ] Add tenantId to database queries on incoming payments
[ ] Acquire tenantId from request headers on routes involving incoming payments and pass them into incoming payment service logic.
[ ] Include tenantId in path of incoming payment URL. e.g. http://exampe-rafiki/:tenantId/incoming-payments/:id
Incoming Payments should become tenanted as per the Multi-Tenancy design, and will be logically separated in the
backenddatabase by atenantIdrow that serves as a foreign key on the tenants table.tenantIdrow toincomingPaymentstable that is required and maps to an id on thetenantstable.tenantIdto database queries on incoming paymentstenantIdfrom request headers on routes involving incoming payments and pass them into incoming payment service logic.tenantIdin path of incoming payment URL. e.g.http://exampe-rafiki/:tenantId/incoming-payments/:idPrerequisites