# TabaPay Production Notes: October 2022

## Key Takeaways

- TabaPay launched its first Production Notes to highlight new platform features.
- Clients can now access Financial Institution issuer names with transactions.
- The notes detail how clients can leverage the latest TabaPay releases.

Welcome to the first edition of TabaPay’s Production Notes which goes into how clients can use functionality from our [most recent releases](https://developers.tabapay.com/changelog). Please [let us know what you like and don’t](mailto:marketing@tabapay.com?subject=release%20feedback) so we can continue to improve.

## Financial Institution name and more

Clients can now have the Financial Institution (FI) Issuer name associated with the card returned with the [CreateTransaction](https://developers.tabapay.com/reference/transactioncreate) and [QueryCard](https://developers.tabapay.com/reference/cardquery) APIs. The name of the FI/Issuer can be helpful for clients using account authentication services (Finicity, MX, Plaid, Yodlee and others) to triangulate a debit card to the user’s DDA (Direct Deposit Account).

Clients can also enhance UX when a user has multiple cards on file. Displaying the Issuer name and the last 4 digits of the card makes it easier for users to identify a card (e.g. use my Chase debit card) beyond the default card brand and the last 4 digits.

Clients can also query:

- If the Issuer is [Reg II or Durbin](https://www.federalreserve.gov/paymentsystems/regii-about.htm) regulated or exempt
- [Networks available for debit routing](/content/connections.html#networks/index.html)
- [AVS](https://developers.tabapay.com/reference/how-to-use-avs), [CVV2 verification](https://developers.tabapay.com/docs/cvv2-verification), and more

### Take a deep dive into the APIs here:

- [Query Card API reference](https://developers.tabapay.com/reference/cardquery)
- [Create Transaction API reference](https://developers.tabapay.com/reference/transactioncreate)

## Sub Clients

_As of this post, the_ [_SubClient API_](https://developers.tabapay.com/reference/createsubclient) _is only available for select customers, we anticipate a general release before the end of the year._

TabaPay ISO clients can use the [SubClient API](https://developers.tabapay.com/reference/createsubclient) to easily create and manage sub-clients. The API is designed for maximum flexibility from a basic sub-client framework to specifying fees and settlement options differently for each sub-client. This API includes sub-client names, types, contact information, MCC, settlement accounts, fees, and other attributes. ISOs can establish custom fees for sub-clients from monthly minimums to fees for payments and payouts across all rails. More detail on specific fees can be found here – [https://developers.tabapay.com/docs/fees-for-sub-clients-during-boarding](https://developers.tabapay.com/docs/fees-for-sub-clients-during-boarding)

## Documentation updates:

- [Duplicate card check](https://developers.tabapay.com/reference/how-to-use-duplicate-card-check)

## Keep current with all things TabaPay

- Check out our new [blog](https://blog.tabapay.com/) and [website](/content/site-root.html)
- Review the [most recent release notes](https://developers.tabapay.com/changelog)
- Ask a [question to our developer community](https://developers.tabapay.com/discuss)