This changelog covers changes to the documentation and API Reference during January 2024.

Content changes

Added the Citcon through Afterpay integration guide. This alternative payment method allows consumers to pay using supported wallet apps on their mobile devices. (1/31/2024)
Updated the Paynet integration guide and SPEI integration guide to remove the specification in the dueDate parameter about requiring the ISO-8601 format. The system accepts the standard date options. For more information, see the details in the Create APM one-time-use token endpoint reference. (1/5/2024)

API changelog

Enhancement/Fix	API Reference	Description
Enhancement	Payments	It is now possible to save a card token for a retail transaction that is run using a terminal. When you specify `true` for the `processingOptions.saveCardToken` parameter when running the transaction (such as in the Process transaction from terminal request), the system creates this token. You can retrieve this token for a transaction with the View terminal transaction status endpoint. (1/10/2024)
Enhancement	Payments	The View surcharge recommendation endpoint has been updated. When submitting the request using a saved card token (`tokenex.token`), if that card token already has the `data.customer.billToState` value set, you do not need to include it in this request. The API Reference has been updated to include this information, and an additional request example has been added to the Try It feature. (1/10/2024)
Fix	Payments	Previously, the API Reference documentation for the Create one-time-use token endpoint indicated that you could use the ISO-8601 date format in UTC for `data.customer.birthDate`. This is valid, but the example given did not work because the system requires the ISO date to include 3 digits of milliseconds. The documentation has been updated to indicate this information. Also, it should be noted that the date must be UTC only -- time offset from UTC is not supported. (1/5/2024)

If you have any questions or feedback, contact us.