2024-04-23

In this version we optimized the way payment network related parameters are collected. Going forward, a payment_rails object is used to collect all the details about the rails over which the payment is processed. These details include the customer's payment details, such as a bank account or card, as well as the payment method, such as ideal, and anything that is tightly related to it.

2024-02-17

We made three small, backwards incompatible changes in the Payment API for consistency.

shopper_canceled to customer_canceled

At Rootline we refer to a buying customer as customer. Therefore, we changed the 'shopper_canceled' scenario to show customer_canceled in the API. Specifically you will find this value in the response of the payment at authorizations.decline_details.code.

The authorization array is now called authorizations

In our first version we accidentally used a singular version for the authorization array. Now the array is correctly called authorizations.

The authentication array is now called authentications

In our first version we accidentally used a singular version for the authentication array. Now the array is correctly called authentications.

2023-07-19

This is our very first API version.