Payments Feature Overview — Integration Payments Domain
Why This Matters
The Payments integration is a newer domain within the Integrations team. Understanding what data it syncs — and how it differs from core patient/appointment sync — gives you a more complete picture of what the team builds.
What You'll Learn
- What the Payments integration team does: bridges the Integrations team and the Payments product team
- What data entities the Payments team syncs: insurance details, claims, transactions, proc logs, accounts
- How payment write-back works at a high level: payments made in Weave are reflected in the PMS ledger
- Why the Payments integration team is described as 'relatively new' and still evolving
- How proc logs relate to appointments and why they're needed for payment data
Watch Video
Lesson Summary
The Payments integration team works at the intersection of Integrations and Payments. Unlike the core integration teams that sync patients and appointments, they sync payment-related entities: insurance details, claims, transactions, procedure logs (proc logs), and accounts. Payment write-back means that when a patient pays in Weave, that payment gets written back to the PMS patient ledger. The team is still evolving — they're actively figuring out which entities to sync and how to structure the pipeline. Proc logs are tightly linked to appointments and procedures and are a key data type for this team.