Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,14 +1,15 @@
1		-An implementer must first perform a POST to this resource to initate the payment with an HTTP POST from your backend with payment info and your accessToken. The response from the POST will contain a payment session URL. Persist the paymentSessionUrl alongside the data representing the initial POST, be it a shopping cart, an order, or similar.
	1	+An implementer must first perform a {{code}}POST{{/code}} to this resource to initate the payment with an HTTP POST from your backend with payment info and your access token. The response from the POST will contain a payment session URL. Persist the {{code}}paymentSessionUrl{{/code}} alongside the data representing the initial POST, be it a shopping cart, an order, or similar.
2	2
3		-The paymentSessionUrl returned from the POST is the base URL to request all other resources related to the [[Payment>>ecommerce.PayEx Checkout.Payment]].
	3	+The {{code}}paymentSessionUrl{{/code}} returned from the {{code}}POST{{/code}} is the base URL to request all other resources related to the [[Payment>>Main.ecommerce.payex-checkout.Introduction.Payment.WebHome]].
4	4
5		-= Create Payment Session =
6	6
	6	+== Create Payment Session ==
	7	+
7	7	To create a Payment Session, you simply perform an HTTP {{code}}POST{{/code}} request with a Payment Session JSON payload as documented below to the Payment Session URL as discovered in the Home Resource.
8	8
9		-This resource requires authentication as mentioned in the [[introduction>>ecommerce.PayEx Checkout.Introduction||anchor="HAuthentication"]].
	10	+This resource requires authentication as mentioned in the [[Intro>>Main.ecommerce.payex-checkout.Introduction.WebHome||anchor="HAuthentication"]].
10	10
11		-== Properties ==
	12	+=== Properties ===
12	12
13	13	|(% style="text-align:right" %)**Property** |=Description
14	14	|(% style="text-align:right" %){{code}}amount{{/code}}
...	...	@@ -69,7 +69,7 @@
69	69	(optional) |(((
70	70	This property can be set so that PayEx Checkout in the future can pre-populate the email address and mobile phone number if the identity of the payer is known. As of now the data is not pre-populated in the frontend.
71	71
72		-{{code language="JavaScript"}}
	73	+{{code language="json"}}
73	73	{
74	74	"email": "<emailAddress>",
75	75	"mobilePhoneNumber": "<mobilePhoneNumber>"
...	...	@@ -82,7 +82,7 @@
82	82	)))|(((
83	83	This property can be set so that PayEx Checkout can add a fee depending on which payment method the user chooses during the PayEx Checkout user flow.
84	84
85		-{{code language="JavaScript"}}
	86	+{{code language="json"}}
86	86	{
87	87	"invoice": {
88	88	"amount": 19.50,
...	...	@@ -211,4 +211,4 @@
211	211
212	212	= Problems =
213	213
214		-If a request fails, its response will have a status code between 400 and 599. The HTTP body of the response will also be in the form of an {{code}}application/problem+json{{/code}} ([[RFC 7807>>https://tools.ietf.org/html/rfc7807]]), explaining in detail why the request failed and which, if any, actions you can take to remedy the problem. You can [[read more about problems here>>doc:ecommerce.PayEx Checkout.Problems.WebHome]].
	215	+If a request fails, its response will have a status code between 400 and 599. The HTTP body of the response will also be in the form of an {{code}}application/problem+json{{/code}} ([[RFC 7807>>https://tools.ietf.org/html/rfc7807]]), explaining in detail why the request failed and which, if any, actions you can take to remedy the problem. You can [[read more about problems here>>doc:Main.ecommerce.payex-checkout.Introduction.Problems.WebHome]].