Institutional Host are entities that people trust to hold their deposits and issue credits into the HC Net for those deposits. All money transactions in the HC Net (except HCX) occur in the form of credit issued by Institutional Hosts, so Institutional Hosts act as a bridge between existing currencies and the HC Net. Most Institutional Hosts are organizations like banks, savings institutions, farmers’ co-ops, central banks, and remittance companies.
Before continuing, you should be familiar with:
As an Institutional Host, you should maintain at least two accounts:
Create them on the test network using the laboratory or the steps from the “get started” guide.
For this guide, we’ll use the following keys:
There are two simple ways to account for your customers’ funds:
Using a single account requires you to do additional bookkeeping, but means you have fewer keys to manage and more control over accounts. If you already have existing banking systems, this is the simplest way to integrate HC Net with them.
In order to act as an Institutional Host, your infrastructure will need to:
Hc Net provides a prebuilt mapping server and regulation server designed for you to install and integrate with your existing infrastructure. The communication server coordinates them and simplifies interacting with the HC Net. This guide demonstrates how to integrate them with your infrastructure, but you can also write your own customized versions.
When using the above services, a complex payment using mapping and regulation works as follows:
When someone is sending a transaction to you, the flow is slightly different:
While these steps can seem complicated, HC Net’s communication, mapping, and regulation services do most of the work. You only need to implement four callbacks and create a HCNet.toml file where others can find the URL of your services.
In the rest of this guide, we’ll walk through setting up each part of this infrastructure step by step.
*Powered by HashCash