Generate an Electronic Signature of a Document

When the mandate requires an electronic signature, the flow is as follows:

  1. Register the mandate via POST /v2/moneyins/sdd/mandate — returns a documentId and mandate in Pending status (0)
  2. Call Generate an Electronic Signature of a Document (POST /v2/accounts/{accountid}/documents/{documentid}/signinit) — returns a signDocument token
  3. Redirect the end user to the Lemonway WebKit with the token as a GET parameter:
    • Sandbox: https://sandbox-webkit.lemonway.fr/{env}/dev/?signingtoken={signDocument}
    • Production: https://webkit.lemonway.fr/{env}/prod/?signingtoken={signDocument}
  4. The debtor receives an OTP SMS, signs the mandate in the WebKit
  5. The end user is redirected to returnUrl (success) or errorUrl (failure)
  6. The mandate status transitions to Active (6)
⚠️

The mobileNumber field is required in the signinit call if no mobile number is already assigned to the wallet.

Path Params
string
required

Account Id

int64
required
Body Params
string
^\d{6,30}$

Required if no mobile number is already assigned to the payment account (using RegisterWallet or UpdateWalletDetails).
Format must be MSISDN : international number with country code, without "+" and "00".

int32
required

Use 21 for SDD mandate

string
required
length between 0 and 2000

Your website will the return URL, called by WEBKIT to terminate the operation.

string
required
length between 0 and 2000

You site will return the URL, called by WEBKIT in case of an error.

Headers
string
required

Authorization bearer (OAuth 2)

string

Response language accepted by final client (PSU). English by default

string
required

IP address of the final client (PSU).

string

User-agent of the final client (PSU).

Responses

401

Unauthorized

500

InternalServerError

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json