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

# Conto Pay Quickstart

> Complete your first Conto Pay test payment.

# Conto Pay Quickstart

This guide takes you from opening Conto Pay to a verified test receipt. It uses the hosted dashboard
flow; you do not need to install an SDK, create an API key, or operate a payment agent.

## Before You Start

You need:

* access to a Conto organization
* permission to use Conto Pay and create payments
* a saved recipient, exact Conto Pay handle, or supported wallet address

<Warning>
  Use an organization that shows the **Test payments** badge. Do not use a production-enabled
  organization for this walkthrough.
</Warning>

## Run Your First Test Payment

<Steps>
  <Step title="Open Conto Pay">
    Sign in to the Conto dashboard, select the intended organization, and open **Conto Pay** from the
    sidebar. Conto loads the hosted payment workspace automatically.
  </Step>

  <Step title="Confirm test mode">
    Look for the **Test payments** badge beside the payment form. This walkthrough should not use
    production funds.
  </Step>

  <Step title="Enter a recipient">
    In **Recipient**, enter a saved recipient name, an exact handle such as
    `@vendor-org/accounts-payable`, or a supported wallet address.

    Prefer an exact handle or wallet address for a first test. It avoids ambiguity when multiple
    profiles have similar names.
  </Step>

  <Step title="Enter a small amount">
    Enter a small test amount, such as `1.00`, and add a recognizable note such as `Conto Pay
          quickstart test`.
  </Step>

  <Step title="Continue to review">
    Select **Continue**. Conto resolves the recipient, checks the available test balance, and applies
    the organization's payment controls.

    This step may authorize a payment request, but it does not send funds.
  </Step>

  <Step title="Handle the result">
    Follow the action shown on the payment:

    * **Send payment** means the payment is authorized and ready.
    * **Review approval** means a person must approve it before sending.
    * A funding message means the hosted test wallet needs more test funds.
    * A recipient error means Conto could not safely resolve a unique destination.
  </Step>

  <Step title="Send and confirm">
    When **Send payment** is available, select it. Review the recipient and amount in the confirmation
    dialog, then select **Confirm send payment**.
  </Step>

  <Step title="Verify the receipt">
    Wait for the payment to complete, then open **View receipt** or the payment status page. Confirm
    that the recipient, amount, note, and final status match the test you intended.
  </Step>
</Steps>

## Expected Result

Your test is complete when:

* the intended recipient was resolved
* the payment passed or followed the expected approval path
* sending required an explicit confirmation
* the final status is complete
* a status page or receipt is available

## Common Problems

<AccordionGroup>
  <Accordion title="The recipient could not be found">
    Retry with the exact Conto Pay handle or full wallet address. A general name can match multiple
    profiles or no saved recipient.
  </Accordion>

  <Accordion title="The payment needs approval">
    Select **Review approval**, complete the approval in **Alerts & Approvals**, then return to Conto
    Pay and refresh the payment status.
  </Accordion>

  <Accordion title="The test wallet needs funds">
    Open **Wallets** and add the required test funds, or ask an organization administrator for help.
    Do not substitute production funds for a test run.
  </Accordion>

  <Accordion title="The payment was denied">
    Open **Payment details** and review the policy result. Change the recipient or amount only if that
    matches the intended test. Otherwise, ask a policy administrator to review the active controls.
  </Accordion>

  <Accordion title="The final status is unclear">
    Refresh the existing payment before trying again. Creating a second payment can produce a
    duplicate if the first payment is still processing.
  </Accordion>
</AccordionGroup>

## Test More Scenarios

After the first payment succeeds:

* use [Testing Payments Safely](/guides/testing-payments) for SDK and environment testing
* use [Testing Spending Policies](/guides/policy-testing) for approved, approval-required, and denied outcomes
* use [Approval Workflows](/guides/approval-workflows) to configure human approvals

<Info>
  Keep setup and testing instructions open beside the dashboard when you need them. Conto Pay keeps
  the default product surface focused on the payment itself.
</Info>