Upload Document via Presigned URL
Attaches a supporting document (e.g. invoice) to an FFMS transaction using a presigned
URL you already control. Provide the presignedUrl in the request body; the backend
downloads the file from that URL and stores it. This is a single-call alternative to
uploading the file directly as multipart form data.
When to Use
Call this when you receive anMCA_FUND_RECEIVED webhook with status DOCUMENT_PENDING and you already have the supporting document (e.g. invoice) hosted at a presigned URL you control. Include that presignedUrl in the request body — the backend downloads the file from it and stores it for the transaction. This is a single-call alternative to uploading the file directly as multipart form data.
Upload Flow
Error Scenarios
Authorizations
Static API Key generated from the PayGlocal Partner Dashboard.
Path Parameters
Unique FFMS transaction identifier (from the MCA_FUND_RECEIVED webhook).
Body
Transaction amount.
"1000.00"
ISO 4217 currency code.
"USD"
Type of document being uploaded.
"INVOICE"
Payment type classification.
"CARD"
Merchant identifier. Must match the transaction.
"merchant_001"
File name including extension (extension max 10 characters).
"invoice_INV-2026-00321.pdf"
A presigned URL you control, pointing to the file to attach. The backend downloads the file from this URL and stores it in GCC's storage. Use this instead of a multipart file upload. The URL must remain accessible when the request is made.
"https://your-bucket.s3.amazonaws.com/invoice.pdf?X-Amz-Signature=..."
Full name of the customer (3–150 characters).
3 - 150"John Doe"
Shipping information (1–120 characters).
120"Bangalore, India"
Invoice reference number (1–100 characters).
100"INV-2026-00321"
Purpose code for remittance reporting.
"P0102"
Foreign exchange rate applied.
"83.12"

