---
title: "Get an invoice's payment instructions"
method: GET
path: "/v2/invoices/{invoiceId}/payment-instructions"
---

# Get an invoice's payment instructions

`GET /v2/invoices/{invoiceId}/payment-instructions`

## Request

- Base URL: `https://api.slash.com`
- URL: `https://api.slash.com/v2/invoices/{invoiceId}/payment-instructions`
- Auth: API key in header `X-API-Key`

Get the bank and crypto details a customer can pay the invoice to, as shown on its PDF and payment page. See [Payment instructions](/docs/v2/invoices/collecting-payment#payment-instructions).

## Response `200`

The invoice's payment instructions.

- InvoicePaymentInstructions: How a payer can pay the invoice outside the payment page.
  - `bankTransfer` object, required: The bank details printed on the invoice. Payments sent with `reference` are matched to the invoice automatically.
    - `beneficiaryName` string, required
    - `beneficiaryAddress` string
    - `bankName` string, required
    - `bankAddress` string
    - `accountNumber` string
    - `routingNumber` string: ABA routing number for ACH, wire and realtime payments.
    - `swift` string: SWIFT code for international wires.
    - `reference` string: What the payer should put in the payment's memo.
  - `crypto` object[], required: Deposit addresses, when the invoice takes `crypto`.
    - `currency` string, required
    - `network` string, required
    - `address` string, required
    - `memo` string: Include with the deposit on networks that need one.

## Other responses

- `400`: - `invalid_request (request shape)` — The body, query, or headers failed validation, or a required header is missing. `details` has one entry per failing location, keyed by JSON pointer or header name.
- `401`: - `unauthorized` — API key authentication is missing or invalid.
- `403`: - `feature_not_enabled` — The feature this request uses is not enabled for the legal entity. Contact Slash support to enable it. - `forbidden (legal entity)` — The credential is not permitted to act for the selected legal entity. - `not_available` — Public API v2 is not yet available. Use [Public API v1](https://docs.slash.com/introduction) in the meantime. - `user_api_key_required` — The API key is scoped to a legal entity rather than a user. Every v2 request needs a user API key, created under Settings → API keys in the Slash dashboard, together with the `x-legal-entity` header.
- `404`: - `not_found` — No resource matches the identifier. When the identifier is a field of the request, `details` names that `field` and the `id` it received.
- `429`: The request exceeded the applicable rate limit. The response body is plain text, not the error object; clients must not depend on its wording.
- `500`: - `internal` — Slash could not complete the request. Quote `referenceId` when contacting Slash support.

## Changes

- **2026-10-16** `8b5d371ffeea`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/slashfi/apis/slash-public-api/changes/v2/invoices/:invoiceId/payment-instructions/get.md)

---

[API](https://skmtc.dev/slashfi/apis/slash-public-api.md) - [All operations](https://skmtc.dev/slashfi/apis/slash-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/slashfi/apis/slash-public-api/revisions/eaed2d63c9e2?raw)