← Back to release summary

Secure Payment Confirmation API V3

Category

Miscellaneous

Type

No developer-visible change

Status

Enabled by default (Chrome 102)

Intent stage

Shipped

Summary

Three changes to the Secure Payment Confirmation API, implemented and flagged as “V3” of the API. - Add Relying Party ID as a required input (https://github.com/w3c/secure-payment-confirmation/issues/164). This is a breaking change, see compatibility section. - Add an optional boolean to allow failed instrument icon download (https://github.com/w3c/secure-payment-confirmation/issues/125) - Add payeeName as an optional input (https://github.com/w3c/secure-payment-confirmation/issues/163)

Standards & signals

• Specification: https://w3c.github.io/secure-payment-confirmation/
• Firefox: No signal
• Safari: No signal
• Web developers: Positive — Support and involvement in API development from multiple web developers and payment industry partners. Both Stripe and AirBnB have publicly stated that they have either completed or are in the process of prototyping/experimenting with SPC
• Tracking bug: https://crbug.com/1298505

View on chromestatus.com