Compliance & funds flow

Wishbone records and routes contributions. It does not hold or move money.

Wishbone is not in the funds flow

Wishbone does not move money. The bank passes a dollar-equivalent value with each donation request, and the school receives funds directly from the bank's redemption processing. Wishbone records the transaction, routes the metadata, and provides confirmation webhooks.

Practically, this means the dollar_amount you send is a statement about value your side has already reserved or debited. Wishbone never debits a cardholder, never holds a balance, and never disburses to a school.

Tax receipts

The receiving school or foundation is the charitable entity and issues the receipt. School records expose the issuing entity and EIN via GET /v1/schools/{school_id}, and a completed donation exposes whether a receipt was issued.

Cardholder data

Wishbone stores the cardholder identifiers you send — your bank_user_id, email and display name — to attribute donations and deliver receipts. It does not receive or store card numbers, points balances, or credentials. Webhook delivery logs record a hash of the payload rather than the payload itself, so donor details are not retained in delivery history.

Unlinking

DELETE /v1/accounts/{wishbone_user_id} marks the account unlinked and emits account.unlinked. In-flight donations are not cancelled, and the record is retained rather than deleted so completed contributions stay attributable for tax purposes.