PaymentsOS API Changelog

Note

You are not automatically upgraded to the latest API version. If you want to upgrade to the latest version, make sure to change the api-version in the API request headers.

January 28, 2018

Introduces Version 1.2.0

You can now save a token, so that customers do not need to re-enter their payment details each time they want to initiate a transaction on your site. The token object has been extended to include a state attribute whose value reflects the token's usage.

November 28, 2017

Introduces Version 1.1.0

  • <Breaking-Change> All amounts and unit_prices have been changed to Minor Currency Units format, and their field types have been changed from double to integer. (For details see the Minor Units Format guide.)
    The following methods were updated with these changes:
    • POST /payments
    • POST /payments/{payment_id}/authorizations
    • POST /payments/{payment_id}/charges
    • POST /payments/{payment_id}/captures
    • POST /payments/{payment_id}/refunds

  • <Breaking-Change> The type attribute was renamed to token_type, and a new type attribute was added.
    The following structures were updated with these changes:
    • The token resource
    • The payment-method resource
    • POST /tokens

  • <Breaking-Change> The country_code format, in the payment-method resource changed from 2 to 3 letter ISO 3166-1 alpha-3 format.

  • <Breaking-Change> The payment_method object is now mandatory for POST /payments/{payment_id}/authorizations and POST /payments/{payment_id}/charges methods.
    The payment_method_token and credit_card_cvv attributes were moved from the body of these methods, into the new mandatory payment_method object.

  • <Breaking-Change> HTTP error code 504 was replaced by error code 503.
    The following methods were updated with this change:
    • POST /payments/{payment_id}/authorizations
    • POST /payments/{payment_id}/charges
    • POST /payments/{payment_id}/voids
    • POST /payments/{payment_id}/captures
    • POST /payments/{payment_id}/refunds

  • <Breaking-Change> If the x-client-ip-address is not sent in the POST /payments/{payment_id}/authorizations or the POST /payments/{payment_id}/charges methods, then we will no longer substitute the server ip_address as the default value.

October 30, 2017

The following Response Sub-categories were added: insufficient_funds and lost_stolen_card.

results matching ""

    No results matching ""