Add Transactions

post

https://dispute-api-{corename}.{env}.gpsrv.com/addTransactions

👍
Availability
No new clients will be set up with Dispute API 2.0. Legacy clients will eventually be migrated to Dispute API 3.0.

Use the Add Transactions endpoint to attach the transactions that the account holder selects. Specify the transactionId as returned by Get Transactions (which is not the transactionId that you pass to identify a unique endpoint request).

This endpoint is part of a conversational API—a series of endpoint calls that must be made in a certain order. For instructions see the Creating an API 2.0 Dispute guide.

Previous endpoint: Get Transactions
Next endpoint: Get Questionnaire

Form Data

apiLogin

string

required

Provider's web service username, as provided by Galileo for the requesting IP address.
Pattern: Max 50 characters
Example: "AbC123-9999"

apiTransKey

string

required

Web service password, as provided by Galileo for the requesting IP address.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

providerId

int32

required

Galileo-issued unique provider identifier.
Pattern: Max 10 digits
Example: 9999

transactionId

string

required

1 to 60

A provider-generated ID that is unique to each API call. A UUID is preferred. Do not reuse this identifier for multiple API calls.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

caseId

string

required

^$|^([0-9]{11}[A-Z]{1})$

Case identifier as returned by Create Case.
Pattern: Max 11 digits with a letter
Example: "22021000017C"

transactionsList

string

required

A list of one or more transaction IDs to attach to the case. Use the transactionId as returned in the transactionList of Get Transactions. The format for a transactionId is P{prog_id}|{prn}|{auth_id}|{network_id}
.Pattern: JSON list
Example: [{"transactionId": "P111|999156868254|798657228|M"}, {“transactionId”: "P111|999156868254|797295274|M"}]

Response

default