Skip to content

GooglePay web request config passthrough batch - #1004

Open
ana-maksimovskikh wants to merge 7 commits into
masterfrom
ana/card-1059-d-google-pay-web-request-config-passthrough-batch
Open

GooglePay web request config passthrough batch#1004
ana-maksimovskikh wants to merge 7 commits into
masterfrom
ana/card-1059-d-google-pay-web-request-config-passthrough-batch

Conversation

@ana-maksimovskikh

@ana-maksimovskikh ana-maksimovskikh commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

First of a few PRs with request-config updates (split for easier code reviews).
I'll submit them as a stack with one changeset at the end. All changes non breaking - so minor version bump would do.

https://linear.app/evervault/issue/CARD-1059/d-google-pay-web-request-config-passthrough-batch

PR1 added 6 fields, all flowing through the same passthrough (types → browser → ui-components types → buildPaymentRequest):

  • checkoutOption — transactionInfo.checkoutOption (e.g. "COMPLETE_IMMEDIATE_PURCHASE" to show "Pay" instead of "Continue" on the sheet)
  • transactionId — transactionInfo.transactionId, for fraud correlation
  • totalPriceStatus — now configurable ("ESTIMATED" / "NOT_CURRENTLY_KNOWN" / "FINAL"), was hardcoded to "FINAL" before
  • allowPrepaidCards / allowCreditCards — on CardParameters (two fields, bundled together since they're structurally identical booleans)
  • softwareInfo — merchantInfo.softwareInfo
  • category on TransactionLineItem (shared type, not Google-Pay-specific) — maps to displayItems[].type ("line_item" / "subtotal" / "tax" / "discount" / "shipping_option"), was hardcoded to "LINE_ITEM" before

External docs: https://github.com/evervault/docs/pull/869

@ana-maksimovskikh
ana-maksimovskikh requested a review from a team as a code owner September 3, 2026 14:49
@changeset-bot

changeset-bot Bot commented Sep 3, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 41dcdea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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.

1 participant