Issuing API browser API reference

API documentation for Viva Wallet issuing service.

Authorization

An authorization request represents a transaction submitted for approval. No actual posting of cardholder accounts occurs during this type of transmission.

Authorization request

After receiving an authorization request, the Partner decides whether to approve or decline the transaction based on the account’s available funds and any applicable fraud rules in place, and responds using one of the designated response codes.

If the authorization is approved, the Partner is required to reserve the corresponding amount of funds on the cardholder’s account.

Special cases of authorization include requests with reference to a previously approved transaction.

Authorization advice

Authorization advice represents a notification for an authorization that has already been decided upon (approved/declined), either by the acquirer or by the payment scheme.

Authorization advice is marked with advice = true and contains the response code provided.

In the case of an approval, the Partner must proceed to reserve the corresponding amount of funds on the cardholder’s account as per normal authorization requests.

Preauthorization

Preauthorizations are special cases of authorizations marked with preauthorization = true. Preauthorizations serve the purpose of reserving funds on behalf of a merchant for longer periods of time, examples include hotel reservations and car hiring.

Partners are required to handle preauthorizations as normal authorization requests, providing the appropriate response and reserving account funds when applicable.

Clearing

Clearing is the process of sending transaction information in a file following an authorization, where applicable. The partner is responsible for applying funds (credit/debit) to the cardholder’s account.

Clearing file

On receipt of the clearing file the Partner is required to post the cardholder’s account; credit or debit the specified amount as indicated by each financial message row. For transaction types that require prior authorization, the corresponding authorizationId is provided to facilitate the release of funds, while for transactions that only appear in Clearing, the partner should only post the accounts.

Note: The clearing file may contain financial presentments for transactions that have not been matched to authorizations (authorizationId = null). As a result, for some debit transactions, cardholder’s may notice both an actual charge and a reserve of funds, for short time intervals.

Funds release policy

The presentment of a transaction should appear in clearing within 13 days of the corresponding authorization, while for preauthorizations the period is adjusted to 31 days.

Partners are required to maintain the funds reserved for the above mentioned time frame. After this period, and given that the transaction has not appeared in Clearing, the authorizations are considered to have expired. The Partner should then release the corresponding reservations, making the funds available to the cardholder’s account.

Request Content-Types: application/json
Response Content-Types: application/json

Authentication

Basic authentication

type
basic

OAuth2

type
oauth2
tokenUrl
flow
application
scopes
issuing_api

Paths

Retrieve embossing requests

GET /embossingrequest
cardId: string
in query

(no description)

dateFrom: string (date-time)
in query

(no description)

dateTo: string (date-time)
in query

(no description)

200 OK

Status 200

Response Content-Types: application/json
Response Example (200 OK)
{
 "cardId": "D0E81396-028F-42E7-9158-8F660DF13935",
 "cardToken": "13A6AFA4C301F8DA2AAA5557F44E3C4BFDB26F66",
 "referenceNumber": "0123456789",
 "trackingNumber": "112233445566",
 "maskedNumber": "537489XXXXXX7968",
 "embossName": "string",
 "errorCode": "number",
 "errorText": "string",
 "expiryYear": "integer",
 "expiryMonth": "integer",
 "Sent": "string (date-time)",
 "eventId": "integer"
}

Create a new embossing request

POST /embossingrequest

Issues a new card

Request Content-Types: application/json
Request Example
[
 {
   "sequenceNumber": 1,
   "productId": 90,
   "lastName": "bar",
   "firstName": "foo",
   "street": "Kokkinaki",
   "streetNumber": "13",
   "city": "Athens",
   "postal": "11423",
   "countryCode": "GR",
   "pin": "1234"
 }
]

The request has succeeded. Returns an array of the successfully processed cards, pending embossing.

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Response Example (200 OK)
[
 {
   "sequenceNumber": 1,
   "cardId": "D0E81396-028F-42E7-9158-8F660DF13935",
   "cardToken": "13A6AFA4C301F8DA2AAA5557F44E3C4BFDB26F66",
   "referenceNumber": "0123456789",
   "trackingNumber": "112233445566",
   "maskedNumber": "537489XXXXXX7968",
   "embossName": "string",
   "errorCode": "number",
   "errorText": "string",
   "expiryYear": "integer",
   "expiryMonth": "integer",
   "sent": "string (date-time)",
   "eventId": "integer"
 }
]

