KYC fields on POST /orders/

POST /orders/ accepts a series of optional fields with personal data about the end customer. Sending them is useful for billing, logistics, and to personalize the payment experience.

Customer personal fields

Field	Type	Max	Description
full_name	string	48	Full name.
email_client	email	128	Email address.
phone_number	string	15	Mobile phone.
nif	string	12	Personal ID (DNI, RFC, CURP, etc.).
home_address	string	256	Full address.
address_number	string	56	Street / building number.
address_additional	string	64	Additional info (floor, door).
city	string	28	City.
province	string	28	Province / state.
zip_code	string	12	ZIP code.
country	string	2	ISO 3166-1 alpha-2 (for example MX, ES).

All are optional at the schema level. Use them if your flow requires it.

Note

For the merchant’s AML/KYB controls, B4bit Pay operates as a “vulnerable activity” under the LFPIORPI (Mexico). Merchant identification tiers are managed from the dashboard; it is not something you control via API. See terms and conditions.

Best practices

• Do not send sensitive data you do not need. If you only care about the email to send the receipt, do not pass the address.
• Validate on your side before sending: B4bit Pay applies only basic length and format validations.
• Do not log these fields in plain text — they are PII. If you need traceability, log only a hash.