Debit Overview
These APIs provide the ability to manage debit cards through various touchpoints.
Platform Support: DBE=Debit Enhanced EPOC
Features
-
Instant Access
Allow cardholders to view all cards issued on the home page of the digital or service portal after account authentication.
-
Mobile or Wallet Provisioning
Enable cardholders to provision cards to pay wallets and contactless payments.
-
Manage Card Controls
Empower cardholders to lock/unlock cards, set spend limits, and receive alerts.
Add Cardholder provides the ability to add a cardholder records to the Fiserv system based on an existing default template or card settings. Support is included for adding a primary account number (PAN) based on an existing PAN (copy) or a default template that the institution has established.
- Default template: Retrieve institution template that is used as a default when adding cards to the system. Some settings are defined according to card class, set common default values for new cardholder records.
- Card template: Retrieve rights and settings from an existing cardholder record.
- Add Card: Add a cardholder record to Fiserv system.
Controls and Alerts enable consumers to set preferences that work best for them so fraudulent activity can be quickly detected and prevented. Consumers can manage which transactions they want to receive real-time alerts for, and control when, where, and how their cards are used.
Platform Support: DBE=Debit Enhanced EPOC, CGW=Credit Gateway, CSL=Credit Select
Financial institutions can empower their customers with confidence when using their cards with the Card Control and Alerts (CCA) features.
- Usage: Set monthly/weekly purchase thresholds to restrict or inform consumers when transactions are over a specified dollar amount.
- Location-based: Create an alert or a control based on the cardholder mobile phone or the merchant location.
- Merchant: Monitor and manage specific purchases such as gas, hotel, travel, restaurants and groceries as well as in-store, e-commerce and ATM transactions.
- Card on/off control: Disable or enable a card from use when it is lost or stolen. If a card is disabled, no purchases or withdrawals are approved. If a card is enabled, transactions are approved.
The foundation of the integration is based on the cardholder account number being and presented in the digital application supplied to Fiserv in successfully return all associated cards tied to that bank account.
- The bank account number is the basis for integrating on mobile banking and online banking applications. It is not used for access to the card number (PAN), maintaining card data, or for card date entry due to compliance requirements associated with card number data—Example: PCI.
- The account numbers supplied must match the account number associated with the users cards maintained in the cardholder record and supplied via account processing in card management batch files, online messages, or web services.
FAQs
The Retrieve Card Details API service enables any financial institution or third part digital app provider that does not maintain a card number to gain access to the card number based on other commonly known information like account number and account type. Those entities can then use the retrieved card number to initiate other API’s to enable maintenance on the card—Example: Add a card using Cardholder Add API or Activate a card using Cardholder Activation API.
No. With Transaction Inquiry API only last 60 days of transaction details can be viewed. You can view up to 50 transactions at one time within the 60-day period. If you have more than 50 transactions within the given 60-day period, you can apply filters to limit the number of viewed transactions. Applying filters enables you to view a specific set of transactions—up to 50.
No, only one card can be added to the Fiserv debit system using the Cardholder Add API at any given time. In order to add multiple cards, the API has to be called multiple times to add each card.
No, the Card Activation API can be used to activate only one card at a time. If there are multiple cards issued to the customer, each card has to be activated separately through unique API call for every card.
Yes, absolutely. Infact one of the multiple benefits of using the Card Activation API is that it can be integrated across multiple systems enabling card activation through various channels like Mobile App, Online Banking and IVR.
Yes, the Card Activation API offers multiple operations and one can use it to get the activation status alone without performing the card activation. Please refer to the API documentation for more details on the API operations.
No, only card (PAN) number can be added using Cardholder Add API.
Yes. You can use the Card Activation API to reset the incorrect PIN attemps to zero after a cardholder has exhausted the PIN attempts by entering wrong PIN multiple times.
Yes, the Retrieve Card Details API will return a maximum of 30 card numbers in a single API call. If there are more card numbers associated to the account the SystemRecordIdentifier from the response will have to be passed to fetch the next set of card numbers in the new API request.
Yes.Transaction Inquiry API provides approval and denial reasons for every transaction in its response.
Alerts and controls take effect immediately.
No. The alerts are consolidated into one message.
Up to 15 cards can be registered to one account.
The APIs offers the ability to integrate financial institution applications into the Fiserv debit processing systems in real-time. Inquires and updates are made realtime thereby giving the financial instituion the flexibility to have their cardholders perform self servicing without the need to be on phone with customer representative.
Debit Processing APIs are RESTful message that enable Fiserv clients to address digital needs of their cardholders by providing an integrated platform that delivers superior customer experience.This will require coding to API specifications and testing in Sandbox prior to onboarding to live environment. The APIs can be interfaced to omnichannels like digital mobile app, online banking, customer service portal etc. Some prominent API's available include Cardholder Add, Cardholder Activation, Transaction Inquiry and many more to be launched.
Using the Cards: Control and Alerts API financial institutions can enable their cardholders to:
Turn credit cards on and off
Establish transaction controls and alerts for dollar amount limits, merchant categories and geographic locations
Create alerts when cards are used, approved or exceed a transaction limit
The Cardholder Add API enables the issuer to add cardholder records to the Fiserv debit processing system. The Cardholder Add API supports primary account number (PAN) addition based on an existing PAN (copy) or a default template that the financial institution has established.
The Card Activation API enables the issuer to activate their customer card instantaneously across multiple channels. Besides activating the card, the API can also be used to view specific details about the card such as when the card was activated or the number of attempts made to activate the card.The API also offers the flexibility to set a date by which a card has to be activated.
An alert is a notification sent to the cardholder to inform them about the use of their card. A control will restrict the use of a card and inform the cardholder.
The Transaction Inquiry API enables the Financial Institution to review all transactions (approvals and denials), including those that are denied at Fiserv and do not pass through the issuer system.
Anyone registered user many establish a card control. The most recent card control will take precedence over the previously set control.
Current support is only specific to debit cards.