Activate card

POST /cards/{cardId}:activate

Activates an issued card by setting its statusId to 1 (Active) and associates the card to a Customer's account.

Each customer may have a single linked card, thus the activation of a new card for the same customer will fail.

In order to activate a new card, a prior call to SetCardStatus is required, to deactivate the existing linked card.

A card is considered deactivated when its statusId is one of the following :

  • 3 - Cancelled
  • 4 - Lost
  • 5 - Stolen
activateCardRequest: activateCardRequest
cardId: string
in path

unique identifier of the card created (Guid)

Request Example
{
 "activateCardRequest": {
   "email": "string",
   "mobile": "number",
   "firstName": "string",
   "lastName": "string",
   "vatNumber": "string",
   "cardholderId": "string",
   "countryCode": "string",
   "cvc": "string"
 }
}
200 OK

The card has been activated

400 Bad Request

The server cannot process the request due to an apparent client error

403 Forbidden

The server understood the request but refuses to authorize it

404 Not Found

The target resource could not be found

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Retrieve card information

GET /cards/{cardId}
cardId: string
in path

(Guid)

200 OK

The request has succeeded

type
object
404 Not Found

The target resource could not be found

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Response Example (200 OK)
{
 "statusId": 1,
 "productId": 90,
 "customerId": "string",
 "maskedNumber": "string",
 "expiryMonth": "number",
 "expiryYear": "number",
 "embossName": "string",
 "limits": [
   {
     "limitValue": "number (double)",
     "limitThreshold": "number (double)",
     "dateRangeTypeId": "integer",
     "transactionTypeId": "string"
   }
 ],
 "amounts": [
   {
     "amount": "number",
     "transactionTypeId": "string",
     "dateRangeTypeId": "string"
   }
 ],
 "securityRules": {
   "disableNonDomesticTransactions": "boolean",
   "disableMSR": "boolean",
   "disableContactless": "boolean",
   "disableATMWithdrawals": "boolean",
   "disablePOSWithdrawals": "boolean",
   "disableCardPresent": "boolean",
   "disableEcommerce": "boolean",
   "mccGroupId": "integer"
 },
 "currencyCode": "string"
}

Delete a card

DELETE /cards/{cardId}

Deletes an issued card and removes the related embossing request. A card can be deleted only when the embossing request has not been forwarded to the printing vendor.

cardId: string
in path

(Guid)

200 OK

Status 200

Set card status

PATCH /cards/{cardId}/status/{statusId}

Modifies an issued card's status in accordance with the transition rules found here.

cardId: string
in path

(Guid)

statusId: string
in path

See Appendices > Card status

200 OK

The request has succeeded

400 Bad Request

The server cannot process the request due to an apparent client error

403 Forbidden

The server understood the request but refuses to authorize it

404 Not Found

The server encountered an unexpected condition that prevented it from fulfilling the request

Retrieve authorization details (using date range)

GET /cards/authorizations?cardToken={cardToken}&dateFrom={dateFrom}&dateTo={dateTo}
cardToken: string
in path

(no description)

dateFrom: string
in path

(no description)

dateTo: string
in path

(no description)

The request has succeeded

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Response example (200 OK)
[
 {
   "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
   "accountTypeId": "string",
   "amountActual": 10.21,
   "currencyCode": "978",
   "transactionTypeId": "00",
   "created": "2018-04-20 12:36:54.4960+03:00",
   "advice": false,
   "preauthorization": "boolean",
   "parentAuthorizationId": "string",
   "cardAcceptorId": "123456789123456",
   "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
   "responseCode": "00",
   "cardAcceptorBusinessCode": "integer",
   "amountTransaction": "integer",
   "currencyCodeTransaction": "string",
   "amountTransactionFee": "integer"
 }
]

