The whole solution consists of your app, Gini Bank SDK, and the Gini Pay API. Your banking app uses Gini Bank SDK, while Gini Bank SDK uses the Gini Pay API. It is within the Gini Pay API where data extraction takes place. The method of connecting to the Gini Pay API depends on the type of network configuration that you choose. On this page, you get familiar with possible data flow while using different network configurations. These are Default Networking, Custom Networking, and combining Custom Networking with your own API.
Default Networking
If you choose Default Networking, we provide you with a helper method connecting you to the Gini Pay API. We recommend using this option.
Custom Networking
If you require specific communication with the Gini Pay API, you can use Custom Networking approach and make a connection yourself.
Custom Networking with user center API
Additionally, you can implement the communication with your own API.
Certificate pinning
Certificate pinning is a security measure that helps protect your users from potential risks, like attacks or fake websites. Normally, when your app communicates with a server, it checks the server's digital certificate to verify its identity. But sometimes, attackers can create fake certificates that pretend to be from the real server. This is where certificate pinning comes in handy.
With pinning, your app saves the real certificate's details the first time it connects to the server. So later when your app communicates with the server again, it checks if the pinned certificate matches the one from the server. If they match, it means the connection is secure, and your app can proceed with confidence.