|
|
|
|
8/6/2015 6:35:10 PM
OnSuccessPaymentControlResult and OnFailurePaymentControlResult results
|
8/6/2015 6:34:20 PM
total ordering creating unreliable ordering of the billing events (and leading to wrong dryRun invoice result)
|
|
|
8/5/2015 9:21:49 PM
lots of switches (hard to debug). See #351
|
|
|
8/5/2015 8:27:32 PM
payment attempts until we reach the enteringState callback (that is
after control plugin had the chance to remove sensitive info, if any).
|
8/5/2015 7:51:54 PM
api calls. The semantics is the same as the one we chose for the other parameters that can be adjusted (paymentMethodId, amount, ...),
where we update the value at each iteration (for each plugin) when it is not null. For plugin properties, it means each plugin should either return null (nothing to adjust) or only modify/delete/update
the value it cares about.
|
|
|
