Time when this object was created; expressed in RFC 3339 format
Time when this object was last updated; expressed in RFC 3339 format
The payment channel for the grant. This is useful to know how the grant will be sent. The payment channel will be one of the following:
The grant amount in cents that will be processed by Chariot and submitted to the DAF. This amount must be in whole dollar increments (rounded to the nearest hundred) as currently all DAFs only accept whole dollar grant amounts.
The identifier of the donor’s DAFpay Workflow Session.
See Capturing Grant Intents for how to get this value from the DAFpay CHARIOT_SUCCESS
event.
A note the donor wants to send to the nonprofit. Maximum length: 400 characters.
The designation to include on the grant. If this is left blank, “Where needed most” will be used. Note that including a custom designation may cause the grant approval process to take longer. Maximum length: 100 characters.
Create and submit a new grant. This should be used to capture a grant intent from an authorized DAFpay workflow session and submit the grant request to the DAF sponsor.
Error handling:
410 Gone
.409 Conflict
.400 Bad Request
.400 Bad Request
.400 Bad Request
.OAuth authentication of the form <token>
.
This parameter specifies the fee your platform plans to take from the grant in cents.
This is a fee in addition to Chariot’s processing fee. With application fees,
Chariot collects the fee you determine from the nonprofit and passes it to your platform.
Please note that platform fees are only taken when the grant is successfully received by the Nonprofit.
The sum of Chariot’s fee and the applicationFeeAmount cannot exceed 5% of the grant’s amount.
If the fee limit is exceeded, a 400 Bad Request
error will be returned.