w3c / w3c/payment-request

Pass SKU instead of Total

Open
#879 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Future Candidate Feature
Dominant language
HTML
Stars
510
Forks
139
PR merge metrics
No merged PRs in 30d

Description

Hi all,

@rsolomakhin passed on this use case today, so recording it here.

Google Play Store requires the merchant to creates SKUs and specify SKUs instead of amounts during the payment flow. There's also a feature to request the price of the SKUs before payment, so that merchant can display the price in their app. Can we add this feature to Payment Request API in the next version? Sample code:

const request = new PaymentRequest([{supportedMethods: 'https://play.google.com/store'}], {total: {sku: '1234567890'}});
const details = await request.getDetailsFromSku();
showAmounts(details);
const response = await request.show();

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Begin with the Payment Request API proposal and the sample entry points PaymentRequest, getDetailsFromSku(), and show(); done means the next-version design specifies SKU-based payment requests and pre-payment price retrieval.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
api, payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.