Skip to main content

Merchant Documents

note

For the full list of document types and their required fields, see the Document Types page.

Provide Merchant Docs​

Depending on the merchant type, the system will need to do various checks to finalize the onboarding process. Each check has a set of required documents. Create a test merchant and inspect the required documents returned by the API to see what's needed for each merchant type.

You can learn more about checks in the API responses (for example, the required_documents field).

Update Merchant Documents​

When a merchant is created, you MUST check the required_documents key to determine what documents need to be uploaded. To upload a document, you need to provide some info and the supporting file. Here is an example of the Bank IBAN:

POST /v1/merchants/88df1418-0290-4563-95c9-4a48eb03987a/documents HTTP/1.1
Host: apimig.moyasar.com
Authorization: Basic <your_api_key_as_basic_base64>
Content-Type: application/json
Content-Length: 200

{
    "type": "bank_iban_certificate",
    "info": {
        "holder": "Dutch van der Linde",
        "iban": "SA9880000000000000012345"
    },
    "file": "data:text/plain;base64,SGlpaWkg8J+RiyE="
}

Each document has different info required, you can learn more here at Documents.

Missing Documents Status​

When the on-boarding team at Moyasar find an issue with the merchants documents or information during the auditing process they will switch the merchant status to missing_docs.

In this status, you are required to update or provide missing information by deleting old files and providing new ones and updating the merchant information when required.

When fetching the merchant information through the API, a key named reasons will hold one or more of the pre-defined reasons found in "rejection-reasons" document.

Last updated on