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

# Supported formats

> See which message formats the Payout Origination API accepts and which path slug to use for each one.

Use this page to choose the correct `{format}` path slug before you Base64-encode and submit a payout request.

Meridian currently accepts these payout origination formats:

| Path slug | Source payload                      | Use when                                                                                                                                  |
| :-------- | :---------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------- |
| `pacs008` | ISO 20022 `pacs.008.*` XML document | You originate payouts from an existing ISO 20022 payment message                                                                          |
| `json`    | JSON object                         | You want to submit a simpler structured payload where `entityId`, `beneficiaryId`, `amount`, `currency`, and `reference` are all required |

## Common intake rules

These rules apply to every supported format:

* Base64-encode the full source payload and send it as the raw `text/plain` request body.
* Sign the request with Meridian HMAC headers.
* Send `Idempotency-Key` as a separate request header.
* Use `POST /v1/payout-origination/{format}` with the correct path slug for your message type.
* Preserve the exact payload bytes you want Meridian to process before you Base64-encode them.

## Format-specific guides

* Use [pacs.008 format](/products/payout-origination/pacs008-format) for ISO 20022 XML submissions.
* Use [JSON format](/products/payout-origination/json-format) for Base64-encoded JSON submissions.

## Choosing a format

Choose `pacs008` when your upstream system already produces a complete `pacs.008.*` payment message and you want Meridian to ingest that original XML.

Choose `json` when you do not have an ISO 20022 payload and want to originate the payout from a minimal JSON document where all of these fields and values are required:

* `entityId`
* `beneficiaryId`
* `amount`
* `currency`
* `reference`

## Related pages

* [Overview](/products/payout-origination/overview)
* [Base64 payload encoding](/products/payout-origination/base64-payload-encoding)
* [Authentication](/products/payout-origination/authentication)