PAY Token
The following payment related claims are used within PAY and KYAPay type tokens:
The following payment-related claims are defined for pay and kya-pay tokens.
| Claim | Description |
|---|---|
spr | OPTIONAL - JSON string representing seller service price in currency units. |
sps | OPTIONAL - Seller pricing scheme, which represents a way for the seller list how it charges for its service or content. One of pay_per_use, subscription, pay_per_mb, or custom. Additional values may be defined and used. |
amt | JSON string representing token amount in currency units. |
cur | Currency unit, represented as an ISO 4217 three letter code, such as "EUR". |
val | JSON string representing token amount in settlement network's units. |
mnr | OPTIONAL - JSON number representing maximum number of requests when sps is pay_per_use. |
stp | Settlement type (one of coin or card). Additional values may be defined and used. |
sti | Meta information for payment settlement, depending on settlement type. |
Agent Identity (sti) Sub-Claims
sti) Sub-ClaimsThe Agent Identity (sti) claim is optional. If present, it contains the following sub-claims.
| Claim | Description |
|---|---|
type | Dependent on stp. For coin - usdc. For card - visa_vic or mastercard_scof. Additional values may be defined and used. |
paymentToken | OPTIONAL - String containing Virtual Payment Card Number in ISO/IEC 7812 format. 12-19 characters. |
tokenExpirationMonth | OPTIONAL - String containing two-digit Expiration Month Number. |
tokenExpirationYear | OPTIONAL - String containing four-digit Expiration Year. |
tokenSecurityCode | OPTIONAL - String containing 3 or 4 digit CVV code. |
Additional sub-claims MAY be defined and used. The recipient MUST ignore any unrecognized sub-claims.
Updated about 23 hours ago
