Skip to content

feat(payments): add PaymentSetup accommodation/airline fields - #239

Merged
armando-rodriguez-cko merged 1 commit into
mainfrom
feat/INT-1696-payment-setup-accommodation-airline-fields
Sep 17, 2026
Merged

armando-rodriguez-cko merged 1 commit into
mainfrom
feat/INT-1696-payment-setup-accommodation-airline-fields

Conversation

@armando-rodriguez-cko

Copy link
Copy Markdown
Contributor

Summary

Adds the new PaymentSetupAccommodation and PaymentSetupAirline fields from the 2026-09-08 spec update to POST/GET/PUT /payments/setups and POST /payments/setups/{id}/confirm/{payment_method_name}. Also fixes Industry, which used the wrong field names and reused an unrelated Payments-contexts type for airline, so the data never reached the API correctly.

Changes

  • checkout_sdk/payments/setups/setups.py — added PaymentSetupAccommodation/PaymentSetupAirline (previously Industry used non-spec field names airline_data/accommodation_data instead of airline/accommodation, and AirlineData.ticket incorrectly reused a Payments-contexts type); added total_number_of_guests, refundable, delivery_recipient, host to accommodation and total_number_of_passengers, travel_type, trip_type, refundable, delivery_recipient, ancillaries, insurance to airline
  • tests/payments/setups/payment_setups_serialization_test.py — added roundtrip coverage for both schemas including every new field

API Reference

  • POST /payments/setups
  • PUT /payments/setups/{id}
  • GET /payments/setups/{id}
  • POST /payments/setups/{id}/confirm/{payment_method_name}

Breaking changes

None for the new fields (additive). The Industry field-name fix changes wire format, but the old shape never matched the API contract, so nothing that worked before is affected.

README

No README changes needed.

Adds total_number_of_guests, refundable, delivery_recipient and host
to PaymentSetupAccommodation, and total_number_of_passengers,
travel_type, trip_type, refundable, delivery_recipient, ancillaries
and insurance to PaymentSetupAirline (POST/GET/PUT /payments/setups,
POST /payments/setups/{id}/confirm/{payment_method_name}).

Also fixes Industry, which used the wrong field names
(airline_data/accommodation_data instead of airline/accommodation)
and reused an unrelated Payments-contexts type for airline, so the
data never reached the API correctly.
@armando-rodriguez-cko
armando-rodriguez-cko requested a review from a team September 16, 2026 14:48
@agent-wall-e

agent-wall-e Bot commented Sep 16, 2026

Copy link
Copy Markdown

🟡 Risk Classification: MINOR

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

Classification reasons

  • exceeds_bounded_scope:261>200

Operational gates

  • ✅ jira_ticket (INT-1696)
  • ✅ independent_review

Files analysed: 2


wall-e 2026.06.19-02 · policy 376219bc71e6…

@agent-wall-e

agent-wall-e Bot commented Sep 16, 2026

Copy link
Copy Markdown
🔬 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
exceeds_bounded_scope261>200 classifying §2.1 M8 More than 200 non-test, non-doc, non-lockfile lines changed.

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

Copy link
Copy Markdown

@armando-rodriguez-cko
armando-rodriguez-cko merged commit f57fca2 into main Sep 17, 2026
4 checks passed
@armando-rodriguez-cko
armando-rodriguez-cko deleted the feat/INT-1696-payment-setup-accommodation-airline-fields branch September 17, 2026 11:16
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