Skip to content

Doc 1438/docs upload supporting documents no code #497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max-koro merged 4 commits into from
Dec 3, 2025
Merged

Doc 1438/docs upload supporting documents no code #497

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d5ef61a
Update guide-missing-information.mdx
max-koro Dec 2, 2025
e950d8d
Update guide-missing-information.mdx
max-koro Dec 2, 2025
9b5c47d
Update guide-missing-information.mdx
max-koro Dec 2, 2025
5a65506
Apply suggestions from code review
max-koro Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 18 additions & 5 deletions docs/topics/merchants/guide-missing-information.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -223,11 +223,11 @@ For more details about required documents, refer to the [Document Center](/partn
1. Call the `merchantProfile` query with your merchant profile ID (line 2).
1. Add the `supportingDocumentCollections` field to your query (line 3).
1. Add a filter for `status: WaitingForDocument` to return only collections waiting for documents (line 4).
1. Include `requiredSupportingDocumentPurposes` with the fields `name` and `acceptableSupportingDocumentTypes` to see which documents are needed (line 11).
1. Include `requiredSupportingDocumentPurposes` with the fields `name` and `acceptableSupportingDocumentTypes` to see which documents are needed (line 12).

<a href="https://explorer.swan.io?query=cXVlcnkgR2V0U3VwcG9ydGluZ0RvY3VtZW50Q29sbGVjdGlvbiB7CiAgbWVyY2hhbnRQcm9maWxlKGlkOiAiJE1FUkNIQU5UX1BST0ZJTEVfSUQiKSB7CiAgICBzdXBwb3J0aW5nRG9jdW1lbnRDb2xsZWN0aW9ucyhmaWx0ZXJzOiB7CiAgICAgIHN0YXR1czogV2FpdGluZ0ZvckRvY3VtZW50CiAgICB9KSB7CiAgICAgIHRvdGFsQ291bnQKICAgICAgZWRnZXMgewogICAgICAgIG5vZGUgewogICAgICAgICAgaWQKICAgICAgICAgIHN0YXR1c0luZm8geyBzdGF0dXMgfQogICAgICAgICAgcmVxdWlyZWRTdXBwb3J0aW5nRG9jdW1lbnRQdXJwb3NlcyB7CiAgICAgICAgICAgIG5hbWUKICAgICAgICAgICAgbGFiZWwKICAgICAgICAgICAgZGVzY3JpcHRpb24KICAgICAgICAgICAgYWNjZXB0YWJsZVN1cHBvcnRpbmdEb2N1bWVudFR5cGVzCiAgICAgICAgICB9CiAgICAgICAgICBzdXBwb3J0aW5nRG9jdW1lbnRzIHsKICAgICAgICAgICAgaWQKICAgICAgICAgICAgc3VwcG9ydGluZ0RvY3VtZW50VHlwZQogICAgICAgICAgICBzdGF0dXNJbmZvIHsgc3RhdHVzIH0KICAgICAgICAgIH0KICAgICAgICB9CiAgICAgIH0KICAgIH0KICB9Cn0K&tab=api" className="explorer-badge">Open in API Explorer</a>
<a href="https://explorer.swan.io?query=cXVlcnkgR2V0U3VwcG9ydGluZ0RvY3VtZW50Q29sbGVjdGlvbiB7CiAgbWVyY2hhbnRQcm9maWxlKGlkOiAiJE1FUkNIQU5UX1BST0ZJTEVfSUQiKSB7CiAgICBzdXBwb3J0aW5nRG9jdW1lbnRDb2xsZWN0aW9ucyhmaWx0ZXJzOiB7CiAgICAgIHN0YXR1czogV2FpdGluZ0ZvckRvY3VtZW50CiAgICB9KSB7CiAgICAgIHRvdGFsQ291bnQKICAgICAgZWRnZXMgewogICAgICAgIG5vZGUgewogICAgICAgICAgaWQKICAgICAgICAgIHN1cHBvcnRpbmdEb2N1bWVudENvbGxlY3Rpb25VcmwKICAgICAgICAgIHN0YXR1c0luZm8geyBzdGF0dXMgfQogICAgICAgICAgcmVxdWlyZWRTdXBwb3J0aW5nRG9jdW1lbnRQdXJwb3NlcyB7CiAgICAgICAgICAgIG5hbWUKICAgICAgICAgICAgbGFiZWwKICAgICAgICAgICAgZGVzY3JpcHRpb24KICAgICAgICAgICAgYWNjZXB0YWJsZVN1cHBvcnRpbmdEb2N1bWVudFR5cGVzCiAgICAgICAgICB9CiAgICAgICAgICBzdXBwb3J0aW5nRG9jdW1lbnRzIHsKICAgICAgICAgICAgaWQKICAgICAgICAgICAgc3VwcG9ydGluZ0RvY3VtZW50VHlwZQogICAgICAgICAgICBzdGF0dXNJbmZvIHsgc3RhdHVzIH0KICAgICAgICAgIH0KICAgICAgICB9CiAgICAgIH0KICAgIH0KICB9Cn0K&tab=api" className="explorer-badge">Open in API Explorer</a>

```graphql {2-4,11-12,15} showLineNumbers
```graphql {2-4,10,12-13,16} showLineNumbers
query GetSupportingDocumentCollection {
merchantProfile(id: "$MERCHANT_PROFILE_ID") {
supportingDocumentCollections(filters: {
Expand All @@ -237,6 +237,7 @@ query GetSupportingDocumentCollection {
edges {
node {
id
supportingDocumentCollectionUrl
statusInfo { status }
requiredSupportingDocumentPurposes {
name
Expand Down Expand Up @@ -268,6 +269,7 @@ query GetSupportingDocumentCollection {
{
"node": {
"id": "$SUPPORTING_DOCUMENT_COLLECTION_ID",
"supportingDocumentCollectionUrl": "$UPLOAD_FORM_URL",
"statusInfo": {
"status": "WaitingForDocument"
},
Expand Down Expand Up @@ -296,14 +298,25 @@ query GetSupportingDocumentCollection {

### Step 5: Upload documents {#step-5}

There are two ways to upload documents:

#### Option 1: Generate upload URL with the API {#option-1}

Supporting documents work the same way as for onboarding and transactions.

Use the collection ID from the previous step to generate the supporting document upload link.
Use the collection ID from the previous step to generate the supporting document upload link.

Refer to the guide: [Upload a supporting document for an onboarding](/topics/accounts/documents/guide-upload-onboarding).

#### Option 2: Use Web Banking {#option-2}

You can direct users to upload documents directly through our Web Banking interface.
Use the `supportingDocumentCollectionUrl` field from the supporting document collection (step 4) to get the upload form link. Share the link with your users so they can upload their documents directly in Web Banking.

When users upload documents through Web Banking, the collection review is requested automatically (skip step 6).

### Step 6: Request a collection review {#step-6}

Request a review for the collection.
If you used option 1 to upload documents, request a review for the collection.

Refer to the guide: [Request a supporting document collection review](/topics/accounts/documents/guide-request-collection-review).