Create Third-Party Customer | Redpin

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

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](/api-guide/getting-started/authentication#oauth-20-authentication)

Authentication

AuthorizationBearer

OAuth 2.0 Bearer token authentication. This API uses OAuth 2.0 Client Credentials flow. Please refer to the Authentication section for detailed information on how to obtain and use your OAuth credentials.

Path parameters

customer_idstringRequired

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

Request

This endpoint expects an object.

client_customer_detailsobjectRequired

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.

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

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

1	import requests
2
3	url = "https://sandbox.currenciesdirect.com/v1/customers/020123456789/third-parties"
4
5	payload = { "client_customer_details": {
6	"client_customer_ref": "SKYLINE-CLIENT-001",
7	"first_name": "Sarah",
8	"last_name": "Johnson",
9	"email": "sarah.johnson@example.com",
10	"mobile_phone": "+14155552671",
11	"country": "USA",
12	"date_of_birth": "1985-03-15",
13	"address": {
14	"address_line": "123 Main St, Apt 4B",
15	"city": "New York",
16	"state": "NY",
17	"post_code": "10001",
18	"country": "USA"
19	},
20	"currency": "USD",
21	"occupation": "Software Engineer",
22	"employer_name": "Google",
23	"income_range": {
24	"currency": "GBP",
25	"min_value": 10000,
26	"max_value": 20000
27	}
28	} }
29	headers = {
30	"Authorization": "Bearer <token>",
31	"Content-Type": "application/json"
32	}
33
34	response = requests.post(url, json=payload, headers=headers)
35
36	print(response.json())

1	{
2	"client_customer_ref": "SKYLINE-CLIENT-001",
3	"status": "PENDING"
4	}