WebAPI/WebPayment: Difference between revisions

m
Line 107: Line 107:
Here is a detailed explanation of the in-app payment JWT:
Here is a detailed explanation of the in-app payment JWT:
**'''iss''': The issuer of the JWT. This is the application key assigned during the app registration process for this specific payment provider (BlueVia).
**'''iss''': The issuer of the JWT. This is the application key assigned during the app registration process for this specific payment provider (BlueVia).
**'''typ''': The JWT type (identifies the payment provider, BlueVia, and the JWT version that must be supported by the provider).
**'''typ''' (mandatory): The JWT type (identifies the payment provider, BlueVia, and the JWT version that must be supported by the provider).
**'''iat''': Issued at time. This is a UTC Unix timestamp of when the JWT was issued.
**'''iat''': Issued at time. This is a UTC Unix timestamp of when the JWT was issued.
**'''exp''': Expiration. A UTC Unix timestamp of when the JWT should expire.
**'''exp''': Expiration. A UTC Unix timestamp of when the JWT should expire.
**'''request''': Request object.
**'''request'''(mandatory): Request object.
*** '''price''': List of prices per country.
*** '''price''' (mandatory): List of prices per country.
**** '''country''': Country code expressed following the recommendations from [http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm ISO 3166 ].
**** '''country''': Country code expressed following the recommendations from [http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm ISO 3166 ].
**** '''currency''': Currency code expressed following the recommendations from [http://www.xe.com/iso4217.php/ ISO 4217].
**** '''currency''': Currency code expressed following the recommendations from [http://www.xe.com/iso4217.php/ ISO 4217].
**** '''amount''': Value withouth taxes of the digital good being sold.
**** '''amount''': Value withouth taxes of the digital good being sold.
*** '''defaultPrice''': (optional if only one value in the former collection) default price to be considered as payment price when there is not matching between the customer currency and the currency prices located in the price collection. This value is expressed following [http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm ISO 3166] and must match with one of the countries in the price list.  
*** '''defaultPrice''': (optional if only one value in the former collection) default price to be considered as payment price when there is not matching between the customer currency and the currency prices located in the price collection. This value is expressed following [http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm ISO 3166] and must match with one of the countries in the price list.  
*** '''name''': A short description of the product.
*** '''name''' (mandatory): A short description of the product.
*** '''description''': A long description of the product.
*** '''description''' (mandatory): A long description of the product.
*** '''productdata''': A freeform string, no longer than 255 characters. This can be anything the app might need to identify the product with when a postback is sent back to the app.
*** '''productdata''': A freeform string, no longer than 255 characters. This can be anything the app might need to identify the product with when a postback is sent back to the app.
*** '''postbackURL''': URL where the payment processor sends an HTTP POST message to whenever a purchase completes. The application server needs to acknowledge these POST messages, or else the transactions will be canceled. If the payment processor stores a different postback URL, this one should override the stored one. This way, application developer could choose different endpoints for different kind of digital goods.
*** '''postbackURL''': URL where the payment processor sends an HTTP POST message to whenever a purchase completes. The application server needs to acknowledge these POST messages, or else the transactions will be canceled. If the payment processor stores a different postback URL, this one should override the stored one. This way, application developer could choose different endpoints for different kind of digital goods.
Confirmed users
483

edits