IAN OCAMPO SYSTEMSBUSINESS STRATEGY BEFORE TECHNOLOGY
SHARED BRIDGE · 07 OCT 2026
BRAND FARM · GoHighLevel AI Studio
SHARED HUB · QUICK TECHNICAL WALKTHROUGH

Payment Proof Upload Bridge

SOWHIP · WhiteN Fairview

A shared technical home for custom proof uploads: separate project routes, storage folders and a repeatable GHL connection.

2 EXISTING SAMPLE SETUPSDIRECT CODE EDITOPEN WALKTHROUGH · NO PASSWORD
01 / TECHNICAL WALKTHROUGH

One hub for payment-proof uploads

Use this hub for our projects that need a custom website to accept a payment-proof image and store it in GHL Media Storage. SOWHIP and WhiteN Fairview already have separate upload routes in this project; future projects can use the same pattern with their own folder and contract.

Shared connection model. One private-integration token serves the projects in this bridge when they use the same GHL location and the required scopes. Each project keeps its own routes and configuration. Another client’s GHL location uses its own authorized integration/token.

SOWHIP / Sociala

Checkout proof uploads routed into Sowhip Payment Proofs. GCash and BPI; readable customer-name filename.

View SOWHIP setup ↓

WhiteN Fairview

Appointment proof uploads routed into WhiteN Fairview Payment Proofs. GCash, BPI and BDO; appointment/submission identifiers.

View WhiteN setup ↓
This bridge returns the stored proof URL. Payment approval, order/appointment updates and customer emails belong to the connected website and native GHL workflows. Upload success means the file was stored; WhiteN labels it Pending Verification.
Shared connectionExisting value / source
AI Studio projectPayment Proof Upload Bridge ↗
1790025897083613790
Public hostuploads.socialaph.com ↗
GHL accountBRAND FARM · DgN0za1SVUav6ss38Kw8
IntegrationPAYMENT PROOF UPLOAD BRIDGE
6ab19b01d04dc88524551fac
Saved token nameSOWHIP_GHL_MEDIA_TOKEN · used by both server routes
Upstream media endpointPOST https://services.leadconnectorhq.com/medias/upload-file
02 / TECHNICAL WALKTHROUGH

How the shared setup was built

  1. 01

    Create a media integration

    Create the GHL media-upload private integration in BRAND FARM. Save its existing token in AI Studio More → Secrets as SOWHIP_GHL_MEDIA_TOKEN.

  2. 02

    Create separate storage folders

    Create Sowhip Payment Proofs and WhiteN Fairview Payment Proofs in GHL Media Storage. Put each folder’s parentId into its own handler.

  3. 03

    Build the server upload routes

    Each handler reads multipart FormData, validates its project fields/image limits, generates the filename and forwards the file server-side with the shared media token.

  4. 04

    Connect each website

    SOWHIP checkout submits to its route; WhiteN appointment/payment flow uses its WhiteN route. Their field requirements and allowed methods differ; use the matching contract below.

  5. 05

    Store the returned URL

    The website receives fileId/url and uses the proof URL in its own order or appointment record and workflow handoff. Keep payment verification in its native process.

  6. 06

    Verify and publish

    Check each project’s folder, allowed origins, fields, filename and error states. For an authorized upload test, confirm the actual stored file and returned URL. Save direct edits and publish with Update.

03 / TECHNICAL WALKTHROUGH

Completed sample · SOWHIP / Sociala

ItemSOWHIP configuration
Server sourcesrc/routes/api/sowhip/payment-proof/upload.ts
Website consumersocialaph.com / www.socialaph.com
EndpointPOST https://uploads.socialaph.com/api/sowhip/payment-proof/upload
FolderSowhip Payment Proofs
parentId 6abe2d5217f6f30939ac2c56
Required multipart fieldsfile, orderReference, paymentMethod, customerName
Payment methodsGCash, BPI, BPI Bank Transfer
Image contractJPEG/JPG, PNG, WebP; max 10485760 bytes (10 MiB). Declared MIME is checked.
FilenameSowhip-YYYYMMDD-HHMM-First-Last-PaymentMethod-Proof.ext · Asia/Manila
Response{ ok: true, fileId, url }
Current behaviororderReference is required but is not used for deduplication or the filename. Repeated requests may store multiple files. CORS response selection is not strict origin rejection.
04 / TECHNICAL WALKTHROUGH

Completed sample · WhiteN Fairview

