You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary: Throughout the year attendees regularly request upgrades, downgrades,
and other modifications of their registration. It would be preferred to manage
these through SCALEReg rather than at Payflow and manually back filling data
into SCALEReg. While it would be ideal to allow the attendee to manager their
own upgrades, an admin only interface would be a great improvement.
Details: Currently there are three attendee modifications that occur
throughout the SCALE planning cycle:
1) Upgrade (ie addition of an item/addon)
2) Download (removal of an item/addon)
3) Cancelation of registration
Each of the above actions should be available in the administrative interface
to SCALEReg. Upon performing those actions a refund/credit or additional
charge should be created. Credits/refunds are supported via PayFlow by
referencing the original transaction ID. Additional charges should forward the
user or administrator to the payment interface for filling in appropriate
payment details.
Original issue reported on code.google.com by [email protected] on 1 Aug 2011 at 8:58
The text was updated successfully, but these errors were encountered:
This is definitely nice to do. Every year at SCALE I've had to do handle the
upgrades / refunds manually. I'm not sure if PayFlow can do refunds
programatically though.
The original transaction ID is included in the silent post from Verisign as
PNREF. It doesn't look like we store it yet. I'll cut a new ticket for that
and add a patch.
I don't think we can do refunds with Payflow Link. It only supports Sale and
Authorization. I think you need Payflow Pro to do other transactions types. See
the Payflow Link users guide pages 34 and 35.
Original issue reported on code.google.com by
[email protected]
on 1 Aug 2011 at 8:58The text was updated successfully, but these errors were encountered: