This is school-side infrastructure, not part of your integration. Evenue is one of the systems participating schools run. Wishbone delivers completed donations into it on the school's behalf. Banks always call the same Wishbone endpoints with the same payload regardless of which platform a school uses — this page just shows where the money lands and what
school_confirmation_id refers to.Integration
POST https://api.evenue.net/v3/patrons/{patron_id}/creditsWishbone → Evenue
Wishbone posts a points-funded ticket credit to Evenue's box-office API so cardholders can apply rewards toward ticket purchases and seat upgrades — credited directly to their Evenue patron account, alongside their existing season-ticket history.
View Docs ↗Bank App
Credit request
Wishbone
Validate & record
Evenue
POST account credit
School CRM
Step 1
Bank submits POST /v1/donations/request with dollar_amount and bank_transaction_ref. Optionally includes an event_id in metadata.
Step 2
Wishbone validates school_id and minimum amount, then creates an internal donation record flagged as a ticket credit.
Step 3
Wishbone resolves the Evenue patron_id and POSTs an account credit with amount, credit_type, and optional event scope.
Step 4
Evenue returns credit_id and the patron's updated available balance. Wishbone fires the donation.completed webhook to the bank.
Request Body
Response
◎
Fire a request to see the response
What Wishbone does with the response
Store the returned credit_id and available_balance, mark the donation 'completed', and fire the donation.completed webhook to the bank. The cardholder sees ticket credit applied to their Evenue patron account — usable at checkout for the next home game.