![]() The value you use should match the intent value in the API call. The funds are captured immediately while the buyer is present on your site. If you're integrating the JavaScript SDK with an older API like the Orders V1 REST API or one of our NVP/SOAP solutions, you can use the following options. Intent options when integrating with older APIs Used along with vault=true and createBillingAgreement to specify this is a billing (without purchase) transaction. ![]() Used along with vault=true to specify this is a subscription transaction. The funds are authorized immediately and then reauthorized or captured later. ![]() This could be the case if you build a cart app, which enables merchants to dynamically set a client ID to add PayPal to their store. If your client-id changes dynamically, you must pass an integration date, which ensures that no breaking changes are made to your integration.If your client-id does not change, you can safely omit the integration-date parameter and the PayPal script guarantees backward compatibility.Your site does not get any backward incompatible updates made to the PayPal script after the specified integration-date, or after the date your client-id was created, if you do not pass the integration-date parameter.You do not need to change integration-date to enable new features.Your site automatically gets any backward-compatible changes made to the PayPal script.This parameter ensures backwards compatibility. Defaults to the date when your client ID was created, and if passed, reflects the date that you added the PayPal integration to your site. ![]() The integration date of the script, passed as a YYYY-MM-DD value. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |