Page MenuHomePhabricator

Figure out LATAM recurring
Closed, ResolvedPublic1 Estimated Story Points

Description

We might be able to do recurring through LATAM processor, but I'm thinking we'll need an API change to support this. Currently, the create subscription call needs to be signed using WMF's secret key, but contains cardholder data. This would affect our PCI level, cos the cardholder data would go through our server.

Ideally, we would make a call to AP that generates a temporary signing token, then provide that token to the client. The client would connect directly to AP. That might be impossible, however. The next best solution would require a larger coding effort: encrypt the cardholder data, transmit from the client to WMF servers, then send encrypted to AP.

Event Timeline

awight raised the priority of this task from to Medium.
awight updated the task description. (Show Details)
awight subscribed.

Waiting for a response from AP. I suggested the following changes:

  • New API that is run from the merchant's server, which returns a one-time token to give to the client.
  • New API to run Save Card from the client, using the one-time token and returning the cc_token to be stored at the merchant's end.
atgo renamed this task from Figure out AstroPay recurring to Figure out LATAM recurring.Feb 2 2015, 8:43 PM
atgo updated the task description. (Show Details)

They responded, to say that they are already planning this feature, but the timeline is TBD. Existing APIs are not appropriate to run from the client side.

awight moved this task from Pending Deployment to Done on the § Fundraising Sprint the Cure board.
awight edited a custom field.

They're estimating "Q3" for this feature, which we assume means July-Aug 2015. We shouldn't be the first adopters.

atgo subscribed.