Payment Responses
Client
←
MTS
Payment responses include the following specific responses:
Balance change response
Deposit response
Withdrawal response
Envelope and Content table:
The envelope provides the content's (Payment response) context and contains the following fields (besides Content):
correlationId
timestampUtc
operation
version
content
See Content object description below
M
Object
correlationId
Client defined string to facilitate the request-response pairing, Sportradar is obliged to return the same string in every response
M
String
timestampUtc
Timestamp of ticket placement as submitted by the client (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000
M
Integer
operation
Declaration of operation type, should be "balance-change-inform" in the case of a Balance change response or
"deposit-inform" in the case of a Deposit response or
"withdrawal-inform" in the case of a Withdrawal response
M
String
version
Indicates the ticket format version
M
String
}
Content object (Payment response)
The Content object includes the following fields:
type
code
message
Please note that in the case of major ticket errors or internal system errors the content object has a different structure and contains "type": "error-reply" instead of "type": "cashout-reply. For description, see Error-reply Response.
Content object table:
Object
type
Declaration of content type, should be "balance-change-inform-reply" in the case of a Balance change response
or
"deposit-inform-reply" in the case of a Deposit response
or
"withdrawal-inform-reply" in the case of a Withdrawal response
or "error-reply" in the case of major ticket errors or internal system errors (see also Error-reply Response).
M
String
code
Response code
M
Integer
message
Readable response code description, minimal string length = 1, maximum string length = 128
M
String
Last updated
Was this helpful?