Quick summary
KeyBank offers two payment rails, Real-Time Payments (RTP) and wire transfers, which support irrevocable, credit‑push payments. The right choice depends on timing, availability, and payment context, not just speed.
Real-time payments
RTP is well suited for just-in-time payments, operational disbursements, and customer or vendor payments where timing certainty is critical.

Choose RTP when:
- You need immediate settlement with confirmation in seconds.
- Payments can be sent 24x7, including weekends and bank holidays.
- You want the flexibility to release funds at the exact moment they are due, without cutoff constraints.
- You need the option of delayed payables to schedule and time the outflow of payments.
Wire transfers
Wire transfers are commonly used for treasury movements, real estate transactions, international payments, and other high‑value use cases that require established wire networks.

Choose wire transfers when:
- You are sending high value or large volume payments.
- Payments occur during business days and can align with bank processing windows.
- The transaction involves complex routing, such as intermediary banks or international destinations.
- Regulatory review, compliance checks, or detailed payment instructions are expected.
RTP API products
Use the RTP Send Payment API to send money immediately. Monitor account activity or get transaction details with the RTP Inquiry API.
Wire API products
Send wire transfers using the Wire Transfer API. Then, follow-up on status and transfer details with the Wire Inquiry API.
RTP and Wire Alerts
Setup KeyBank webhooks in your application to receive real-time alerts when the status of an RTP or wire transaction changes.
How it works
Payment flow
- Provide authentication. Get your KeyBank access token and include the required credentials. (Check out how to get an access token.)
- Initiate a payment or transfer. When sending a payment through KeyBank’s RTP or Wire service rails, every request you build must supply the information needed to move funds accurately, securely, and without duplication. Your request must include a set of reference IDs and clearly defined party details.
- Unique reference IDs ensure payments are not duplicated and can be reconciled later.
- Party details identify who is sending and receiving the money and what the payment represents.
- Submit and review. Submit your request and review the response. A response that indicates acceptance (not necessarily settlement).
- Monitor status and progress. Use inquiry endpoints or webhooks to monitor status and outcome of your transaction.
Payment scenarios
The following sections describe common payment scenarios for RTP, Wire, or both. Each scenario can affect how you structure a payment request, especially when it comes to identifying the participating parties and financial institutions. Refer to the API documentation for detailed conditions and requirements when submitting a payment request. See RTP Key notes or Wire Key notes for request structure requirements.
Domestic payments (RTP and Wire)
I want to send money from my KeyBank account to pay a company.
This is the most common type of payment. A KeyBank client sends U.S. dollars to a beneficiary that banks with a different U.S. financial institution.
Example: Tom Jones sends money from his KeyBank account to ABC Company, which banks at Northstar Financial Bank.
Domestic third-party payment (Wire)
I want to wire money to a smaller bank that does not accept wire transfers directly.
This is a domestic third-party (or intermediary) wire payment. Some smaller banks and credit unions do not accept wire transfers directly from the Federal Reserve. Instead, they rely on a correspondent or intermediary bank that does accept wires.
Example: John Smith wants to wire money from his KeyBank account to Beatrice Simpson, who banks at Otto’s Savings and Loan. Otto’s does not accept wire transfers directly. Beatrice provides wiring instructions from her bank, which specify an intermediary bank—Northstar Financial Bank.
In this scenario, KeyBank sends the wire to Northstar, which then forwards the funds to Otto’s Savings and Loan for credit to Beatrice’s account.
On Behalf Of payment (RTP and Wire)
I need to pay on behalf of someone else.
An On Behalf Of (OBO) payment occurs when the sender initiates a payment on behalf of the payer—the individual or organization that owes the funds. The sender executes the payment, but the payer retains the financial obligation. The payee is the party receiving the funds (for example, a vendor, employee, or utility company).
Notes:
- Nested OBO payments (involving more than one payer or payee) are not supported.
- OBO payments are more common with RTP. When used with wire transfers, they are generally treated as domestic third‑party wire payments.
Example: Perry Johnson operates a property management company and needs to pay utility bills on behalf of tenants. Perry uses Summit National Bank as a payment processor. Summit holds the account at KeyBank and initiates the payment.
Summit sends the funds from its KeyBank account to EZ Electric Company, which banks at Northstar Financial Bank. In this scenario, Summit National Bank is the KeyBank account holder, not Perry Johnson.
Domestic drawdown (Wire)
I need to request funds from another party.
A domestic drawdown payment is used when you need funds from another party’s account. Payroll processors and similar service providers commonly use this. There must be a signed debit authorization agreement between the parties.
Example: ABC Company has a debit authorization agreement with XYZ Company, which banks at Northstar Financial Bank. ABC Company submits a drawdown request for a specific amount. Northstar can either release the funds or reject the request based on the agreement and available funds.
International Payment (Wire)
I need to send money to a company outside the United States.
International wire transfers support beneficiaries whose banks are located outside the United States and its territories. Payments are currently supported in USD and require global bank identifiers such as a BIC.
Example: Geraldine Marmalade sends a payment from their KeyBank account to DE Sports; a company located in Germany. The beneficiary bank is Worldlink Financial in Stuttgart.
Monitor RTP and Wire transactions
KeyBank offers one of two ways to monitor your transactions - inquiry APIs or webhooks. With the RTP Inquiry API or Wire Inquiry API, you can validate payment activity and monitor the lifecycle of the payment, from initiation to settlement. With webhooks, you get real-time change event notification.
Inquiry APIs
Use the Inquiry APIs when you need visibility into payment activity. The list endpoint helps you retrieve groups of transactions for reporting and reconciliation, while the detail endpoint allows you to inspect a single transaction’s complete lifecycle, including its participating parties and status events.
Search for related transactions
Use /list when you need to view multiple transactions tied to the same originating account or a broader time window.
Use cases
Daily cash-position monitoring
A treasury or finance application queries all RTP or Wire transactions for a business account each morning to confirm which payments are settled overnight (Wire) or in real time (RTP). This helps the business verify expected outflows and adjust liquidity planning.
Reconciliation across a billing cycle
A billing system retrieves transactions from the last 30–60 days to match payments against invoices. This is especially helpful when the system uses
originatorReferenceorreceiversReferenceto reconcile incoming payments.Investigate customer inquires
Customer support may need to quickly locate all payments initiated by a specific business account within a date range to determine:
- whether a payment was sent,
- if it is still in flight (IN_PROCESS, IN_REVIEW),
- or if it failed.
Batch reporting for downstream systems
Clients that run downstream operations (ERP, accounting, order management, payouts, etc.) can run periodic list calls to ingest a full ledger of recent RTP or Wire activity into their systems of record.
Retrieve a specific transaction
Use /detail when you want complete information about a specific payment, including status and parties.
Use cases
Confirming settlement status
Systems can poll the detail endpoint after initiation to check whether the payment has been completed, settled, or rejected. This is especially helpful for RTP due to its real-time speed, or Wire when regulatory, OFAC, or repair checks may delay the transaction.
Compliance or audit inquiry
Regulatory teams may need all associated details (originator, beneficiary, amounts, timestamps, and references) for a transaction. The detail endpoint provides this without exposing unrelated payment data.
Troubleshooting missing or delayed payments
If a customer says, “Did my payment go through,” retrieving the transaction by ID immediately shows whether the payment is:
- stuck in IN_REVIEW,
- waiting for a downstream bank acknowledgement,
- or has failed and needs repair or resubmission.
Webhook notifications
Webhooks are automated notifications your system can receive when something important happens with an RTP or wire transaction — like if the payment is complete or pending more details. Rather than polling for transaction status, webhooks let you know in real time when there is a change event, so you can act right away (like updating a dashboard or notifying a customer).
6-minute read
updated Feb. 25, 2026



