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.

Sign up for GitHub

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

Jump to bottom

How do we deal with eWay restriction on Purchase action on createCardRequest #25

Open
eileenmcnaughton opened this issue Oct 15, 2017 · 1 comment
Open

How do we deal with eWay restriction on Purchase action on createCardRequest #25

eileenmcnaughton opened this issue Oct 15, 2017 · 1 comment

Comments

@eileenmcnaughton
Copy link
Contributor

In general the createCardRequest method can do a purchase at the same time in the action is set to 'Purchase'. eWay supports this for the Transparent Redirection, Responsive Shared Page or IFrame payment methods but not the DirectConnection (which is 'RapidDirect' in the omnipay plugin).

The point of the Omnipay plugin is that the calling code should not need to know about these gateway vagaries. We have all the information within the processor to complete the purchase when the action is purchase before returning a response and I think we should do so
@eileenmcnaughton
Copy link
Contributor Author

(I've added the above into #23)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eileenmcnaughton