PayPal Gateway - 2013 Guía de usuario Pagina 78
- Pagina / 256
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
Submitting Credit Card Transactions
Submitting Soft Merchant Information
6
78 07 February 2013 Gateway Developer Guide and Reference
NOTE: The pinless debit tender type requires essentially the same parameters as a credit card
transaction. In addition to the values required by all transactions, pass values for the
ACCT and AMT parameters. The First Data Merchant Services (FDMS) South
processing platform supports sale and credit transactions only.
Typical Sale Transaction Parameter String
The following is a typical NVP string passed in a sale transaction.
TRXTYPE=S&TENDER=C&USER=SuperUser&PWD=SuperUserPassword&VENDOR=SuperUser&PA
RTNER=PayPal&ACCT=5105105105105100&EXPDATE=1215&CVV2=123&AMT=99.00&BILLTOFI
RSTNAME=John&BILLTOLASTNAME=Smith&BILLTOSTREET=123 Main St.&BILLTOCITY=San
Jose&BILLTOSTATE=CA&BILLTOZIP=12345&COMMENT1=Reservation&INVNUM=1234567890&
PONUM=C12345&VERBOSITY=HIGH
Besides the required parameters that you pass in a sale transaction, this string includes other
typical parameters. The COMMENT1 (and COMMENT2) fields help to track transaction
information. Pass the customer’s street address (BILLTOSTREET) and zip code (BILLTOZIP)
to use address verification service. To validate card security codes, pass the CVV2 parameter.
For details on address verification service and card security code, see the following:
“Submitting Card Present (SWIPE) Transactions” on page 65
“Using Card Security Code” on page 83
Submitting Soft Merchant Information
Soft merchant information is detailed data about a merchant such as the merchant’s name,
business address, business location identifier, and contact information.
About Soft Merchant Information
Merchants aggregators, who perform transactions on behalf of other merchants under a single
merchant account, provide the processor with soft merchant information. Soft merchant
information identifies the merchant making the sale and includes information about that
merchant on the buyer’s card statement.
Say, for example, Outdoor Apparel has a chain of 12 stores located in the Western United
States with the corporate office in Oakland, California. John Lui purchases a pair of hiking
boots online from Hiker’s Duds in San Jose, California, and charges them to his credit card.
The transaction goes to the aggregator at Outdoor Apparel in Oakland. The aggregator sends
soft merchant information about the Hiker’s Duds store with the transaction to the credit card
processor. When John receives his credit card statement, he recognizes the charge for the
hiking boots he purchased at Hiker’s Duds in San Jose.
- Gateway Developer 1
- Guide and Reference 1
- Related Documentation 13
- Intended Audience 13
- Who Should Use This Document 14
- Revision History 17
- Introducing the Gateway 23
- Checkout Solutions 23
- Gateway Product Details 24
- About Security 26
- Supported Payment Types 29
- Supported Languages 29
- Recurring Billing Service 30
- Fraud Protection Service 30
- Secure Token 31
- Pages: Transparent Redirect 32
- Secure Token Errors 33
- Configuring Hosted Checkout 37
- Customize 39
- Using the PARMLIST Parameter 44
- Silent Posts 47
- Payflow SDK 49
- Host URL Addresses 50
- About Name-Value Pairs 51
- Payflow Connection Parameters 52
- User Parameter Data 53
- Sale Transaction Example 54
- Submitting Credit Card 55
- Transactions 55
- About Credit Card Processing 56
- Credit Card Features 57
- Core Credit Card Parameters 59
- EXPDATE 68
- Example Reference Transaction 75
- TRXTYPE 76
- TENDER 76
- Submitting Void Transactions 80
- Using Card Security Code 83
- Testing Transactions 85
- PayPal Processor 90
- Result Values Based On Amount 91
- Card Security Code Results 100
- Transaction Responses 101
- Transaction Parameters 111
- Internet Transaction Data 112
- xxx-xxx-xxxx (US numbers) 113
- SFO to DEN 115
- DEN to LAX 115
- LAX to SFO 115
- Parameters 118
- AVS Parameters 122
- Y (default) 124
- F = First occurrence 127
- Other Parameters 133
- CA = California, USA 134
- NS = Nova Scotia, Canada 134
- COS = Colima Mexico 134
- TeleCheck Electronic Check 137
- Processing 137
- NFTF Guidelines 139
- TeleCheck Parameters 140
- Required TeleCheck Parameters 141
- Example Test Transaction 143
- Response Code Values 145
- Adjustment Code Values 146
- Authorization – Sales Consent 147
- Language Sample for PPD 149
- Submitting Purchasing Card 151
- Level 2 and 3 Transactions 151
- Accepted BIN Ranges 152
- Supported Transaction Types 152
- Avoiding Downgrade 153
- Edit Check 153
- Transaction Processing 161
- starting at 0 165
- Parameter String 168
- Heartland Level 2 Parameters 168
- Litle Level 2 Parameters 174
- Litle Level 3 Parameters 175
- SecureNet Level 2 Parameters 189
- ) and unit price 194
- ) fields 194
- Vantiv Purchasing Parameters 201
- WorldPay Level 2 Parameters 202
- WorldPay Level 3 Parameters 204
- Payflow Header Parameters 207
- The Payflow Message Protocol 208
- Transaction Message 211
- Integrator-Provided Data 212
- Transaction Results 215
- ISO Country Codes 217
- Codes Used by FDMS South Only 219
- Visa Country Codes 226
- Units of Measure 233
- PayPal Acquirer 241
- Moneris Solutions 243
- Payflow Link Migration 245
- Payflow Gateway MagTek 247
- Payflow Gateway 248
- Delayed Capture (TRXTYPE=D) 249
- Sale (TRXTYPE=S) 249
- Vo i d ( TRXTYPE=V) 249
Relacionado con productos y manuales para Gateways / Controladores PayPal Gateway - 2013
(124 paginas)© 2020, manymanuals.es. Todos los derechos reservados | 0.360 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales