Contacts & Bank Accounts
Contacts & Bank Accounts
Contacts represent your customers or providers in the Koywe system, storing their information and linked bank accounts for payment operations.
What are Contacts?
A Contact is a person or business entity that you interact with through payments:
- Customers who pay you (PAYIN)
- Providers who you pay (PAYOUT)
- Both in marketplace scenarios
Why Use Contacts?
Track payment history per customer or provider
Store KYC/compliance information (documents, tax IDs)
Link bank accounts for easy recurring payments
Generate reports per contact or business type
Contact Structure
Required Fields
Optional Fields
Creating Contacts
Basic Contact Creation
Response:
Document Types by Country
Colombia (CO)
Brazil (BR)
Mexico (MX)
Chile (CL)
Argentina (AR)
Bank Accounts
Linking Bank Accounts to Contacts
For PAYOUT operations, you need to link a bank account to the contact:
Automatic Association: Bank accounts are automatically linked to the contact’s information. The holder name is taken from the contact’s fullName. Bank codes can be deduced from account numbers for most countries.
Country-Specific Requirements: See Merchant External Accounts for detailed validation rules by country. Contact bank accounts follow the same validations (CLABE for Mexico, CCI for Peru, CVU/CBU for Argentina, etc.).
Retrieving Contacts
List All Contacts
Get Specific Contact
Get Contact’s Bank Accounts
Updating Contacts
Validation Requirements
Person vs Company
For PERSON (individual):
- Use individual document types (CC, DNI, CPF, etc.)
businessType:"PERSON"- Individual’s full name
For COMPANY (business):
- Use company document types (NIT, CNPJ, CUIT, etc.)
businessType:"COMPANY"- Company legal name
Document Number Formats
Document numbers must match the expected format for each country:
- Colombia CC: 6-10 digits
- Brazil CPF: 11 digits (with or without formatting)
- Mexico RFC: 12-13 characters
- Chile RUT: Format XX.XXX.XXX-X
Best Practices
When to Create Contacts
Create contacts for:
- Customers making payments (PAYIN) - for tracking and compliance
- Providers receiving payments (PAYOUT) - required for bank account linking
- Recurring transactions with the same entity
Reusing Contacts
Reuse existing contacts for the same customer/provider to:
- Maintain payment history
- Avoid duplicate records
- Simplify reconciliation
Data Privacy
Security Considerations:
- Store only necessary information
- Follow GDPR/data protection regulations
- Don’t store sensitive data in metadata fields
- Implement proper access controls