Custom Risk Providers
Follow the steps below to enable support for a custom risk provider.
Get Your Risk Provider's API Keys
Usually, this can be done via their web user interface.
Get 21 Travel Rule Secrets
Obtain the CLIENT_ID
and CLIENT_SECRET
as described
here.
Clone Existing Integration Example
Clone the deployment project onto your machine.
git clone https://gitlab.com/21analytics/21-travel-deployment.git
Create Custom Risk Provider Integration
cp 21-travel-deployment
cp -r ./beosin ./my-custom-provider
git add my-custom-provider
git commit -m "init: started work on new provider"
Then edit the files found in my-custom-provider
.
Test Your Changes on Your Local Machine
Change the 21 Travel Rule API URLs as found in the sample code such that you can test your changes locally.
Configure Secrets on Deployment Machine
Either add the new secrets to your .env
file or export
them on the command
line.
export CLIENT_SECRET=🤫🤫🤫🤫🤫🤫
export CLIENT_ID=🤐🤐🤐🤐🤐🤐
export APP_SECRET=🤫🤫🤫🤐🤐🤐
export APP_ID=🤐🤐🤐🤫🤫🤫
Also, make sure that all required environment variables are present. Then, proceed with the following commands.
docker-compose down
docker-compose up -d