The recurring workflow looks bad and is confusing. We're going to need some hand holding if we expect to progress beyond the magic parameters level.

This is as good as could get it for now:
First screen:

Second screen (pt 1):

Second screen (below the fold):

Problems I've noticed:

• There is no clear explanation of the billing terms. The only place "Monthly" is mentioned is in the text we provide.
• The second screen doesn't add any more information about the subscription, or emphasize that it is not one-time.
• The OK button on the second page is below the fold.
• The page style is not consistent with one-time Express Checkout.

@Ppena you might want to take a look at the comment above...

I got some helpful feedback from Marshal C, case #3207220, but we're still in about the same position as before, just better informed. Making a one-time donation plus a subscription that starts in a month is indeed the semi-official workaround. The workflow is segmented in various ways, and the Express Checkout "new" workflow is not fully rolled out. This means that Marshal was able to get to the new recurring workflow using *exactly* the same API string that gave me the older workflow. Hopefully, the live servers will give us another chance to hit the new workflow, because we at least have to test it before risking donors potentially getting into that workflow before us.

In other words, let's go ahead with internal testing for what we have now, and evaluate how that behaves.

Note to self: Marshal had me remove the ITEMCATEGORY param, make that change in code.

Change 288253 had a related patch set uploaded (by Awight):
Stop sending item category

https://gerrit.wikimedia.org/r/288253

Most of the support is in this patch:
https://gerrit.wikimedia.org/r/#/c/287036/7

Change 287036 merged by jenkins-bot:
PayPal Express Checkout: recurring

https://gerrit.wikimedia.org/r/287036

Change 288253 merged by jenkins-bot:
Stop sending item category

https://gerrit.wikimedia.org/r/288253

Kicking back into the backlog--recurring subscriptions failed during the feasibility test, so we need to investigate and fix the issues.

One of our Japanese testers tried this method on the 25th, here is a screenshot of what the attempt looks like @ PayPal, fyi. Nothing reached Civi from this.

@DStrine
Let's ice this one until after ActiveMQ?

We still need to feed a real recurring charge (first and second!) through, and record exactly what data comes back in through the listener and audit parser.

We're never reaching the CreateRecurringPaymentsProfile call, so the recurring flag is absent in the response processor.

We're still getting the old workflow when creating a recurring subscription. Need to talk to our rep again.