API endpoints and JSON samples
Each use case is linked to a JSON and a PAYONE E-Payment API endpoint. Each JSON contains certain COF-relevant properties. Find a detailed description in the dedicated table.
Sample A
CreateHostedCheckout | CreatePayment |
---|---|
|
|
Sample B
CreateHostedCheckout | CreatePayment in combination with CreateHostedTokenization |
---|---|
|
CreateHostedTokenization
CreatePayment
|
Sample C
CreateHostedCheckout | CreatePayment in combination with CreateHostedTokenization |
---|---|
C1) Selection of the card to use on the merchant site:
C2: Selection on the card to use on Hosted Checkout Page
|
CreateHostedTokenization
CreatePayment
|
Sample D
{
"subsequentCardPaymentMethodSpecificInput": {
"subsequentType": "installment"
},
"order": {
"amountOfMoney": {
"amount": 100,
"currencyCode": "EUR"
}
}
}
Sample E
{
"subsequentCardPaymentMethodSpecificInput": {
"subsequentType": "recurring"
},
"order": {
"amountOfMoney": {
"amount": 100,
"currencyCode": "EUR"
}
}
}
Sample F
{
"subsequentCardPaymentMethodSpecificInput": {
"subsequentType": "unscheduled"
},
"order": {
"amountOfMoney": {
"amount": 100,
"currencyCode": "EUR"
}
}
}
Sample G / H / I / J
Populate "subsequentCardPaymentMethodSpecificInput.subsequentType" with the appropriate value depending on your use case. Find an overview of all possible values in this chapter.
{
"subsequentCardPaymentMethodSpecificInput": {
"subsequentType": "resubmission" / "partialShipment" / "delayedCharge" / "noShow"
},
"order": {
"amountOfMoney": {
"amount": 100,
"currencyCode": "EUR"
}
}
}
Sample X
Any valid CreateHostedCheckout/CreatePayment request. It does not have to contain any of the COF-relevant properties. Find examples in our card payment method guides, the Hosted Checkout Page and Server-to-server guide.