-
Notifications
You must be signed in to change notification settings - Fork 22
Single to monthly payment upsell #26
Comments
Agree option 2 is best user option so need to understand both implication of using Vaulting and priority of upsell to MoFo. |
Not clear where the Upsell screen appears in the process as it appears to be a 2 step thank you for single payments i.e. Upsell (get info for ongoing payment) and then thank you (get email address). There is a risk here of significant drop off and not getting the email address. Need clarity fo the priority of the email address over Upsell for long term engagement. |
@philwakefield I assume you meant option 1 in your first comment? I believe we had a conversation elsewhere, but I confirmed with Will that the priority here is definitely the upsell. A lot of our donations come from our mailing list already, so many of the donors won't even see the ask for newsletter subscriptions. (As we hide the ask if someone comes in with a query string of |
I have been doing some due diligence on this while setting up the basic integrations. I don't see any issues with card upsell, but for Paypal a separate auth flow is required if you want to be able to set up a monthly subscription for a customer. Here is what the donor sees when making a single payment: And here is what they see if we are setting up a subscription: it is possible to use the latter flow for single payments (in which case upsell is easy), but this means the donor is giving consent for recurring payments even if they only intend to make a single payment. I think there is a risk of upsetting people with that. The alternative would be to ask the user to go through another auth flow at the point of upsell. They would already be logged in to Paypal at this point, so it wouldn't be a very lengthy process. |
I double-checked my gut and confirmed with Will. Go with the alternative you presented: Different flow based on OTG and recurring, with a second auth flow for upsell. |
@alanmoo on the current site, monthly upsell is only displayed for a small number of currencies (those with |
This was partially due to the fact that we could only accomplish upsells with Stripe, combined with effort to put it in place for other currencies. From Will:
|
From what I can see Braintree doesn't document any restrictions on which currencies you can set up subscriptions for - it's just that you have to manually set up a plan for each currency that you want to support. So technically it is possible for us to support all currencies. @alanmoo what is your preference at this stage? Should we support all or limit to the ones listed by Will above? |
Support all, if it's no more work than putting in default amounts. (Do you need those or is that configurable in an admin panel? Either way, I'll get that info for you.) |
The default amounts are currently hard-coded. Rather than having to define upgrade amounts for every single currency, I would suggest that we define a sensible set of defaults (i.e., for single payment of X, suggest monthly donation of Y, regardless of currency), and use these for any currency where |
Sounds good. Will is working on identifying what currencies from the list in #72 need overrides. |
Amounts are here, I'm happy to dump this into a JSON file or admin panel myself though, if you've got somewhere to point me. |
@alanmoo I'm bringing the discussion on #97 here. Regarding minimum amounts, can you confirm:
In either case I think we will need to specify a threshold for all currencies - or skip upsell entirely for those currencies where we don't have this specified. Would it be feasible for you to extend the upsell spreadsheet to include all the currencies that are listed here? |
In addition to the above query @alanmoo , are there any other situations in which upsell should be skipped? |
Hey @solarissmoke ... |
@solarissmoke on B above, that's now filled out, here. |
Implementation of a workflow to enable donors to set up a monthly payment having just completed a single payment.
Technical notes
Braintree requires a slightly different approach for setting up subscriptions - specifically creating subscriptions requires vaulting of a payment method.
The options here are:
(2) obviously makes for poor user experience, so I think (1) is the preferred option - we just need to investigate what the implications are of vaulting one-off payments (if any) and whether the Paypal flow for vaulting is more involved (if so there may be a more nuanced tradeoff that we need to make a decision on).
The text was updated successfully, but these errors were encountered: