Skip to content

Conversation

@Jon-edge
Copy link
Collaborator

@Jon-edge Jon-edge commented Oct 30, 2025

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

Note

Disables ach payment type for banxa in ramp constraints.

  • Ramps constraints (src/plugins/ramps/rampConstraints.ts):
    • Banxa: Block ach payment type via new constraint in constraintGenerator.

Written by Cursor Bugbot for commit 797b21d. This will update automatically on new commits. Configure here.


Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 89 to 96
//
// Banxa
//

// Disable Banxa completely
if (params.rampPluginId === 'banxa') {
yield false
}

Choose a reason for hiding this comment

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

P1 Badge Constraint still lets Banxa hit network

Adding yield false disables Banxa only at the constraint level, but the Banxa plugin’s checkSupport and fetchQuotes both call fetchProviderConfig() before validateRamp* is invoked. With Banxa supposed to be offline, these calls still hit Banxa’s APIs and will throw, and useRampQuotes surfaces those errors to the user even though the provider is meant to be disabled. The constraint should short‑circuit before any network work or the plugin should be omitted entirely so that disabling Banxa does not keep producing visible errors or network traffic.

Useful? React with 👍 / 👎.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

With the current change, Banxa will be filtered out by supported-plugins before quotes run, so no Banxa errors are shown to the user.

Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't the ask to only disable ACH for banxa not banxa completely?

Comment on lines 89 to 96
//
// Banxa
//

// Disable Banxa completely
if (params.rampPluginId === 'banxa') {
yield false
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't the ask to only disable ACH for banxa not banxa completely?

@Jon-edge
Copy link
Collaborator Author

Yep, verified that the task is only to disable ACH due to bank workflow issues

// Banxa
//

// Disable Banxa completely
Copy link
Contributor

Choose a reason for hiding this comment

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

Change comment to reflect the fixup!

@Jon-edge Jon-edge merged commit bd585b7 into develop Oct 31, 2025
2 of 3 checks passed
@Jon-edge Jon-edge deleted the jon/disable-banxa branch October 31, 2025 17:22
@Jon-edge Jon-edge changed the title Disable Banxa Disable Banxa ACH Oct 31, 2025
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