API ReferenceCustomersAPI IntegrationThird Parties

Create Third-Party Customer

Beta

This is a compliance data collection endpoint that gathers information about the actual end users (funding parties) who will be making property payments through Redpin’s platform via partner applications, without creating direct customer relationships with Redpin. These end users are referred to as “third-parties” because they access Redpin’s services indirectly through their relationship with the partner, making them third-party to the direct Redpin-partner relationship.

This allows Redpin to meet regulatory requirements for international property payments while the customer relationship remains entirely with the partner platform.

Common Use Cases This endpoint is specifically designed for:

  • Property Developers facilitating international buyer payments
  • Real Estate Asset Management Platforms handling investor transactions
  • Fractional Investment Platforms managing partial property ownership payments
  • Title Company Software Providers processing closing transactions
  • Real Estate Sales Management Solutions coordinating international property purchases

Authentication: Bearer token required

Path parameters

customer_idstringRequired

Unique identifier of the partner platform creating the third-party customer

Headers

AuthorizationstringRequired

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.
client_customer_detailsobjectRequired
property_detailslist of objectsRequired

Array of property details to associate with the third-party customer.

Multiple Properties Support: This endpoint supports creating a customer with multiple property associations in a single request. Each property in the array will be processed and linked to the customer, enabling management of diversified property portfolios under one customer profile.

Response

Third-party customer created successfully

client_customer_refstring
The customer reference that was provided in the request
statusenum

Status of the third party customer.

  • APPROVED: Compliance check has passed successfully.
  • REJECTED: Compliance check has failed due to validation or regulatory issues.
  • PENDING: Compliance check is still in progress.
Allowed values:

Errors