Terms of Service

You should make your customers accept BlindPay terms of service before initiating their KYC process.

What is the terms of service?

BlindPay's Terms of Service is a legal agreement that must be accepted by your customers before creating a receiver. This acceptance is required for regulatory compliance and allows BlindPay to legally provide services such as generating blockchain wallets and creating virtual accounts on behalf of your customers.

The terms can only be accepted by users accessing the BlindPay URL https://app.blindpay.com on the client side, so all requests from servers will be ignored.

Generating terms of service url

Before generating a terms of service url, you need to:

  1. Create an account on BlindPay
  2. Create a development instance
  3. Create your API key

Remember: replace YOUR_SECRET_TOKEN with your API key and in_000000000000 with your instance ID.

Remember: we only accept uuid on the idempotency_key field.

Bash
cURL

After you do this request, the API will return a url with the following query parameters:

Bash
URL Example
ParamRequiredExample
session_tokenyeseyJ0eXAi...E0I (jwt)
idempotency_keyyes5d8b149e-a55d-4b5b-a8f8-7c4fa315f854 (uuid)
redirect_urlnohttps://blindpay.com/
receiver_idnore_000000000000 (mandatory for accepting a new TOS version)

We strongly recommend adding a redirect_url parameter. When users accept the terms of service, they will be automatically redirected back to your application, creating a seamless user experience.

Accepting terms of service

After the user accepts the terms of service, we will redirect them to the redirect_url and automatically add a query parameter tos_id.

You need to use this tos_id when creating a receiver.

You'll also receive a webhook event tos.accept when the terms of service is accepted. See the payload here.

Accepting a new version of terms of service

If BlindPay updates the terms of service, all requests to payout quote and payin quote endpoint will return an error with message please_accept_terms_of_service.

If you receive this, please generate a new terms of service and make sure to set the receiver_id parameter on the url returned.

After the customer accepts the new version of terms of service, all quotes endpoints won't return the error anymore.