Developer's Guide

Adaptive Payments Developer Guide August 7, 2012 281
1.3.0 Features
Changes to the Pay API Operation for Version 1.3.0
Changes to PayRequest Message
Field Description
ClientDetails.applicationId This field is no longer required. The application ID is passed in
a new HTTP header. For information, refer to the Specifying
Application and Device Information section.
ClientDetails.ipAddress This field is no longer required.
fundingConstraint New field:
ap:FundingConstraint
Specifies a list of allowed funding types for the payment. This
list can be in any order. If this field is omitted, the payment can
be funded by any funding type that is supported by Adaptive
Payments.
NOTE: This feature is available for applications with special
permission level.
FundingTypeList.fundingTypeInfo New field:
ap:FundingTypeInfo
Specifies a list of allowed funding types for the payment. This
list can be in any order. If this field is omitted, the payment can
be funded by any funding type that is supported by Adaptive
Payments.
NOTE: This feature is available for applications with special
permission level.
fundingType New field:
xs:string
Specifies the allowed funding types that can be used as
funding sources for the payment.
Allowable values are:
 ECHECK – Electronic check
 BALANCE – PayPal account balance
 CREDITCARD – Credit card
NOTE: This feature is available for applications with special
permission level.
logdefaultShippingAddress This field has been removed. Pay requests that use this field
are executed, but the logdefaultShippingAddress is
ignored.
Receiver.paymentType New field:
xs:string
The transaction subtype for the payment. Allowable values
are:
 GOODS – This is a payment for goods
 SERVICE – This is a payment for services (default)