Data Access & Monitoring
Accessing merchant transaction data
Once live, you have access to anonymized, aggregated transaction data. This surface is read-only.
Daily anonymized transaction manifest. A daily snapshot of merchant transaction data, scoped to merchants in your approved segment. The endpoint returns a list of signed URLs pointing to .parquet files. Each parquet file contains one row per transaction with the following columns:
| Column | Description |
|---|---|
| id | Unique transaction ID |
| merchant_id | Merchant account ID -- see note below |
| payment_amount | Settled transaction amount (centavos) |
| refund_amount | Refund amount applied against this transaction (centavos) |
| payment_status | Final status of the transaction |
| declined | Boolean flag indicating whether the transaction was declined |
| response | Raw response code or message returned by the payment processor or issuing bank |
| paid_at | Timestamp when the payment was successfully captured. |
| created_at | Timestamp when the transaction record was first created in the system |
| available_at | Timestamp when the funds from this transaction become available for settlement to the merchant |
| source_type | Payment method used |
| updated_at | Timestamp of the last update to this transaction record |
merchant_id is the merchant's PayMongo account ID. This is the same value you supply as id when inviting accounts to an offer. Use merchant_id from your manifest analysis to identify and target specific merchants in the origination step.
Get Anonymized Transaction API Reference
Replace {start_date} and {end_date} with an ISO date (e.g. 2026-04-20 and 2026-04-21). You can request 6 months of historical data with maximum 7 days of date range.