What you’ll build
Your developer connects your platform to Roster so a donor can start giving and your team can follow the results. That connection needs to:
- Register your churches and send the information they need for setup.
- Let a donor start giving from your product, with the correct church attached to their journey.
- Pass along information you’re allowed to provide, such as a name your platform already knows. This saves typing, though the donor may still need to confirm or correct it.
- Receive updates about recurring gifts and donations, and check for any updates your software missed.
- Use the donation and permitted donor information in your own reports and existing connection to church-management software.
Suppose a donor starts a $25 recurring gift. Your platform receives updates when the arrangement is created and activated. When Roster records a deposit, your platform receives the details of that donation. The next deposit is another donation under the same arrangement.
Your developer builds this connection in your software. The portal gives the team a place to set it up, check the results and manage it afterward.