Customer Solutions Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting: It includes "We are Vitesse – the treasury and payment partner of choice for insurance. Your next adventure awaits! Join the team who are redefining the payments space. About Us ..." Then "The Role Reporting to Head of Operations..." Then "What You'll Be Doing" list of duties. Then "Your Mission". Then "Success in Your First Year". Then "What You'll Need to Succeed". Then "Why You'll Love Working Here". Then "Our Values – or what we call “Vitesse at Our Best”" with three attributes. Then "We are an Equal Opportunity Employer" (EEO boilerplate) which we need to remove. Also "If you require any interview adjustments please contact Clara Moretti-Parker on clara.moretti-parker@vitesse.io." That's application instructions? Possibly contact for adjustments; might be considered application instructions? The instruction says remove application instructions. So we should remove that line.
We need to decide sections: About Us (maybe "About Us" heading). The Role description maybe "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: "About Us" could be "About the role"? Actually "About Us" is company description; maybe we can treat as "About the role"? But they said "About the role" as example. However we can still use "About Us" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests these examples. Safer to stick to those examples. So we need to map content to those headings.
We have:
- About Us (company overview) -> could be "About the role"? Not exactly. Could be "About the role" includes description of role and maybe company? But we have separate "The Role". Maybe we can treat "About Us" as "About the role"? Might be okay. Or we could omit About Us section and incorporate into role description? But we need to preserve all substantive information. So we need to include company overview somewhere. Could put under a heading "About the role" but that might be misleading. However instruction says we can use those examples, not limited to them. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings or others? It says e.g., meaning for example. So we can use other headings as long as they are . Probably fine to use "About Us". But to be safe, we could use "About the role" for company overview and role description combined? But we also have "What You'll Be Doing" which is responsibilities. So we could have sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (what you need to succeed), Qualifications (maybe not separate), Skills (maybe part of requirements), Benefits (Why you'll love working here), Pay (not present), Schedule (flexible schedule 35 hours a week). Actually schedule is mentioned: "flexible working schedule - at Vitesse you’re expected to work 35 hours a week." That's schedule info. So we can create a Schedule section.
Pay: not mentioned, so we should not create Pay section.
Benefits: "Why You'll Love Working Here" includes real impact, continuous learning, collaborative culture, opportunities to grow alongside a scaling global fintech. Also flexible schedule. That's benefits. So we can create Benefits section.
Qualifications: maybe not separate; we have "What You'll Need to Succeed" which includes experience, skills, etc. That could be Requirements or Qualifications. We'll treat as Requirements.
Skills: maybe we can extract skills from that list: strong analytical, problem-solving, attention to detail, organisation, prioritisation, communication, payments/FinTech experience advantageous, CRM/support platforms beneficial. Could be Skills section.
But we should avoid many thin sections. Prefer few substantive sections. So we could combine Requirements and Skills into one section "Requirements" that includes both experience and skills. Or we could have "Requirements" and "Skills". But instruction says prefer few substantive sections over many thin ones. So maybe we have three sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (experience + skills), Benefits (why you'll love working here), Schedule (flexible hours). That's five sections. Could we combine Benefits and Schedule? Schedule is a benefit but it's specific; maybe keep separate.
We must not include EEO boilerplate. Remove duplicated lines. Ensure we preserve all substantive information.
Let's extract content:
Company overview (About Us):
- We are Vitesse – the treasury and payment partner of choice for insurance.
- Your next adventure awaits! Join the team who are redefining the payments space.
- At Vitesse, we're more than just a payments platform – we're the trusted financial infrastructure connecting the global insurance ecosystem.
- Tailor-made for insurers, brokers, MGAs, and TPAs, our unified platform optimises claims funds, enables real-time global payments, and delivers full financial control.
- Our impact is real: over $20 billion in payments across 200+ countries, hundreds of millions returned to insurers’ balance sheets, and counting.
- We’re licensed in the UK (FCA), Europe (DNB), and New York (NYDFS), with over 260 amazing colleagues worldwide.
- With $93 million recently raised in Series C funding from KKR, our journey is just beginning, and our ambitions are sky-high.
- Headquartered in the heart of London and expanding across Europe and the US, Vitesse is where your ideas power tomorrow’s insurance solutions.
- Are you ready to make a difference? You're in the right place.
Role description (The Role):
- Reporting to Head of Operations, you'll join our growing US Operations team as a Solutions Analyst, supporting customers through platform configuration, onboarding, optimisation and operational support while maintaining strong operational controls and customer experience.
What You'll Be Doing (Responsibilities):
List items:
- Become a Vitesse product expert, supporting clients with platform setup, configuration, optimisation, and ongoing use.
- Provide technical guidance and configuration support to clients and internal stakeholders.
- Resolve customer enquiries and perform solution configuration updates.
- Configure new client accounts and manage users, permissions, MFA, notifications, account updates and closures.
- Support user access reviews and account configuration updates.
- Support UK↔US migrations, SSO, mergers, pricing updates and legacy account restructuring.
- Support onboarding, testing, UAT and platform releases.
- Partner with Customer Support, Product, Engineering, Implementation, Pre-Sales and Customer Success.
- Maintain documentation and meet SLA expectations.
- Follow operational risk controls, verification processes and escalate high-risk requests.
Your Mission:
- Deliver an exceptional customer experience by becoming a trusted expert in the Vitesse platform while maintaining operational excellence, security and client service.
Success in Your First Year:
- Become a trusted product expert.
- Independently manage customer configuration requests.
- Support onboarding, migrations and platform enhancements.
- Meet SLA and quality targets.
- Drive continuous improvement opportunities.
What You'll Need to Succeed:
- Experience in customer-facing, operations, implementation or technical support.
- Strong analytical and problem-solving skills.
- Excellent attention to detail and organisation.
- Ability to prioritise in a fast-paced environment.
- Strong communication skills.
- Payments, FinTech or Financial Services experience is advantageous.
- Experience with CRM/support platforms such as Salesforce or Zendesk is beneficial.
Why You'll Love Working Here:
- Real impact, continuous learning, collaborative culture, and opportunities to grow alongside a scaling global fintech.
- We understand that everyone has their own work rhythm and believe in a flexible working schedule - at Vitesse you’re expected to work 35 hours a week.
Our Values – or what we call “Vitesse at Our Best”:
- Confident Humility: We believe the best ideas come from listening and learning. We leave ego at the door, ask for help when we need it, and celebrate collective success. When one of us wins, we all do.
- Driven to Succeed: We’re ambitious about the opportunity ahead and committed to achieving it together. We hold ourselves to high standards, take pride in what we deliver, and push for meaningful outcomes for our customers, our partners, and each other.
- Tenacious Responsibility: We take ownership of our work, our decisions, and our results. We face challenges with resilience, learn from setbacks, and see things through to completion. Because doing the right thing matters.
We need to include values maybe as part of Benefits or separate? Could be part of Benefits or Culture. But we already have Benefits section; we could include values there. However values are substantive; we could include them under Benefits or maybe a separate "Culture" section but not in list of headings. Since we prefer few sections, we could incorporate values into Benefits section.
Schedule: flexible working schedule - 35 hours a week. Already mentioned in Why You'll Love Working Here. Could be part of Benefits.
Thus we can have sections:
- About the role (company overview + role summary)
- Responsibilities (duties list)
- Requirements (experience + skills)
- Benefits (why you'll love working here, values, schedule)
We must not include Pay section.
We must not include duplicate lines.
We need to format using for each section heading, then content: either
for prose,
- for lists.
We need to ensure we preserve all substantive information. Let's craft.
Section About the role: combine company overview and role summary (The Role). Could be two paragraphs: first company overview, then role summary.
We must not repeat job title as heading; we are not.
We must not include Job ID etc.
Now produce HTML.
Let's write:
About the role
We are Vitesse – the treasury and payment partner of choice for insurance. Your next adventure awaits! Join the team who are redefining the payments space. At Vitesse, we're more than just a payments platform – we're the trusted financial infrastructure connecting the global insurance ecosystem. Tailor-made for insurers, brokers, MGAs, and TPAs, our unified platform optimises claims funds, enables real-time global payments, and delivers full financial control. Our impact is real: over $20 billion in payments across 200+ countries, hundreds of millions returned to insurers’ balance sheets, and counting. We’re licensed in the UK (FCA), Europe (DNB), and New York (NYDFS), with over 260 amazing colleagues worldwide. With $93 million recently raised in Series C funding
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: It includes "We are Vitesse – the treasury and payment partner of choice for insurance. Your next adventure awaits! Join the team who are redefining the payments space. About Us ..." Then "The Role Reporting to Head of Operations..." Then "What You'll Be Doing" list of duties. Then "Your Mission". Then "Success in Your First Year". Then "What You'll Need to Succeed". Then "Why You'll Love Working Here". Then "Our Values – or what we call “Vitesse at Our Best”" with three attributes. Then "We are an Equal Opportunity Employer" (EEO boilerplate) which we need to remove. Also "If you require any interview adjustments please contact Clara Moretti-Parker on clara.moretti-parker@vitesse.io." That's application instructions? Possibly contact for adjustments; might be considered application instructions? The instruction says remove application instructions. So we should remove that line. We need to decide sections: About Us (maybe "About Us" heading). The Role description maybe "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: "About Us" could be "About the role"? Actually "About Us" is company description; maybe we can treat as "About the role"? But they said "About the role" as example. However we can still use "About Us" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests these examples. Safer to stick to those examples. So we need to map content to those headings.
We have:
- About Us (company overview) -> could be "About the role"? Not exactly. Could be "About the role" includes description of role and maybe company? But we have separate "The Role". Maybe we can treat "About Us" as "About the role"? Might be okay. Or we could omit About Us section and incorporate into role description? But we need to preserve all substantive information. So we need to include company overview somewhere. Could put under a heading "About the role" but that might be misleading. However instruction says we can use those examples, not limited to them. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings or others? It says e.g., meaning for example. So we can use other headings as long as they are . Probably fine to use "About Us". But to be safe, we could use "About the role" for company overview and role description combined? But we also have "What You'll Be Doing" which is responsibilities. So we could have sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (what you need to succeed), Qualifications (maybe not separate), Skills (maybe part of requirements), Benefits (Why you'll love working here), Pay (not present), Schedule (flexible schedule 35 hours a week). Actually schedule is mentioned: "flexible working schedule - at Vitesse you’re expected to work 35 hours a week." That's schedule info. So we can create a Schedule section.
Pay: not mentioned, so we should not create Pay section.
Benefits: "Why You'll Love Working Here" includes real impact, continuous learning, collaborative culture, opportunities to grow alongside a scaling global fintech. Also flexible schedule. That's benefits. So we can create Benefits section.
Qualifications: maybe not separate; we have "What You'll Need to Succeed" which includes experience, skills, etc. That could be Requirements or Qualifications. We'll treat as Requirements.
Skills: maybe we can extract skills from that list: strong analytical, problem-solving, attention to detail, organisation, prioritisation, communication, payments/FinTech experience advantageous, CRM/support platforms beneficial. Could be Skills section.
But we should avoid many thin sections. Prefer few substantive sections. So we could combine Requirements and Skills into one section "Requirements" that includes both experience and skills. Or we could have "Requirements" and "Skills". But instruction says prefer few substantive sections over many thin ones. So maybe we have three sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (experience + skills), Benefits (why you'll love working here), Schedule (flexible hours). That's five sections. Could we combine Benefits and Schedule? Schedule is a benefit but it's specific; maybe keep separate.
We must not include EEO boilerplate. Remove duplicated lines. Ensure we preserve all substantive information.
Let's extract content:
Company overview (About Us):
- We are Vitesse – the treasury and payment partner of choice for insurance.
- Your next adventure awaits! Join the team who are redefining the payments space.
- At Vitesse, we're more than just a payments platform – we're the trusted financial infrastructure connecting the global insurance ecosystem.
- Tailor-made for insurers, brokers, MGAs, and TPAs, our unified platform optimises claims funds, enables real-time global payments, and delivers full financial control.
- Our impact is real: over $20 billion in payments across 200+ countries, hundreds of millions returned to insurers’ balance sheets, and counting.
- We’re licensed in the UK (FCA), Europe (DNB), and New York (NYDFS), with over 260 amazing colleagues worldwide.
- With $93 million recently raised in Series C funding from KKR, our journey is just beginning, and our ambitions are sky-high.
- Headquartered in the heart of London and expanding across Europe and the US, Vitesse is where your ideas power tomorrow’s insurance solutions.
- Are you ready to make a difference? You're in the right place.
Role description (The Role):
- Reporting to Head of Operations, you'll join our growing US Operations team as a Solutions Analyst, supporting customers through platform configuration, onboarding, optimisation and operational support while maintaining strong operational controls and customer experience.
What You'll Be Doing (Responsibilities):
List items:
- Become a Vitesse product expert, supporting clients with platform setup, configuration, optimisation, and ongoing use.
- Provide technical guidance and configuration support to clients and internal stakeholders.
- Resolve customer enquiries and perform solution configuration updates.
- Configure new client accounts and manage users, permissions, MFA, notifications, account updates and closures.
- Support user access reviews and account configuration updates.
- Support UK↔US migrations, SSO, mergers, pricing updates and legacy account restructuring.
- Support onboarding, testing, UAT and platform releases.
- Partner with Customer Support, Product, Engineering, Implementation, Pre-Sales and Customer Success.
- Maintain documentation and meet SLA expectations.
- Follow operational risk controls, verification processes and escalate high-risk requests.
Your Mission:
- Deliver an exceptional customer experience by becoming a trusted expert in the Vitesse platform while maintaining operational excellence, security and client service.
Success in Your First Year:
- Become a trusted product expert.
- Independently manage customer configuration requests.
- Support onboarding, migrations and platform enhancements.
- Meet SLA and quality targets.
- Drive continuous improvement opportunities.
What You'll Need to Succeed:
- Experience in customer-facing, operations, implementation or technical support.
- Strong analytical and problem-solving skills.
- Excellent attention to detail and organisation.
- Ability to prioritise in a fast-paced environment.
- Strong communication skills.
- Payments, FinTech or Financial Services experience is advantageous.
- Experience with CRM/support platforms such as Salesforce or Zendesk is beneficial.
Why You'll Love Working Here:
- Real impact, continuous learning, collaborative culture, and opportunities to grow alongside a scaling global fintech.
- We understand that everyone has their own work rhythm and believe in a flexible working schedule - at Vitesse you’re expected to work 35 hours a week.
Our Values – or what we call “Vitesse at Our Best”:
- Confident Humility: We believe the best ideas come from listening and learning. We leave ego at the door, ask for help when we need it, and celebrate collective success. When one of us wins, we all do.
- Driven to Succeed: We’re ambitious about the opportunity ahead and committed to achieving it together. We hold ourselves to high standards, take pride in what we deliver, and push for meaningful outcomes for our customers, our partners, and each other.
- Tenacious Responsibility: We take ownership of our work, our decisions, and our results. We face challenges with resilience, learn from setbacks, and see things through to completion. Because doing the right thing matters.
We need to include values maybe as part of Benefits or separate? Could be part of Benefits or Culture. But we already have Benefits section; we could include values there. However values are substantive; we could include them under Benefits or maybe a separate "Culture" section but not in list of headings. Since we prefer few sections, we could incorporate values into Benefits section.
Schedule: flexible working schedule - 35 hours a week. Already mentioned in Why You'll Love Working Here. Could be part of Benefits.
Thus we can have sections:
- About the role (company overview + role summary)
- Responsibilities (duties list)
- Requirements (experience + skills)
- Benefits (why you'll love working here, values, schedule)
We must not include Pay section.
We must not include duplicate lines.
We need to format using for each section heading, then content: either
. Probably fine to use "About Us". But to be safe, we could use "About the role" for company overview and role description combined? But we also have "What You'll Be Doing" which is responsibilities. So we could have sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (what you need to succeed), Qualifications (maybe not separate), Skills (maybe part of requirements), Benefits (Why you'll love working here), Pay (not present), Schedule (flexible schedule 35 hours a week). Actually schedule is mentioned: "flexible working schedule - at Vitesse you’re expected to work 35 hours a week." That's schedule info. So we can create a Schedule section.
Pay: not mentioned, so we should not create Pay section.
Benefits: "Why You'll Love Working Here" includes real impact, continuous learning, collaborative culture, opportunities to grow alongside a scaling global fintech. Also flexible schedule. That's benefits. So we can create Benefits section.
Qualifications: maybe not separate; we have "What You'll Need to Succeed" which includes experience, skills, etc. That could be Requirements or Qualifications. We'll treat as Requirements.
Skills: maybe we can extract skills from that list: strong analytical, problem-solving, attention to detail, organisation, prioritisation, communication, payments/FinTech experience advantageous, CRM/support platforms beneficial. Could be Skills section.
But we should avoid many thin sections. Prefer few substantive sections. So we could combine Requirements and Skills into one section "Requirements" that includes both experience and skills. Or we could have "Requirements" and "Skills". But instruction says prefer few substantive sections over many thin ones. So maybe we have three sections: About the role (company overview + role summary), Responsibilities (duties), Requirements (experience + skills), Benefits (why you'll love working here), Schedule (flexible hours). That's five sections. Could we combine Benefits and Schedule? Schedule is a benefit but it's specific; maybe keep separate.
We must not include EEO boilerplate. Remove duplicated lines. Ensure we preserve all substantive information.
Let's extract content:
Company overview (About Us):
- We are Vitesse – the treasury and payment partner of choice for insurance.
- Your next adventure awaits! Join the team who are redefining the payments space.
- At Vitesse, we're more than just a payments platform – we're the trusted financial infrastructure connecting the global insurance ecosystem.
- Tailor-made for insurers, brokers, MGAs, and TPAs, our unified platform optimises claims funds, enables real-time global payments, and delivers full financial control.
- Our impact is real: over $20 billion in payments across 200+ countries, hundreds of millions returned to insurers’ balance sheets, and counting.
- We’re licensed in the UK (FCA), Europe (DNB), and New York (NYDFS), with over 260 amazing colleagues worldwide.
- With $93 million recently raised in Series C funding from KKR, our journey is just beginning, and our ambitions are sky-high.
- Headquartered in the heart of London and expanding across Europe and the US, Vitesse is where your ideas power tomorrow’s insurance solutions.
- Are you ready to make a difference? You're in the right place.
Role description (The Role):
- Reporting to Head of Operations, you'll join our growing US Operations team as a Solutions Analyst, supporting customers through platform configuration, onboarding, optimisation and operational support while maintaining strong operational controls and customer experience.
What You'll Be Doing (Responsibilities):
List items:
- Become a Vitesse product expert, supporting clients with platform setup, configuration, optimisation, and ongoing use.
- Provide technical guidance and configuration support to clients and internal stakeholders.
- Resolve customer enquiries and perform solution configuration updates.
- Configure new client accounts and manage users, permissions, MFA, notifications, account updates and closures.
- Support user access reviews and account configuration updates.
- Support UK↔US migrations, SSO, mergers, pricing updates and legacy account restructuring.
- Support onboarding, testing, UAT and platform releases.
- Partner with Customer Support, Product, Engineering, Implementation, Pre-Sales and Customer Success.
- Maintain documentation and meet SLA expectations.
- Follow operational risk controls, verification processes and escalate high-risk requests.
Your Mission:
- Deliver an exceptional customer experience by becoming a trusted expert in the Vitesse platform while maintaining operational excellence, security and client service.
Success in Your First Year:
- Become a trusted product expert.
- Independently manage customer configuration requests.
- Support onboarding, migrations and platform enhancements.
- Meet SLA and quality targets.
- Drive continuous improvement opportunities.
What You'll Need to Succeed:
- Experience in customer-facing, operations, implementation or technical support.
- Strong analytical and problem-solving skills.
- Excellent attention to detail and organisation.
- Ability to prioritise in a fast-paced environment.
- Strong communication skills.
- Payments, FinTech or Financial Services experience is advantageous.
- Experience with CRM/support platforms such as Salesforce or Zendesk is beneficial.
Why You'll Love Working Here:
- Real impact, continuous learning, collaborative culture, and opportunities to grow alongside a scaling global fintech.
- We understand that everyone has their own work rhythm and believe in a flexible working schedule - at Vitesse you’re expected to work 35 hours a week.
Our Values – or what we call “Vitesse at Our Best”:
- Confident Humility: We believe the best ideas come from listening and learning. We leave ego at the door, ask for help when we need it, and celebrate collective success. When one of us wins, we all do.
- Driven to Succeed: We’re ambitious about the opportunity ahead and committed to achieving it together. We hold ourselves to high standards, take pride in what we deliver, and push for meaningful outcomes for our customers, our partners, and each other.
- Tenacious Responsibility: We take ownership of our work, our decisions, and our results. We face challenges with resilience, learn from setbacks, and see things through to completion. Because doing the right thing matters.
We need to include values maybe as part of Benefits or separate? Could be part of Benefits or Culture. But we already have Benefits section; we could include values there. However values are substantive; we could include them under Benefits or maybe a separate "Culture" section but not in list of headings. Since we prefer few sections, we could incorporate values into Benefits section.
Schedule: flexible working schedule - 35 hours a week. Already mentioned in Why You'll Love Working Here. Could be part of Benefits.
Thus we can have sections:
- About the role (company overview + role summary)
- Responsibilities (duties list)
- Requirements (experience + skills)
- Benefits (why you'll love working here, values, schedule)
We must not include Pay section.
We must not include duplicate lines.
We need to format using for each section heading, then content: either
for prose,
- for lists.
We need to ensure we preserve all substantive information. Let's craft.
Section About the role: combine company overview and role summary (The Role). Could be two paragraphs: first company overview, then role summary.
We must not repeat job title as heading; we are not.
We must not include Job ID etc.
Now produce HTML.
Let's write:
About the role
We are Vitesse – the treasury and payment partner of choice for insurance. Your next adventure awaits! Join the team who are redefining the payments space. At Vitesse, we're more than just a payments platform – we're the trusted financial infrastructure connecting the global insurance ecosystem. Tailor-made for insurers, brokers, MGAs, and TPAs, our unified platform optimises claims funds, enables real-time global payments, and delivers full financial control. Our impact is real: over $20 billion in payments across 200+ countries, hundreds of millions returned to insurers’ balance sheets, and counting. We’re licensed in the UK (FCA), Europe (DNB), and New York (NYDFS), with over 260 amazing colleagues worldwide. With $93 million recently raised in Series C funding