Application Sign Certificate

Submits a signed certificate (as a Base64-encoded PDF) to complete the online signature step for a merchant's Merchant Processing Agreement (MPA). This endpoint is called after the merchant has reviewed and signed the MPA, providing the signed document back to the system for record-keeping and workflow progression.

Endpoint

POST /api/v1/merchant/signatureCertificate

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this endpoint as part of the MPA signing workflow, after generating the MPA PDF (POST /api/v1/merchant/generateMPAPDF) and initiating the signature request. Once the signer has completed signing, call this endpoint to upload the resulting signed certificate PDF. The file must be a valid PDF and the filename must end in .pdf. This step is required to advance the merchant's status through the signing workflow.

Request Body

{
  "id": 48291,
  "data": "JVBERi0xLjQKJeLjz9MKMSAwIG9iago8PAovVHlwZSAvQ2F0YWxvZwovUGFnZXMgMiAwIFIKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL1BhZ2VzCi9LaWRzIFszIDAgUl0KL0NvdW50IDEKPD4KZW5kb2JqCg==",
  "fileName": "mpa_signed_48291.pdf"
}

Response

200 OK

{
  "requestId": 77042,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

Common Mistakes

• Providing a fileName that does not end in .pdf — the field validates against the regex ^.+\.pdf$.
• Sending raw binary data instead of a Base64-encoded string in the data field — always encode the PDF bytes as Base64 before including in the request body.
• Omitting id when the system cannot infer the merchant from context — include the merchant profile ID whenever available.
• Uploading a corrupted or truncated Base64 string — ensure the full PDF is encoded without line breaks or padding issues.

Related Endpoints

• POST /api/v1/merchant/generateMPAPDF — generate the MPA PDF that the merchant will sign
• POST /api/v1/merchant/requestSignature — initiate the online signature request for the merchant
• GET /api/v1/merchant/getSigningStatus — check the current status of the signing workflow

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/signatureCertificate \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 48291,
    "data": "JVBERi0xLjQKJeLjz9MKMSAwIG9iago8PAovVHlwZSAvQ2F0YWxvZwovUGFnZXMgMiAwIFIKPj4KZW5kb2JqCg==",
    "fileName": "mpa_signed_48291.pdf"
  }'