Skip to content

Preserve payment receipt extensions#180

Closed
parvahuja wants to merge 1 commit into
parv/payment-response-hooksfrom
parv/receipt-extensions
Closed

Preserve payment receipt extensions#180
parvahuja wants to merge 1 commit into
parv/payment-response-hooksfrom
parv/receipt-extensions

Conversation

@parvahuja

Copy link
Copy Markdown
Member

Stacked on #179.

Summary

  • preserve unknown top-level receipt fields across parsing and serialization
  • keep the nested extra field distinct
  • reject extension collisions with core receipt fields

Testing

  • uv run --all-extras --group dev ruff check .
  • uv run --all-extras --group dev pyright
  • uv run --all-extras --group dev pytest -q (814 passed, 41 skipped)

@parvahuja
parvahuja force-pushed the parv/payment-response-hooks branch from 7972f02 to aecac76 Compare July 21, 2026 16:32
@parvahuja
parvahuja force-pushed the parv/receipt-extensions branch from 9775e18 to 36c2bf0 Compare July 21, 2026 16:32
@parvahuja
parvahuja force-pushed the parv/payment-response-hooks branch from aecac76 to d378ca5 Compare July 21, 2026 16:34
@parvahuja

Copy link
Copy Markdown
Member Author

Superseded by #170, which consolidates the shared runtime, sync transport, instrumentation, response hooks, and receipt extensions into one draft.

@parvahuja parvahuja closed this Jul 21, 2026
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.

1 participant