ItemWhiteN configuration
Server sourcesrc/routes/api/whiten/payment-proof/upload.ts
Website consumerhttps://whitenfairview.brandfarm.top
EndpointPOST https://uploads.socialaph.com/api/whiten/payment-proof/upload
FolderWhiteN Fairview Payment Proofs
parentId 6ac02d78849322987424b7d9
Required multipart fieldsfile, appointmentId, paymentMethod, paymentReference, customerName, orderReference
Optional contactId
Payment methodsGCash, BPI, BDO · COD does not use this route.
Allowed originshttps://whitenfairview.brandfarm.top
https://preview-1787944262849276735.vibepreview.com
Disallowed origins return HTTP 403.
Image contractJPEG, PNG, WebP; max 10 MiB. Actual image signature is validated, and its extension is used.
FilenameWhiteN-YYYYMMDD-HHMM-AppointmentId-SubmissionId-Method-Proof.ext · Asia/Manila
Retry handling30-minute cache per worker, max 512 entries. Composite key includes identifiers, method, payment reference and file SHA-256. It is not persistent or shared across workers.
Response{ ok: true, fileId, url, appointmentId, orderReference, paymentMethod, paymentReference, status: "Pending Verification" }
URL validationRequires an HTTPS media URL before reporting success.

These are the existing handler contracts inspected from source. This documentation update does not perform a payment upload or claim a new end-to-end payment test.

05 / TECHNICAL WALKTHROUGH

Shared credential and project routing codes

The owner’s Payment Proof Upload Bridge — Secret Codes PDF contains the full plaintext token plus both folder IDs and endpoint references.

Setting / codeWhere obtained / storedUsage
SOWHIP_GHL_MEDIA_TOKENGHL Settings → Private Integrations → PAYMENT PROOF UPLOAD BRIDGE. Saved in this AI Studio project’s More → Secrets.Shared with WhiteN: Authorization Bearer value used server-side by SOWHIP and WhiteN.
Version: v3
Accept: application/json
Constants in both route handlers.Headers for the upstream GHL media API.
Project folder parentIdGHL Media Storage folder; hardcoded in each handler.Routes each project’s uploaded proof into its own folder.
Password / session keyNo fixed upload password or private session key is read by either handler.The media API token is the saved private credential. GHL login credentials are not stored in this bridge.
06 / TECHNICAL WALKTHROUGH

How to add our next project

  1. 01

    Add a project-specific route

    Use /api/<project>/payment-proof/upload with a clearly named source folder. Keep existing SOWHIP and WhiteN endpoints working.

  2. 02

    Create its storage and contract

    Create its GHL Media folder, record parentId, required fields, accepted payment methods, image checks/size limits, filename format and retry policy.

  3. 03

    Connect its domain and handoff

    Add the real consumer/preview origins and wire its upload form to its own endpoint. Save the returned proof URL into that project’s order/appointment process.

  4. 04

    Validate and document

    Check file storage, naming, error handling and the native verification workflow. Add a completed sample section here. Reuse the same-account token only when the integration covers that project.

07 / TECHNICAL WALKTHROUGH

How to replicate in another client’s GHL

  1. 01

    Copy into the client’s GHL project

    Create a bridge for the client’s location and point their website to its host.

  2. 02

    Use the client’s media integration

    Issue an integration in their account and save their own media token server-side. Do not copy the BRAND FARM token into the client’s bridge.

  3. 03

    Replace project configuration

    Create the client’s media folder and replace parentId, route/project prefix, allowed origins, payment methods, form fields and naming/handoff rules.

  4. 04

    Verify the full process

    Check an authorized sample upload lands in the client’s folder, the website saves its URL and the client’s native payment verification process receives the correct data.

08 / TECHNICAL WALKTHROUGH

Source map and verification

Source / responseMeaning
src/routes/index.tsxThis shared root walkthrough.
src/routes/api/sowhip/payment-proof/upload.ts
src/routes/api/whiten/payment-proof/upload.ts
Existing project-specific server handlers.
Authorization: Bearer <SOWHIP_GHL_MEDIA_TOKEN>Server → GHL only; the browser submits multipart fields without this token.
HTTP 200A stored proof URL returned successfully.
HTTP 400 / 403Bad input/upstream client error; WhiteN also rejects disallowed origins.
HTTP 500 / 502Missing configuration or processing/upstream failure.

Check the matching handler before changing the website form. Changing the shared media token affects both routes. To diagnose an upload, compare required fields, the project’s allowlist and target folder, then inspect whether the website saved the returned proof URL.