This section aims to help Sending Anchors (capable of initiating cross-border payments) to onboard with Bitso's Receiving Anchor services; it presents the following items:

  • The [requirements](🔗) Sending Anchors must meet to use the services.

  • [Important information](🔗) to consider when using the services.

  • The [KYC fields](🔗) the service requires for registering sender and recipient users.

## Requirements

Sending Anchors must comply with the following:

  • It is a legal requirement that the Sending Anchors' Legal Entity goes through Bitso's regular business onboarding and KYC.

  • Sending Anchors must have a Money Services Business (MSB) or equivalent license to comply with Anti-Money Laundering and Counter-Terrorism Financing (AML/CTF) requirements.

  • Sending Anchors must provide Bitso with their Omnibus Stellar Public Key so that Bitso can include it in an allowlist. The service uses this key for authentication in production (public net). Only anchors included in the allowlist can use Bitso's Receiving Anchor services. In non-production environments, the service does not make use of an allowlist.

  • To use the services in production, Sending Anchors must finish their KYC process and sign a legal agreement for using Bitso's Stellar Anchor services.

## Important Information

Take the following into consideration when using Bitso's Receiving Anchor services:

(Script tags will be stripped)

## KYC Fields

Sending Anchors are responsible for the sender and recipient users' KYC process. Bitso's Receiving Anchor services require the KYC fields listed below to register sender and recipient users. For receiving users, the fields change according to their country of residence, and the service currently supports paying out transfers in Mexico, Colombia, and Argentina.

  • [Sending User](🔗)

  • [Receiving Users](🔗)

### Sending User

Customer Type: `sending_user`

### Receiving Users

The Customer Type for the different jurisdictions supported is as follows:

  • Mexico: `receiving_user`

  • Colombia: `receiving_user_col`

  • Argentina: `receiving_user_arg`