Skip to main content
To comply with EU regulations, CryptoProcessing by Coinspaid has to collect user data for all transactions. This affects three endpoints: As an EU-based entity, CryptoProcessing by Coinspaid is required to comply with the MiCA (Markets in Crypto-Assets) regulations that aim to combat money laundering. This includes collecting certain data about natural persons and companies who send and receive crypto using our services. We are not collecting anything outside of the data you and your customers provide in API calls and in-app transactions.

​
What data is required

When you generate a new crypto address or create a payment request, you need to provide certain user data depending on who the sender is. This includes the sender_type parameter (either legal or natural) and the sender_data object. To make a withdrawal, you also need to share the same information about the recipient (receiver_type and receiver_data). In case of internal transfers within a company, receiver_type can be set to self. For legal entities, we ask for the company name and registration country. For natural persons, you need to provide the sender’s first and last names and their date of birth.
Legal entityNatural person
  • Company name (required)
  • Country of registration (required)
  • Email (optional)
  • First name (required)
  • Last name (required)
  • Date of birth (required)
  • Email (optional)

​
Requesting data from the customer

When requesting funds via a payment request, you can omit the sender_type and sender_data parameters. In this case, CryptoProcessing will use the data provided earlier for the same user, according to end_user_reference. If the data is omitted and cannot be found for the given end_user_reference (or if end_user_reference is omitted, too), the user will see a form for entering the data manually. They will have to fill in the data before they are shown the crypto address for sending funds.
User data form in the payment request interface
Last modified on July 14, 2026