Charge a user using savec CC (Stripe) and Privacy rules

Bugs
1

Hello,
I am experiencing a weird bug using the “charge a user with a saved CC” action.
The action is triggered in a workflow by the payee (not the charged user).
If the payee can access all fields of the charged user, the transaction succeed.
If I set some privacy rules on the “User” data type, for instance to restrict access to some fields, the transaction fails with the following error:

“Désolé, cet utilisateur n’a pas indiqué les informations de sa carte de paiement. Il ne peut pas être débité”
in english: “Sorry, this user has not given his credit card information. He cannot be charged.”

However, the user does have credit card information, since it work when the payee has access to all fields.

In the privacy tab, I see nowhere how to set access or not to Stripe fields. Is that normal ?
Did someone experienced a similar issue ?

Thanks !

2

I confirm this is a bug that can be easily reproduced, I just filled a bug report.
I wonder if this was caused bu the recent update allowing to handle multiple credit cards?

Update : for other users experiencing the same issue, in the privacy rules you must give access to Social Networks to get it working again. Not sure if this is exected or not since a credit card is not really related to social networks.

2 Likes
3

This topic was automatically closed after 14 days. New replies are no longer allowed.