fix(payment-methods): Fix provider payment methods #1795
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Stripe payment methods were automatically overridden by Lago.
Steps to reproduce:
Create a customer via API with stripe as the payment provider and "provider_payment_methods": ["card","sepa_debit"];
Update the customer account via API by sending only external_id and a random field, such as city (do not send anything related to billing_configuration);
In the API response, you can see that Lago automatically removed "sepa_debit" from the list of available payment methods.
Expected behaviour: when updating a customer, only the attributes included in the request payload should be modified.
Description
This PR fixes updating provider customer specifically the payment methods when no payment method is sent.