Report a card enrichment as incorrect
Endpoint to report a card enrichment as incorrect. An enrichmentId and an errorDescription are required fields to report an enrichment. Optional request fields such as incorrectLocation, incorrectLocationDescription, incorrectCategory, incorrectCategoryDescription, incorrectChannel, incorrectChannelDescription, incorrectCounterparty, and incorrectCounterpartyDescription, can be set to indicate what needs to be addressed in the enrichment. Once a report has been addressed, you will receive a corrected enrichment via a callback url you set with Spade. See the callback section to learn more on how we send back a corrected enrichment.
Authorizations
Body
Schema for reporting an enriched transaction.
Enrichment id represented as a string UUID.
Description of incorrect details in enrichment.
1024"Enrichment has an incorrect location. Wrong postal code."
Bool indicating if the enrichment has a wrong location.
true
Description of incorrect location details in enrichment.
1024"The location's city is incorrect."
Bool indicating if the enrichment has a wrong Category.
false
Description of incorrect category details in enrichment.
1024"The category returned is incorrect."
Bool indicating if the enrichment has a wrong Channel.
false
Description of incorrect channel details in enrichment.
1024"The spending channel should have been physical."
Bool indicating if the enrichment has a wrong Counterparty.
false
Description of incorrect counterparty details in enrichment.
1024"The counterparty is incorrect."
Callbacks
POSThttps://example.com/your/callback/endpointCorrectedEnrichment
Body
Our ID representing the enrichment, not to be confused with your provided transactionId.
An array of counterparties matched to the transaction, ordered by descending match score.
The mobile app information for the transaction. This object is only non-null if the transaction was matched to a mobile app.
This is a premium Spade field available depending on your product package.
A dictionary containing the custom attributes that were included in the enrichment request (if any).
{
"custom_attribute_1": "value_1",
"custom_attribute_2": "value_2"
}An array of triggered actions, or null if no triggers matched.
This field is only present if your integration has the actions feature enabled.
When a transaction matches one or more registered triggers, this array contains the action details
including your custom action data. Multiple matches are possible when triggers are registered
at different scopes (account, program, user, card).
[
{
"id": "trigger-12345",
"type": "merchant_trigger",
"action": { "type": "REWARD", "rewardPercent": 5 },
"scope": "account",
"source": "counterparty"
}
]Response
Your server returns this code if it accepts the callback
Response
Enrichment reported successfully
Response for reporting an enriched transaction.
"Enrichment Successfully Reported."

