-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
109 additions
and
55 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
|
||
The **Example 1** integration consists of three main steps. **Creating** the payment order, | ||
**displaying** the payment menu, and **capturing** the funds. In addition, there | ||
are other post-purchase options you need. We get to them later on. | ||
|
||
## Create Payment Order | ||
|
||
When your customer has initiated a purchase, you need to create a payment order. | ||
Start by performing a `POST` request towards the `paymentorder` resource with | ||
payer information and a `completeUrl`. | ||
|
||
The `productName` field has been removed in v3.1, and you identify the | ||
`paymentOrder` version as v3.1 in the header instead. | ||
|
||
`POST`, `PATCH`, `GET` and `PUT` requests use this header: | ||
|
||
`Content-Type: application/json;version=3.1` | ||
|
||
`GET` requests can also use this header: | ||
|
||
`Accept: application/json;version=3.1` | ||
|
||
Valid versions are **3.1**, **3.0** and **2.0**. If you do not add a version, | ||
the request will default to **2.0**. Using the `productName` and setting it to | ||
`checkout3` will default to **3.0**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
|
||
The **Example 3** integration consists of three main steps. **Creating** the payment order, | ||
**displaying** the payment menu, and **capturing** the funds. In addition, there | ||
are other post-purchase options you need. We get to them later on. | ||
|
||
## Create Payment Order | ||
|
||
When your customer has initiated a purchase, you need to create a payment order. | ||
Start by performing a `POST` request towards the `paymentorder` resource with | ||
payer information and a `completeUrl`. | ||
|
||
The `productName` field has been removed in v3.1, and you identify the | ||
`paymentOrder` version as v3.1 in the header instead. | ||
|
||
`POST`, `PATCH`, `GET` and `PUT` requests use this header: | ||
|
||
`Content-Type: application/json;version=3.1` | ||
|
||
`GET` requests can also use this header: | ||
|
||
`Accept: application/json;version=3.1` | ||
|
||
Valid versions are **3.1**, **3.0** and **2.0**. If you do not add a version, | ||
the request will default to **2.0**. Using the `productName` and setting it to | ||
`checkout3` will default to **3.0**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters