2007
Table Of Contents
- Name-Value Pair API Reference for Germany
- Preface
- Overview
- Accepting PayPal in Express Checkout
- Basic Checkout with PayPal
- Support giropay and electronic funds transfer
- Controlling the Shipping Address Using SetExpressCheckout
- Changing the Language on the PayPal Login Page Using SetExpressCheckout
- Changing the Logo on the PayPal Pages Using SetExpressCheckout
- Form-Filling Your Payment Review Page Using GetExpressCheckoutDetails
- Making a Sale Using DoExpressCheckoutPayment
- Changing the URL for IPN Using DoExpressCheckoutPayment
- Including Line Item Details Using DoExpressCheckoutPayment
- Including Subtotals Using DoExpressCheckoutPayment
- Updating Order Details Using DoExpressCheckoutPayment
- Updating the Shipping Address Using DoExpressCheckoutPayment
- Back-Office Administration
- NVP API Method and Field Reference
- Error Message Reference
- NVP API Web Samples
- The Java SDK
- The ASP.NET SDK
- Country Codes
- Index
The Java SDK
Profiles
106 April 2007 Name-Value Pair API Developer Guide and Reference
Profiles
Before the SDK can be used, it must know the profile of the user accessing its services. A
profile is a collection of information about a merchant or developer who uses the PayPal SDK.
An API profile is associated with API Services and includes:
z A PayPal API username and password.
z If you are using API certificates, the path to the API certificate in P12 format and the
private key password to that certificate.
z If you are using API signatures, the signature string.
z The optional name of a third-party who authorizes the caller to invoke PayPal APIs on his
behalf. This third-party is called a subject
z The PayPal environment for processing API calls: live or sandbox.
An EWP profile is associated with EWP Services includes:
z The path to the merchant’s local copy of that public certificate
z The private key password for that public certificate
z The path to a merchant’s private key file for digitally signing data
z The URL to which the button form POSTs
z The optional URL of a payment button image. The default is PayPal’s standard Buy Now
button.
For more information about how EWP works, see the Website Payments Standard Integration
Guide, available at
https://www.paypal.com/en_US/pdf/PP_WebsitePaymentsStandard_IntegrationGuide.pdf.
Overview to Profile-related Classes
The primary interfaces and classes for SDK profiles are described in Table D.5, “Interface and
Classes for SDK Profiles,” on page 106
TABLE D.5 Interface and Classes for SDK Profiles
Interface/Class Descriptions
APIProfile interface This interface defines the basic information that PayPal needs to
know about a user of the PayPal Web Service APIs. Developers must
create an instance of APIProfile for each account that accesses the
APIs. For single-merchant developers, only a single APIProfile
instance is needed. PayPal provides two implementation classes
suitable for the needs of most SDK developers: CertificateAPIProfile
and SignatureAPIProfile. However, you are free to write a custom
implementation if you need additional functionality the default
classes do not offer.