Migration Guide
| V3/Legacy Endpoint | V4 Recommended Endpoint |
|---|---|
GET /ecommerce/refunds | GET /ecommerce/transactions?type=REFUND |
GET /ecommerce/refunds/:id | GET /ecommerce/transactions/:id |
Key Differences
Transactions (New - Recommended)
The unified Transactions model includes:- Transaction Types:
PAYMENT,REFUND,CREDIT_NOTE,FEE,CHARGEBACK,PAYOUT,ADJUSTMENT - Payment Method Details:
CARD,BANK_TRANSFER,WIRE_TRANSFER,PAYPAL,APPLE_PAY,GOOGLE_PAY,CHECK,CASH,CRYPTO,OTHER,UNKNOWN - Gateway Information: Payment processor name and gateway transaction ID
- Original Transaction Link: For refunds, reference to the original payment
- Reason Codes: Standardized reasons for refunds (
CUSTOMER_REQUEST,FRAUD, etc.)
Refunds (Legacy)
The Refunds model provides:- Basic refund information tied to orders
- Limited payment method details
- Separate from payment records
Example Migration
Legacy Refunds Request:Properties Supported (Legacy)
| Property | Type | Description |
|---|---|---|
| platform_id | string | The Platform’s ID for the refund |
| parent_data_model | string | The parent data model type |
| parent_data_model_id | string | The ID of the parent order |
| currency_id | string | Currency code |
| sub_total | number | Subtotal of refund |
| total_amount | number | Total refund amount |
| created_at | string | Created timestamp |
| updated_at | string | Updated timestamp |