Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert Vault with Purchase on Client #173

Merged
merged 3 commits into from
Aug 3, 2023
Merged

Conversation

KunJeongPark
Copy link
Collaborator

Summary of changes

  • Reverting implementation of vault with purchase on the client.
    As of now, plan is for merchant to implement this on their server side
    because of issues with a merchant integration pattern that requires authentication to be
    passed from server side

Checklist

  • [ x] Added a changelog entry

Authors

@KunJeongPark KunJeongPark requested a review from a team as a code owner August 1, 2023 21:54
@KunJeongPark KunJeongPark changed the title revert vault with purchase on client Revert Vault with Purchase on Client Aug 1, 2023
Copy link

@Holsta0822 Holsta0822 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Collaborator

@jaxdesmarais jaxdesmarais left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also want to remove the Vault.swift file as well as the vault objects from ConfirmPaymentSourceRequest

@KunJeongPark
Copy link
Collaborator Author

KunJeongPark commented Aug 2, 2023

Hi @jaxdesmarais I think vault objects are removed from ConfirmPaymentSourceRequest. Good catch on the Vault.swfit
Addressed in commit ddb7e64

@KunJeongPark KunJeongPark merged commit 257df31 into main Aug 3, 2023
4 checks passed
@KunJeongPark KunJeongPark deleted the revertVaultWithPurchase branch August 3, 2023 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants