ChurchInput

Church display name, kept on one line. Line breaks and other control characters become a space, invisible and text-direction characters are removed, and surrounding whitespace is trimmed; a name with nothing left is 400. The stored name is the one we return.

The church's settlement account. Roster verifies ownership immediately, on its own, against the bank network — the church is never contacted. Send it with the import whenever you have it: a church starts receiving paycheck gifts only after Roster verifies it, this account included. When the account changes later, donations wait in the donor's account until the new one is verified. Ignored when another platform registered the church first (the response carries linked: existing_church and no bank_verification).

The church's IRS Employer Identification Number. Send it and we recognise a church that another partner already registered with the same EIN, instead of creating a second record for the same institution. When that happens the response carries linked: existing_church; the church keeps one id, one page and one settlement account, and simply gains your channel alongside the one it already had. The settlement account and the church's legal details stay with the platform that registered the church first. We never store the number: it becomes a keyed hash on arrival. The sandbox test EINs (00-0000001 to 00-0000099) are refused here: POST /v1/churches answers 400, and POST /v1/churches/import returns that item as rejected while the rest of the batch goes on. In the sandbox they belong in the church verification request (on creation they would turn every church that shares one into a single church); in production that request refuses them too.

Not yet covered: a church that signed up with Roster directly. Matching those is coming with church verification for partner churches — until then, sending the EIN for one of them creates a new record as before.

When the church receives its payouts. daily (the default) sends each donation at the first weekday 4:00 p.m. ET cutoff after it is ready. weekly sends them once a week: a donation deposited any day goes out on the next Monday, or on the next business day when that Monday is a bank holiday; a donation deposited on Monday waits for the following Monday. Only the day changes: each donation is still its own transfer, and the money waits in the donor's account until then. Ignored when another platform registered the church first. Change it later with POST /v1/churches/{id}/payout-schedule.

Your own id for this church — its stable identity on our side. Registering the same reference again (even under a different Idempotency-Key) returns the existing church instead of creating a second one. Consents sent earlier with the same church_reference are joined to it.