Retrieve authorization details (using the authorization Id)

GET /cards/authorizations/{authorizationId}
authorizationId: string
in path

(no description)

The request has succeeded

404 Not Found

The target resource could not be found

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Response Example (200 OK)
{
 "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
 "accountTypeId": "string",
 "amountActual": 10.21,
 "currencyCode": "978",
 "transactionTypeId": "00",
 "created": "2018-04-20 12:36:54.4960+03:00",
 "advice": false,
 "preauthorization": "boolean",
 "parentAuthorizationId": "string",
 "cardAcceptorId": "123456789123456",
 "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
 "responseCode": "00",
 "cardAcceptorBusinessCode": "integer",
 "amountTransaction": "integer",
 "currencyCodeTransaction": "string",
 "amountTransactionFee": "integer"
}

PIN Advice

GET /cards/{cardId}/pin

Retrieves the Personal Identification Number (PIN) for a card

cardId: string
in path

(no description)

200 OK

The request has succeeded

type
string
404 Not Found

The target resource could not be found

500 Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request

Response Example (200 OK)
"string"

Set a card's PIN

PATCH /cards/{cardId}/pin
pin: string

Up to 4 digits

cardId: string
in path

(no description)

Request Example
{
 "pin": "string"
}
200 OK

Status 200

Create a Limit

POST /cards/{cardId}/spendinglimits
limit
cardId: string
in path

(no description)

Request Example
[
 {
   "limitValue": "number (double)",
   "limitThreshold": "number (double)",
   "dateRangeTypeId": "integer",
   "transactionTypeId": "string"
 }
]
200 OK

The request has succeeded

400 Bad Request

The server cannot process the request due to an apparent client error

403 Forbidden

The server understood the request but refuses to authorize it

Delete a Limit

DELETE /cards/{cardId}/spendinglimits
transactionTypeId: string
in query

(no description)

dateRangeTypeId: number
in query

(no description)

cardId: string
in path

(no description)

200 OK

The request has succeeded

400 Bad Request

The server cannot process the request due to an apparent client error

403 Forbidden

The server understood the request but refuses to authorize it

404 Not Found

The server encountered an unexpected condition that prevented it from fulfilling the request

Update a Limit

PATCH /cards/{cardId}/spendinglimits
limitValue: number
limitThreshold: number
transactionTypeId: string
in query

(no description)

dateRangeTypeId: number
in query

(no description)

cardId: string
in path

(no description)

Request Example
{
 "limitValue": "number",
 "limitThreshold": "number"
}
200 OK

The request has succeeded

400 Bad Request

The server cannot process the request due to an apparent client error

403 Forbidden

The server understood the request but refuses to authorize it

404 Not Found

The server encountered an unexpected condition that prevented it from fulfilling the request

Add security rules to a card

POST /cards/{cardId}/securityrules

undefined

cardId: string
in path

(no description)

Request Example
{
 "disableNonDomesticTransactions": "boolean",
 "disableMSR": "boolean",
 "disableContactless": "boolean",
 "disableATMWithdrawals": "boolean",
 "disablePOSWithdrawals": "boolean",
 "disableCardPresent": "boolean",
 "disableEcommerce": "boolean",
 "mccGroupId": "integer"
}
200 OK

Status 200

Update a card's security rules

PATCH /cards/{cardId}/securityrules

undefined

cardId: string
in path

(no description)

Request Example
{
 "disableNonDomesticTransactions": "boolean",
 "disableMSR": "boolean",
 "disableContactless": "boolean",
 "disableATMWithdrawals": "boolean",
 "disablePOSWithdrawals": "boolean",
 "disableCardPresent": "boolean",
 "disableEcommerce": "boolean",
 "mccGroupId": "integer"
}
200 OK

Status 200

Request Authorization

POST /(TBD)/:authorize

A financial Authorization request to be approved or declined by the Partner.

