Get sandbox card account transactions
GET/v1/sandbox/card-accounts/:mockCardAccountId/transactions
Only for managing sandbox data, not part of the production API. Get all card transactions on a card account created using POST /v1/sandbox/card-accounts. Only includes transactions created using POST /v1/sandbox/card-accounts/{mockCardAccountId}/transactions
Request
Path Parameters
Query Parameters
Possible values: [booked
, pending
, both
]
Advertises which date the client wishes to receive transactions from.
Advertises which date the client wishes to receive transactions to.
Advertises how many transactions should be skipped before starting to count the limit.
Possible values: >= 1
Advertises how many transactions should be returned.
Header Parameters
- keyId must be formatted as
keyId="SN=XXX,CA=YYY"
whereXXX
is the serial number of the signing certificate in hexadecimal encoding andYYY
is the full Distinguished Name of the Certificate Authority having certificate - algorithm must identify the same algorithm for the signature as presented in the signing certificate and should be
rsa-sha256
- headers must contain
date
,digest
,x-request-id
,psu-id
,psu-corporate-id
, andtpp-redirect-uri
when available - signature must be computed as
Base64(RSA-SHA256(signingString))
Advertises which content types, expressed as MIME types, the client is able to understand. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice with the Content-Type response header.
Advertises which character set the client is able to understand. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice within the Content-Type response header.
Advertises which content encoding, usually a compression algorithm, the client is able to understand. Using content negotiation, the server selects one of the proposals, uses it and informs the client of its choice with the Content-Encoding response header.
Advertises which natural languages the client is able to understand, and which locale variant is preferred. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice with the Content-Language response header.
The domain name of the server (for virtual hosting), and (optionally) the TCP port number on which the server is listening.
Request identifier, unique to the call, as determined by the TPP.
The certificate used for signing the request in base64 encoding.
HTTP Message Signature as specified by https://tools.ietf.org/html/draft-cavage-http-signatures-10 with requirements imposed by Berlin Group's NextGenPSD2 Framework.
If any values in the Signature header is ISO-8859-1 or UTF-8 encoded you need to URL encode the Signature header according to RFC 2047 which means MIME encoding the signature.
Also the signature must be wrapped using this format: =?charset?encoding?encoded signature?=
Example of this encoding: =?utf-8?B?a2V5QTQsQ0E9Mi41LjQuOTc9IzB........jMTM1MDUzNDQ0ZTRmMmQ0NjUz?=
Java example of how to implement encoding:
if (charset.equals(StandardCharsets.UTF_8)) {
Signature = String.format("=?utf-8?B?%s?=", Base64.getEncoder().encodeToString(signature.getBytes(StandardCharsets.UTF_8)));
}
Responses
- 200
- application/json
- Schema
- Example (from schema)
- application/json;charset=utf-8
Schema
Array [
]
cardAccount
object
required
cardTransactions
object
required
booked
object[]
required
transactionAmount
object
required
originalAmount
object
required
{
"cardAccount": {
"maskedPan": "1234xxxxxxxx4321"
},
"cardTransactions": {
"booked": [
{
"cardTransactionId": "41a2078c-1772-46f8-b654-0c7454abd965",
"bookingDate": "2019-05-08",
"transactionDate": "2019-05-16",
"transactionAmount": {
"amount": 100,
"currency": "NOK"
},
"originalAmount": {
"amount": 100,
"currency": "NOK"
},
"merchantCategoryCode": "BOB"
}
],
"pending": []
}
}
{
"cardAccount": {
"maskedPan": "1234xxxxxxxx4321"
},
"cardTransactions": {
"booked": [
{
"cardTransactionId": "41a2078c-1772-46f8-b654-0c7454abd965",
"bookingDate": "2019-05-08",
"transactionDate": "2019-05-16",
"transactionAmount": {
"amount": 100,
"currency": "NOK"
},
"originalAmount": {
"amount": 100,
"currency": "NOK"
},
"merchantCategoryCode": "BOB"
}
],
"pending": []
}
}