This operations is applicable when:
Signing a debit consent can be done with:
Call to begin consumer debit consent signature using an electronic id - BankID or mobile BankID.
POST /v1/orders/rSW0BZRvtwQ0ZZxj3jje/signatures
x-api-key: njdfdsdkjfl5598503mnfkfe
x-merchant-key: 86969769
Content-Type: application/json
{
"signatureType": "DEBIT_CONSENT",
"identification": {
"method": "SE_BANKID_MOBILE",
"identifier": null
}
}
The orderId have to be submittet in the url.
The response will either be OK or an error code.
The response contains following information:
Status: 201 created
{
"id": "rSW0BZRvtwQ0ZZxj3jje",
"status": "OUTSTANDING_TRANSACTION",
"startURL": "bankid:///?autostarttoken=DUMMY-AUTOSTART",
"pollTime": 5000
}
Here we got status OUTSTANDING_TRANSACTION and a poll time at 5000ms and that means we are going to make the collect call to check the status in 5000ms.
You make the collect call with the id returned from Initialize electronic debit consent or Collect electronic debit consent.
Call to collect status on the signature process.
GET /v1/orders/rSW0BZRvtwQ0ZZxj3jje/signatures/<signatureId>
x-api-key: njdfdsdkjfl5598503mnfkfe
x-merchant-key: 86969769
Content-Type: application/json
All request parameters have to be submittet in the url. No message body should be sent.
The response will either be OK or an error code.
The response contains following information:
Status: 200 OK
{
"id": "v5HjBADhxAcM4QnZR3wS",
"status": "COMPLETE",
"startURL": "bankid:///?autostarttoken=DUMMY-AUTOSTART",
"pollTime": 1500
}