PayPal Gateway - 2013 Betriebsanweisung Seite 60
- Seite / 256
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Submitting Credit Card Transactions
Core Credit Card Parameters
6
60 07 February 2013 Gateway Developer Guide and Reference
EXPDATE (Required) Expiration date of the credit card. For example, 1215 represents
December 2015.
Limitations: mmyy format
AMT (Required) Amount (Default: U.S. based currency).
Limitations: Specify the exact amount to the cent using a decimal point. For example,
use 34.00 not 34. Do not include comma separators. For example, use 1199.95 not
1,199.95. Your processor or Internet Merchant Account provider may stipulate a
maximum amount.
10 numeric characters plus decimal
COMMENT1 (Optional) Merchant-defined value for reporting and auditing purposes.
Limitations: 128 alphanumeric characters
COMMENT2 (Optional) Merchant-defined value for reporting and auditing purposes.
Limitations: 128 alphanumeric characters
CVV2 (Optional) A code printed (not imprinted) on the back of a credit card. Used as partial
assurance that the card is in the buyer’s possession.
Limitations: 3 or 4 digits
RECURRING (Optional) Identifies the transaction as recurring. It is one of the following values:
Y – Identifies the transaction as recurring.
N – Does not identify the transaction as recurring (default).
This value does not activate the Payflow Recurring Billing Service API. If the
RECURRING parameter value is Y in the original transaction, this value is ignored
when forming credit, void, and force transactions. If you subscribe to the Payflow
Fraud Protection Services:
To avoid charging you to filter recurring transactions that you know are reliable,
the fraud filters do not screen recurring transactions.
To screen a prospective recurring customer, submit the transaction data using
PayPal Manager’s Manual Transactions page. The filters screen the transaction in
the normal manner. If the transaction triggers a filter, follow the normal process to
review the filter results.
NOTE: If your transaction is declined and the PAYMENTADVICECODE response
parameter is supported by your processor, a PAYMENTADVICECODE value is
returned representing the reason that the transaction was declined. Obtain the
meaning of PAYMENTADVICECODE values from your acquiring bank.
Character length and limitations: 1 alpha character
Parameter Description
- 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
Verwandte Produkte und Handbücher für Gateways / Controller PayPal Gateway - 2013
(124 Seiten)© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.048 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern