December of 2023
We have updated the API Reference section to reference the Checkout Bricks in the following endpoints: "Create test user", "Create payment", "Search payments", "Get preference", "Search preferences", "Update preference", "Save card", "Get customer card", "Get card", "Create customer" and "Get customer".
We have updated the description of the response parameter money_release_date in the Get Payment and Update Payments APIs to inform that the field can take the values "pending" or "released", where the first indicates that the payment has not yet been released (money held for a period) and “released” means that the money has already been released to the user's available balance.
November of 2023
We've added the x-idempotency-key parameter to the Payments POST. This function allows for safely repeating requests and ensures that the same action is not executed multiple times by mistake, preventing potential errors, such as creating two identical payments. See more details in our API Reference.
October of 2023
Information has been added about values that are not valid for the configuration of the
back_urls value, such as 'localhost/' or '127.0.0.1' with or without a specified port. We recommend using a server with a named domain (DNS) or development IPs to be able to return to the site after payment. Otherwise, the "Something went wrong" message will appear at the end of the checkout process.