SimpliFi
HomeContact Us
HomeContact Us
  1. Card
  • Introduction
  • SimpliFi Architecture
  • Webhooks
  • Auth
    • Login to generate JWT token
      POST
  • Card Program
    • Create Card Program
      POST
    • Get Card Program
      GET
    • Change Card Program Status
      PATCH
    • Link Funding Source to Card Program
      POST
    • Get Balance of Funding Source
      GET
    • Transfer funds from one Card Program to other
      POST
    • Raise Funding Document Upload
      POST
    • Raise Funding
      POST
    • Funding Source Statement
      GET
  • Funding Source
    • Create Rule Group on Funding Account
      POST
    • Update Rule Group on Funding Account
      PUT
    • Delete Rule Group on Funding Account
      DELETE
    • Get Rule Groups on Funding Account
      GET
    • Appply Rule Group on Funding Account
      POST
    • Remove Rule Group on Funding Account
      DELETE
  • Card
    • List all Cards
      GET
    • Create a Card
      POST
    • Get Card Details
      GET
    • Retrieve Balance on the Card
      GET
    • Activate a Card
      POST
    • Manage Card Status
      POST
    • Load a Card
      POST
    • Unload a Card
      POST
    • Renewal of the Card
      POST
    • Request a Physical Card
      POST
    • Get Card Statement
      GET
    • Apply rule group on card
      POST
    • Remove rule group on card
      DELETE
  • User
    • List all Users
    • Create a User
    • Upload Document
    • Retrieve a User
    • Update a User
    • Delete a User
  • Transaction
    • List All Transactions
  • Fee
    • Add fee configuration
    • Fetch fee config
    • Change the status of fee config
    • Add Fee event against card uuid in queue
    • Apply fee against card uuid present in queue
  • Webhook
    • Get all events
    • Create a webhook
    • Update a Webhook
    • Delete a Webhook
    • Updates the status of Webhook
  1. Card

Get Card Statement

GET
https://{{env}}-lb.simplifipay.com/v1/statement/card/{uuid}
CardTransaction
Get card statement based on date range.
Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request GET 'https://uat-lb.simplifipay.com/v1/statement/card/' \
--header 'requestUuid;'
Response Response Example
200 - Example 1
{
    "companyName": "SimpliFi",
    "statementDate": "2025-02-28",
    "maskPan": "************2737",
    "currency": "AED",
    "startDate": "2025-02-28 13:31:00",
    "endDate": "2025-02-28 13:31:00",
    "openingBalance": "6.95",
    "currentBalance": "6.95",
    "settledBalance": "6.95",
    "unsettledBalance": "6.95",
    "blockedAmount": "6.95",
    "totals": {
        "property1": 0,
        "property2": 0
    },
    "transactions": [
        {
            "transactionUuid": "f0888e10-43e3-4686-9c79-256633d79559",
            "transactionId": "6712309",
            "cardUuid": "95e8008f-c14b-4d4c-bc3b-6378be83618c",
            "maskedPan": "**********1234",
            "userName": "john.smith",
            "userEmail": "user@simplifipay.com",
            "userFullName": "John Smith",
            "transactionType": "Auth",
            "statusCode": "00",
            "statusCodeDescription": "Approved",
            "authResponse": "51",
            "mccCode": "6011",
            "merchantId": "F09089372443345",
            "merchantName": "GOOGLE *TEMPORARY HOLD",
            "transactionAmount": "100.54",
            "transactionCurrency": "AED",
            "transactionDate": "2025-02-28 13:31:00",
            "billAmount": "6.95",
            "billCurrency": "AED",
            "fxFee": "0.31",
            "feeOperationType": "PRIMARY_VIRTUAL_CARD_ISSUANCE",
            "feeOperationTypeDescription": "Virtual Card Issuance Fee",
            "comments": "string"
        }
    ]
}

Request

