Changelog

Date	Section	Details
10 February 2025	4.1.1 Attributes	metadata An arbitrary string which you can attach to this redemption request. The maximum length of the string is 1000 characters. This will be available in the transaction data which can be used for the merchant’s reconciliation purposes. We highly recommend the inclusion of the following information if available for better visibility and dispute resolution scenarios: Branch / store ID POS / Terminal / Counter ID Cashier / staff ID Cashier / staff Name Verifier ID Receipt number required SKU required
29 November 2024	3.1 In event of leaked API key	API keys do not expire at the moment. In the event of a leaked API key: For test environment, you may revoke the leaked key and create a new key via developer's portal For live environment, email [e-mail] for a new key
1 Oct 2024	4.1. POST /v1/vouchers/redeem	SKU: and receipt_number: are only required for Climate Vouchers programme. It is mandatory, and the format should follow the above example specifically for these 2 details. Do note to only include eligible items’ SKUs.
20 Sep 2024	4.1. POST /v1/vouchers/redeem	SKU: and receipt_number: are only required for Climate Vouchers programme. It is mandatory, and the format should follow the following example specifically for these 2 details: e.g. receipt_number:789,SKU:001,002
13 Aug 2024	6.2 Error codes	For all campaigns - You should show the error.message below as-is on your POS
27 June 2024	4.1. POST /v1/vouchers/redeem	For Climate Vouchers only - Additional requirement to include receipt_number:xxx in metadata
14 May 2024	4.2.1 Introduction	For all campaigns - Compulsory to include idempotency key whenever making a redemption call to RedeemSG API