Review
Customers represent the end users who send or receive payments through your integration. Each customer undergoes automatic identity verification and fraud screening upon creation. Use customers to track payment history, manage bank account connections, and maintain a secure record of all transactions associated with a user. Customers can be either individuals or businesses with appropriate compliance checks for each type.
Review a customer's identity results
Update a customer's verification status
Update a customer's identity decision
ModelsExpand Collapse
CustomerReviewV1 = object { data, meta, response_type }
data: object { customer_details, identity_details }
customer_details: object { id, created_at, email, 11 more }
An object containing the customer's address. This is optional, but if provided, all required fields must be present.
compliance_profile: optional object { dob, ssn } or object { ein, legal_business_name, representatives, website }
PII required to trigger Patriot Act compliant KYC verification.
BusinessComplianceProfile = object { ein, legal_business_name, representatives, website }
identity_details: optional object { breakdown, created_at, decision, 7 more }
breakdown: object { address, business_evaluation, business_identification, 5 more }
Detailed breakdown of the customer verification results, including decisions, risk scores, correlation score, and more.
business_evaluation: optional IdentityVerificationBreakdownV1 { codes, correlation, correlation_score, 2 more }
business_identification: optional IdentityVerificationBreakdownV1 { codes, correlation, correlation_score, 2 more }
business_validation: optional IdentityVerificationBreakdownV1 { codes, correlation, correlation_score, 2 more }
synthetic: optional IdentityVerificationBreakdownV1 { codes, correlation, correlation_score, 2 more }
kyc: optional object { validations, codes, decision }
reputation: optional object { codes, decision, insights, risk_score }
response_type: "object" or "array" or "error" or "none"
Indicates the structure of the returned content.
- "object" means the
datafield contains a single JSON object. - "array" means the
datafield contains an array of objects. - "error" means the
datafield contains an error object with details of the issue. - "none" means no data is returned.