HostedConfiguration
The hosted configuration acts as the default values for most of the session initialization parameters. If fields such as `maxAttempts` is not defined within the `/cit` call, the value will be fetched from the hosted configuration instead.
{
"instantCapture": "OFF",
"scaMode": "SKIP",
"timeout": 60,
"notificationUrl": "https://example.com/notification",
"successUrl": "https://example.com/success",
"failureUrl": "https://example.com/failure",
"retryUrl": null,
"maxAttempts": 10,
"processor": [
"shift4",
"nets"
],
"exemptions": [
"TRA",
"LVT"
],
"reportFailure": false
}If the payment should be captured instantly or not.<ul><li> `OFF` indicates that the payment should not be captured instantly.</li><li> `VOID` indicates that the payment should be captured instantly and if somehow the instant capture fails the payment is voided.</li><li> `NO_VOID` indicates that the payment should be captured instantly and if the capture fails the authorization is kept (no void is made)</li></ul>
How 3D secure is handled:<br/><ul><li>`SKIP` 3DS is not tried and full liability is put at merchant.</li><li>`NORMAL` 3DS flow is attempted as normal guidelines suggests - Both challenge and frictionless can occur.</li><li>`FORCE` A challenge flow is forced. Note: Third parties in the 3DS flow might ignore this instruction.</li></ul>
"SKIP""NORMAL""FORCE"How many minutes sessions stays active.
The URL to receive webhook notifications for any attempted transactions
uriThe URL the client is redirected to on successful payments
uriThe URL the client is redirected to when no more payment attempts is possible for the current session.
uriThe URL the client is redirected to on failed payments while there is still more attempts available. If null, then failureUrl is used as a fallback.
uriThe maximum number of transaction attempts allowed for the payment session
**DEPRECATED:** *This parameter will soon be removed and will no longer have any effect. The functionality has been replaced by routing rules in the ePay back office.* List of processors to use. This is the routing of the payment. The value can be `shift4`, `clearhaus` and `nets`.<br/><br/>The priority of the processors is made on the order. That means that if the first processor fails / declines then the next in the list will be used and so on until all processors in the list have been tried. The order is not guaranteed as it depends on external factors such as the specific payment card used by the cardholder.
Identifier of a payment processor. This value determines which payment gateway(s) are used to process a payment.
"shift4""clearhaus""nets""worldline"List of exemptions to apply when possible. Note exemptions shifts liability from the issuer to the merchant.
"TRA""LVT"If true, the notificationUrl will also receive webhooks for failed transactions. Otherwise, only successful transactions is notified.
Boolean flag to enable / disable receiving webhook notifications for sessions that reach the expired state.