> ## Documentation Index
> Fetch the complete documentation index at: https://docs.natural.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When building application code, use `@naturalpay/sdk` for TypeScript or `naturalpay` for Python.
> When operating Natural directly for a user, use the payments MCP at `https://mcp.natural.com`.
> When searching Natural documentation, use the docs MCP at `https://docs.natural.com/mcp`.
> Use the Natural CLI for terminal and CI automation.
> Use REST only for unsupported languages or when the user explicitly requests raw HTTP.
> Start integration development and testing in the sandbox. Do not use production unless the user explicitly requests it.
> For sandbox requests that require `customerPartyId`, list customers first. Reuse only the intended fixture; otherwise create a customer.
> REST and SDK amounts use integer minor units. Payments MCP amounts use decimal strings with a required currency code.

# Sandbox fixtures

> Reserved test identifiers and synthetic counterparties for your sandbox organization

A fixture is a synthetic counterparty that only your sandbox organization can see. Fixtures stand in for the other side of every flow: the recipient of your payment, the payer of your request, the customer who authorizes your agents.

## Send a payment

Pay any of these identifiers and your recipient fixture receives it:

| Identifier | Value                                    |
| ---------- | ---------------------------------------- |
| Email      | `payment-recipient@sandbox.natural.test` |
| Phone      | `+14155550101`                           |
| Handle     | `@sandbox.payment_recipient`             |

## Request a payment

Address a payment request to the payer fixture, then [fulfill](/api-reference/simulations/fulfill-payment-request) or [decline](/api-reference/simulations/decline-payment-request) it as the payer. The payer is always funded.

| Identifier | Value                                        |
| ---------- | -------------------------------------------- |
| Email      | `payment-request-payer@sandbox.natural.test` |
| Phone      | `+14155550102`                               |
| Handle     | `@sandbox.request_payer`                     |

## Pay someone who hasn't joined yet

Payments to these identifiers wait as claims, just as they would for a real person without a Natural account. [Complete the claim](/api-reference/simulations/complete-payment-claim), or call `simulate_payment_claim_completion` through MCP, to simulate the payee joining and receiving the funds.

| Identifier | Value                                |
| ---------- | ------------------------------------ |
| Email      | `payment-claim@sandbox.natural.test` |
| Phone      | `+14155550103`                       |

## Simulate Connect

[Connect](/guides/products/connect) is how customers authorize your agents to act for them. [Invite a test customer](/api-reference/simulations/create-test-customer) by choosing its agents. Natural creates the synthetic customer, visible only to your organization, and leaves one invitation `PENDING` for each agent; no customer contact details are required.

[Accept](/api-reference/simulations/accept-customer-invitation) or [decline](/api-reference/simulations/decline-customer-invitation) each returned invitation as the test customer. After acceptance, [fund the customer](/api-reference/simulations/fund-test-customer), pay on its behalf with `customerPartyId`, and [revoke access](/api-reference/simulations/revoke-agent-connection) when a test needs a clean slate.