Skip to content

fix(setups): rename confirm param to paymentMethodName per spec#618

Merged
armando-rodriguez-cko merged 1 commit into
masterfrom
fix/payment-setups-confirm-param-name
Jul 16, 2026
Merged

fix(setups): rename confirm param to paymentMethodName per spec#618
armando-rodriguez-cko merged 1 commit into
masterfrom
fix/payment-setups-confirm-param-name

Conversation

@armando-rodriguez-cko

Copy link
Copy Markdown
Contributor

Problem

The confirm endpoint path parameter is payment_method_name — the name of the payment method to process the payment with (for example, tabby, klarna, card) — not an option id. The confirmPaymentSetup client method named this argument paymentMethodOptionId, which misleads integrators into passing an id instead of a method name.

Change

Rename the paymentMethodOptionId argument to paymentMethodName across the client interface, implementation, and tests, and update the doc comments with the spec's examples. The value is appended to the request path, so behaviour is unchanged — this is a naming/clarity fix.

Follow-up to #616, which aligned PaymentSetupsConfirmResponse with the PaymentSetup schema.

Verification

  • ./gradlew compileJava compileTestJava — passes.
  • Setups unit tests pass.

The confirm endpoint path parameter is payment_method_name (the name of the
payment method to process with, e.g. tabby, klarna, card), not an option id.
Rename the misleadingly-named paymentMethodOptionId argument to paymentMethodName
across the client interface, implementation, and tests.
@sonarqubecloud

Copy link
Copy Markdown

@armando-rodriguez-cko
armando-rodriguez-cko requested a review from a team July 16, 2026 15:42
@armando-rodriguez-cko
armando-rodriguez-cko merged commit 077d4a1 into master Jul 16, 2026
6 checks passed
@armando-rodriguez-cko
armando-rodriguez-cko deleted the fix/payment-setups-confirm-param-name branch July 16, 2026 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants