Credit Statements
A credit statement contains information about transactions that occur within a billing cycle for a credit account. This includes debits, credits, fees, and details like the credit limit. Credit statement files do not contain Personally Identifiable Information (PII).
Galileo delivers a credit statement file following the close of your cardholders' billing cycle. For example, if the billing cycle closes the 15th of the month, Galileo generates the credit statement file the next calendar day and delivers it on the 17th.
You receive one main credit statement file for each billing cycle close date, so the number of files you receive during the period depends on your billing cycle configuration. If you have one billing cycle date configured for all accounts, you will receive one credit statement file. If you have monthly or weekly billing cycle configuration, you will receive multiple credit statement files within two days of the respective billing cycle close dates. See Configuring billing cycles for details.
Accessing the credit statement file
Galileo uses Secure File Transfer Protocol (SFTP) to deliver the credit statement file. You can arrange to retrieve the files from Galileo's SFTP server, or Galileo can push the files to your SFTP server. Galileo secures connections using SSH keys.
You must provide Galileo with the following information to deliver the SFTP file:
- SFTP hostname/IP — The address of the SFTP server where you will receive the file
- Public PGP key — Used to encrypt the statements files. Ensures the file is only accessible to you.
- Accepted encryption formats: PGP (Pretty Good Privacy) and GPG (GNU Privacy Guard)
Credit statement file
Galileo uploads a compressed credit statement file. This file contains a set of individual JSON files, one per primary credit account, collectively called the account statement file.
The tgz (.tar.gz) filename for the credit statement file is {prod_id]_{schema_name}_{cycle_close_date}_batch_{batch_num}.tgz.
The date is formatted as YYYY_MM_DD and represents the cycle close date. The filename also includes a batch number, which is five digits from 00000–99999.
Example filename: 9999_Galileo_2025-12-17_batch_00000.tgz.
The following table shows an estimation of the file size depending on the number of accounts in your program.
| Number of accounts | Uncompressed size | File size* |
|---|---|---|
| 10,000 | 200 MB | 40 MB |
| 100,000 | 2 GB | 400 MB |
| 1,000,000 | 20 GB | 4 GB |
*Estimated 5:1 ratio
Account statement file
The JSON filename for the account statement files is formatted {prod_id]_{schema_name}_{cycle_close_date}_{payment_reference_number}.json.
The PRN is associated with the primary account. For example, if the PRN of the primary account is 112233 the individual filename is 9999_Galileo_2025-12-17_112233.json.
Field details
The following are the fields contained in the account statement file.
accounts object
accounts objectThe accounts object contains all the accounts in a credit statement file. This always includes a primary account. This also includes authorized users' accounts linked to this primary account.
| Field name | Data type | Description |
|---|---|---|
account_type | string | Type of account to which the transactions belong to. The statement file groups transactions by account type: primary or authorized user. Example: “primary” |
pmt_ref_no | string | 12-digit Galileo-generated account identifier that you can provide to the account holder as their account number. Example: "999101310817" |
transactions | object | Contains information about all transactions for the account in the billing cycle. See the table below for details of each field. |
transactions object
transactions objectThe transactions object contains information about all transactions for the account in the billing cycle. These fields are nested in the transactions object for each transaction.
| Field name | Data type | Description |
|---|---|---|
act_type | string | See <a href"=ref:api-reference-activity-type" target="_blank">Activity Type for possible values. Example: "VI" |
amt | decimal | Transaction amount. Can be a positive or negative number, depending on the type of transaction. Example: -482.79 |
card_id | string | Galileo-generated identifier for a card. Maps to the PAN. Example: "39745" |
details | string | Description provided by the merchant about the transaction. Example: "E-Check" |
pmt_ref_no | string | Payment reference number (PRN) of the account the transaction is associated with. Example: "999101310817" |
post_ts | datetime | The date the transaction settled in Galileo system time. Format: YYYY-MM-DDThh:mm:ss. Example: "2025-11-30 01:00:31.000" |
tag | string | Additional tag used to group transactions. Possible values: Payments/Credits, Refunds/Reversals, Disputes, Fees, Purchases, Cash Advance |
trans_id | integer | Unique identifier for a transaction. Example: "46691" |
local_amt* | decimal | Amount in the currency at the point of sale. This amount does not include upcharges or fees (DE004). Example: 1245.20 |
local_curr_code* | string | Currency code for local_amt (DE049). Example: “124” |
billing_amt* | decimal | Billing amount in the currency of the account (DE006). Example: 482.79 |
billing_curr_code* | string | Currency code for billing_amt (DE051). Example: 840 |
settle_amt* | decimal | Transaction amount in the settlement currency (DE005). Example: 482.79 |
settle_curr_code* | string | Currency code for settle_amt (DE050). Example: 840 |
mcc | string | Category code for the merchant that initiated the transaction (DE018). Example: “5172” |
trans_ts | datetime | Authorization timestamp. Format: YYYY-MM-DDThh:mm:ss. Example: "2025-11-29 01:00:15.000" |
*Field is only included when the transaction involves a currency conversion.
The following fields are also included in the account statement file following the transactions object.
| Field name | Data type | Description |
|---|---|---|
amount_paid | decimal | Amount paid towards the reported billing cycle. Example: 15.00 |
amount_past_due | decimal | Amount past due. This can include amounts from previous billing cycles. Example: 10.00 |
available_credit | decimal | Credit amount currently available. Example: 150.00 |
credit_limit | decimal | Credit limit amount at the billing cycle close date. Example: 350.00 |
current_balance | decimal | Total amount of all transactions and fees (minus payments/credits). This value is the same amount as reported in minimum_payment. Example: 25.00 |
current_cycle_fees | decimal | Total fees applied within the reported billing cycle. Example: 10.00 |
days_in_billing_cycle | integer | Number of days in the reported billing cycle. Example: 30 |
due_date | date | Due date for the reported billing cycle. Example: "2025-12-04" |
start_date | date | Date on which the billing cycle was started. Example: "2025-11-01" |
end_date | date | Date on which the billing cycle was closed. Example: "2025-11-30" |
fees_year_to_date | decimal | Sum of all the fees charged to the primary and authorized user accounts year to date. Example: 200.00 |
minimum_payment | decimal | Minimum amount due for the cycle. This value is the same amount as reported in current_balance. Example: 25.00 |
primary_pmt_ref_no | string | Payment reference number (PRN) of the primary account, this is a unique account identifier generated by Galileo. Example: 0.00 |
previous_amount_paid | decimal | Amount paid from the previous generated statement. If no statement, this will be 0. Example: 0.00 |
previous_amount_past_due | decimal | Amount past due from the previous generated statement. If no statement, the returned as 0. Example: 0.00 |
previous_balance | decimal | Balance from the previous generated statement. If no statement, the returned as 0. Example: 0.00 |
Example
The following shows an example account statement file.
{
"accounts": [
{
"account_type": "primary",
"pmt_ref_no": "999101310817",
"transactions": [
{
"act_type": "FE",
"amt": 39,
"card_id": "39745",
"details": "Late Fee",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-01 01:00:32.000",
"tag": "Fees",
"trans_id": "56690"
},
{
"act_type": "AD",
"amt": 10,
"card_id": "39745",
"details": "Transfer Passthrough #gMfw",
"mcc": "389957",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-02 14:22:18.000",
"tag": "",
"trans_id": "50308"
},
{
"act_type": "FE",
"amt": 29,
"card_id": "39745",
"details": "Late Fee",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-12 01:00:31.000",
"tag": "Fees",
"trans_id": "55923"
},
{
"act_type": "PM",
"amt": -65,
"card_id": "39745",
"details": "E-Check",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-16 00:00:04.000",
"tag": "Payments/Credits",
"trans_id": "50441"
},
{
"act_type": "AD",
"amt": 5,
"card_id": "39745",
"details": "Transfer Passthrough #mVld",
"mcc": "390004",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-16 14:30:10.000",
"tag": "",
"trans_id": "50311"
},
{
"act_type": "AD",
"amt": 500,
"card_id": "39745",
"details": "GCash Transfer - ApproveMe Lastq",
"mcc": "289149",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-17 17:14:06.000",
"tag": "",
"trans_id": "49578"
},
{
"act_type": "AD",
"amt": 10,
"card_id": "39745",
"details": "Bank Transfer - ApproveMe Lastq",
"mcc": "389795",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-20 06:10:29.000",
"tag": "",
"trans_id": "50279"
},
{
"act_type": "AD",
"amt": 1,
"card_id": "39745",
"details": "Bank Transfer - ManualReviewMe Test",
"mcc": "403116",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-23 08:10:04.000",
"tag": "",
"trans_id": "51219"
},
{
"act_type": "AD",
"amt": -10,
"card_id": "39745",
"details": "Bank Refund - ApproveMe Lastq",
"mcc": "389796",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-24 06:10:34.000",
"tag": "",
"trans_id": "50280"
},
{
"act_type": "FE",
"amt": 39,
"card_id": "39745",
"details": "Late Fee",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-24 01:00:31.000",
"tag": "Fees",
"trans_id": "57559"
},
{
"act_type": "AD",
"amt": 12,
"card_id": "39745",
"details": "Bank Transfer - ApproveMe Last",
"mcc": "389804",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-24 06:47:30.000",
"tag": "",
"trans_id": "50281"
},
{
"act_type": "AD",
"amt": 10,
"card_id": "39745",
"details": "Bank Transfer - ApproveMe Last",
"mcc": "389989",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-24 14:29:05.000",
"tag": "",
"trans_id": "50310"
},
{
"act_type": "PM",
"amt": -10,
"card_id": "39745",
"details": "Transfer Passthrough #gMfw",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-24 14:22:18.000",
"tag": "Payments/Credits",
"trans_id": "50309"
},
{
"act_type": "AD",
"amt": 50,
"card_id": "39745",
"details": "GCash Transfer - ManualReviewMe Last",
"mcc": "289154",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-26 17:16:35.000",
"tag": "",
"trans_id": "49579"
},
{
"act_type": "PM",
"amt": -5,
"card_id": "39745",
"details": "Transfer Passthrough #mVld",
"pmt_ref_no": "999101310817",
"post_ts": "2025-11-26 14:30:09.000",
"tag": "Payments/Credits",
"trans_id": "50312"
}
]
}
],
"amount_paid": 0,
"amount_past_due": 0,
"credit_limit": 0,
"current_balance": 0,
"current_cycle_fees": 0,
"days_in_billing_cycle": 30,
"due_date": "2025-12-04",
"end_date": "2025-11-30",
"fees_year_to_date": 0,
"minimum_payment": 0,
"primary_pmt_ref_no": "999101310817",
"start_date": "2025-11-03"
}
Updated 15 days ago
