PayPal Gateway - 2012 Guide de l'utilisateur Page 24
- Page / 230
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
Introducing the Gateway Checkout Solutions
Processing Platforms Supporting Card-Present Transactions
1
24 31 July 2012 Gateway Developer Guide and Reference
6. The Gateway processes the payment through the payment processing network.
7. The Gateway server transparently returns the customer to the location on your website that
you specified in the request to obtain a secure token. You display the results to the customer
on your website.
NOTE: If you do not get a response from the Gateway server, submit an Inquiry transaction,
passing in the secure token to see if the transaction has completed. For details, see
“Submitting Inquiry Transactions” on page 61.
PCI Compliance Without Hosted Pages: Transparent Redirect
PayPal Payments Pro and Payflow Pro merchants who want PCI compliance while
maintaining full control over designing and hosting checkout pages on their website can use
Transparent Redirect. Transparent Redirect posts payment details silently to the Gateway
server, so this sensitive information never goes through the merchant’s website.
Implementing Transparent Redirect is very similar to implementing hosted pages. It differs
only in the steps shown in boldface below:
1. The customer clicks Buy to purchase merchandise on your website.
2. You request a secure token by passing a secure token ID to the Gateway server. In the
request, you pass the name-value pair, SILENTTRAN=TRUE. This name-value pair
prevents the hosted pages from displaying.
3. The Gateway server returns the secure token and your token ID to your website.
4. You display the credit card fields to the customer in a checkout page on your website.
5. The customer enters their credit card number, expiration date, and other sensitive
data into the credit card fields and clicks Submit. The browser posts the payment data
directly to the Gateway server, avoiding your website and easing your PCI
compliance requirements.
NOTE: To ensure that the post goes from the browser directly to PayPal and not back to
your website, you should add scripting.
6. The Gateway processes the payment through the payment processing network.
7. The Gateway server transparently sends the customer to the location on your website that
you specified in the request to obtain a secure token. You display the results to the customer
on your website.
Processing Platforms Supporting Card-Present Transactions
The following processing platforms support card-present transactions.
- Gateway Developer 1
- Guide and Reference 1
- Related Documentation 11
- Intended Audience 11
- Revision History 15
- Introducing the Gateway 19
- Checkout Solutions 19
- Gateway Product Details 20
- About Security 22
- Secure Token 23
- Hosted Checkout Pages 23
- Supported Payment Types 25
- Recurring Billing Service 26
- Pages: Transparent Redirect 28
- Configuring Hosted Checkout 31
- Customize 34
- Variables 36
- Silent Posts 38
- Payflow SDK 41
- Host URL Addresses 42
- About Name-Value Pairs 43
- Payflow Connection Parameters 44
- User Parameter Data 45
- Sale Transaction Example 46
- Submitting Credit Card 47
- Transactions 47
- About Credit Card Processing 48
- Credit Card Features 48
- Core Credit Card Parameters 51
- EXPDATE 60
- PNREF value: 62
- Credit 66
- TRXTYPE 68
- TENDER 68
- Submitting Void Transactions 72
- Using Card Security Code 75
- Testing Transactions 77
- PayPal Processor 82
- Result Values Based On Amount 83
- Card Security Code Results 92
- Transaction Responses 100
- Transaction Parameters 103
- Internet Transaction Data 104
- xxx-xxx-xxxx (US numbers) 105
- DEN to LAX 107
- LAX to SFO 107
- SFO to DEN 107
- Parameters 110
- AVS Parameters 114
- Y (default) 116
- F = First occurrence 119
- Other Parameters 125
- CA = California, USA 126
- NS = Nova Scotia, Canada 126
- COS = Colima Mexico 126
- TeleCheck Electronic Check 129
- Processing 129
- NFTF Guidelines 131
- TeleCheck Parameters 132
- Required TeleCheck Parameters 133
- XX – State code 134
- Response Code Values 137
- Adjustment Code Values 138
- Authorization – Sales Consent 139
- Language Sample for PPD 141
- Submitting Purchasing Card 143
- Accepted BIN Ranges 144
- Supported Transaction Types 144
- Avoiding Downgrade 145
- Edit Check 145
- Transaction Processing 153
- starting at 0 157
- Parameter String 160
- Heartland Level 2 Parameters 160
- Litle Level 2 Parameters 166
- Litle Level 3 Parameters 167
- SecureNet Level 2 Parameters 181
- ) and unit price 186
- ) fields 186
- Vantiv Purchasing Parameters 193
- WorldPay Level 2 Parameters 194
- WorldPay Level 3 Parameters 196
- VERBOSITY: Viewing Processor 199
- Specific Transaction Results 199
- ISO Country Codes 201
- Codes Used by FDMS South Only 203
- Visa Country Codes 210
- Units of Measure 217
- PayPal Acquirer 225
- Moneris Solutions 227
- Payflow Link Migration 229
Produits connexes et manuels pour Passerelles/contrôleurs PayPal Gateway - 2012
(261 pages)© 2020, manymanuals.fr. Tous droits réservés | 0.030 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels