Difference between revisions of "ImplementPaymentGateway"
Line 18: | Line 18: | ||
** These are the 'Response Reason Codes' that authorize dot net sends that should be communicated on the client side. The rest will be handled by alerting our system operator. | ** These are the 'Response Reason Codes' that authorize dot net sends that should be communicated on the client side. The rest will be handled by alerting our system operator. | ||
− | {| border="1" | + | {| border="1" align="center" |
|- | |- | ||
! S# !! Response Reason Code !! Response Reason Text | ! S# !! Response Reason Code !! Response Reason Text |
Revision as of 09:36, 20 December 2007
What (summary)
Accept money from those who want to buy what we offer.
Why this is important
We need to be able to accept payment in order to drive revenue
DoneDone
- We can accept payment for the "SponsorThisPage" offering using our Authorize.net payment gateway
-
create a gateway and hook it into screen flow at right place - extend the gateway to return transaction information to be saved in db
- find all ways that transaction can fail. return reasonable error messages in each case
- find all ways that transaction can fail that require system operator attention. log them somehow and alert operations
-
Steps to get to DoneDone
- Understand the different APIs of Authorize dot net (see references for links to guides)
- These are the 'Response Reason Codes' that authorize dot net sends that should be communicated on the client side. The rest will be handled by alerting our system operator.
S# | Response Reason Code | Response Reason Text |
---|---|---|
1 | 6 | |
2 | 7 | |
3 | 8 | |
4 | 17 | |
5 | 28 | |
6 | 37 | |
7 | 78 |
References
- http://www.authorize.net/files/gettingstarted.pdf
- Implementation guides:
- AIM (Advanced Integration Method)
- SIM (Server Integration Method)
- ABR (Automated Recurring Billing)
- CIM (Customer Information Manager)