You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all modern mobile apps for banking, they must use REST to fetch the data. In FIBI for example, it super simple because their website is shitty, but in mobile app they are using REST. Same with Pepper.
You can either use Charles for iOS (https://www.charlesproxy.com/documentation/ios/), or use Charles for Mac (with it's Custom SSL certificate, and install the profile on your mobile phone with a proxy. This way all requests are being decrypted and you can track the complete request on your Macbook, and log the requests and responses).
I did some experiments on the iOS app of Poalim, found the following for example (for getting information about the current account's transactions):
I think this might simplify the implementation, no? We can even do JSON schema and GraphQL Mesh for that...
The text was updated successfully, but these errors were encountered:
In all modern mobile apps for banking, they must use REST to fetch the data. In FIBI for example, it super simple because their website is shitty, but in mobile app they are using REST. Same with Pepper.
You can either use Charles for iOS (https://www.charlesproxy.com/documentation/ios/), or use Charles for Mac (with it's Custom SSL certificate, and install the profile on your mobile phone with a proxy. This way all requests are being decrypted and you can track the complete request on your Macbook, and log the requests and responses).
I did some experiments on the iOS app of Poalim, found the following for example (for getting information about the current account's transactions):
I think this might simplify the implementation, no? We can even do JSON schema and GraphQL Mesh for that...
The text was updated successfully, but these errors were encountered: