Managing API 3.0 Disputes
Availability
Dispute API 3.0 is still under development. The information in this reference is subject to change as development proceeds and is not a guarantee of future functionality. If you are interested in using this API, contact Galileo for details.
This guide explains how to manage disputes after they have passed through the entire intake flow, as described in Creating an API 3.0 Dispute. The /claim/intake/submit
endpoint must have been called for a claim before you can manage it with the processes in this guide.
Note
Most of the request and response field names are in
PascalCase
, but a few are incamelCase
. This is intended. Make sure you follow the same case conventions as shown in the reference.
Manage claims
Follow these steps to manage the claims.
Attach required documents
If you did not retrieve and submit the required PDF during the intake flow (/claim/intake/retrieveDocRequirements
and /claim/intake/addDocuments
), you can call two other endpoints after the claim has been submitted.
- Call
/claim/documents/retrieveRequirements
. - Galileo returns one of two options:
- A message saying that no further documents are required.
- A base64-encoded PDF (
templateDocumentationStream
) that the user must fill out and return. When the user has filled out the form, you call/claim/documents/add
to send the completed form to Galileo. - Send only one document at a time with
/claim/documents/add
. If you need to send multiple documents at this stage, call/claim/documents/add
once for each document to return.
View claims
To view all claims for a cardholder, call /claim/list
with these parameters:
DaysToLookBack
— Input an integer to specify the number of days in the past to retrieve claims.- Pass only one of the following:
accountNo
— Format:P{prog_id}|{prn}
ClaimId
— As returned by /claim/intake/createCustomerId
— Format:P{prog_id}|{prn}
If you did not pass ClaimId
for /claim/list
, call /claim/details/retrieve
with the ClaimId
. This endpoint returns:
{
"claimListResponse": [
{
"accountHolder": "William James Murray",
"requiredDocumentCount": 0,
"customerContactDate": "20271005T000000.000 GMT",
"claimId": "2110050013C",
"externalCaseId": "123456789",
"accountNumber": "4447111111117413",
"claimStatus": "Open-Execute",
"createName": "creat or",
"accountType": "Credit",
"customerId": "123456789",
"isClaimSubmitted": "true",
"totalClaimAmount": 150.23
}
],
"StatusList": [
{
"Type": "Success",
"Message": "Success",
"Code": "200"
}
],
"rtoken": "984513-395483653-4483483478",
"StatusCode": "200"
}
Checking on claim status
To provide your account holders with an up-to-date claim status, call /claim/retrieve
with the ClaimId
. You can display the claimStatus
along with any TalkingPoints
To notify clients when the status changes, set up a cron job to poll the endpoint periodically, and then when claimStatus
changes, you can send a notification.
Manage transactions
Follow these instructions to manage disputed transactions.
View the transactions in a claim
To view all of the transactions that are included in an existing claim, call /claim/transactions/list
with the ClaimId
. The endpoint returns:
{
"TransactionList": [
{
"TransactionAmount": "100.000000000",
"CardLastFourDigits": "8557",
"DisputedAmount": "100.000000000",
"DisputeId": "2307190009D",
"Description": "Galileo Bank BRANCH #2145",
"PostingDate": "20270727",
"PostingDateTime": "202707272T020235.184 GMT",
"CurrentStage": "Analyze",
"LastCommitDate": "20270728T020235.184 GMT",
"TransactionId": "2",
"DisputeStatus": "Open-Disposition"
}
],
"StatusList": [
{
"Type": "Success",
"Message": "Success",
"Code": "200"
}
],
"rtoken": "984513-395483653-4483483478",
"StatusCode": "200"
}
Add attachments
To add an attachment to an existing claim, first convert the document into a base-64 encoded string and then call /claim/attachments/add
to add it to the claim. You can use this endpoint to attach multiple documents with one call.
Updated 5 days ago