Non-zero card balances report

Product version 3.91
Last edited January 2023

This report contains a list of all cards with an actual balance greater than zero. The purpose of this report is to keep track of cards with outstanding balances. It is generated daily and covers all cards issued on the previous day with a balance greater than zero.

Latest version: 3.13.0
File repository path: Non-Zero Card Balances/Daily
File name pattern: Non_Zero_Card_Balance_daily

Contains the name of the community to which a client belongs as set up in Nium.
The name of the client as set up in Nium.
A unique Nium reference of the card.
A friendly name for the card.
The client provides the external ID of the card.
Contains the first six and the last four digits of a card. This should not be used to match or map card numbers (multiple cards can share the same first six and last four digits). Card reference should be used instead. For example, 406742******8806.
The currency of the virtual card.
The card scheme of the virtual card.
The total amount loaded onto the card since the card issue date.
The total purchase settlement amount for the card since the card issue date.
The total refund settlement amount for the card since the card issue date.
The total amount deducted from the card since the card issue date.
The actual balance on the card.

Note: Only cards with a balance greater than zero are included.
Calculated as: financialBalance − availableBalance
The available spendable balance on the card.

Note: The available balance can be greater than the actual balance when a refund has been processed in the provider system and has not yet been received by Nium for processing.
The date when the card was issued.
customField1 to customField20
The client may choose to pass specific information relating to the transaction by attaching additional information in the custom fields. Custom information allows the client to reconcile card activity (payments and refunds). Custom field data is retrieved from the “cardInfo” parameter when creating a card using theIssueVirtualCard() API, or from the “additional details” form when creating a card in the Nium Portal. This information is passed as a name: value pairs. For example, custom fields may contain the following information:
Client Customer Identifier : John123
Client Customer Booking Identifier : Paris321
Client Travel Package Type Descriptor : LOWCOST
Client Travel Package Identifier : LC21
Client Company Subsidiary Descriptor : Spain

Note: In the Nium Portal, custom fields are referred to as additional details.
The latest date when the card had a balance greater than zero.

Note: this is the day of report generation minus one.