School platforms
The school-side systems Wishbone delivers into. You do not integrate with these.
Nothing here changes your integration. You always call the same Wishbone endpoints with the same payload. This page exists so you know where a donation ends up and what school_confirmation_id refers to when you see it on a webhook.
Each participating school runs its own donor or ticketing system. Wishbone normalizes your donation request and delivers it through a per-platform adapter, then returns that platform's confirmation identifier to you.
| Platform | What a donation becomes | Detail |
|---|---|---|
| PAC io | A gift record on the donor CRM, which allocates priority points and updates the seat-priority queue. | Integration detail → |
| Evenue | A ticket credit on the fan's patron account, usable at checkout. | Integration detail → |
| Ticketmaster | An account credit usable across the school's athletics events. | Integration detail → |
Why you might still care
Two reasons. First, school_confirmation_id on a donation.completed webhook is the platform's own reference — it is what a cardholder's support ticket will quote. Second, a school's platform determines what the cardholder receives: priority points move you up a seat queue, a ticket credit does not. If your app describes the benefit, read it from the school record rather than hardcoding it.