[
https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588403#action_12588403
]
David E. Jones commented on OFBIZ-1716:
---------------------------------------
The NSF retry stuff can be used for any order, but is mostly intended for
automatic orders done through ShoppingLists.
Either way, it totally depends on business policy and desired process.
For CVV codes it doesn't matter anyway. You cannot store or in any way remember
them beyond the time scope of the transaction they were entered for (and if it
is split into auth and capture then that would be ONLY the auth part you can
keep the code for).
That means for ALL automatic retries you will not have the CVV code, and will
not get the benefit of the discounted transaction fee for having the CVV code.
That's the only real difference.
Again, it's all a business decision to be made with an understanding of these
sorts of constraints. Whatever is done OOTB in OFBiz needs to be changeable to
different situations. Well, it is always changeable, but the goal is to make
more common variations easier to configure.
> POS: CVV2 code is not always deleted from the DB
> ------------------------------------------------
>
> Key: OFBIZ-1716
> URL: https://issues.apache.org/jira/browse/OFBIZ-1716
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: SVN trunk, Release Branch 4.0
> Reporter: Chris Lombardi
> Assignee: Jacques Le Roux
> Priority: Critical
>
> I ran a transaction that was declined by the processor. I later noticed that
> the cvv2 code was still present in the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
