For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Contact usLogin
GuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelog
  • Getting Started
    • Navigating the Docs
  • DAFpay
    • Overview
    • FAQ
  • Disbursements
    • Overview
    • How It Works
    • Disbursement Lifecycle
    • Compliance
    • Sandbox
    • How Chariot Compares
    • FAQ
  • Gift Processing
    • Overview
    • How It Works
    • Getting Started
    • FAQ
  • Lockbox Providers
    • Lockbox Provisioning
LogoLogo
Contact usLogin
On this page
  • Request ID
Lockbox Providers

Provisioning

Was this page helpful?
Previous
Built with

For dedicated PO boxes, the provisioning flow is as follows. See the Provision a Lockbox API reference for endpoint details.

Also see: Mail Uploads | Rescans

1

Chariot requests a new PO Box via Email

Chariot sends an email to the lockbox provider containing:

  • The organization’s name and EIN (e.g., “Some Nonprofit, 12-3456789”)
  • A request ID generated by Chariot (e.g., req_01kkmjrdgdjtwgk7wdkba1kn9s)
2

Provider provisions the PO Box

The provider reserves and sets up the new PO box (e.g., PO 9876).

3

Provider notifies Chariot via API

Once the PO box is live, the provider sends a request to the Chariot provisioning endpoint:

POST /lockbox/provision
1{
2 "request_id": "req_01kkmjrdgdjtwgk7wdkba1kn9s",
3 "location_id": "po_9876",
4 "address": {
5 "line1": "123 Main St",
6 "line2": "STE 12345",
7 "city": "New York",
8 "state": "NY",
9 "zip": "12345-1234"
10 }
11}

Request ID

  • The request ID is a one-time unique value generated by Chariot for each PO box request
  • The provider returns the request ID when notifying Chariot that the box has been provisioned
  • The request ID is not included in subsequent API calls (e.g., batch uploads)