Request Example
{
 "accountTypeId": "string",
 "cardToken": "string",
 "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
 "amountActual": 10.21,
 "currencyCode": "978",
 "transactionTypeId": "00",
 "cardAcceptorBusinessCode": "integer",
 "cardAcceptorId": "123456789123456",
 "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
 "preauthorization": "boolean",
 "transmissionDateTime": "2018-06-21T14:54:34+00:00",
 "advice": {
   "responseCode": "00 = Approved"
 },
 "amountTransaction": "integer",
 "currencyCodeTransaction": "string",
 "amountTransactionFee": "string"
}

The request has succeeded

500 Internal Server Error

Status 500

Response Example (200 OK)
{
 "responseCode": "00",
 "amountAvailable": 30,
 "currencyCode": "978"
}

Request Authorization (referencing previous authorization)

PATCH /(TBD)/{parentAuthorizationId}

This endpoint is used to modify/adjust the amount of a previously approved authorization and is applicable to all transaction types.

The field actualAmount identifies the new amount for the initial authorization.

The partner is required to adjust the reserved funds on the account accordingly.

In the case of actualAmount = 0, the request indicates a full reversal of the initial authorization.

The initial and reversal authorizations will not appear in clearing.

parentAuthorizationId: string
in path

(no description)

Request Example
{
 "accountTypeId": "string",
 "cardToken": "string",
 "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
 "amountActual": 10.21,
 "currencyCode": "978",
 "transactionTypeId": "00",
 "cardAcceptorBusinessCode": "integer",
 "cardAcceptorId": "123456789123456",
 "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
 "preauthorization": "boolean",
 "transmissionDateTime": "2018-06-21T14:54:34+00:00",
 "advice": {
   "responseCode": "00 = Approved"
 },
 "amountTransaction": "integer",
 "currencyCodeTransaction": "string",
 "amountTransactionFee": "string"
}

Status 200

500 Internal Server Error

Status 500

Response Example (200 OK)
{
 "responseCode": "00",
 "amountAvailable": 30,
 "currencyCode": "978"
}

Schema Definitions

embossingRequest: object

The address details provided in the corresponding fields will be used by the postal service to deliver the physical card.

sequenceNumber: integer

A unique within the request’s context, number

productId: number

identifies the dedicated white-label product type to be created

lastName: string

the cardholder’s last name

firstName: string

the cardholder’s first name

street: string
streetNumber: string
city: string
postal: string
countryCode: string

ISO 3166 Two letter country code ( https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)

Shipping is currently supported only for: Austria, Belgium, Bulgarian, Croatia, CzechRepublic, Cyprus, Denmark, Estonia, Finland, France, Germany, GreatBritain, Greek, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Iceland, Norway

pin: string (4 chars)

The Personal Identification Number. Comprised of 4 digits.

Example
{
 "sequenceNumber": 1,
 "productId": 90,
 "lastName": "bar",
 "firstName": "foo",
 "street": "Kokkinaki",
 "streetNumber": "13",
 "city": "Athens",
 "postal": "11423",
 "countryCode": "GR",
 "pin": "1234"
}

embossingResponse: object

sequenceNumber: integer

A unique within the request's context, number

cardId: string

Guid

cardToken: string
referenceNumber: string
trackingNumber: string
maskedNumber: string
embossName: string

Cardholder's name as will be printed on the card

errorCode: number
errorText: string
expiryYear: integer

The card's expiration year (2 digits)

expiryMonth: integer

The card's expiration month

sent: string (date-time)

The date and time, the embossing request was sent to the partner for printing

eventId: integer
Example
{
 "sequenceNumber": 1,
 "cardId": "D0E81396-028F-42E7-9158-8F660DF13935",
 "cardToken": "13A6AFA4C301F8DA2AAA5557F44E3C4BFDB26F66",
 "referenceNumber": "0123456789",
 "trackingNumber": "112233445566",
 "maskedNumber": "537489XXXXXX7968",
 "embossName": "string",
 "errorCode": "number",
 "errorText": "string",
 "expiryYear": "integer",
 "expiryMonth": "integer",
 "sent": "string (date-time)",
 "eventId": "integer"
}

