Release Version 2.0.10 | 22/12/2022
- Description: Add product_class field in /users/{username} endpoint
Release Version 2.0.9 | 11/05/2022
- Description: Add ineligible_amount field in /capture endpoint
- Description: Add example for ineligible_amount field
Release Version 2.0.8 | 18/03/2022
- Description: Display the correct URL for all requests
- Before
https://directpayment.sbx.eu.edenred.io/v2/transactions/{transaction_id} - After
https://directpayment.stg.eu.edenred.io/v2/transactions/{transaction_id}
- Description: Fix/Add error code description and correct transaction names
| Endpoints | Description |
|---|
| GET:/transactions | Fix name from GetTrasactions in GetTransactions |
| GET:/transactions | Fix the error from 500 to 400 for code INVALID_SEARCH_PERIOD |
| POST:/transactions | Add error code 400 INVALID_REQUEST "The configuration allows only single/dual messaging requests." | |
| GET:/transactions/{transaction_id} | Fix name from GetTrasaction in GetTransaction |
| POST:/transactions/{transaction_id}/actions/capture | Remove 400 error code INVALID_AMOUNT "Ensure that the amount you want to capture matches the authorized amount." |
| POST:/transactions/{transaction_id}/actions/refund | Remove 400 error code INVALID_AMOUNT "Ensure that the amount you want to refund matches the authorized amount" |
Release Version 2.0.7 | 24/02/2022
- Description: Improve error codes in all endpoints.
Release Version 2.0.5 & 2.0.6 | 04/02/2022
- Description: Migrate API contract from RAML to OAS.
Release Version 2.0.4 | 14/12/2021
- Description: Add the X-Session-Id header as optional when making a POST /transactions.
- Description: Add session_id field when making a GET /transactions and GET /transactions/{transaction_id}. (This will be displayed when we make a POST /transactions that contain the X-Session-Id)
- Description: Update GET /transactions and /transactions/{transaction_id} examples to display the session_id field.
Release Version 2.0.3 | 30/07/2021
- Description: Added three_d_s_url in POST /transactions response
Release Version 2.0.1/2.0.2 | 28/06/2021
- Description: Fix POST:/transactions Request Body
Release Version 2.0.0 | 20/04/2021
- Description: Mule 4 - migration
Release Version 1.1.4 | 11/03/2021
- Description: Added "expiry_date" in the GET:/balances response
Release Version 1.1.3 | 10/0/2021
- Description: Set Authorization header as optional:
| Endpoints | Description |
|---|
| GET:/transactions | Set Authorization header as optional |
| GET:/transactions/{transaction_id} | Set Authorization header as optional |
Release Version 1.1.1 | 09/02/2021
- Description: Add Response headers for GET:/transactions:
Accept-Ranges: The Accept-Ranges response HTTP header is a marker used by the server to advertise its support of partial requests. Content-Range: The Content-Range response HTTP header indicates where in a full body message a partial message belongs.
Release Version 1.1.0 | 08/02/2021
- Description: Add new endpoints:
| Endpoints | Description |
|---|
| GET:/transactions | This endpoint allow partner or merchant to retrieve a set of transactions according to a specific criteria |
| GET:/transactions/{transaction_id} | This endpoint allow partner or merchant to retrieve the transaction details for the given identifier |
More details: Transaction History