Gravity Forms eWAY Pro v1.3.0 has just been released. Client Side Encryption now works with multiple feeds, each with their own eWAY account; multiple feeds with complex conditional logic work correctly; and there’s a new custom merge tag for the Entry Date.
Multiple Feeds and Client Side Encryption
If you have multiple eWAY accounts and want to submit payments to them from the one website, you can. Until now, that only worked if you used separate forms, or didn’t use the Direct Connection method, because each eWAY account has a separate Client Side Encryption (CSE) key. With this release, you can now build one form that can submit a payment to any of your eWAY accounts using conditional logic.
This change is in response to a client who is using a single form to accept invoice payments for over a dozen medical specialists, each with their own eWAY account! They were forced to use the Responsive Shared Page, but can now accept card details directly on their website and still process payments against separate accounts. Thanks, Raymond!
Multiple Feeds and Conditional Logic
Another client helped me find an error with conditional logic on feeds. In all of my testing, I have been looking at relatively simple conditions where the field being tested is always visible. What I hadn’t tested was more complex situations where one field determines whether a second field is shown, and that second field is used for the feed’s conditional logic. Thanks, Patrick!
Entry Date merge tag
If you are sending Gravity Forms notifications as receipts, you probably use the standard Date merge tag. For eWAY transactions, you can now use the Entry Date instead — and you should, because if you resend a notification you want it to have the date of submission, not today’s date. Thanks, Ellyse!
You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for Gravity Forms eWAY Pro.
Tags: Gravity Forms eWAY ProPosted on