I have been tweaking around with CSK. Client has WebPayments Pro and i am working through the steps. I had a digital cert created by PP and installed on DASP. I am working through the config and trying to make sense of it all. <PayPalProSettings isActive="true" useSandbox="false" APIUserName="*" APIPassword="*" certificateName="csk.pfx" certificatePassword="*"/> <PayPalStandardSettings isActive="false" useSandbox="true" businessEmail="*" PDTID="*" /> <PaymentService acceptCreditCards="true" defaultProvider="PayPalPaymentProvider"> <providers> <clear /> <add serviceUserName="*" servicePassword="commerce" sslCertFile="csk.pfx" sslCertPassword="*" merchantID="*" currencyCode="USD" name="PayPalPaymentProvider" type="Commerce.Providers.PayPalPaymentProvider" /> </providers> </PaymentService> So this is what is in the config... Of course * are actual values. I am curious to know what the certificateName attributeof the PayPalProSettingsand the sslCertFile attribute under the PaymentServiceshould be set to... What is required here and what isn't? Any help would be greatly appreciated. BZ
The new version of "Dash Commerce Starter Kit" (2.2) corrected this for me. Dash is the new name of the CSK... The certificateName attribute is droped/ deprecated. RA