Glossary This page serves as a brief glossary of commonly used terms throughout Fusion documentation. They are covered in much more detail in Resource Types.
Term
Description
Account
An Account corresponds to one single liability or asset ledger and represents one integral value in a specified currency (balance).
Account Holder
Account holder is a real/legal customer to Fusion. Drawing from the real world analogy, account holder could be an actual person who holds an account at a bank or could be a legal entity like a corporate, merchant, so on.
...
KYC Methods: IDFC Bank We have partnered with the IDFC Bank to provide the KYC services to the fintechs. The IDFC Bank enables the fintech to complete the KYC of the account holder using either of the following methods-
Minimal KYC Aadhaar OTP KYC Minimal KYC Step 1: Details’ verification In minimal KYC, the fintech shall verify the contact number, generally done via one-time passwords(OTP), and the identification proof, i.
...
About iOS Card SDK Cards SDK comes packed with a rich feature set to solve for different card use cases. With Cards SDK, fintech organisations can avoid the burden of spending several months on being compliant for card issuance, lifecycle management & operations which serve as a bottleneck. Now, you can focus on innovating your products with out-of-the-box security provided by SDK & launch financial products in a remarkable time frame.
...
iOS Card SDK Fusion APIs that deal with retrieval of Card information require the organization to be PCI DSS compliant. To avoid the burden of PCI compliance, Fusion introduces Card SDKs. By integrating these Card SDKs, the organizations can fetch sensitive Card details like PAN, Card CVV, and more.
In this article, SDK integration is documented in both Swift and Objective C languages.
Before you begin Take care of the following prerequisites before you begin with SDK setup:
...
JWT Token Generation Apollo SDKs need to be authenticated to provide access to the SDK to a designated user on the tenant app. This is achieved by passing a signed JWT token to the SDK. The private key used to sign the token is owned by the tenant. The corresponding public key is then used by Zeta’s backend to verify the token.
Generation of the tenantAuthToken should be done server-side as it involves signing the data with a private key.
...
