---
title: "Create Wire Out Transfer"
method: POST
path: "/programs/{programCode}/accounts/{accountIdentifier}/wires"
tags: ["Transfers"]
---

# Create Wire Out Transfer

`POST /programs/{programCode}/accounts/{accountIdentifier}/wires`

This new endpoint allows Partners to wire out transactions and testing in PIE. 

Note: This feature must be explicitly requested and configured on a per partner basis. Contact your Green Dot Account Liaison for assistance. 

How it works: Call POST …/accounts/{accountIdentifier}/wires and include the following information:

## Path parameters

- `programCode` string, required
- `accountIdentifier` string, required

## Headers

- `X-GD-RequestId` string, required

## Request body

- WireOutRequest — Represents a request to initiate a wire transfer (Wire Out) from a Green Dot account to an external beneficiary. Contains all required information for processing a wire transfer, including identifiers, amount, currency, beneficiary details, optional memo and OBI (Other Beneficiary Information), and intermediary bank data if applicable.
  - `wireIdentifier` string, nullable — Required. The unique identifier for the wire transfer. Used for tracking, idempotency, and reference.
  - `amount` number, double — Required. The amount to be transferred via wire.
  - `currency` string, nullable — Required. The ISO 4217 currency code for the transfer (e.g., "USD").
  - `obi` string, nullable — Optional. Other Beneficiary Information (OBI) to be included with the wire transfer.
  - `memo` string, nullable — Optional. A memo or note to associate with the wire transfer.
  - `encryptedBeneficiaryData` EncryptedData — Represents a container for encrypted data used in secure data transfer operations. Contains the encrypted payload and associated cryptographic metadata, including encryption version, ephemeral public key, and public key hash. Used to securely transmit sensitive information such as user data, ensuring confidentiality and integrity during transport.
    - `version` string, nullable — The version of the encryption algorithm used to encrypt the data (e.g., "v1", "v2").
    - `ephemeralPublicKey` string, nullable — The ephemeral public key used in the encryption process, typically for key exchange or session establishment.
    - `publicKeyHash` string, nullable — The hash of the public key used to verify the integrity and authenticity of the encryption key.
    - `data` string, nullable — The encrypted data payload, typically base64-encoded, containing the sensitive information.
  - `IntermediaryBank` BankData — Represents bank information required for wire transfers or ACH transactions. Contains the routing number and the name of the financial institution involved in the transaction. Used to identify intermediary or beneficiary banks in payment operations.
    - `routingNumber` string, nullable — The routing number (ABA number) of the bank. Used to identify the financial institution for wire or ACH transactions.
    - `bankName` string, nullable — The name of the bank or financial institution.

## Response `201`

Created

- WireOutResponse — Represents the response returned after processing a wire transfer (Wire Out) request. Inherits standard response metadata from Gd.Bos.DataTransfer.Response.ResponseBase, including request identifiers, status, and response details. Used to indicate the outcome of a wire transfer operation, including success, failure, or error information.
  - `responseDetails` ResponseDetail[], nullable — Required: A list of response details providing status codes, descriptions, and additional information about the result of the operation.
    - `code` integer — The primary status or error code for the response (e.g., 200 for success, 400 for validation error).
    - `subCode` integer, nullable — An optional subcode providing more granular detail about the response or error.
    - `description` string, nullable — A human-readable description of the response, error, or status.
    - `url` string, nullable — A URL linking to documentation or a web page with more information about the response code.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/greendot/apis/baas-apis.md) · [All operations](https://skmtc.net/greendot/apis/baas-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/greendot/baas-apis/versions/666553766b78/schema)