[david-ruiz-cko]

This release adds card payouts to network tokens, unreferenced refunds and the missing card payout and bank payout request fields, the Payment Setup payment type, and the Dunning and Downtime payment retry types. It also makes the Issuing revoke and suspend request optional, aligns the PaymentType::MOTO value with the API, and deprecates the members the API no longer accepts on requests. Every deprecated member keeps working and will be removed in the next major version.

Added

Issuing (#225)

• IssuingClient#revoke_card and IssuingClient#suspend_card can now be called without a request; the request argument is optional and an empty JSON object is sent when it is omitted.

Payment Setups (#226)

• PaymentSetupPaymentType with the lowercase values of the Payment Setups API: REGULAR, RECURRING, MOTO, INSTALLMENT, PAY_LATER, UNSCHEDULED. Use it for the :payment_type key of a Payment Setup create or update request.
• AccountFundingTransactionSender#reference.

Payouts and unreferenced refunds (#229)

• PaymentsClient#request_unreferenced_refund and UnreferencedRefundRequest, sent to POST /payments with payment_type set to UnreferencedRefund.
• NetworkTokenDestination and DestinationType::NETWORK_TOKEN, for card payouts and unreferenced refunds to a network token.
• PayoutRequest#segment, #items, #previous_payment_id and #processing.
• CardPayoutProcessing (affiliate_id, affiliate_url, processing_speed, purchase_country) and CardPayoutItem (type, sub_type).
• PaymentInstruction#remittance and InstructionRemittance (reference), for bank payouts.
• CheckoutSdk::Common::ResidentialStatusType (RESIDENT, NON_RESIDENT) for AccountHolder#residential_status. The field is optional and only used by bank payouts.

Payments (#229)

• PaymentType::PAY_LATER (PayLater).

Payment retries, hosted payments, payment links and payment sessions (#228)

• PaymentRetryRequest#dunning and #downtime, with the new DunningRetryRequest (enabled, max_attempts, end_after_days) and DowntimeRetryRequest (enabled).
• CheckoutSdk::Common::CustomerRetry (max_attempts).
• PaymentSessionsRequest#customer_retry and #instruction.
• PaymentLink#instruction and #payment_method_configuration.

Changed

• CustomerRetry moves from CheckoutSdk::Accounts to CheckoutSdk::Common; CheckoutSdk::Accounts::CustomerRetry remains as an alias of the same class (fix(payments): load retry types and add customer_retry to sessions #228).
• PaymentSessionsRequest#payment_type is documented as a PaymentType string; it was documented as a boolean (fix(payments): load retry types and add customer_retry to sessions #228).
• PayoutSource#amount is documented as an Integer; it was documented as a String ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• Request fields of payouts, unreferenced refunds, Payment Setups, hosted payments, payment links and payment sessions now document whether they are required or optional per request, with the limits and enum values of the API reference (feat(setups): add setup payment type, drop rejected identification types #226, fix(payments): load retry types and add customer_retry to sessions #228, feature/INT-1714 - new payout destination types in payments (network token) #229).

Fixed

• PaymentSegment is now loaded by the gem, so PayoutRequest#segment, UnreferencedRefundRequest#segment and PaymentRequest#segment can take a PaymentSegment object ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PaymentRetryRequest is now loaded by the gem; it could not be referenced before (fix(payments): load retry types and add customer_retry to sessions #228).

Deprecated

All deprecated members keep working and will be removed in the next major version.

• CheckoutSdk::Issuing::CardUpdateHeaders and the headers argument of IssuingClient#update_card: the API no longer documents these headers; call update_card(card_id, update_card_request). Headers that are set are still sent unchanged (deprecate(issuing): update-card headers, optional revoke/suspend body #225).
• AccountFundingTransactionSender#first_name, #last_name, #country_of_birth, #nationality and #address: not part of the Payment Setups sender; no replacement (feat(setups): add setup payment type, drop rejected identification types #226).
• AccountFundingTransactionRecipient#account_type: not part of the Payment Setups recipient; no replacement (feat(setups): add setup payment type, drop rejected identification types #226).
• AccountHolder#full_name: not in any account holder request; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• AccountHolder#gender: not in any account holder request; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• BankAccountDestination#bank: not in the bank payout destination; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PaymentInstruction#charge_bearer, #repair and #quote_id: not in the payout instruction request, still returned when retrieving a payout; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PaymentInstruction#skip_expiry and #mvv: not in the API; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• InstructionScheme::SWIFT: the bank payout request only accepts local and instant; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PayoutSource#amount: not in any payout or unreferenced refund source request; no replacement ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PaymentSessionsRequest#retry: not part of the payment sessions request and ignored by the API; no replacement (fix(payments): load retry types and add customer_retry to sessions #228).
• HostedPaymentsSession#payment_ip, PaymentLink#payment_ip and PaymentSessionsRequest#ip_address: deprecated by the API; no replacement (fix(payments): load retry types and add customer_retry to sessions #228).
• CheckoutSdk::Accounts::CustomerRetry: use CheckoutSdk::Common::CustomerRetry (fix(payments): load retry types and add customer_retry to sessions #228).

Breaking changes required by the API ⚠️

• AccountFundingTransactionIdentificationType::TAX_ID and ::OTHER are removed, because the API rejects them with a 422. Use DRIVING_LICENSE, PASSPORT or NATIONAL_ID (feat(setups): add setup payment type, drop rejected identification types #226).

Breaking changes (SDK alignment) ⚠️

• PaymentType::MOTO sends MOTO instead of Moto. Code that uses the constant needs no change; code that compares responses or stored values with the literal Moto should compare with MOTO ( feature/INT-1714 - new payout destination types in payments (network token) #229).
• PaymentRetryRequest#max_attempts and #end_after_day are removed. The class could not be loaded before this release, so no working code is affected. Use dunning.max_attempts and dunning.end_after_days (fix(payments): load retry types and add customer_retry to sessions #228).

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 1

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

🔵 Advisory review: Sound, but needs your judgement

This PR needs a human approval. The code itself reads as correct; whether it should land depends on context I don't have.

This diff only bumps the version from 2.7.1 to 2.8.0; the actual feature changes described in the PR body are not visible in this diff, so correctness of the release cannot be verified from what is shown.

For you to decide

• The diff is partial — only version.rb is shown, but the PR claims to add/change/deprecate/break many classes and modules across payments, issuing, payouts, and sessions; none of that code is visible here.
• The version bump itself (2.7.1 → 2.8.0) is consistent with the PR's claim of a minor release, but the PR also lists breaking changes (removed constants, changed PaymentType::MOTO value, removed PaymentRetryRequest fields) which would warrant a major version bump under strict semver — a human should decide whether the project's versioning policy treats these as acceptable for a minor release.
• Whether the breaking changes listed (AccountFundingTransactionIdentificationType::TAX_ID/::OTHER removal, MOTO value change, PaymentRetryRequest field removal) are acceptable to ship and have been communicated to consumers is a product/team decision not resolvable from this diff alone.

---

_{This is not an approval. wall-e cannot auto-approve this PR — it is an opinion to help whoever does. Advisory review · us.anthropic.claude-sonnet-4-6 · wall-e 2026.06.19-02}

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 1

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 1

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud