---
id: overview
title: "Post-purchase"
sidebar_label: Overview
hide_title: true
description: "Overview of the Walley APIs you use after a payment has been created: Management API, settlements and webhooks"
---

import Ingress from "../../src/components/ingress/ingress.react";
import Link from "@docusaurus/Link";

<Ingress title="Post-purchase">
  The purchase is only the first step. After it, you ship and capture, you handle
  returns, and you match the payout against your books. These three APIs cover
  the rest of the order's life, and they work the same way no matter which Walley
  product created it.
</Ingress>

<div className="overview-cards">
  <Link className="overview-card" to="/docs/manage/getting-started/overview">
    <h3>📦 Management API</h3>
    <p>
      Act on an order once it exists. Capture what you ship, refund what comes
      back, change it before it leaves the warehouse, and read its current state
      whenever you need to.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/reports/overview">
    <h3>💰 Settlements</h3>
    <p>
      Get the payout report that explains what Walley paid you and why. Fetch it
      with the Reports API or download it from Merchant Hub.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/webhooks/overview">
    <h3>🔔 Webhooks</h3>
    <p>
      Let Walley call your system when something changes: an order is updated, an
      authorization comes through, a settlement is ready.
    </p>
  </Link>
</div>

## Common tasks

The scenarios most merchants build first, walked through end to end.

<div className="overview-cards overview-cards--compact">
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/pre-delivery/change-order"
  >
    <h4>✏️ Change an order</h4>
    <p>Adjust items or amount before anything is captured.</p>
  </Link>
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/delivery/full-deliver"
  >
    <h4>🚚 Deliver an order</h4>
    <p>Capture on shipment, in full or in parts.</p>
  </Link>
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/post-delivery/refund-order"
  >
    <h4>↩️ Refund a return</h4>
    <p>Give money back, in full or per item.</p>
  </Link>
  <Link
    className="overview-card overview-card--compact"
    to="/docs/reports/settlements-api/search"
  >
    <h4>🧾 Reconcile a payout</h4>
    <p>Find a settlement and read the transactions on it.</p>
  </Link>
</div>

## How the pieces fit together

1. A payment is created, by [Walley Checkout](/docs/checkout/overview), Pay
   Link, a token charge or the [Payments API](/docs/paymentsApi/getting-started/).
2. Your system acts on the order through the
   [Management API](/docs/manage/getting-started/overview). Capture is what
   triggers the payout.
3. [Webhooks](/docs/webhooks/overview) tell you when the order changes, including
   changes made in Merchant Hub or by Walley.
4. Captures, returns and fees land on a
   [settlement](/docs/reports/overview) that you reconcile against your ledger.

## Before you integrate

- Both APIs use OAuth2 client credentials. Create the API key in
  [Merchant Hub](/docs/merchanthub/access/apikeys), then read
  [Management API authentication](/docs/manage/getting-started/authentication) or
  [Reports API authentication](/docs/reports/authentication).
- Point at the test environment first. See
  [Management API endpoints](/docs/manage/getting-started/endpoints) and
  [Reports API endpoints](/docs/reports/endpoints).
- Webhook URLs are registered in
  [Merchant Hub](/docs/merchanthub/access/webhooks), not through an API.
- Changes are applied asynchronously. Read
  [Asynchronous operations](/docs/manage/concepts/asynchronous-operations) before
  you build retries, and
  [Order lifecycle](/docs/manage/concepts/order-lifecycle) to know which actions
  an order accepts.

## Getting access

Your organization needs access to these services before you can create an API
key. Contact Merchant Services to get set up.

:::info CONTACT DETAILS
**[help@walley.se](mailto:help@walley.se)**<br />
**[+46 10 161 01 25](tel:+46101610125)**
:::
