PayPal Website Payments Pro - 2007 - HTTPS Interface Uživatelská příručka Strana 13

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 14
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 12
HTTPS Interface Developer’s Guide August 2007 11
Reference
Common problems
X-VPS-REQUEST-ID is the same ID sent in the transaction request.
N OTE: Ignore the X-VPS-RESPONSE-ID. It will be removed at a later time.
Transaction response body
The transaction response body contains the response to the request. The following is an
example response body in NVP format:
RESULT=0&PNREF=V53A0A30B542&RESPMSG=Approved&AUTHCODE=882PNI&
AVSADDR=X&AVSZIP=X&IAVS=X&PREFPSMSG=No Rules Triggered&
POSTFPSMSG=No Rules Triggered
Common problems
Problem Description
Result code 1 User authentication error. Can be caused by:
z Invalid login information or IP restrictions on the account. Verify that
there are no IP restrictions in PayPal Manager.
z Verify USER, VENDOR, PARTNER, and PASSWORD. Remember that
USER and VENDOR are both the merchant login ID unless a Payflow
Pro USER was created. All field values are case-sensitive.
z Not appending /transaction to the host URL. This requirement
will be removed in the future.
Result code 26 Verify USER, VENDOR, PARTNER, and PASSWORD. Remember that USER
and VENDOR are both the merchant login ID unless a Payflow Pro USER
was created. All field values are case-sensitive.
No response received Usually caused by posting to an incorrect host URL.
Zobrazit stránku 12
1 2 ... 8 9 10 11 12 13 14

Komentáře k této Příručce

Žádné komentáře