Environment setup - SohoPay

Integrate against staging. It runs Protocol V2 on Base Sepolia. Production hosts and contract addresses are issued when an account is cut over. Do not hard-code mainnet settlement addresses.

Do not use api-sandbox.sohopay.xyz. That host is not the current API.

Hosts

Surface	Staging
API	`https://staging.api.sohopay.xyz`
MCP	`https://staging.mcp.sohopay.xyz/mcp`
App and consent	`https://staging.sohopay.xyz`
Borrower portal	`https://staging.borrower.sohopay.xyz`
Agent skills	`https://agents.sohopay.xyz/skills/v1/` — use the `*-staging.md` skills
Docs	`https://docs.staging.sohopay.xyz`

Facilitator routes are under https://staging.api.sohopay.xyz/api/v1/facilitator/.

Chain and token

	Staging
Network	Base Sepolia
Chain id	`84532`
CAIP-2	`eip155:84532`
Asset	USDC (protocol mock) `0xa5807998c65c16d92048Cbf50E98955d0c85C700`
Settlement	`SohoSettlementV2` `0xd4C9919cbaa3Cd9D21F7a251CBA4DFFfe2E77c44`
Merchant registry	`SohoMerchantRegistry` `0x1a7AAfEE379F249e9D86Ef7fc4cE401c5516a264`
Lender vault	`SohoVault` `0x817a2e8A167E46926C449c527B818d511Aa23ef8`

Protocol V1 SohoSettlement is not deployed on staging. Explorer: sepolia.basescan.org. Staging uses the protocol mock USDC and the contracts above.

What you install

Agents need a host that speaks remote MCP (Cursor, Claude, or another OAuth-capable client) and, for signing, @sohopay/agent-signer. Merchants need an HTTP client that can POST the capture body and poll status. Neither path needs a SohoPay REST SDK.

Next steps

Authentication

OAuth scopes and merchant API keys.

Quickstart

Run the agent or merchant track.