Change Details

We might be able to do recurring through AstroPay, 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.

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.

We might be able to do recurring through AstroPayLATAM 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.