Open Banking API

I am beginning tom read up a bit on the new banking software standaard. Beginner.

They have a lab sandbox to try out some transactions.  The big plus, they do all their interacting in JSON, a standard and natural gtext notation.  They do PUT and GET to the web site.

Some calls are complex, like create a new account to prequalify in a liquidity net. Do that off line, like they have already set up dummy account profiles.

Once you have granted PoA to a bot inside the market, it is all bearer asset.  Prequal, check in and check out.    Your bot is inside the computer, sharing space with the piot boss, the two will directly adjust accounts.  Each bot can generate a valid prequal as it is assigned the cryptobadge,  Inside the API is a direct manipulation of the instruction cache.

So, we have the secure, transaction safe kernel, prequalified, verifiable  bot code, and your hand held generates a public verification key.  All assert exchanges go through the spectre secure instruction cache.

So, break the Open Banking standard up  into components and the tiniest component having a few key operations stand out for microcode.

Flow
We plug our card into our handheld and bring up the set and adjust accounts application.  The card is acting as your bank, your personal accountant.  So it has to take the few most important APIs and embed them.  

There are other APIs the card can emit,for authorization and set up of a trading bot the.  Only your thumb printed card can start up robotic trading in the liquidity network.  The card is peer to peer, there is always another card at the other end or your are running an application.  

The card is both an investment banker and a personal account manager, so it plays both sides of the API.  That means subselect the most important from each group.  Put those as macros on the card, and go on with the JSON interface.