account: array

object
accountTypeId: accountTypeId
Example
[
 {
   "accountTypeId": "string"
 }
]

accountTypeId: string

Describes the available financial account types See Appendices > Account Types

string 00, 10, 20, 30 00

authorizationDetail: object

authorizationId: string

unique identifier of the authorization request (Guid)

accountTypeId: accountTypeId
amountActual: number

indicates the actual amount of funds requested (decimal)

currencyCode: string

indicates the cardholder's account currency (defined by ISO 4217)

transactionTypeId: string

indicates the type of the requested transaction See Appendices > Transaction Types

created: string (date-time)

the datetime offset of the authorization

advice: boolean

identifies an advice request

preauthorization: boolean false

indicates a preauthorization request

parentAuthorizationId: string null

reference to the original authorization, in the case of a reversal request (Guid)

cardAcceptorId: string

identifies the card acceptor code at the point of service

cardAcceptorNameLocation: string

identifies the card acceptor's name and location at the point of service

responseCode: string (2 chars)

the Issuer-generated ISO response code

cardAcceptorBusinessCode: cardAcceptorBusinessCode
amountTransaction: integer

The amount of funds, in the currency's minor unit of measurement, the cardholder requested in the local currency of the acquirer or source location of the transaction.

currencyCodeTransaction: string

The local currency of the acquirer or source location of the transaction.

amountTransactionFee: integer

The fee charged (for example, by the acquirer) for transaction activity in the currency of currencyCodeTransaction

Example
{
 "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
 "accountTypeId": "string",
 "amountActual": 10.21,
 "currencyCode": "978",
 "transactionTypeId": "00",
 "created": "2018-04-20 12:36:54.4960+03:00",
 "advice": false,
 "preauthorization": "boolean",
 "parentAuthorizationId": "string",
 "cardAcceptorId": "123456789123456",
 "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
 "responseCode": "00",
 "cardAcceptorBusinessCode": "integer",
 "amountTransaction": "integer",
 "currencyCodeTransaction": "string",
 "amountTransactionFee": "integer"
}

authorizationRequest: object

Describes the body of an authorization request

accountTypeId: accountTypeId
cardToken: string
authorizationId: string

A unique identifier of the Authorization request (Guid).

amountActual: number

indicates the requested funds amount. (decimal)

currencyCode: string (3 chars)

Indicates the currency of amountActual. A three digit currency code should be used, as defined in ISO 4217 https://en.wikipedia.org/wiki/ISO_4217

transactionTypeId: string (2 chars)

indicates the type of the requested transaction

cardAcceptorBusinessCode: cardAcceptorBusinessCode
cardAcceptorId: string (up to 15 chars)

identifies the card acceptor code at the point of service

cardAcceptorNameLocation: string

indicates the card acceptor's name and location at the point of service

preauthorization: boolean false

Indicates whether the request is a Preauthorization Request.

transmissionDateTime: string (date-time)

Indicates the date time that the transaction entered the interchange network. Datetime is expressed according to the ISO-8601 format.

advice: object

When not null, indicates whether the request is an Authorization Advice

responseCode: string

Indicates the response code as decided by the payment scheme

amountTransaction: integer

The amount of funds, in the currency’s minor unit of measurement, the cardholder requested in the local currency of the acquirer or source location of the transaction.

currencyCodeTransaction: string

The local currency of the acquirer or source location of the transaction.

amountTransactionFee: string

The fee charged (for example, by the acquirer) for transaction activity in the currency of currencyCodeTransaction

Example
{
 "accountTypeId": "string",
 "cardToken": "string",
 "authorizationId": "c7ef2f1c-6a66-423f-a884-c049d6f5fe16",
 "amountActual": 10.21,
 "currencyCode": "978",
 "transactionTypeId": "00",
 "cardAcceptorBusinessCode": "integer",
 "cardAcceptorId": "123456789123456",
 "cardAcceptorNameLocation": "VIVA PAYMENT SERVICES SA ATHENS GR",
 "preauthorization": "boolean",
 "transmissionDateTime": "2018-06-21T14:54:34+00:00",
 "advice": {
   "responseCode": "00 = Approved"
 },
 "amountTransaction": "integer",
 "currencyCodeTransaction": "string",
 "amountTransactionFee": "string"
}

authorizationResponse: object

Defines the data required in the authorization response by the Partner

responseCode: string (2 chars)

the partner initiated authorization response (accept/decline)

amountAvailable: number

the available funds of the account (decimal)

currencyCode: string (3 chars)

the currency code of amountAvailable (as defined by ISO)

Example
{
 "responseCode": "00",
 "amountAvailable": 30,
 "currencyCode": "978"
}

cardAcceptorBusinessCode: integer

Classifies the type of business applicable to the card acceptor as described in Mastercard’s Quick reference booklet

Example
"integer"

activateCardRequest: object

email: string

The customer's email

mobile: number

The customer's mobile phone number. Used for cardholder authentication purposes (3D Secure).

firstName: string

The customer's first name.

lastName: string

The customer's last name.

vatNumber: string

The customer's tax identification number (unique).

Required for GR country code.

cardholderId: string (up to 255 chars)

Uniquely identifies a customer within the Partner's system.

countryCode: string

Account country code.

ISO 3166 Two letter country code ( https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)

cvc: string

The Card verification code

Example
{
 "email": "string",
 "mobile": "number",
 "firstName": "string",
 "lastName": "string",
 "vatNumber": "string",
 "cardholderId": "string",
 "countryCode": "string",
 "cvc": "string"
}

limit: object

limitValue: number (double)

Actual value for blocking card's transactions

limitThreshold: number (double)

The limit that when reached, will trigger an event (webhook), notifying the Partner about an imminent card block.

dateRangeTypeId: integer
transactionTypeId: string

Supported transaction types: Purchase "00", Withdrawal "01", Cash Disbursement "17", Purchase With CashBack "09"

More on Transaction types

Example
{
 "limitValue": "number (double)",
 "limitThreshold": "number (double)",
 "dateRangeTypeId": "integer",
 "transactionTypeId": "string"
}

updateLimitOptions: object

limitValue: number (double)
limitThreshold: number (double)
Example
{
 "limitValue": "number (double)",
 "limitThreshold": "number (double)"
}

securityRules: object

disableNonDomesticTransactions: boolean
disableMSR: boolean
disableContactless: boolean
disableATMWithdrawals: boolean
disablePOSWithdrawals: boolean
disableCardPresent: boolean
disableEcommerce: boolean
mccGroupId: integer
Example
{
 "disableNonDomesticTransactions": "boolean",
 "disableMSR": "boolean",
 "disableContactless": "boolean",
 "disableATMWithdrawals": "boolean",
 "disablePOSWithdrawals": "boolean",
 "disableCardPresent": "boolean",
 "disableEcommerce": "boolean",
 "mccGroupId": "integer"
}

embossingInfo: object

cardId: string

Guid

cardToken: string
referenceNumber: string
trackingNumber: string
maskedNumber: string
embossName: string

Cardholder's name as will be printed on the card

errorCode: number
errorText: string
expiryYear: integer

The card's expiration year (2 digits)

expiryMonth: integer

The card's expiration month

Sent: string (date-time)
eventId: integer
Example
{
 "cardId": "D0E81396-028F-42E7-9158-8F660DF13935",
 "cardToken": "13A6AFA4C301F8DA2AAA5557F44E3C4BFDB26F66",
 "referenceNumber": "0123456789",
 "trackingNumber": "112233445566",
 "maskedNumber": "537489XXXXXX7968",
 "embossName": "string",
 "errorCode": "number",
 "errorText": "string",
 "expiryYear": "integer",
 "expiryMonth": "integer",
 "Sent": "string (date-time)",
 "eventId": "integer"
}

AmountInfo: object

amount: number
transactionTypeId: string
dateRangeTypeId: string
Example
{
 "amount": "number",
 "transactionTypeId": "string",
 "dateRangeTypeId": "string"
}