Across
- 1. Transfers of funds out to accounts
- 5. In‑app browser surface used to securely host in‑app account and payment experiences
- 6. 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. Get funds immediately
- 15. Lightweight dashboard
- 16. Appearance setting requested for the dashboard
- 17. Customization of colors and styles
- 18. Individual charges and their statuses
- 19. Reusable UI modules such as disputes, payouts and payments lists
- 21. Provide information and get activated
- 23. Platforms can enable with low or no code
- 24. Type of UI module rendered inside a platform’s own app or site
Down
- 2. Ability to measure errors, latency and reliability
- 3. Branding model where Company’s UI hides most Company identity
- 4. Frontend version the team must upgrade to
- 7. Library for integrating Company’s UI modules in native apps
- 8. Short‑lived objects used to securely access account UIs
- 10. Could be better
- 12. Configurable fields shown in payment lists
- 13. Extra key‑value information that can be attached to payments
- 20. Often a friction point for our users
- 22. Documentation surface explaining how to integrate UI modules