v3.0.2

3.0.2 (2024-09-11)

Bug Fixes

• ivr: prompt customer to check their statement to verify payment when an unknown error is encountered (e7437d3)
• ivr: remove "you have not been charged" message when an unknown error occurs as it's possible that the customer has still been charged (510fcfe)

v3.0.1

3.0.1 (2024-08-27)

Bug Fixes

• address issue where errors were not returned to the agent, resulting in a stuck payment request app (abb74d8)
• agent-assisted ivr: address error when taking multiple payments in the same call (e681e48)

v3.0.0

3.0.0 (2024-08-26)

⚠ BREAKING CHANGES

• renames existing workspace apps

New Features

• add receipt app to allow agents to send receipts after a self-service transfer (7aa969e)
• ivr: add basic bank account number length validation (f56b9de)
• pass payment submission error messages to call flow and agent (22aa00e)

Bug Fixes

• handle situation where error messages from Zift weren't spoken correctly (812ce06)

Important

If you are already using the Payment Request workspace app in Amazon Connect, there are a few extra steps you will need to follow in order to update from previous versions. Before deploying with the new version, please complete the following:

1. Remove the Payment Request app from any security profiles in Amazon Connect.
2. Remove any instances associated with the Payment Request third-party application in the AWS Amazon Connect Console.
3. Delete the Payment Request third-party application in the AWS Amazon Connect Console.
4. Deploy the new version of the stack as normal. This will recreate the Payment Request app as before. Remember to re-add your third-party application to the security profiles for your agents.

v2.1.0

2.1.0 (2024-08-20)

New Features

• ivr: add ability to configure speaking rate and volume (4a12830)
• perform basic length validation on unrecognized credit card networks (8ac6b74)

Bug Fixes

• correctly accept AWS profile in synth and deploy commands (e3857bc)
• deploy correctly when receipt queue ARN is not provided (98d4389)
• ivr: address issue preventing cards or bank accounts from being validated (306ed9b)
• ivr: proceed with the payment process if any internal errors occur when validating (927564f)

v2.0.0

2.0.0 (2024-08-18)

⚠ BREAKING CHANGES

• renames existing Lambda integrations

• bump major version number (e1fbf5f)

New Features

• ivr: perform basic input validation on payment info (c1bfd36)
• ivr: speak the last 4 digits of the previously used payment to the customer (d6d965d)
• self-service ivr: add option to ask the customer if they would like to receive a receipt by speaking to a representative (a5ee00d)

Bug Fixes

• correctly handle line breaks instead of speaking "nn" (b705133)
• specify bash command to fix scripts when using Windows (362e841)

Important

There have been naming changes in this release that requires an extra step in order to update from previous versions. Please add "skipAssociations": true to options in your cdk.context.json file and deploy. This will remove the previously named Lambda function integration associations.

Once deployed successfully, remove the skipAssociations line and deploy again. This will re-add the associations with the updated names.

v1.4.0

1.4.0 (2024-08-08)

New Features

• add script for compressing Lambda files (d59b8e4)

v1.3.0

1.3.0 (2024-08-07)

New Features

• add option to disable Lambda code signing (1e4089e)
• add option to skip creating workspace app in Amazon connect (d315c81)
• ivr: updated wording to mention debit cards, expiration date format, "customer" instead of "contact", and "entry" instead of "input" (72c8c0d)
• output payment request app URL after synth/deploy (3140252)
• pass tokenization error messages to call flow and agent (73762b1)

Bug Fixes

• remember previously entered payment info, regardless of card or bank type (f9db6d4)

v1.2.1

1.2.1 (2024-07-22)

Bug Fixes

• add missing dependency for agent message (f8d75f8)

v1.2.0

1.2.0 (2024-06-26)

New Features

• support creating multiple stacks in the same AWS account (#194) (236e3f5)

v1.1.1

1.1.1 (2024-06-21)

Bug Fixes

• don't prompt the customer to re-use payment info if the last payment was unsuccessful (#190) (885bb96)