Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
title: Newline Platform Transactions API
version: 1.0.0
description: "\nWelcome! In this section of our docs experience, you'll be able to go through common payment scenarios that both you and your end customers may encounter as you start to offer financial products through your own technology stack. These guides will also help to highlight and expand on concepts discussed in our API references, like [Synthetic Accounts](https://developers.newline53.com/reference/synthetic-accounts), [Transfers](https://developers.newline53.com/reference/transfers), [Transactions ](https://developers.newline53.com/reference/transactions) and [Customers](https://developers.newline53.com/reference/customers).\n\nOur guides are broken out by supported use cases. If you find there isn't a specific use case that fits your business, reach out to our [Sales & Partnership team](https://newline53.com/contact-us.html) and they'll be able to help determine how we can support your business and provide any other questions or feedback.\n\nLastly, when you're ready to build, check out our [Onboarding Overview](https://developers.newline53.com/docs/overview) and [Sandbox Walkthrough](https://developers.newline53.com/docs/sandbox-walkthrough) guides.\n\n## About our API\n\nThe Newline API is organized around REST. With a few exceptions, our API has standard resource-oriented URLs, accepts form-encoded OR JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.\n\n## FAQs\n\nWant to quickly review some common questions about Newline and our financial experiences, check out our [FAQs](https://developers.newline53.com/docs/faqs) guide.\n\n# Overview\n\n## Newline Onboarding 101\n\nOnboarding to any SaaS product can be a daunting task, and at Newline we seek to make this experience as smooth as possible. Part of that is getting you, our Client, familiar with the process by which we establish key resources like your Program, Products, Customers, Custodial Accounts, and Synthetic Accounts.\n\nThe following guide details, in short order, the Program and resources that Newline will configure for you and how each of these components affect your ability to use our API Reference.\n\n<img src=\"https://files.readme.io/955347d-image.png\">\n\nThe above visualization shows the Program and resources Newline will provide and maintain for Clients going through onboarding and implementation, but we'll enumerate the details for each resource above.\n\n> **Note**\n> In the above visualization, the lighter color items are preset and created by Newline for any Client implementation. Synthetic Accounts is a special case where general Synthetic Accounts are preset and Clients will be responsible for creating their own external Synthetic Accounts and VRNs..\n\n- **Program** - the Program dictates the origination terms to which the Client and Newline mutually agree. This could include payment limitations like amounts, frequency, and the need for pre-funding (ex. ACH). Your Program will be created and configured by Newline.\n\n- **Products** - these are distinct Product offerings supported by Newline. For instance, this can include payment rails like ACH, Wire, and Instant Payments that are configured as available synthetic_account_types. Newline creates and configures a Program's Products.\n\n - Products can be applied across multiple Customers, and Customers can be attached to multiple Products. Essentially there is a many-to-many relationship between these resources, which make them, in some cases, parallel.\n\n - A Product can support multiple payment rails.\n\n- **Customer Type** - Customers are provided a Customer Type at creation. For instance, Primary Customers are considered full account owners and have complete authority to take any actions associated with their accounts and associated resources. You can also limit certain Customer Types to have access to only certain Products. Permitted Customer Types are configured by Newline.\n\n- **Pool** - Container for one or more Synthetic Accounts, with Assets owned by one or more Customers. Pools allow for shared assets and flexibility in ownership and transfer of assets. Newline will create Pools.\n\n- **Customer** - This is the entity that owns the Account and Funds stored at Newline. This entity also is deemed the Originator when it comes to any payment creation. Clients can also be Customers in the event they meet those criteria. Customers are created by Newline or by the Client depending on the use case.\n\n- **Custodial Account** - This is the Account that exists in our Synthetic Core and represents the reciprocal Account on Fifth Third's ledger. These are the accounts you can access via Fifth Third Direct. Custodial Accounts will be created by Newline.\n\n- **Synthetic Account** - How Newline represents the assets held by your Customers. These are the accounts that Customers view and interact with on your application. Synthetic Accounts are also used to manage external accounts that your Customers will likely use within your application. Synthetic Accounts of the general category will be created by Newline or by the Client depending on your use case. Clients will create external Synthetic Accounts like wire_external, ach_external, and instant_payment_external.\n\n- **Virtual Reference Number** - Virtual Reference Numbers (or VRNs) are virtualized account numbers. They are aliases to a synthetic account and can form a many-to-one relationship with their parent synthetic account.\n\n# Postman Collection\n\nHow to set up Postman, add our Newline collection, and use it to test Newline platform APIs.\n\n## Installing Postman\n\nPostman is available on a variety of platforms. Visit [Postman](https://www.postman.com/downloads/) to see if your platform is supported. \nTo install Postman:\n\n1. Go to [Postman downloads](https://www.postman.com/downloads/).\n\n<img src=\"https://files.readme.io/fd1743f-Postman_Dowload_snip.jpg\">\n\n1. Download the required version.\n\n2. After your download is complete, run the downloaded file to install Postman.\n\n## Import the Newline Collection\n\nTo import our collection, click on the following [▶ Newline Collection](https://www.postman.com/newline53) button, and you will be redirected to our Newline Postman workspace, where you can download our collection.\n\nFor further information, see the [Postman documentation on importing data](https://learning.postman.com/docs/getting-started/importing-and-exporting-data/).\n\n## Configure Your Postman Environment\n\n1. Create a Sandbox Environment.\n\n2. Set Sandbox variables.\n\n3. Save the environment.\n\n4. Ensure the new environment is selected.\n\n**Set API Keys** \nYou will need to set your HMAC Key and Program UID as environment variables. You can set the variables in the headers in the environment tab within the Postman Collection.\n\n# Terminology\n\nThe terms, which represent API resource objects in Newline, below are referenced in our API documentation and endpoint definitions. \nSome important notes while reading through this list:\n\nResource Objects often interact with one another, so please be sure to review our endpoints to see which serve as required inputs or are collected as outputs.\n\nCertain objects, like Transfers, are described differently in the payments industry depending on the Transaction Type. For instance, ach transactions are often referred to as entries rather than payments, as they can represent both credits (i.e., ODFI pushes) and debits (i.e., ODFI pulls). \nWhile Resource Objects are distinct, they, in some cases, can represent the same entity.\n\n- Ex. 1 - Clients can also be Customers if they manage and own the financial products in question.\n\n- Ex. 2 - Transfers produce Transactions, but the produced Transactions (in aggregate) represent the original money movement.\n\n| Term | Definition |\n| --- | --- |\n| Customer | The end user of your application and the owner of assets in your Program. For example, when initiating a payment, this entity would be considered the **originator**. |\n| Client | The application or product owning organization that is affording end users (i.e., Customers) the ability to access the financial products.<br><br><br>**Note**<br>Clients can also be Customers in the event they own and have management over the financial products or the funds involved. |\n| Transmitter | Transmitters are the parties who have _requested_ the Transfer in question. When the Transmitter and Customer are the same party, Newline pulls origination information from the created Customer record. When the Transmitter and Customer are not the same party, it's the Client's responsibility to provide that information when making a Transfer. <br> <br>Transmitters are only required for the `wire` and `instant_payment` types (see the `wire_transmitter` and `instant_payment_transmitter` objects in the [Initiate a Transfer](https://developers.newline53.com/reference/post_transfers) reference). Client's should also take note of the `initiator_type` field, which dictates from where Transmitter information is pulled. For more context on Transmitters, refer to the [Payment Rail Regulation](https://newline-enterprise-group.readme.io/docs/transfer#payment-rail-regulation) section below. |\n| Partner | Any infrastructure partner integrated within the Newline Platform. |\n| Program | The Program is custom tailored to your offering and purpose built to enable financial products on your application. The Program defines what Synthetic and Custodial Account types, Customer Types, and Transactions Types are available for your Customers to utilize. The Program configuration is defined between the Client and Newline based on your (i.e., the Client's) use case. |\n| Product | Products represents the financial products available to your Customers. The Product object contains the account, compliance, and customer profile responses necessary for your Customers to gain access. |\n| Customer Product | The Customer Product is created when the Customer is added to a Product and respective Program. This often includes Newline automatically creating any needed financial products for the Customers' use. For instance, a Synthetic Account to represent the origination account at Fifth Third. |\n| Service Offering | The financial product offered by the Newline platform. These can be (but are not limited to) checking, savings, brokerage, or retirement accounts. |\n| Pool | Container for one or more Synthetic Accounts, with Assets owned by one or more Customers. Pools allow for shared assets and flexibility in ownership and transfer of assets. |\n| Custodial Accounts | This resource within Newline represents the assets held by your Customers, with direct alignment to accounts opened at Fifth Third. Custodial Accounts have the following relationships: one-to-one with Customers, and one-to-Many with Synthetic Accounts. |\n| Synthetic Accounts | How Newline represents the assets held by your Customers. These are the accounts that Customers view and interact with on your application. Synthetic Accounts are also used to manage external accounts (i.e., Counterparties) that your Customers will likely use within your application. |\n| Virtual Reference Number (VRN) | Virtual Reference Numbers (or VRNs) are virtualized account numbers. They are aliases to a Synthetic Account, and can form a many-to-one relationship with their parent Synthetic Account. |\n| Transfer | The movement of assets from one Synthetic Account to another Synthetic Account. Most of asset movement initiated by your application will result in a Transfer. A successful Transfer will result in at least one Transaction. |\n| Transaction | Transactions are created based on how you instruct Newline to move assets (a Transfer) or how assets are moved or spent outside of your application (For example, ACH, Wire, and Instant Payments Transfers). The Transaction contains the amount, origin, and destination of assets. Newline categorizes Transactions into types to assist in their classification and representation. |\n| Transaction Events | The steps taken to complete the Transaction. These can be used to view the progress of an in-flight Transaction or see the history of a completed Transaction. |"
servers:
- url: https://sandbox.newline53.com/api/v1
security:
- ApiKeyAuth: []
tags:
- name: Transactions
description: "Transactions represent asset movements, such as ACH payments, wire transfers, or card purchases. Track transaction statuses and events through these endpoints. \n**Endpoints:**\n\n- GET [List Transactions: GET /transactions](https://developers.newline53.com/reference/get_transactions)\n\n- GET [Get a single Transaction: GET /transactions/{uid}](https://developers.newline53.com/reference/get_transactions-uid)\n\n- PUT [Approve or deny a Transaction: PUT /transactions/{uid}/authorize](https://developers.newline53.com/reference/put_transactions-uid-authorize)\n\n- GET [List Transaction Events: GET /transaction_events](https://developers.newline53.com/reference/get_transaction-events)\n\n- GET [Get a single Transaction Event: GET /transaction_events/{uid}](https://developers.newline53.com/reference/get_transaction-events-uid)\n\n- GET [List Synthetic Line Items: GET /synthetic_line_items](https://developers.newline53.com/reference/get_synthetic-line-items)\n\n- GET [Get a single Synthetic Line Item: GET /synthetic_line_items/{uid}](https://developers.newline53.com/reference/get_synthetic-line-items-uid)\n\n- GET [List Custodial Line Items: GET /custodial_line_items](https://developers.newline53.com/reference/get_custodial-line-items)\n\n- GET [Get a single Custodial Line Item: GET /custodial_line_items/{uid}](https://developers.newline53.com/reference/get_custodial-line-items-uid)\n\nTransactions are created based on how you instruct Newline to move assets (a Transfer) or how assets are moved or spent outside your application (ATM withdrawals, debit card purchases, wire transfers, etc…). The Transaction contains the amount, origin, and destination of assets. Newline categorizes Transactions into types to assist in their classification and representation.\n\nTransactions fall into many categories, including debit card purchases, direct deposits, interest, and fees. This endpoint can retrieve a list of Transactions or track the status of an ongoing Transaction.\n\nTransaction Events are created as a result of a Transaction. They capture the steps required to complete the Transaction. These can be used to view the progress of an in-flight Transaction or see the history of a completed Transaction.\n\nLine Items are created for each Transaction Event. They catalog the individual credits and debits associated with the accounts involved in the Transaction."
paths:
/transactions:
parameters:
- $ref: '#/paths/~1auth/parameters/0'
get:
tags:
- Transactions
summary: List Transactions
description: Retrieves a list of Transactions. Transactions representing expired authorizations or expired reversals are suppressed by default.
parameters:
- $ref: '#/paths/~1pools/get/parameters/0'
- $ref: '#/paths/~1transfers/get/parameters/2'
- name: source_synthetic_account_uid
in: query
schema:
type: string
example: 4XkJnsfHsuqrxmeX
description: 'Filter by source Synthetic Account. Multiple values are allowed, e.g. `source_synthetic_account_uid[]=4XkJnsfHsuqrxmeX&source_synthetic_account_uid[]=aeD4RMVyTKaspEzj`.
'
- name: destination_synthetic_account_uid
in: query
schema:
type: string
example: exMDShw6yM3NHLYV
description: 'Filter by destination Synthetic Account. Multiple values are allowed, e.g. `destination_synthetic_synthetic_uid[]=exMDShw6yM3NHLYV&destination_synthetic_account_uid[]=1WVbRrp1s1MvTaAe`.
'
- name: synthetic_account_uid
in: query
schema:
type: string
example: 4XkJnsfHsuqrxmeX
description: 'Filter by Synthetic Account, source or destination. Multiple values are allowed, e.g. `synthetic_account_uid[]=4XkJnsfHsuqrxmeX&synthetic_account_uid[]=exMDShw6yM3NHLYV`.
'
- name: type
in: query
schema:
type: string
enum:
- ach
- ach_return
- atm_withdrawal
- book_transfer
- card_load
- card_purchase
- card_refund
- cash_load
- corporate_action
- credit
- denied_authorization
- dispute
- fee
- instant_payment
- interest
- other
- peer_to_peer_transfer
- reversal
- reversed_transfer
- wire
example: ach
description: 'Filter by type. Multiple values are allowed, e.g. `type[]=dispute&type[]=fee`.
'
- name: has_return
in: query
schema:
type: boolean
example: true
description: 'Filter by return. Only transactions that have returns (present or absend) to be included in the results.
'
- name: show_denied_auths
in: query
schema:
type: boolean
example: true
description: 'Causes transactions with a status of `denied` (suppressed by default) to be included in the results.
'
- name: show_expired
in: query
schema:
type: boolean
example: true
description: 'Causes transactions with a status of `expired` (suppressed by default) to be included in the results.
'
- name: status
in: query
schema:
type: string
enum:
- canceled
- queued
- pending
- settled
- failed
- expired
- denied
description: 'Filter by status. Multiple values are allowed, e.g. `status[]=queued&status[]=pending`.
'
- name: search_description
in: query
schema:
type: string
example: Transfer*
description: 'Attempts to search for the provided string in the description field. ''*'' can be used as a wildcard at the beginning or end of the string. Any record with a match will be returned.
'
- name: include_zero
in: query
schema:
type: boolean
example: true
description: 'Causes transactions with a `us_dollar_amount = 0` (suppressed by default) to be included in the results.
'
- $ref: '#/paths/~1pools/get/parameters/1'
- $ref: '#/paths/~1pools/get/parameters/2'
- name: sort
in: query
schema:
type: string
enum:
- created_at_asc
- created_at_desc
- description_asc
- description_desc
- id_asc
- id_desc
- settled_index_asc
- settled_index_desc
- us_dollar_amount_asc
- us_dollar_amount_desc
- name: created_at_after
in: query
schema:
$ref: '#/paths/~1transactions/get/parameters/17/schema'
description: 'Return only results with `created_at` after the provided ISO 8601 date or timestamp
'
- name: created_at_before
in: query
schema:
$ref: '#/paths/~1transactions/get/parameters/17/schema'
description: 'Return only results with `created_at` before the provided ISO 8601 date or timestamp
'
- name: settled_at_after
in: query
schema:
type: string
format: date-time
example: '2020-01-01T00:00:00Z'
description: 'Return only transactions with `settled_at` after the provided ISO 8601 timestamp
'
- name: settled_at_before
in: query
schema:
$ref: '#/paths/~1transactions/get/parameters/17/schema'
description: 'Return only transactions with `settled_at` before the provided ISO 8601 timestamp
'
- name: initial_action_at_after
in: query
schema:
$ref: '#/paths/~1transactions/get/parameters/17/schema'
description: 'Return only transactions with `initial_action_at` after the provided ISO 8601 timestamp
'
- name: initial_action_at_before
in: query
schema:
$ref: '#/paths/~1transactions/get/parameters/17/schema'
description: 'Return only transactions with `initial_action_at` before the provided ISO 8601 timestamp
'
- name: settled_index_after
in: query
schema:
type: integer
example: 123
description: 'Return only transactions with `settled_index` after the provided value
'
- name: settled_index_before
in: query
schema:
type: integer
example: 123
description: 'Return only transactions with `settled_index` before the provided value
'
- name: id_after
in: query
schema:
type: integer
example: 123
description: 'Return only transactions with `id` after the provided value
'
- name: id_before
in: query
schema:
type: integer
example: 123
description: 'Return only transactions with `id` before the provided value
'
responses:
'200':
description: A list of Transactions is returned
headers:
x-trace-id:
$ref: '#/paths/~1auth/post/responses/201/headers/x-trace-id'
content:
application/json:
schema:
allOf:
- $ref: '#/paths/~1pools/get/responses/200/content/application~1json/schema/allOf/0'
- type: object
properties:
data:
type: array
items:
allOf:
- $ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/0'
- type: object
properties:
instant_payment:
type: object
description: 'Instant payment information. Only present if the Transaction is an instant payment.
'
allOf:
- $ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/instant_payment/allOf/0'
wire:
type: object
description: 'Wire-specific information. Only present if the Transaction is a wire.
'
allOf:
- allOf:
- $ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/wire/allOf/0/allOf/0/allOf/1'
- $ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/wire/allOf/0/allOf/1'
- $ref: '#/paths/~1sandbox~1mock_transactions/post/requestBody/content/application~1json/schema/allOf/1'
- $ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/wire/allOf/0/allOf/3'
required:
- counterparty_name
ach:
type: object
description: 'ACH-specific information. Only present if the Transaction is an ACH. The optional `iat` object within `ach` contains details for International ACH Transactions. It is only included if `iat_ach_display_enabled` is set to `true` for the program and the transaction contains IAT data.
'
allOf:
- allOf:
- $ref: '#/paths/~1transfers/post/responses/201/content/application~1json/schema/allOf/0/allOf/3/properties/ach/allOf/0'
- type: object
properties:
ach_return_code:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/ach_return_code'
ach_return_reason:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/ach_return_reason'
noc_code:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/noc_code'
noc_reason:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/noc_reason'
transfer_trace_id:
$ref: '#/paths/~1transfers/post/responses/201/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/transfer_trace_id'
originator_routing_number:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/originator_routing_number'
counterparty_name:
type: string
description: Counterparty name.
iat:
$ref: '#/paths/~1transactions~1%7Buid%7D/get/responses/200/content/application~1json/schema/allOf/1/properties/ach/allOf/0/allOf/1/properties/iat'
- $ref: '#/paths/~1transactions~1%7Buid%7D~1authorize/put/responses/200/content/application~1json/schema'
examples:
transactions:
value:
total_count: 24
count: 8
limit: 8
offset: 1
data:
- adjustment_uid: null
customer_uid: Trzqy9t6j6tFGoG3
created_at: '2019-10-15T15:53:13.591Z'
custodial_account_uids:
- Gw4gr1T81YrvLT6M
- 66gso857LyQWC6XN
description: Transfer from "Bank ABC" to "Emergency Cupcake Funds"
destination_synthetic_account_uid: 15gTLPAEzHxtSrU6
id: 27
initial_action_at: '2019-10-15T15:53:13.586Z'
net_asset: positive
return_uid: null
settled_at: '2019-10-16T12:51:12.673Z'
settled_index: 8
source_synthetic_account_uid: rJuYjZuLei2TZji9
statement_posted_at: '2019-10-17T00:01:53.682Z'
status: settled
transaction_batch_uid: '3'
transaction_event_uids:
- MB2yqBrm3c4bUbou
transfer_uid: 1qVSAEjsV55vDZxX
type: ach
uid: SMwKC1osz77DTEiu
us_dollar_amount: '5.21'
virtual_reference_number_uid: null
ach:
originator_name: Mr. Original
originator_routing_number: '123456789'
company_id: ABC654
company_discretionary_data: Shhhh
counterparty_name: Receiver Account Name
prenote: false
sec_code: CCD
payment_type: S
entry_description: Excellent entry
service_processing: STANDARD
effective_entry_date: '2023-12-12'
id_number: 543-DEF
ach_return_code: null
ach_return_reason: null
addenda: Oops, forgot to mention
noc_code: C04
noc_reason: Bank account name change
noc_corrected_data: Aaron Velazquez
transfer_trace_id: A1Z2b3y4c5x6DW78
iat:
foreign_exchange_indicator: FF
foreign_exchange_reference_indicator: '3'
foreign_exchange_reference: null
iso_destination_country_code: US
iso_originating_currency_code: USD
iso_destination_currency_code: USD
transaction_code: '22'
transaction_type_code: MIS
foreign_payment_amount: null
foreign_trace_number: null
originator_street_address: 410 TERRY AVENUE NORTH
originator_city_state_province: SEATTLE*WA
originator_country_postal_code: US*98109
odfi_name: BANK OF AMERICA NA
odfi_identification_number_qualifier: '01'
odfi_id: '121000358'
odfi_branch_country_code: US
rdfi_name: FIFTH THIRD BANK NATIONAL ASSOCIA
rdfi_identification_number_qualifier: '01'
rdfi_id: 071919133
rdfi_branch_country_code: US
counterparty_street_address: 228 S BURNS
counterparty_city_state_province: INDEPEDENCE*KS
counterparty_country_postal_code: US*67301
payment_related_information_1: NTE*ADD*FCS003348198932 PAYMENT-NUM 351380\\NTE*ADD*601 POP GOODS AND SERVICES
payment_related_information_2: null
foreign_correspondent_banks:
- name: BANK OF AMERICA CANADA
id_number_qualifier: '01'
id_number: '121000358'
branch_country_code: CA
- adjustment_uid: null
customer_uid: Trzqy9t6j6tFGoG3
created_at: '2023-07-17T07:07:07.707Z'
custodial_account_uids:
- Gw4gr1T81YrvLT6M
- 66gso857LyQWC6XN
description: ACH return debited from 15gTLPAEzHxtSrU6
destination_synthetic_account_uid: rJuYjZuLei2TZji9
id: 40
initial_action_at: '2023-07-17T07:07:07.707Z'
net_asset: negative
return_uid: 9ZZ87saSFLkkDG7z
settled_at: '2023-07-17T09:07:07.707Z'
settled_index: 8
source_synthetic_account_uid: 15gTLPAEzHxtSrU6
statement_posted_at: '2019-10-17T00:01:53.682Z'
status: settled
transaction_batch_uid: '3'
transaction_event_uids:
- MB2yqBrm3c4bUbou
transfer_uid: 1qVSAEjsV55vDZxX
type: initiated_ach_return
uid: SMwKC1osz77DTEiu
us_dollar_amount: '5.21'
virtual_reference_number_uid: null
ach:
ach_return_code: R02
ach_return_reason: Account closed
addenda: TXN0055BADD1E cancelled
company_discretionary_data: Shhhh
company_id: ABC654ZY12
counterparty_name: Marge's
# --- truncated at 32 KB (146 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/fifth-third-bancorp/refs/heads/main/openapi/fifth-third-bancorp-transactions-api-openapi.yml