Skip to content

fix: Remove Visa Checkout#1653

Open
buzzamus wants to merge 4 commits into
mainfrom
remove-visa-checkout
Open

fix: Remove Visa Checkout#1653
buzzamus wants to merge 4 commits into
mainfrom
remove-visa-checkout

Conversation

@buzzamus

Copy link
Copy Markdown
Contributor

Summary of changes

  • This PR removes the Visa Checkout module from the SDK since it has officially been archived and no longer in use

AI Usage

Which AI Agent Was Used?

  • Copilot
  • Claude
  • Other (Type Name Here)

How was AI used?
Used Claude to find and remove the majority of the Visa Checkout code. I also used Claude to verify there were tests still in place for if a configuration response has Visa Checkout enabled that we will simply ignore. Finally, Claude was used to find a bug where the project would not build after everything seemed to be safely deleted. It turns out one of the payment buttons was actually pointing to a Visa Checkout "Blue" color reference instead of the correct one (They were the same color, so no change)

Estimated AI Code Contribution

  • less than 30%
  • 30 - 60%
  • 60 - 100%

Checklist

  • Added a changelog entry
  • Tested and confirmed payment flows affected by this change are functioning as expected

Authors

List GitHub usernames for everyone who contributed to this pull request.

@buzzamus
buzzamus requested a review from a team July 17, 2026 17:02
@buzzamus
buzzamus requested a review from a team as a code owner July 17, 2026 17:02
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities found.

Scanned Files

  • settings.gradle

@saralvasquez saralvasquez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If we are removing the visa checkout module all together is it worth deprecating values that can't be used instead of removing them?

Comment thread Demo/src/main/res/layout/fragment_ui_components.xml
@buzzamus

Copy link
Copy Markdown
Contributor Author

If we are removing the visa checkout module all together is it worth deprecating values that can't be used instead of removing them?

I sort of took 2 approaches: delete where we could delete and deprecate where we needed to.

So, for example the VisaCheckout module was fully deleted since it is never actually released and published. For the Configuration properties those were left and given a @Deprecated tag to avoid breaking any integrations where merchants might be using any values in there

@saralvasquez

Copy link
Copy Markdown
Contributor

If we are removing the visa checkout module all together is it worth deprecating values that can't be used instead of removing them?

I sort of took 2 approaches: delete where we could delete and deprecate where we needed to.

So, for example the VisaCheckout module was fully deleted since it is never actually released and published. For the Configuration properties those were left and given a @Deprecated tag to avoid breaking any integrations where merchants might be using any values in there

Ah I didn't notice that commented out publishing for VisaCheckout. This approach makes sense to me!

@saralvasquez saralvasquez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🎉

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.

3 participants