PayPal Gateway - 2013 Podręcznik Użytkownika Strona 208
- Strona / 256
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
Payflow Header Parameters
Posting Transactions Directly Without the Payflow SDK
D
208 07 February 2013 Gateway Developer Guide and Reference
Posting Transactions Directly Without the Payflow SDK
The Payflow SDK is recommended for .NET and Java users to simplify the Payflow
integration. Developers who prefer to write code in other programming languages can go to
the PayPal Labs integration wizard web site (
https://www.paypal-
labs.com/integrationwizard/index.php.). The wizard generates customizable code samples in
languages such as PHP.
Developers also have the option to post transactions directly to the Payflow servers using the
Payflow message protocol, without the need to install an SDK. This section describes the
HTTP headers that are required to post transactions directly to the Payflow servers.
The Payflow Message Protocol
What is the Payflow message protocol and what are its advantages?
PayPal’s Payflow message protocol is an HTTP-compatible protocol for transactions. The
HTTP-compliant implementation of this protocol has the following goals:
It enhances flexibility to developers integrating with the Payflow Service. Merchants can
use the protocol in either of these ways:
– Using a Payflow SDK such as .NET or Java that uses this protocol.
– Integrating this protocol directly into your own client application without using an SDK.
– It increases reliability through adherence to open standards.
– Built-in tools to prevent duplicate transactions and authorizations.
The Payflow message protocol provides the underlying transport for application-level
transactions, using either the Payflow name-value pair or XMLPay 2.0 format. All
transaction data as documented in this guide is embedded in the body of a standard HTTPS
POST and POSTed to the URLs specified.
What is the disadvantage of building your own integration?
Since you are building your own integration, you will need to add your own error handling,
retry logic and duplicate transaction handling within your code.
NOTE: If you prefer not to write your own client, you can use the .NET SDK, which can also
be used with classic ASP, or the Java SDK if appropriate. See “Payflow SDK” on
page 49 for more information about the SDKs.
What code changes are required when migrating from a previous Payflow SDKs to this
service?
The Payflow HTTPS service uses the same name-value-pair parameters or XMLPay schema
as found in the current SDKs. The the only code change needed is the way you communicate
with the Payflow servers. Instead of using an SDK to send the data, you will use the methods
- 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
Powiązane produkty i podręczniki dla Bramy / kontrolery PayPal Gateway - 2013
(124 strony)© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.030 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji