Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modification of Attendee Registration #25

Open
GoogleCodeExporter opened this issue Mar 17, 2015 · 5 comments
Open

Modification of Attendee Registration #25

GoogleCodeExporter opened this issue Mar 17, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

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

@GoogleCodeExporter
Copy link
Author

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.

Original comment by [email protected] on 4 Aug 2011 at 6:54

  • Changed state: Available

@GoogleCodeExporter
Copy link
Author

Payflow supports "credits" via the api assuming you have the original 
transaction ID.

Original comment by [email protected] on 4 Aug 2011 at 7:37

@GoogleCodeExporter
Copy link
Author

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.

Original comment by [email protected] on 18 Sep 2011 at 9:14

@GoogleCodeExporter
Copy link
Author

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 comment by [email protected] on 2 Oct 2011 at 5:40

@GoogleCodeExporter
Copy link
Author

@Lei, Looks like you're right.  I've sent an inquiry to paypal for confirmation.

Original comment by [email protected] on 3 Oct 2011 at 5:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant