Integration guidelines
This guide outlines integration approaches for property developers and platforms enabling international property payments through Redpin’s APIs.
Common use cases
This guide is designed for property developers, real estate platforms, and fintech companies facilitating cross-border property transactions.
Integration approaches
Redpin offers two distinct integration methods. The following comparison helps property developers select the optimal approach:
Decision framework
When to choose:
- Fast time to market is priority
- Limited development resources available
- Standard payment flows meet requirements
- Minimal ongoing maintenance preferred
When to choose:
- Custom user experience requirements
- Existing payment workflows to integrate
- Full control over customer journey needed
- Advanced customization and branding required
Hosted integration workflow
The hosted approach simplifies implementation by redirecting customers to Redpin’s hosted payment interface.
Step 1: Submit third-party customer data
Step 2: Session creation
Step 3: Customer interaction
The session creation response provides options for customer interaction:
- Web applications: Redirect customers to the returned session URL
- Embedded iframe: Embed the session URL within your application for integrated experiences
- Native mobile apps: Open the URL inside an “out of process” WebView, such as
ASWebAuthenticationSession
in iOS or Android Custom Tab, making the process feel seamless within your application
Customers complete their payment journey within Redpin’s hosted environment, including any required verification steps.
Step 4: Callback handling
Implement callback URLs to handle successful and failed payment scenarios.
Step 5: Session expiration
Monitor session expiration times and create new sessions as needed for incomplete payments.
API integration workflow
The following workflow demonstrates complete payment lifecycle management through direct API calls.
Step 1: Payment method validation
Before initiating any payment flow, determine if Redpin should be presented as a payment option.
Display Redpin as the recommended payment method when:
- User needs to send cross-border multi-currency transfers, and
- User’s preferred currency is supported by Redpin, and
- User resides in a country supported by Redpin
Step 2: Submit third-party customer data
Step 3: Customer verification status
If customer verification passes, continue with the payment flow. If additional verification is required, handle it before proceeding.
Check customer status: Monitor the customer status to determine if you can proceed with payment creation:
If verification is complete:
- Customer status is “success”
- Continue to quote generation (Step 4)
If additional verification needed:
- Customer status is “pending” or “failure”
- Webhook will provide required documents
- Handle document collection in your UI
- Monitor status until customer verification succeeds
Step 4: Quote generation
Quotes typically expire after 30 minutes, so ensure timely customer decision-making.
Currency selection: Allow customers to select their source currency, destination currency, amount, and BUY/SELL operation.
Quote request:
The system returns a quoted amount, quote_id, and expiry time. Monitor quote expiration and regenerate as needed.
Step 5: Payment execution
Step 6: Payment instruction display
Step 7: Payment status monitoring
Real-time webhook notifications ensure customers stay informed throughout the payment process.
Webhook notifications: Receive real-time updates on conversion and payment status changes for customer service and reconciliation purposes.
Payment status examples:
Awaiting funds:
Payment completed:
Implementation considerations
Authentication requirements
Both integration approaches require OAuth 2.0 authentication using Client Credentials flow.
Reference the Authentication documentation for implementation details.
Webhook configuration
Implement webhook endpoints to receive real-time status updates for:
- Customer verification status changes
- Payment status transitions
- Conversion execution confirmations
Error handling
Implement comprehensive error handling for:
- Quote expiration scenarios
- Customer verification failures
- Payment processing delays
- Session timeout events
See the Error handling guide for detailed implementation.
Compliance requirements
Partners must ensure regulatory compliance for cross-border payment facilitation.
Required implementations:
- Display of Redpin’s Terms and Conditions
- Customer consent collection for data sharing
- Fraud prevention message presentation based on customer jurisdiction
- Regulatory compliance for cross-border payment facilitation
Testing environment
Utilize Redpin’s sandbox environment for comprehensive integration testing before production deployment.
For complete environment details, see the Environments guide.
Support and resources
- API documentation: Complete endpoint specifications available in the API Reference section
- Integration support: Contact the Partner Integrations Team
- Webhook testing: Use sandbox webhooks for development validation