Payment Write-backs & Bulk Collections — Technical Overview
Why This Matters
Payment write-backs and bulk collections are the two primary payment features Weave provides. Understanding both at a technical level — including how capabilities are added to standard.json — is your entry point into Payments integration work.
What You'll Learn
- The two payment integration features: payment write-back and bulk collection
- Payment write-back: a payment made in Weave → reflected in the patient's PMS ledger
- How to enable payment write-back: add a 'payment_type' capability to standard.json for the integration
- Bulk collection: syncing accounts with outstanding balances for the Weave collections tab
- How the PXE team (Payments Experience team) uses bulk collection data
- The standard.json capability model and how it gates feature availability per integration
Watch Video
Lesson Summary
Two payment features exist at the integration level. Payment write-back: when a patient pays in Weave, that payment is written to their account in the PMS ledger. Enabling it requires adding a 'payment_type' capability entry to the integration's standard.json file. Bulk collection: syncing the list of patients with outstanding balances (aging data) into Weave so offices can send bulk payment request messages. The PXE team (Payments Experience) consumes bulk collection data to populate the collections tab. Capabilities in standard.json act as feature flags — if the capability isn't listed, the feature isn't available for that integration.