Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes replace the old Sources and Token based APIs from Stripe with the new and recommended Payment Methods API. This new API will handle all card based interaction and in the future also new payment methods like IDEAL, Bancontact, etc.
Basically all card-based methods and its related class were replayed by payment method methods (wording djeez) and a new PaymentMethod class. New tests for these methods were added.
There's one legacy backwards compatibility that's maintained and that's for the defaultPaymentMethod method. This will return an instance of a Stripe\Card or Stripe\BankAccount source if no default payment method was found. This way, older apps migrating to the new Cashier release, can still use these objects to interact with their apps.
The subscription creation process now also requires a payment method instead of a Stripe token.
Developers will need to update their Stripe JS integration to make use of the new payment method apis.
Closes #649