Fiserv deposits
GET /api/partner/merchants/{merchant_id}/deposits returns deposits for merchants processed on Fiserv Omaha (FSP and Retail) and Fiserv North, as well as TSYS. Before this change, a Fiserv merchant returned 404. meta.data_coverage is now tsys_and_fiserv on every deposits response (it was tsys_only).
What one deposit is
- Omaha (FSP and Retail): one ACH line, identified by its ACH trace.
reference_numberis the trace. - North: every funding line of one batch number on one report date: the card lines of a batch (one per card brand), the day’s non-batch fee lines, or one adjustment.
reference_numberis the batch number, and null for the non-batch fee entry.
Amounts are signed decimal dollars, split into card_deposits, fees, chargebacks and other, which sum to amount. A negative amount is a debit.
Dates, status and reconciliation
processing_dateis the report date Fiserv lists the deposit under.- Fiserv reports no funded date:
effective_onandeffective_throughare null andhas_unknown_effective_dateis true. cycleis alwaysOTHER.- Fiserv sends no control total to check the lines against, so
reconciledis false andstatusisunreconciled. For Fiserv this means “no control total yet”, not a failed check.
Detail and batches
The detail route lists the deposit’s lines. transaction_type is the component each line counts toward (DEPOSIT, FEES, CHARGEBACKS or OTHER), card_type is the North card program, and description is the Fiserv transaction code description. Bank routing and account numbers are never returned.
batch_count is 1 for a North card-deposit entry (its batch number) and 0 otherwise. related_batches is empty for Fiserv deposits, and /deposits/{deposit_id}/batches/{header_id} returns 404 for them.
History and corrections
Fiserv deposits start on 2025-06-18. Fiserv restates the most recent report dates for about a week; an entry keeps its deposit_id while its merchant, report date and trace are unchanged, so a corrected amount arrives on the same id.