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

Which product is this package supporting? #23

Open
dilab opened this issue Jun 5, 2017 · 15 comments
Open

Which product is this package supporting? #23

dilab opened this issue Jun 5, 2017 · 15 comments

Comments

@dilab
Copy link

dilab commented Jun 5, 2017

CyberSource has a wide range of integration methods.
It is not clear which method this package is supporting.

List of CyberSource integration methods:

  • Simple Post
  • Secure Web/Mobile
  • Simple Order
  • SOAP Toolkit
  • Batch Upload
@eileenmcnaughton
Copy link
Contributor

I feel like it's simple post - it is the type generally known as a transparent redirect

@dilab
Copy link
Author

dilab commented Jun 7, 2017

okay, thanks for that.

I modified the code a bit and made a package that supports Secure Web/Mobile.

https://github.com/dilab/omnipay-cybersource

@eileenmcnaughton
Copy link
Contributor

Looks like you didn't start from a fork? I tried to see what a pull request would look like but it didn't seem to want to do one

@dilab
Copy link
Author

dilab commented Jun 7, 2017

@eileenmcnaughton no, I didn't. as I did not think you could merge it. So I made it stand-alone. What do you suggest?

@WillZWL
Copy link

WillZWL commented Jun 7, 2017

@dilab I also want this package can support Secure Web/Mobile. There need to modified the code to support, I also find there are some bugs need to fix first.

@WillZWL
Copy link

WillZWL commented Jun 7, 2017

@eileenmcnaughton I would like to join this project to help this package to support Secure Web/Mobile

@rdiaztushman
Copy link
Member

@dilab and @WillZWL You have both been added as contributors to this repo. Thanks!

@dilab
Copy link
Author

dilab commented Jun 7, 2017

@WillZWL @eileenmcnaughton one way of doing that is to rename the current Gateway to indicate which product it supports. My modified package is already supporting Secure Web/Mobile and I do not mind merging it over.

@eileenmcnaughton
Copy link
Contributor

Take a look at how Authorize.net supports multiple versions within the same gateway

@dilab
Copy link
Author

dilab commented Jun 8, 2017

@eileenmcnaughton that is what I mean. they have prefix for each product. essentially we need to have those prefix for all cybersource products.

@eileenmcnaughton
Copy link
Contributor

Can we grandfather it in?

@dilab
Copy link
Author

dilab commented Jun 8, 2017

@eileenmcnaughton meaning by default Gateway will be the current supporting product?

@eileenmcnaughton
Copy link
Contributor

I would probably suggest keeping Gateway / the top level name as the current product, but grandfathering in a new name for the new product & deprecating the current name of just 'Cybersource' ie. be backward compatible but recognise that down the track there is no top level product

@adriangordon1231
Copy link

adriangordon1231 commented Nov 17, 2020

Is it simple post or simple order (are they the same thing)? I am not seeing any mention of "simple post" in their api documentation.

@dilab
Copy link
Author

dilab commented Nov 17, 2020

@adriangordon1231 it is been a while since last push. I am not sure if the products support are up to the date.

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

No branches or pull requests

5 participants