Feature/handle ticket voucher when single brand #2122
Merged
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.
Summary
Ticket Edenred (tx_variant
'ticket'
) is a meal voucher provider in Brazil.The card component is used to pay with this voucher, but it does not come with an expiry date.
/binLookup
recognises this idea and returnsexpiryDatePolicy:'hidden'
for this brand, but, when'ticket'
was set as the only brand ("single-branded-card" scenario) - we didn't have a startup rule in place for this brand, in order to immediately hide theexpiryDate
field.Now we do.
Tested scenarios
expiryDate
field hidden at start when `'ticket`` is the only supported brandAll unit tests pass
Fixed issue: COWEB-1190