Payment button for clients with a not-enabled SO
Jira: BIF-8696 · Epic: BIF-8695
Overview
Clients whose Sales Order (SO) has not been enabled should be able to pay their
subscription directly from the subscription-period banner, instead of being routed to
"Contact Support". SO status comes from the so_url datamart provided by the BI team.
Scope Changes
- Backend — subscription-period banner scheduler reads the
so_urldatamart. - Frontend — banner shows "Payment" vs "Contact Support" button.
8. User Stories + Acceptance Criteria
| User Story | Importance | Mockup / Technical Notes | Acceptance Criteria |
|---|---|---|---|
| [PAYSO-S01] — Direct payment for not-enabled SO As a client whose SO has not been enabled, I want the subscription-period banner to show a "Payment" button instead of "Contact Support", so that I can pay for my subscription directly without waiting on support. | Should Have | SO status source: so_url datamart (BI team). | — Happy Path — • AC-1: Given today is 00:00, when the subscription-period banner scheduler runs, then it reads the so_url datamart to determine each CID's SO status.• AC-2: Given a CID has a not_enabled SO in the datamart, when the banner is shown to the client, then show the "Payment" button (instead of "Contact Support") so the client can pay directly. Payment URL data source: mekari_datamart.qontak_active_subscription_payment_link.— Fallback — • AC-3: Given a CID does not have a not_enabled SO, or is absent from the datamart, when the banner is shown, then show the "Contact Support" button (current behaviour). |
Open questions
- Exact
so_urldatamart field/value that denotesnot_enabled(confirm with BI). Destination URL/flow the "Payment" button links to.Resolved: payment URL comes frommekari_datamart.qontak_active_subscription_payment_link.- Confirm refresh cadence is daily at 00:00 and the acceptable staleness for the banner.