Normal 0 false false false EN-US X-NONE X-NONE
Hi All,
Not that long ago (within the past 8 months or so), there was a change to how we process credit card payments when working in the Contributions window with a controlled batch. This change being that authorization of the credit card payments are now made en mass when you close the batch. Previously these payments would be authorized before finishing the individual transaction. I can’t remember if this change came by way of a patch or some other update, but this is the current arrangement in our Live (12.1) environment.
The Science Museum is preparing to upgrade from 12.1 to 12.5 and so we have been going through our testing checklist to make sure everything is ship-shape when we go live. When I was in our test environment I tested membership sales made through the Contributions window using a Controlled batch, and paying with a credit card I noticed something “funny”. We are again prompted to authorize our credit card payment (or at least the “Authorization” button is again available in the Payments window) before completing the individual payment, not when we close the batch.
Has anyone else seen this?
Jenny
Hi Jennifer,
The behavior you describe sounds like an uncontrolled batch, in which each payment is processed individually. A controlled batch holds all processing to be done at once, at the end.
Megan
In Test is your CC_ALLOW_PREAUTH in T_DEFUALTS set to Yes or No? If Yes, the cc will behave the way you described in your Test system. If No, then it will not authorize until the batch is closed. The default is Yes, and Element set up suggest it be switched to No if you are using Element.
Jenny,
We saw this change when we moved from Trancend to Element last fall. In the system table T_Defaults, you are able to change whether the authorization happens at the time of the transaction, or when the batch is closed using the entry CC_ALLOW_PREAUTH. When it's set to "Yes" it will authorize at the time of the transaction. When it's set to "No" it will authorize when you close the batch. Originally, we had it set to "Yes". We were told, that if it was set to "Yes" while using a controlled batch, and the transaction was later deleted, it would still go through in Element, but not in Tessitura. So we set it to "No" and now transactions authorize when we close our batches.
Kristina
From: Jennifer O'Neill-Englund <bounce-jenniferoneill4251@tessituranetwork.com>Sent: 3/15/2016 2:26:01 PM