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

Add definition for Card Transaction Type #466

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add definition for Card Transaction Type #466

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -349,6 +349,7 @@ All gateways will accept a subset of these options:
* clientIp
* returnUrl
* cancelUrl
* cardTransactionType (one of 'ecommerce', 'continuous', 'moto' or 'retail', see below for more)

Pass the options through to the method like so:

Expand Down Expand Up @@ -492,6 +493,18 @@ recurring billing profiles. Also in most cases token billing will cover your nee
store a credit card then charge it on whatever schedule you like. Feel free to get in touch if
you really think this should be a core feature and worth the effort.

## Card transaction Type

Some gateways support multiple card transaction types with different requirements. For example eWay
requires the cvn to be re-entered in an 'ecommerce' token transaction where the card owner is present
but not when processing a 'continuous' transaction - such as a monthly donation.

You can set this as:
- ecommerce: card owner present online; 3D-Secure supported; saved tokens may be used.
- continuous: card owner not present; repeats a previous approved transaction.
- moto: card owner MAY be present; NO 3D-Secure; saved tokens may be used.
- retail: POS machine or similar. Card owner present, PIN authorization possible. No 3D-Secure, no saved tokens.

## Incoming Notifications

Some gateways (e.g. Cybersource, GoPay) offer HTTP notifications to inform the merchant about the completion (or, in
Expand Down