Developer's Guide

Gateway Developer Guide and Reference 31 July 2012 49
Submitting Credit Card Transactions
Planning Your Gateway Integration
6
The Payflow SDK also supports the following credit card features:
 Address verification service and card security code validation
 Card-present (SWIPE) transactions
 Partial authorizations for pre-paid cards
 Purchasing card transactions
 Reference transactions (also called tokenization)
 Submitting Soft Merchant information
Planning Your Gateway Integration
When designing your Gateway integration, evaluate:
 Whether to use a one-step or two-step transaction process. One-step: Submit a sale
transaction, which performs the authorization and (if successful) then flags the transaction
for settlement. Two-step: Perform an authorization-only transaction and then later perform
a delayed capture transaction. The delayed capture transaction can be for the same amount
as the original transaction or for a lower amount. (In the case of a split shipment, you can
perform a delayed capture transaction for the initial shipment and a reference transaction
for the final payment.
According to card association rules, most physical goods merchants should use a two-step
process, since settlement should occur when the merchant ships the goods. A two-step
process is also useful for evaluating information in the response, such as whether the issuer
verifies the billing address, and so on. Electronic goods merchants, who fulfill the order
immediately, can use the one-step process. Check with your Internet Merchant Account
provider for suggestions on the best method for you.
 Whether or how to use risk management tools such as address verification service and card
security code. For the address verification service, if the initial transaction submits the data,
Balance Inquiry No
Credit Yes
Delayed Capture No
Inquiry No
Sale Yes
Voice Authorization Yes
Vo i d Ye s
Transaction Type Billable