You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Payment method details on PaymentResult: After successful card, bank-account, or offsite tokenize, and after successful CVV recache, merchants can read the API payment_method via result.paymentResponse?.transaction?.paymentMethod (Swift) — including lastFourDigits, firstSixDigits, card/ACH/offsite fields, and typed binMetadata. Objective-C: paymentResponseDictionary on PaymentResult (same nested camelCase shape).
Security
Click to Pay host-page injection hardening: srcDpaId and locale are validated before host load and safely encoded when substituted into the Click to Pay WebView host page; Mastercard lib.js query parameters are percent-encoded.
Click to Pay WebView hardening: Release builds no longer mark Click to Pay WebViews as inspectable; native bridge handlers accept main-frame messages only; inbound bridge payloads reject additional cardholder-data key aliases; sandbox Mastercard hosts are allowed only when isSandbox is true.
Mandate nesting resource guard: Mandates that nest beyond the client resource depth are rejected at request construction instead of risking a host-app crash during tokenization.