Authorization
JWT
Add the parameter
Authorization
to Headers
Example:
Authorization: ********************
or
Path Params
uuid
string 
required
This field contains a unique identifier of the card.
Query Params
startDate
string <date>
optional
start date of date-range
Example:
2025-02-28
endDate
string <date>
optional
end date date of date-range
Example:
2025-02-28
sortBy
string 
optional
sort statement column value
sortDir
string 
optional
sort direction
Header Params
requestUuid
string 
required
A unique id is required to be passed as part of the header whenever a SimpliFi API is called from your
system. This would help us in debugging in case of a discrepancy in the expected behavior of the API.
Example:
00d366f2-a6e9-4714-b172-02c4e58c29d8

Responses

🟢200OK
application/json
successful operation
Body
companyName
string 
required
Name of the company.
Example:
SimpliFi
statementDate
string <date>
required
The date on which the statement is created.
Example:
2025-02-28
maskPan
string 
required
The Masked PAN of card.
Example:
************2737
currency
string 
required
The currency of the card.
Example:
AED
startDate
string <date-time>
required
The start date of the date range.
Example:
2025-02-28 13:31:00
endDate
string <date-time>
required
The end date of the date range.
Example:
2025-02-28 13:31:00
openingBalance
number 
required
The opening balance of the card from the start date of the date range.
Example:
6.95
currentBalance
number 
required
The current balance of the card
Example:
6.95
settledBalance
number 
required
The settled balance of the card
Example:
6.95
unsettledBalance
number 
required
The unsettled balance of the card
Example:
6.95
blockedAmount
number 
required
The blocked amount of the card
Example:
6.95
totals
object 
required
Additional properties
number 
optional
transactions
array[object (TransactionResponseDetails) {23}] 
required
The array of transactions.
transactionUuid
string 
required
This is a unique identifier of the transaction.
Example:
f0888e10-43e3-4686-9c79-256633d79559
transactionId
string 
required
This is an identifier of the transaction.
Example:
6712309
cardUuid
string 
required
This is a unique identifier of the card.
Example:
95e8008f-c14b-4d4c-bc3b-6378be83618c
maskedPan
string 
required
Last 4 digits of the card.
Example:
**********1234
userName
string 
required
username of user.
Example:
john.smith
userEmail
string 
required
email of user.
Example:
user@simplifipay.com
userFullName
string 
required
full name of user.
Example:
John Smith
transactionType
enum<string> 
required
This is a transaction type
Allowed values:
AuthReversalSettlementRefundLoadUnloadFees
Example:
Auth
statusCode
string 
required
This field contains the status code of the transaction code received from processor.
Example:
00
statusCodeDescription
string 
optional
This field contains the status description of the transaction code received from processor.
Example:
Approved
authResponse
string 
required
This field contains the auth response value of the transaction received from processor.
Example:
51
mccCode
string 
optional
This field contains the Merchant Category Code. These, MCCs are four-digit numbers that
describe a merchant's primary business activity.
Example:
6011
merchantId
string 
optional
This field contains the registered merchant ID.
Example:
F09089372443345
merchantName
string 
optional
This field contains the registered merchant name.
Example:
GOOGLE *TEMPORARY HOLD
transactionAmount
number 
required
This field contains the total amount that was transacted.
Example:
100.54
transactionCurrency
string 
required
This field contains the currency in which the amount was transacted.
Example:
AED
transactionDate
string <date-time>
required
This field contains the date on which the transaction was carried out.
Example:
2025-02-28 13:31:00
billAmount
number 
optional
This field contains the billed amount.
Example:
6.95
billCurrency
string 
optional
This field contains the name of currency in which the amount is stored in the card
Example:
AED
fxFee
number 
optional
This field contains the FX fee amount.
Example:
0.31
feeOperationType
string 
optional
This field specifies the Fee Operation Type
Example:
PRIMARY_VIRTUAL_CARD_ISSUANCE
feeOperationTypeDescription
string 
optional
This field specifies the Fee Operation Type description
Example:
Virtual Card Issuance Fee
comments
string 
optional
Any notes for this transaction
🟠400Bad Request
🟠401Unauthorized
Modified at 2025-06-27 12:44:57
Previous
Request a Physical Card
Next
Apply rule group on card
Built with