Stellar provides standard way of handling compliance, but it's not part of the core protocol, because it is not required for all transactions on the network.
Works as a second layer basically, using core protocol primitives. And now to your questions:
It can simply refund all unknown / unauthorized payments.
Not for XLM. For assets anchor can control who ...
As far as I know, all wallets and other clients search for stellar.toml using the HTTPS scheme, so HTTP setup just won't work. You can try to issue a self-signed SSL certificate for your test domain.
In case if you have dedicated API and own some domain (say, mypersonaldomain.com), there is an easier way to achieve your goals. Using https://certbot.eff....
The approach I take on https://debtmoney.xyz/ is basically to keep a list of users in the database, along with their addresses and seed keys.
The keys are created whenever the user signs up and prefunded whenever the user attempts to use his account for the first time, then the keys are stored as plaintext on Postgres.
The code for the entire app is on ...
Check the Compliance README:
id required ID of the payment/transaction. In case of pending response or errors, you should resubmit the request with the same id value.
This should be an unique ID identifying your payment.
Not sure if I got your question right, just see if it helps.
I can perform my own due diligence on those businesses and audit their actual AML processes and then set up the compliance protocol so that the transactions only be allowed between mine and the selected businesses (the ones that I’ve okayed)?
the users of my stablecoin will ...
So, a step by step way of doing this would be:
Download and configure (bridge.cfg) the bridge server. Make sure to add the receive callback as well
Download and configure (compliance.cfg) the compliance server. Add all the urls for fetch_info, ask_user and sanctions callbacks
Implement the bridge receive callback as endpoint in your application server (i.e ...
The issuer/anchor will have to figure out a process for that, and it can vary significantly depending on their compliance process.
For example, an anchor may require a customer to register on their website providing KYC information (along with their stellar address), and if everything checks out, they'd execute the Allow Trust operation on the address.
In theory this should be possible, though I have not tested this out. In doing this however you will need to consider the following:
The multiple bridge servers should be able to connect to the compliance server internal port securely. You shouldn't make the internal port publicly accessible.
The callbacks you provide will need to be able to differentiate ...