PayPal Website Payments Pro - 2009 - HTTPS Interface Guide de l'utilisateur télécharger pdf (Page 13)

HTTPS Interface Developer’s Guide April 2009 13

Reference

Common Problems

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

N OTE: For additional information on transaction result values, see the appropriate developer’s

guide: Payflow Pro Developer’s Guide or Website Payments Pro Payflow Edition

Developer’s Guide.

Problem Description

Result value 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

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 value 26 Verify USER, VENDOR, PARTNER, and PASSWORD. Remember that USER

and VENDOR are both the merchant login ID unless a Payflow a was

created. All field values are case-sensitive.

No response received Usually caused by posting to an incorrect host URL.

1 2 ... 8 9 10 11 12 13 14

Pas de commentaire

PayPal Website Payments Pro - 2009 - HTTPS Interface Guide de l'utilisateur Page 13