Routing Amex to the legacy gateway breaks payments via an unchanged capability the diff can't see
Tier 1 easy go · cross-file · authored, execution-grounded case
Ground-truth defects
RouteCard() is changed to send Amex to the Adyen gateway instead of Stripe — a plausible routing tweak with no local smell. But the unchanged consumer capabilities.go records that this service's Adyen integration only handles Visa and Mastercard, so Amex payments routed there can no longer be processed. Whether the legacy gateway supports Amex is a codebase-specific fact stated only in the unchanged Supports(); a diff-only reviewer has no basis to know the reroute is wrong.
The change under review
diff
@@ -21,7 +21,7 @@ const ( func RouteCard(c Card) Gateway { switch c { case Amex: - return GatewayStripe + return GatewayAdyen default: return GatewayStripe }
Leaderboard for this case
easy · 8 of 9 bots fully caught it (89% solve rate) · 89% avg coverage.
| # | Bot | Result | Caught | Coverage | Findings | False alarms |
|---|---|---|---|---|---|---|
| 1 | Claude Code (Opus 5.5) | solved | 1/1 | 100.0% | 1 | 0 |
| 2 | cursor | solved | 1/1 | 100.0% | 1 | 0 |
| 3 | Drape (Deep Review) | solved | 1/1 | 100.0% | 1 | 0 |
| 4 | Drape (Review) | solved | 1/1 | 100.0% | 1 | 0 |
| 5 | greptile | solved | 1/1 | 100.0% | 1 | 0 |
| 6 | Mjolnir (Opus 5.5) | solved | 1/1 | 100.0% | 2 | 0 |
| 7 | Mjolnir (Sonnet 5.5) | solved | 1/1 | 100.0% | 2 | 0 |
| 8 | qodo | solved | 1/1 | 100.0% | 1 | 0 |
| 9 | Cubic | miss | 0/1 | 0.0% | 0 | 0 |
Bot results
Claude Code (Opus 5.5) · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (1)
RouteCard now sends Amex cards to GatewayAdyen, but capabilities.go says Adyen can't take Amex yet: Supports(GatewayAdyen, Amex) returns false because Adyen's Amex onboarding isn't finished. Every Amex payment will go to a gateway that can't process it, so those payments will be rejected or fail. Before this change, Amex went to Stripe, which accepts every card type. Keep Amex on Stripe until Adyen supports Amex, or have RouteCard check Supports() and fall back to Stripe.
Cubic · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✗ | — |
raw comments (1)
<!-- cubic:review-summary:start -->
**No issues found** across 1 file
<!-- cubic:review-summary:end -->
<sub>[Re-trigger cubic](https://www.cubic.dev/action/re-review/pr/drape-io/crbench-cubic-2026-09/1/ai_pr_review_github_delivery_f0515618dcc793ff681865956be3cf3bed08b120806bd5a8042c034d7921e16d?returnTo=https%3A%2F%2Fgithub.com%2Fdrape-io%2Fcrbench-cubic-2026-09%2Fpull%2F1)</sub>
<!-- cubic:review-post:ai_pr_review_github_delivery_f0515618dcc793ff681865956be3cf3bed08b120806bd5a8042c034d7921e16d:a35949101dbb259fa720be9650b4bbd9c9d60981:db0ba33d-fa2e-53f2-a45c-627ad5fcec10 -->
cursor · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (2)
### Amex routed to unsupported Adyen
**High Severity**
<!-- DESCRIPTION START -->
`RouteCard` now sends `Amex` to `GatewayAdyen`, but `Supports` still treats Adyen as Visa/Mastercard only and documents that Amex onboarding is not done. Amex charges would go to a processor this service does not accept for that card type.
<!-- DESCRIPTION END -->
<!-- BUGBOT_BUG_ID: e462117f-b5b6-41e5-baf5-f9899b7c4f40 -->
<!-- LOCATIONS START
gateway.go#L22-L24
LOCATIONS END -->
<div><a href="https://cursor.com/open?link=eyJ2ZXJzaW9uIjoxLCJ0eXBlIjoiQlVHQk9UX0ZJWF9JTl9DVVJTT1IiLCJkYXRhIjp7InJlZGlzS2V5IjoiYnVnYm90OjZiYTkzNDQzLWZhYjEtNDQ0Zi1iMjNmLTc5NGI3NmNjNTY2ZCIsImVuY3J5cHRpb25LZXkiOiItTVluWU9obzJkNHh1VTlkN00zRTNPeEtnckFvWU05MzVmeEdIWGFrNUxZIiwiYnJhbmNoIjoidDEtZ28tcm91dGUtYW1leC10by11bnN1cHBvcnRpbmctZ2F0ZXdheSIsInJlcG9Pd25lciI6ImRyYXBlLWlvIiwicmVwb05hbWUiOiJjcmJlbmNoLWN1cnNvci0yMDI2LTA5IiwicHJvdmlkZXIiOiJnaXRodWIifX0" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/fix-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/fix-in-cursor-light.png"><img alt="Fix in Cursor" width="115" height="28" src="https://cursor.com/assets/images/fix-in-cursor-dark.png"></picture></a> <a href="https://cursor.com/agents?link=eyJ2ZXJzaW9uIjoxLCJ0eXBlIjoiQlVHQk9UX0ZJWF9JTl9XRUIiLCJkYXRhIjp7InJlZGlzS2V5IjoiYnVnYm90OjZiYTkzNDQzLWZhYjEtNDQ0Zi1iMjNmLTc5NGI3NmNjNTY2ZCIsImVuY3J5cHRpb25LZXkiOiItTVluWU9obzJkNHh1VTlkN00zRTNPeEtnckFvWU05MzVmeEdIWGFrNUxZIiwiYnJhbmNoIjoidDEtZ28tcm91dGUtYW1leC10by11bnN1cHBvcnRpbmctZ2F0ZXdheSIsInJlcG9Pd25lciI6ImRyYXBlLWlvIiwicmVwb05hbWUiOiJjcmJlbmNoLWN1cnNvci0yMDI2LTA5IiwicHJOdW1iZXIiOjEsImNvbW1pdFNoYSI6IjBhYjcwMTMwMDdlYzBjNGNlMGViOTAwNDNmYmYyODU3MGVlMzRmZDAiLCJwcm92aWRlciI6ImdpdGh1YiJ9fQ" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/fix-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/fix-in-web-light.png"><img alt="Fix in Web" width="99" height="28" src="https://cursor.com/assets/images/fix-in-web-dark.png"></picture></a></div>
<sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 0ab7013007ec0c4ce0eb90043fbf28570ee34fd0. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- BUGBOT_REVIEW -->
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
<!-- BUGBOT_FIX_ALL -->
<a href="https://cursor.com/open?link=eyJ2ZXJzaW9uIjoxLCJ0eXBlIjoiQlVHQk9UX0ZJWF9BTExfSU5fQ1VSU09SIiwiZGF0YSI6eyJyZWRpc0tleSI6ImJ1Z2JvdC1tdWx0aTpmYjY0N2NlOS0xMDk1LTRhZTAtYjYzYy1iOWI1NGUzYjU4NDciLCJlbmNyeXB0aW9uS2V5Ijoia2M0UnpZaW44YnVlTEtraTJOeGtHRUFWakstc18wZnowSjlOZnNsV3FkOCIsImJyYW5jaCI6InQxLWdvLXJvdXRlLWFtZXgtdG8tdW5zdXBwb3J0aW5nLWdhdGV3YXkiLCJyZXBvT3duZXIiOiJkcmFwZS1pbyIsInJlcG9OYW1lIjoiY3JiZW5jaC1jdXJzb3ItMjAyNi0wOSIsInByb3ZpZGVyIjoiZ2l0aHViIn19" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/fix-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/fix-in-cursor-light.png"><img alt="Fix All in Cursor" width="115" height="28" src="https://cursor.com/assets/images/fix-in-cursor-dark.png"></picture></a>
<!-- /BUGBOT_FIX_ALL -->
<!-- BUGBOT_AUTOFIX_REVIEW_FOOTNOTE_BEGIN -->
<sup>❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the [Cursor dashboard](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- BUGBOT_AUTOFIX_REVIEW_FOOTNOTE_END -->
<sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 0ab7013007ec0c4ce0eb90043fbf28570ee34fd0. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>
Drape (Deep Review) · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (1)
**Amex payments routed to unsupported Adyen gateway**
`RouteCard` now sends Amex to Adyen, but `Supports` says Adyen only handles Visa and Mastercard because its Amex onboarding isn't finished. Every Amex payment goes to a gateway that can't process it. Keep Amex on Stripe until Adyen's Amex onboarding is done and `Supports` allows it.
```
gateway.go:24 return GatewayAdyen
capabilities.go:3 // Supports reports whether a gateway is wired up to process a given card type in this service. The
capabilities.go:4 // Adyen integration was added for Visa and Mastercard volume; its Amex onboarding is not done yet.
capabilities.go:5 func Supports(g Gateway, c Card) bool {
capabilities.go:6 if g == GatewayAdyen {
capabilities.go:7 return c == Visa || c == Mastercard
capabilities.go:8 }
```
Drape (Review) · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (1)
**Amex routed to gateway that doesn't support it**
RouteCard now sends Amex to Adyen, but Supports() says Adyen's Amex onboarding isn't done and returns false for Adyen+Amex. Amex payments go to a gateway that can't process them. Keep Amex on GatewayStripe until Adyen Amex onboarding is complete, or update Supports() together with the routing change.
```
gateway.go:24 return GatewayAdyen
capabilities.go:3 // Supports reports whether a gateway is wired up to process a given card type in this service. The
capabilities.go:4 // Adyen integration was added for Visa and Mastercard volume; its Amex onboarding is not done yet.
capabilities.go:5 func Supports(g Gateway, c Card) bool {
capabilities.go:6 if g == GatewayAdyen {
capabilities.go:7 return c == Visa || c == Mastercard
capabilities.go:8 }
```
greptile · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (2)
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=9" align="top"></a> **Unsupported Amex Gateway**
Routing Amex to `GatewayAdyen` creates an unsupported card and gateway pairing. Adyen currently accepts only Visa and Mastercard, so `Supports(GatewayAdyen, Amex)` returns false. Callers relying on `RouteCard` to select a compatible processor will therefore be unable to process Amex payments.
```suggestion
return GatewayStripe
```
<h3>Greptile Summary</h3>
This PR changes Amex routing from Stripe to Adyen.
- Routes `Amex` cards through `GatewayAdyen`.
- Conflicts with the existing capability contract, which does not support Amex on Adyen.
<h3>Confidence Score: 4/5</h3>
The PR is not safe to merge until Amex is routed to a gateway that currently supports it.
The changed route selects Adyen for Amex even though the gateway capability contract explicitly limits Adyen to Visa and Mastercard, preventing callers from obtaining a compatible processor for Amex.
**Files Needing Attention:** gateway.go
<details><summary><h3>Important Files Changed</h3></summary>
| Filename | Overview |
|----------|----------|
| gateway.go | Changes Amex routing to Adyen, creating a card/gateway pairing rejected by the repository's capability check. |
</details>
<!-- greptile_other_comments_section -->
<sub>Reviews (1): Last reviewed commit: ["Update gateway.go"](https://github.com/drape-io/crbench-greptile-2026-09/commit/f957dab83f28dc70965d85dd7a922487eefa7abb) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=64284054)</sub>
Mjolnir (Opus 5.5) · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
The change sends Amex to Adyen. In capabilities.go, Supports(GatewayAdyen, Amex) returns false ("return c == Visa || c == Mastercard"), and its comment says Adyen's Amex onboarding is not done. Before the change, Amex went to Stripe, which accepts every card type. [grounded: diff] [consensus 3/3: valid=3]
raw comments (2)
[P1] Amex is now sent to Adyen, but Adyen can't process Amex
`RouteCard(Amex)` now returns `GatewayAdyen`. According to `capabilities.go:3-8`, the Adyen integration only handles Visa and Mastercard ("its Amex onboarding is not done yet"), so `Supports(GatewayAdyen, Amex)` returns false. Every Amex payment will therefore go to a gateway that isn't set up to process it, and those payments will fail or be rejected. Before this change, Amex went to Stripe, which accepts every card type. Amex should stay on `GatewayStripe` until Adyen's Amex support is in place and `Supports` is updated to match.
[P1] Amex is now routed to Adyen, which can't process Amex
`RouteCard(Amex)` now returns `GatewayAdyen`. But `Supports` in `capabilities.go:5-8` returns true for Adyen only for Visa and Mastercard, and its doc comment says Adyen's Amex onboarding is not done yet. So `Supports(RouteCard(Amex), Amex)` is now false. Every Amex payment goes to a gateway this service has not set up for Amex, so Amex transactions will be rejected or fail. Before this change, Amex went to Stripe, which accepts every card type. Amex should keep going to Stripe until Adyen's Amex support is added and `Supports` is updated to match.
Mjolnir (Sonnet 5.5) · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
The change sends Amex to Adyen. In capabilities.go, Supports(GatewayAdyen, Amex) returns false, and its comment says Adyen's Amex onboarding is not done yet. Before the change, Amex went to Stripe, which accepts every card type. [grounded: diff] [consensus 3/3: valid=3]
raw comments (2)
[P1] Amex routed to Adyen, which doesn't support Amex
`RouteCard` now sends `Amex` to `GatewayAdyen`. But `Supports` in capabilities.go says the Adyen integration only handles Visa and Mastercard, and that its Amex onboarding isn't finished. So every Amex payment goes to a gateway that can't process it. Amex charges will fail or be declined until the Adyen onboarding is done. Amex should stay on `GatewayStripe` until `Supports(GatewayAdyen, Amex)` returns true.
[P1] Amex routed to Adyen, which doesn't support Amex
RouteCard` now sends `Amex` to `GatewayAdyen`. `Supports` in capabilities.go says Adyen is wired up only for Visa and Mastercard, and that its Amex onboarding is not done. Every Amex payment would go to a gateway that can't process it, so those payments would likely fail. Stripe accepts all card types, and the previous routing was correct
qodo · cross-file engine perris 0.11.1+proven.tiered0.25.call.read.subclass.type
| Defect | Severity | Found | Grade |
|---|---|---|---|
| d1 | high | ✓ | exact |
raw comments (3)
<img src="https://img.shields.io/badge/High-634FD1?style=flat-square" height="20px" alt="Action required">
1\. Amex payments cannot be processed <code>🐞 Bug</code> <code>≡ Correctness</code>
<pre>
<b><i>RouteCard</i></b> now returns <b><i>GatewayAdyen</i></b> for <b><i>Amex</i></b>, while <b><i>Supports</i></b> explicitly excludes that
card-and-gateway combination. Whenever routing receives an Amex card, it selects an integration that
is not wired up to process it instead of the gateway documented as accepting every card type.
</pre>
<details>
<summary><strong>Agent Prompt</strong></summary>
```
## Issue description
`RouteCard` sends Amex cards to Adyen even though the service explicitly marks Adyen as unsupported for Amex.
## Fix Focus Areas
- gateway.go[21-24]
- capabilities.go[3-9]
## Recommended Fix
Restore the Amex route to `GatewayStripe`. Only route Amex to Adyen after the integration supports that card network and `Supports` is updated accordingly.
```
<code>ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools</code>
</details>
<h3>Code Review by Qodo</h3>
<code>🐞 Bugs (1)</code> <code>📘 Rule violations (0)</code> <code>📜 Skill insights (0)</code>
<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<br/>
<img src="https://img.shields.io/badge/High-634FD1?style=flat-square" height="20px" alt="Action required">
<details>
<summary> 1. Amex payments cannot be processed <code>🐞 Bug</code> <code>≡ Correctness</code></summary>
<br/>
> <details open>
><summary>Description</summary>
><br/>
>
><pre>
><b><i>RouteCard</i></b> now returns <b><i>GatewayAdyen</i></b> for <b><i>Amex</i></b>, while <b><i>Supports</i></b> explicitly excludes that
>card-and-gateway combination. Whenever routing receives an Amex card, it selects an integration that
>is not wired up to process it instead of the gateway documented as accepting every card type.
></pre>
></details>
> <details>
><summary>Code</summary>
><br/>
>
><code>[gateway.go[24]](https://github.com/drape-io/crbench-qodo-2026-09/pull/1/files#diff-381fc1538fcabc4f3c951608256b04bfb57661fd8940f39eeb49e30a1345b938R24-R24)</code>
>
>```diff
>+ return GatewayAdyen
>```
></details>
> <details>
><summary>Evidence</summary>
><br/>
>
><pre>
>The changed route returns Adyen for Amex, but the gateway capability definition says Adyen was added
>only for Visa and Mastercard because its Amex onboarding is unfinished; Stripe is documented as
>accepting every card type.
></pre>
>
> <code>[gateway.go[20-27]](https://github.com/drape-io/crbench-qodo-2026-09/blob/5c781625412afe8bb640fc3254bb2100768db912/gateway.go/#L20-L27)</code>
> <code>[capabilities.go[3-9]](https://github.com/drape-io/crbench-qodo-2026-09/blob/5c781625412afe8bb640fc3254bb2100768db912/capabilities.go/#L3-L9)</code>
></details>
> <details>
><summary>Agent prompt</summary>
><br/>
>
>```
>The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
>
>## Issue description
>`RouteCard` sends Amex cards to Adyen even though the service explicitly marks Adyen as unsupported for Amex.
>
>## Fix Focus Areas
>- gateway.go[21-24]
>- capabilities.go[3-9]
>
>## Recommended Fix
>Restore the Amex route to `GatewayStripe`. Only route Amex to Adyen after the integration supports that card network and `Supports` is updated accordingly.
>```
> <code>ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools</code>
></details>
<hr/>
</details>
<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<!-- qodo-context:start -->
<details><summary><strong>Context sources</strong></summary>
<div>Review mode: <code>⚖️ Balanced</code>: This is a one-line behavioral routing change affecting Amex gateway selection, so it warrants a careful review despite being localized.</div>
<!-- qodo-context:end -->
</details>
<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<!-- qodo-daily-tip:start -->
<details>
<summary><strong>Tip of the day</strong></summary>
<br/>
<pre>💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper</pre>
<a href="https://docs.qodo.ai/tips-and-tricks">More tips ↗</a> | <a href="https://app.qodo.ai/configurations?tab=display-preferences">Customize Qodo ↗</a> | <a href="https://docs.qodo.ai">Qodo docs ↗</a>
</details>
<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<!-- qodo-daily-tip:end -->
<!-- https://github.com/drape-io/crbench-qodo-2026-09/commit/5c781625412afe8bb640fc3254bb2100768db912 -->
<a href="https://www.qodo.ai"><img src="https://www.qodo.ai/wp-content/uploads/2025/03/qodo-logo.svg" width="80" alt="Qodo Logo"></a>
<h3>PR Summary by Qodo</h3>
Route American Express cards to Adyen
<code>✨ Enhancement</code> <code>🕐 Less than 5 minutes</code>
<img src="https://www.qodo.ai/wp-content/uploads/2025/11/light-grey-line.svg" height="10%" alt="Grey Divider">
<details>
<summary>AI Description</summary>
<dl>
<dd>
<br/>
><pre>
>• Routes American Express cards to Adyen instead of Stripe.
>• Leaves all other card networks routed to Stripe.
>• Conflicts with capability checks that still mark Adyen as unsupported for American Express.
></pre>
</dd>
</dl>
</details>
<details>
<summary>Diagram</summary>
<dl>
<dd>
<br/>
```mermaid
graph TD
A["Card Network"] --> B["RouteCard"] --> C{"Amex?"} -->|Yes| D["Adyen Gateway"]
C -->|No| E["Stripe Gateway"]
```
</dd>
</dl>
</details>
<details>
<summary>High-Level Assessment</summary>
<dl>
<dd>
<br/>
>The following are alternative approaches to this PR:
<details>
<summary><b>1. Keep Amex on Stripe</b></summary>
<dl>
<dd>
- ➕ Preserves routing to a gateway that currently supports American Express.
- ➕ Avoids failed or rejected payment processing.
- ➖ Delays migration of American Express traffic to Adyen.
</dd>
</dl>
</details>
<details>
<summary><b>2. Atomic Adyen enablement</b></summary>
<dl>
<dd>
- ➕ Keeps routing and capability declarations consistent.
- ➕ Allows tests to verify support before traffic is redirected.
- ➖ Requires completing the Adyen onboarding and adding broader changes.
</dd>
</dl>
</details>
>**Recommendation:** Do not redirect American Express traffic to Adyen in isolation. Keep Stripe routing until Adyen onboarding is complete, then update RouteCard and Supports together with coverage for the routing-capability invariant.
</dd>
</dl>
</details>
<details>
<summary> Files changed (1) <code> +1 / -1 </code> </summary>
<dl>
<dd>
<br/>
<details>
<summary>Enhancement (1) <code> +1 / -1 </code></summary>
<dl>
<dd>
<details>
<summary>gateway.go<code>Route American Express cards to Adyen</code> <code>+1/-1</code></summary>
<br/>
>Route American Express cards to Adyen
>
><pre>
>• Changes RouteCard to return GatewayAdyen for American Express cards instead of GatewayStripe. The default route remains Stripe, although the existing capability logic states that Adyen does not yet support American Express.
></pre>
>
><a href='https://github.com/drape-io/crbench-qodo-2026-09/pull/1/files#diff-381fc1538fcabc4f3c951608256b04bfb57661fd8940f39eeb49e30a1345b938'>gateway.go</a>
</details>
</dd>
</dl>
</details>
</dd>
</dl>
</details>