Client Token / Client Session
2021-10-19
- The
amount value on response is now either calculated based on the order or whatever was provided on request.
nationalDocumentId field was added on the request and response
paymentMethod.options was added to enable surcharging. Read more about payment method options here. Read more about surcharging here.
- Additional validation has been put in place to ensure that a
currencyCode is always passed if any amount value is passed.
2021-09-27
- The
/auth/client-token endpoint was renamed to /client-session
/client-session endpoint now takes a payload including order, customer and other fields
/client-session is now versioned
- A variety of request/response bugs were fixed. Some of the effects are:
- The request and response are both fully camelCase
- Some fields would no longer accept empty strings in the request
null values are not returned anymore
Client Session Actions
2021-10-19
- Endpoint was added with support for
SELECT_PAYMENT_METHOD, UNSELECT_PAYMENT_METHOD, and SET_BILLING_ADDRESS actions. Read more about Client Session Actions here.
Payments API
2021-09-27
- Creating a payment using only a payment method token is now possible. The
order, customer and metadata passed on the Client Session request is then used for the payment.
- The create payment endpoint request was extended to include
order, customer, etc. It now more closely resembles the /client-session endpoint
- The response of all the Payments API endpoints was refactored to match the create payment request structure