Summary

📋 Legacy Payment APIs Documentation: Documented legacy v2 Payment API endpoints and provided migration guidance to help existing integrations transition to the improved v3 Payments API.

All Legacy API endpoints have been superseded by newer versions that offer improved functionality and consistency. We strongly recommend migrating to the latest versions for better performance, enhanced tracking, and improved error handling.

Legacy Payment APIs

Legacy APIs

  • What’s New: Documented legacy v2 Payment API endpoints
  • Purpose: Provide migration guidance for existing integrations
  • Status: These endpoints remain functional but are no longer actively developed. New features and improvements are only available in the v3 Payments API.

Migration Guide

The following legacy endpoints have been superseded by v3 alternatives:

Legacy endpointRecommended alternative
POST /v2/customers/{customer_id}/paymentsCreate Payment (v3)
GET /v1/customers/{customer_id}/paymentsList Payments (v3)
GET /v1/customers/{customer_id}/payments/{payment_id}Get Payment Details (v3)

Benefits of Migrating to v3

The v3 Payments API provides several improvements over the legacy endpoints:

  • Unified workflow: Combined FX conversion and payment creation in a single request
  • Enhanced tracking: More detailed payment status information
  • Bank transfer instructions: Dedicated endpoint for retrieving funding instructions
  • Improved error handling: More detailed and actionable error responses
  • Same-currency support: Handles both FX conversion and same-currency payments

Breaking Changes

  • None. Legacy endpoints remain functional. However, we strongly recommend migrating to v3 for improved functionality and consistency.