Hide payment confirmation in back-office #895
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://eaflood.atlassian.net/browse/RUBY-1141 We have come across an issue where we need to change behaviour in the journey based on whether a registration or renewal is being carried out in either the front-office app or the back-office app. We should have known, but have just realised that Worldpay does not send payment confirmation emails if the merchant code used is MOTO. So there is no point in asking for and validating a payment confirmation email if the registration or renewal is created in the back-office. So this change updates the engine to amend the behaviour of the payment summary screen, specifically whether to include the payment confirmation section, and expect a value in the POST based on whether the host app as told us it's the back-office.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://eaflood.atlassian.net/browse/RUBY-1141
We have come across an issue where we need to change behaviour in the journey based on whether a registration or renewal is being carried out in either the front-office app or the back-office app.
We should have known, but have just realised that Worldpay does not send payment confirmation emails if the merchant code used is MOTO.
So there is no point in asking for and validating a payment confirmation email if the registration or renewal is created in the back-office.
So this change updates the engine to amend the behaviour of the payment summary screen, specifically whether to include the payment confirmation section, and expect a value in the POST based on whether the host app as told us it's the back-office.