2007

The ASP.NET SDK
Profiles
114 April 2007 Name-Value Pair API Developer Guide and Reference
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 E.5, “Summary of
ASP.NET SDK Profile-related Interfaces and Classes.”
TABLE E.5 Summary of ASP.NET SDK Profile-related Interfaces and Classes
Interface/Class Description
IAPIProfile 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 IAPIProfile for each account that accesses the
APIs. For single-merchant developers, only a single IAPIProfile
instance is needed. PayPal provides a default implementation class
called DefaultAPIProfile suitable for the needs of most SDK
developers. However, you are free to write a custom implementation
if you need additional functionality the default class does not offer.
ProfileFactory class This class creates the IAPIProfile object. It contains static methods
that handle the instantiation and construction of profile objects.
EWPProfile interface This interface defines the basic information that PayPal needs to
know about a user of PayPal’s Encrypted Website Payments (EWP)
service. Developers must create an instance of EWPProfile for each
account that generates the encrypted button code; for single-merchant
users this will just be a single instance). PayPal provides a basic
implementation class called DefaultEWPProfile suitable for the needs
of most SDK developers. However, you are free to write a custom
implementation if you need functionality the default class does not
offer.