Change Details

We're looking into a v.zero (Braintree) integration, but for global currencies will be using the NVP interface anyway, so that should be developed first. https://developer.paypal.com/docs/classic/express-checkout/gs_expresscheckout/ This task is complete when we can call and test the API, and a workflow is in place to interact with the donor.

We will be using the name value pair (NVP) integration because it's mature and supports the longest list of currencies, including Japanese accounts. https://developer.paypal.com/docs/classic/express-checkout/gs_expresscheckout/ https://developer.paypal.com/docs/classic/api/country_codes/ This EC NVP support should be written as a new payment method under the PayPal adapter. This is a redirect method, so the only form is an interstitial in case of an invalid amount. This task is complete when we can call and test the API, and a workflow is in place to interact with the donor. Followup work: We're looking into a v.zero (Braintree) integration once that is mature and as it supports currencies.

We're lookWe will be using into a v.zero (Braintreethe name value pair (NVP) integration, but for global currencies will be using the NVP interface anyway because it's mature and supports the longest list of currencies, so that should be developed firstincluding Japanese accounts. https://developer.paypal.com/docs/classic/express-checkout/gs_expresscheckout/ https://developer.paypal.com/docs/classic/api/country_codes/ This EC NVP support should be written as a new payment method under the PayPal adapter. This is a redirect method, so the only form is an interstitial in case of an invalid amount. This task is complete when we can call and test the API, and a workflow is in place to interact with the donor. Followup work: We're looking into a v.zero (Braintree) integration once that is mature and as it supports currencies.