Stay up-to-date with the latest improvements, new features, and changes to the Redpin Platform API.
We regularly update our API to provide better functionality and security. All changes are backwards compatible unless explicitly noted.
What’s in a changelog entry?
Each changelog entry includes:
- Summary: Overview of the release
- New Features: Fresh functionality added to the API
- Bug Fixes: Issues resolved in this version
- Breaking Changes: Any changes that might affect existing integrations
Summary
🚀 New Third Party Customer APIs: Added APIs for property developers and real estate platforms to manage end-user customer profiles.
These APIs enable property developers, real estate platforms, and fractional investment platforms to onboard and manage their customers for international property payments while maintaining compliance requirements. 🚀 New API Endpoint Released: We’ve added the Create Payment Session API to the Hosted B2B API suite, enabling platforms to initiate secure, temporary payment sessions for hosted integration use cases.
The Create Payment Session API is now available for integration. It enables you to generate a hosted payment session and receive a secure session URL for seamless cross-border payments. The API supports multiple recipients and integrates smoothly with your system via robust callback/webhook support.
New Features
Create Third-Party Customer
- Api-Reference: Create Third Party Customer
- Endpoint:
POST /api/v1/customers/{customer_id}/third-parties - Purpose: Onboard end users (buyers/investors) for property transactions without creating direct Redpin customer relationships
Get Third-Party Customer
- Api-Reference: Get Third Party Customer
- Endpoint:
GET /api/v1/customers/{customer_id}/third-parties/{client_customer_reference} - Purpose: Retrieve customer profiles and compliance status for ongoing transaction management
Update Third-Party Customer
- Api-Reference: Update Third Party Customer
- Endpoint:
PUT /api/v1/customers/{customer_id}/third-parties/{client_customer_reference} - Purpose: Update customer information and trigger re-verification when needed
Create Payment Session API
- Endpoint:
POST /api/v1/customers/:customer_id/sessions - Purpose: Start a hosted payment session for cross-border payments.
- Highlights:
- Generates a secure, time-limited session URL for embedding in your app or website
- Supports multi-recipient payments with detailed recipient and bank account data
- Configurable allowed origins and callback URLs for real-time status updates
- Secured with OAuth 2.0 authentication
- Sessions automatically expire at the defined timestamp; a new session must be created if the previous one expires before completion