Overview
The Account Intelligence Feedback endpoint allows you to report return events that occurred despite receiving an acceptable risk score from GrailPay’s Account Intelligence system. By submitting feedback, you help GrailPay track real-world outcomes, monitor model performance, and continuously improve risk accuracy.
Feedback collected through this endpoint is used for analytics, evaluation, and model training—not for real-time score correction. This creates a reliable feedback loop that improves visibility into edge cases and supports ongoing model refinement.
This endpoint is only available to clients actively integrated with the Risk Intelligence API.
When to Submit Feedback
You should submit feedback when:
- A transaction results in an unexpected return despite receiving a low-risk Account Intelligence score
- You want to help improve the accuracy of future risk evaluations
- You need to report false negatives for internal tracking and model monitoring
Request Fields
When submitting feedback, your request payload should include details about the account, the return event, and a
reference to the original Account Intelligence evaluation. Required fields ensure we can accurately link your feedback
to the original prediction, while optional fields provide additional context that helps improve model analysis.
Required Fields
| Field | Type | Description |
|---|
account_number | string | The account number from the original evaluation |
routing_number | string | The routing number from the original evaluation |
outcome_status | string | The outcome status of the transaction |
return_code | string | The ACH return code received |
name_match_requested | boolean | Whether name matching was enabled in the original request |
| Field | Type | Description |
|---|
inference_request_id | UUID | The request ID returned by GrailPay in the original Account Intelligence response (preferred) |
inference_timestamp | timestamp | The UTC timestamp of the original request, if the request ID is unavailable |
Providing the inference_request_id is strongly recommended as it ensures accurate linkage to the original risk evaluation.
Optional Fields
| Field | Type | Description |
|---|
returned_at | timestamp | When the return was received |
transaction_initiated_at | timestamp | When the transaction was initiated (client-side) |
sec_code | string | The SEC code of the transaction |
amount | decimal | The transaction amount |
direction | string | Transaction direction: credit or debit |
Usage Recommendations
- Submit feedback promptly after a return event occurs to ensure accurate timestamps and traceability.
- Always include the
inference_request_id when available for precise linkage to the original prediction.
- Provide optional fields like
amount, sec_code, and direction when possible to enrich the feedback data.
- Use feedback submission as part of your standard return-handling workflow to maximize model improvement benefits.
Questions?
If you’re encountering any issues, please reach out to [email protected].
