From 876bb232914929b4ee0ea45518ba9cd2020e4cb7 Mon Sep 17 00:00:00 2001
From: Marcos Caceres
- The Basic Card Payment specification describes the data formats used by
- the PaymentRequest API [[!PAYMENT-REQUEST-API]] to support payment by
- payment cards such as credit or debit cards.
+ This specification describes data structures for card-based payments
+ using WebIDL. It is used by other specifications to facilitate monetary
+ transactions with "basic cards", such as credit and debit cards.
- This specification was derived from a report published previously by - the Web Platform Incubator - Community Group. -
-- Sending comments on this document -
+
If you wish to make comments regarding this document, please raise
them as
Introduction
- This specification is a Payment Method specification for use with the
- PaymentRequest API [[!PAYMENT-REQUEST-API]]. With it, merchants can
- collect the basic card details (card holder name, card number, etc.)
- through the PaymentRequest API that they have traditionally collected
- through Web forms, but with an improved user experience.
+ This specification is a Payment Method specification for use, for
+ instance, with the PaymentRequest
+ API. With it, merchants can collect the basic card details (card
+ holder name, card number, etc.) as an alternative to collecting the
+ same information through a HTML form.
The Web Payments Working Group is also investigating payment methods
that offer greater security (e.g., through tokenization).
- This specification relies on several other underlying specifications.
+ The standardized
+ payment method identifier for this specification is
+ "
+ The BasicCardRequest dictionary contains the following members:
- The payment method identifier string for the Basic Card Payment
- method is
+ The supportedNetworks and supportedTypes members are both
+ optional. If neither is provided then any card may be returned. If only
+ supportedNetworks is provided then any card type may be returned
+ provided it matches one of the networks. If only supportedTypes
+ is provided then a card may be returned from any network provided it
+ matches one of the types.
- This section describes payment method specific data that is supplied as
- part of the
- The
- The
- The
- The
+ The BasicCardResponse dictionary contains the following members:
+
- Dependencies
+ Payment Method Identifier
basic-card
".
+
+ BasicCardRequest dictionary
+
+
+ dictionary BasicCardRequest {
+ sequence<DOMString> supportedNetworks;
+ sequence<BasicCardType> supportedTypes;
+ };
+
+
-
- Payment Method Identifier
-
- basic-card
.
+
- Payment Method Specific Data for the PaymentRequest constructor
+ BasicCardType enum
- data
argument to the PaymentRequest
- constructor.
-
- BasicCardRequest
-
-
- enum BasicCardType { "credit", "debit", "prepaid" };
-
- dictionary BasicCardRequest {
- sequence<DOMString> supportedNetworks;
- sequence<BasicCardType> supportedTypes;
- };
-
- BasicCardRequest
dictionary contains the following
- fields:
-
-
- supportedNetworks
- supportedNetworks
field contains a sequence of
- identifiers for card networks that the merchant accepts. W3C
- maintains a list of approved
- card network identifiers.
- supportedTypes
- supportedTypes
field contains a sequence of card
- types that the merchant accepts. Implementations will determine how
- to match the type values credit
, debit
,
- and prepaid
.
- supportedNetworks
and supportedTypes
- fields are both optional. If neither is provided then any card may be
- returned. If only supportedNetworks
is provided then any
- card type may be returned provided it matches one of the networks. If
- only supportedTypes
is provided then a card may be
- returned from any network provided it matches one of the types.
-
+ enum BasicCardType { "credit", "debit", "prepaid" };
+
+
+
- Payment Method Response
-
- BasicCardResponse
dictionary contains the
- response from the PaymentRequest API when a user accepts payment with a
- Basic Payment Card payment method.
-
- BasicCardResponse
-
-
+
+ BasicCardResponse dictionary
+
+
dictionary BasicCardResponse {
- DOMString cardholderName;
required DOMString cardNumber;
+ DOMString cardholderName;
+ DOMString cardSecurityCode;
DOMString expiryMonth;
DOMString expiryYear;
- DOMString cardSecurityCode;
-
PaymentAddress? billingAddress;
};
- BasicCardResponse
dictionary contains the following
- fields:
-
-
- cardholderName
- cardholderName
field contains the cardholder's
- name as it appears on the card.
- cardNumber
- cardNumber
field contains the primary account
- number (PAN) for the payment card.
- expiryMonth
- expiryMonth
field contains a two-digit string for
- the expiry month of the card in the range 01
to
- 12
.
- expiryYear
- expiryYear
field contains a four-digit string for
- the expiry year of the card in the range 0000
to
- 9999
.
- cardSecurityCode
- cardSecurityCode
field contains a three or four
- digit string for the security code of the card (sometimes known as
- the CVV, CVC, CVN, CVE or CID).
-
+
01
to
+ 12
.
+ 0000
to
+ 9999
.
+ PaymentAddress
+ that represents the billing address associated with the card.
+