Across
- 1. Transfers of funds out to connected accounts
- 5. In‑app browser surface used to securely host embedded flows
- 6. Suite of balance and payout summaries for reconciliation
- 9. Chargeback‑related events handled via dedicated dashboard surfaces
- 11. Process of matching payouts and balances with platform records
- 14. Feature that lets connected accounts get funds immediately
- 15. Stripe’s lightweight dashboard flavor for connected accounts
- 16. Appearance setting requested for Express and documentation sites
- 17. Customization of colors and styles for embedded experiences
- 18. UI surface showing individual charges and their statuses
- 19. Reusable UI modules like disputes, payouts and payments lists
- 21. Flow where new connected accounts provide information and get activated
- 23. Express‑style UI surface that platforms can enable with low or no code
- 24. Type of component rendered inside a platform’s own app or site
Down
- 2. Ability to measure errors, latency and reliability of components
- 3. Branding model where Stripe’s UI hides most Stripe identity
- 4. Frontend framework version CAX must upgrade to
- 7. Library for integrating embedded components in native apps
- 8. Short‑lived objects used to securely open connected account UIs
- 10. Time it takes for dashboards and components to load
- 12. Configurable fields shown in lists like embedded payments
- 13. Extra key‑value information that can be attached to payments
- 20. Short for “authentication,” often a friction point in onboarding
- 22. Documentation surface explaining how to integrate components