You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 24, 2020. It is now read-only.
Why must the inputs be bound to $scope.number, $scope.expiry and $scope.cvc? It would be very nice if they could be bound to any $scope property. For example my scope already has so many properties and I would like to group the stripe ones under $scope.stripe. Is this possible?
The text was updated successfully, but these errors were encountered:
not sure if this is still relevant for someone, but in case:
you can achieve using $scope.stripe if you change in angular-payments.js in the method _getDataToSend the for(i in possibleKeys){ part to (I guess this is quite dirty but works for me):
Why must the inputs be bound to $scope.number, $scope.expiry and $scope.cvc? It would be very nice if they could be bound to any $scope property. For example my scope already has so many properties and I would like to group the stripe ones under $scope.stripe. Is this possible?
The text was updated successfully, but these errors were encountered: