PayPal Name-Value Pair API - 2009 Guia do Utilizador descarregar pdf (Página 127)

Name-Value Pair API Developer Guide 08 April 2009 127

Recurring Payments and Reference Transactions API Operations

GetBillingAgreementCustomerDetails API

Billing Agreement Details Fields

SetCustomerBillingAgreement Response

SetCustomerBillingAgreement Response Fields

GetBillingAgreementCustomerDetails API

Obtain information about a billing agreement’s PayPal account holder.

z “GetBillingAgreementCustomerDetails Request” on page 128

z “GetBillingAgreementCustomerDetails Response” on page 128

Field Description

L_BILLINGTYPEn (Required) Type of billing agreement.

For recurring payments, this field must be set to RecurringPayments. In this case,

you can specify up to ten billing agreements.

NOTE: Other defined values are not valid.

L_BILLINGAGREEMENTD

ESCRIPTIONn

Description of goods or services associated with the billing agreement, which is

required for each recurring payment billing agreement.

PayPal recommends that the description contain a brief summary of the billing

agreement terms and conditions. For example, customer will be billed at “9.99 per

month for 2 years”.

Character length and limitations: 127 single-byte alphanumeric bytes.

L_PAYMENTTYPEn (Optional) Specifies type of PayPal payment you require for the billing agreement.

z Any

z InstantOnly

NOTE: For recurring payments, this field is ignored.

L_CUSTOMn (Optional) Custom annotation field for your own use.

NOTE: For recurring payments, this field is ignored.

Character length and limitations: 256 single-byte alphanumeric bytes.

Field Description

TOKEN A unique time-stamped token, which uniquely identifies this transaction for

subsequent API calls.

NOTE: The token expires after three hours.

Character length and limitations: 20 single-byte characters.

1 2 ... 122 123 124 125 126 127 128 129 130 131 132 ... 242 243

Sem comentários

PayPal Name-Value Pair API - 2009 Guia do Utilizador Página 127