Account Information

What are the different account information features?

All the features available in the API are listed in the FeatureEnum object.

The account information features are described in the following table.

Does Yapily provide MCCs (merchant category codes) for transactions?

As a gateway, Yapily can only return the information that the institution provides. As MCCs are an optional field for ASPSPs to provide, the presence of this information is completely dependent on whether the Institution provides this or not.

If supported by the Institution, the ACCOUNT_TRANSACTIONS_WITH_MERCHANT feature will be present in the features array of the GET Institution endpoint.

Why can I not get identity data from my institution?

As a gateway, Yapily can only return the information that the institution provides. As identify information is optional for ASPSPs to provide, the presence of this information is completely dependent on whether the Institution provides this or not.

If supported by the Institution, the IDENTITY feature will be present in the features array of the GET Institution endpoint.

Are joint and business accounts supported by Yapily?

Joint accounts and business accounts are accounts that may require multiple authorisations in order to obtain financial data depending on the Institution.

In the event that multiple authorisations are required by the Institution, once the initiating user authorises the account authorisation request, the state of the Consent object will change status from AWAITING_AUTHORISATION to AWAITING_FURTHER_AUTHORIZATION until the required authorisations have taken place offline e.g. Email, SMS or Phone call.

The Consent object will contain information about how many authorisations are required and how many have been authorised while in this state.

Is pagination supported for obtaining transactions?

Yes, see Pagination for more information.

Does Yapily support any enrichment?

Yes, see Enrichment for more information.