Candescent Marketplace Technical Integration Questionnaire — Refer a Friend
1. Partner Overview
| Field | Details |
|---|---|
| Partner Technical Contact | hello@nuevesolutions.com |
| Maturity of the Product | Generally Available (GA) — production-deployed across multiple financial institutions on Q2 and other digital banking platforms with proven reliability and scale. |
| Requesting Customers | Old National Bank (demo completed), Bluepeak Credit Union (expressed interest), Bay Federal Credit Union (expressed interest). |
| Technical Documentation | https://nueve-dfd2a7f8-dev.mintlify.app/guides/products/refer-a-friend/candescent/introduction |
2. Business and User Journey
| Question | Answer |
|---|---|
| Who initiates the flow? | The end user (bank member) initiates the flow after authenticating into the Candescent digital banking portal. |
| When does the journey begin? | Post-login — members can access the referral program from the dashboard widget, landing page, or promotional banners. |
- Member logs into digital banking
- Views referral widget showing offer details and referral count
- Shares referral code via email, SMS, or social media
- Referred person signs up and submits referral code at first login
- Both parties track eligibility progress within digital banking
- System automatically dispenses rewards when criteria are met
| Question | Answer |
|---|---|
| Embedded experience required? | Yes — the feature is delivered as an embedded widget within the Candescent digital banking experience. |
| Onboarding / Provisioning Required | Yes — FI-level onboarding is required. This involves configuring campaign type, qualifying activity rules, reward amounts, messaging, and disclosures specific to the financial institution. |
- If referral code validation fails, the system displays an inline error with guidance (e.g., “Invalid code” or “Code already used”).
- If reward dispensation fails, the system retries automatically via a daily batch job and flags the issue for FI admin review.
- Expired campaigns or submission windows display appropriate messaging to the user.
- No reward is issued until all qualifying criteria are confirmed complete.
3. Integration Scope & Access
Candescent APIs Required:| API | Used For |
|---|---|
/db-accounts/v1/ | Fetch member’s account information for eligibility verification |
/ux-users/v1/ | Member profile — name, contact details, referral history |
/banking-activity/v2/ | Post-referral — alert notifications + OLB dashboard reload |
/disclosures/v1/ | Pull FI-specific terms and conditions before referral submission |
| Question | Answer |
|---|---|
| API only or UI/application access required? | Both — API integrations for referral tracking and reward processing, plus an embedded widget UI within the Candescent digital banking experience. AccountReload is an SDK signal fired from inside the widget to refresh the member’s dashboard. |
| Known core platform dependencies? | Yes — the integration connects to the FI’s core banking system to verify account openings, transaction counts, and deposit thresholds for eligibility tracking. |
4. Data Requirements (High Level)
| Question | Answer |
|---|---|
| What data is required from Candescent? | User identity (user ID), linked account information, and account activity for eligibility verification. |
| Read-only or write access? | Both — read for displaying referral status and eligibility progress; write for submitting referral codes and updating reward status. |
| Source of truth | Core banking system for account and transaction data; Nueve backend for referral campaign state. |
| How is data exchanged? | Real-time for user-initiated actions (code submission, sharing); batch/scheduled for daily eligibility checks and reward dispensation. |
5. Authentication and Authorization
| Question | Answer |
|---|---|
| Supported authentication standards | Standard Candescent session token model — the widget inherits the authenticated user session established at login. |
| Is SSO required? | No |
| Integration level | Widget — embedded within the authenticated Candescent session. |
| Claims / roles / entitlements required | Yes — standard end-user entitlements as configured in Candescent are required to access the referral widget. |
| Provisioning or JIT needed | Yes — FI-level campaign configuration required; no per-user provisioning. |
| User mapping approach | User identity is derived from the Candescent session context passed into the widget at runtime. |
| Session management details | Session lifecycle is managed entirely by Candescent. The widget respects existing session timeouts and re-authentication flows without requiring independent session handling. |
6. UI / Experience Requirements
| Question | Answer |
|---|---|
| UI pattern | Embedded widget (web) and feature (mobile) rendered within the Candescent digital banking shell, supporting desktop and mobile breakpoints. Multiple surface options: sidebar widget, full-width landing page, dashboard card, or smart ads. |
| Delivery model | Delivered within the Candescent experience layer — no external application redirect. On mobile, native share sheet integration for seamless referral sharing. |
| Theming / branding | Fully themed to the FI’s Candescent branding using design system tokens and components. |
| Additional requirements | Terms & Conditions acceptance required before referral code submission. Gamification elements (referral count, progress tracking) to drive engagement. Post-action OLB dashboard refresh via SDK signal. |
| Access logs | Yes — all user interactions within the referral widget (share, submit code, check eligibility) are logged including user ID, action performed, and timestamp for audit and compliance purposes. |
| Data residency constraints | Data is stored and managed within Candescent’s database infrastructure. |
| Marketplace constraints | No restrictions — the product is available as an open listing on the Candescent Partner Marketplace. |
© Candescent Marketplace | Confidential