Data Model - Receiver

Receiver Overview

The Receiver data model defines the structure for recipient information in pay-out transactions. This model encapsulates recipient identification, contact information, and regional compliance requirements.

Data Model Structure

Parameter	Type	Description
name	String	Recipient's full name for transaction identification Format: UTF-8 encoded string Usage: Required for most regions, used for transaction records and recipient verification Examples: "John Doe", "Maria Rodriguez Lopez"
email	String	Recipient's email address for notifications Format: Valid email address Usage: Transaction notifications, payment confirmations, and communication Examples: "[email protected]", "[email protected]"
phone	String	Recipient's phone number for contact purposes Format: International phone number format Usage: Transaction verification, support communication, and SMS notifications Examples: "62895359978010", "51987654321"
address	String	Recipient's physical address Format: UTF-8 encoded string Usage: Optional for most transactions, used for compliance and verification Examples: "123 Main Street, City, Country"
idType	String	Identity document type specification Format: Predefined identity type codes Usage: Varies by region, used for identity verification and compliance Examples: DNI, CE, PAS, RUC, CC
identity	String	Identity document number Format: Alphanumeric string Usage: Must match the specified idType format, used for recipient verification Examples: "12345678909", "48982488880"
taxNumber	String	Tax identification number Format: Alphanumeric string Usage: Required for Brazil pay-out transactions, used for tax compliance Examples: "0123456789", "12345678988"

Regional Requirements

Brazil Pay-Out Requirements

• Required Fields: taxNumber
• Optional Fields: All other fields
• Purpose: Tax compliance and regulatory requirements

Peru Pay-Out Requirements

• Required Fields: name, idType, identity, email, phone
• Optional Fields: address, taxNumber
• Identity Types: DNI (ID Card), CE (Foreigner ID), PAS (Passport), RUC (Tax ID)

Colombia Pay-Out Requirements

• Required Fields: name, idType, identity, email, phone
• Optional Fields: address, taxNumber
• Identity Types: CC (Domestic documents), CE (Foreigner documents)

Chile Pay-Out Requirements

• Required Fields: name, idType, identity, email, phone
• Optional Fields: address, taxNumber
• Identity Types: DNI, CE, PAS, RUT

India Pay-Out Requirements

• Required Fields: name
• Optional Fields: All other fields
• Purpose: Basic recipient identification

Philippines Pay-Out Requirements

• Required Fields: name
• Optional Fields: All other fields
• Purpose: Basic recipient identification

Implementation Examples

{
  "taxNumber": "0123456789"
}

{
  "name": "Rajesh Kumar"
}

{
  "email": "[email protected]",
  "idType": "DNI",
  "identity": "12345678909",
  "name": "Carlos Rodriguez Mendoza",
  "phone": "51987654321"
}

{
  "email": "[email protected]",
  "idType": "CC",
  "identity": "12345678909",
  "name": "Maria Rodriguez Lopez",
  "phone": "3001234567"
}

{
  "email": "[email protected]",
  "idType": "DNI",
  "identity": "12345678909",
  "name": "Juan Perez Gonzalez",
  "phone": "56987654321"
}

{
  "name": "Maria Santos Cruz"
}

Compliance and Validation

Identity Verification

• Document Validation: All identity documents must be valid and current
• Format Verification: Identity numbers must match regional format requirements
• Cross-Reference: Identity information is verified against official databases where applicable

Data Privacy

• Encryption: All personal data is encrypted in transit and at rest
• Access Control: Strict access controls for sensitive recipient information
• Audit Trail: Complete audit trail for all data access and modifications

Regional Compliance

• Local Regulations: Adherence to regional data protection and privacy laws
• Tax Requirements: Compliance with local tax reporting requirements
• AML/KYC: Anti-money laundering and know-your-customer compliance