Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Digital Core
Modernize with cloud-native core banking technology.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.

RTP Errors

Docs > Payments > Payments > RTP (Real Time Payments) > RTP Errors

Possible RTP Errors

Class NameFieldConstraint TypeErrorHTTP/Error Status CodePayments Orchestrator / JH ErrorError ExplanationCorrective Action
RtpAccountDetailsaccountNumberBlankerror.accountNumber.blank400Payments OrchestratorAccount Number field is emptyEnsure Account Number field is not empty
RtpAccountDetailsaccountNumberSizeerror.accountNumber.size400Payments OrchestratorAccount Number is too short or too longAccount number size: min = 3, max = 20
RtpAccountDetailsaccountNumberPatternerror.accountNumber.invalid400Payments OrchestratorAccount Number does not meet required formatThe Payments Orchestrator system accepts account numbers that can include any combination of letters (both uppercase and lowercase), numbers, dots (.), slashes (/), parentheses (), ampersands (&), single quotes ('), spaces, and hyphens (-)
RtpAccountDetailsroutingNumberBlankerror.routingNumber.blank400Payments OrchestratorRouting Number field is emptyEnsure Routing Number field is not empty
RtpAccountDetailsroutingNumberSizeerror.routingNumber.size400Payments OrchestratorRouting Number is too short or too longRouting number size: min = 9, max = 9
RtpAccountDetailsroutingNumberPatternerror.routingNumber.invalid400Payments OrchestratorRouting Number does not meet required formatOur system expects a routing number that is exactly 9 digits long and only includes number 0-9
RtpCreditPayeevictorCounterpartyIdBlankerror.victorCounterpartyId.blank400Payments OrchestratorCounterparty field is emptyEnsure Counterparty field is not empty
RtpCreditPayeevictorCounterpartyIdSizeerror.victorCounterpartyId.size400Payments OrchestratorCounterparty field is too longThe Payments Orchestrator system accepts a counterpartyId that has has a maximum of 16 characters and can include any combination of letters (both uppercase and lowercase) and numbers (0-9).
RtpCreditPayeeultimateCreditorSizeerror.ultimateCreditor.size400Payments OrchestratorUltimateCreditor field is too longThe Payments Orchestrator system accepts an UltimateCreditor description that has a maximum of 100 characters. This can only be included if the originator_type is BUSINESS
RtpCreditPayeraccountNumberBlankerror.accountNumber.blank400Payments OrchestratorAccount Number field is emptyEnsure Account Number field is not empty
RtpCreditPayeraccountNumberSizeerror.accountNumber.size400Payments OrchestratorAccount Number is too short or too longAccount number size: min = 3, max = 20
RtpCreditPayeraccountNumberPatternerror.accountNumber.invalid400Payments OrchestratorAccount Number does not meet required formatThe Payments Orchestrator system accepts account numbers that can include any combination of letters (both uppercase and lowercase), numbers, dots (.), slashes (/), parentheses (), ampersands (&), single quotes ('), spaces, and hyphens (-)
RtpCreditPayerultimateDebtorSizeerror.ultimateDebtor.size400Payments OrchestratorUltimateDebtor field is too longThe Payments Orchestrator system accepts an UltimateDebtorr description that has a maximum of 100 characters. This can only be included if the originator_type is BUSINESS
RtpCreditPaymentDetailsamountBlankerror.amount.blank400Payments OrchestratorAmount field is emptyEnsure Amount field is not empty
RtpCreditPaymentDetailsamountPatternerror.amount.invalid400Payments OrchestratorAmount field does not meet required formatThe Payments Orchestrator system accepts an Amount that is either a whole number (i.e 10, 100) or decimal number (i.e 10.10, 100.10)
RtpCreditPaymentDetailsoriginatorTypeNullerror.originatorType.null400Payments OrchestratorOriginatorType field is emptyEnsure OriginatorType field is not empty
RtpCreditPaymentDetailsoriginatorTypeEnum Patternerror.originatorType.invalid400Payments OrchestratorOriginatorType field does not meet expected valueThe Payments Orchestrator system expects an OriginatorType field that is either BUSINESS or CONSUMER (case sensitive).
RtpCreditPaymentDetailsnotesSizeerror.notes.size400Payments OrchestratorNotes field is too longThe Payments Orchestrator system accepts a Notes field that has a maximum of 150 characters.
RtpCreditPaymentRequestclientReferenceIdSizeerror.clientReferenceId.size400Payments OrchestratorClientReferenceID field is too longThe Payments Orchestrator system accepts a ClientReferenceID that is 128 characters long
RtpRefundRequestvictorTransactionIdBlankerror.victorTransactionId.blank400Payments OrchestratorvictorTransactionId is emptyEnsure victorTransactionId is not empty
RtpRefundRequestvictorTransactionIdSizeerror.victorTransactionId.size400Payments OrchestratorvictorTransactionId is too longvictorTransactionId has a maximum of 36 characters
RtpRefundRequestreasonCodeBlankerror.reasonCode.blank400Payments OrchestratorReasonCode field is emptyEnsure ReasonCode field is not empty
RtpRefundRequestreasonCodeSizeerror.reasonCode.size400Payments OrchestratorReasonCode field too longReasonCode field can have a maximum of 4 characters
RtpRefundRequestreasonCodePatternerror.reasonCode.invalid400Payments OrchestratorReasonCode field does not meet expected valueTechnical error, contact Payments Orchestrator support.
RtpRefundRequestnotesSizeerror.notes.size400Payments OrchestratorNotes field is too longThe Payments Orchestrator system accepts a Notes field that has a maximum of 150 characters. Notes field can include any combination of letters (both uppercase and lowercase), numbers, dots (.), slashes (/), parentheses (), ampersands (&), single quotes ('), spaces, and hyphens (-)
RtpRefundRequestclientReferenceIdSizeerror.clientReferenceId.size400Payments OrchestratorClientReferenceID field is too longThe Payments Orchestrator system accepts a ClientReferenceID that is 128 characters long and
General RTP Errorserror.rtp.payment634Payments OrchestratorTwo possible reasons for this error:
1. Unable to create RTP transaction
2. Thread interrupt while waiting to retry RTP action		Possible technical error, please try again. If it persists please contact Payments Orchestrator support.
General RTP Errorserror.get.rtp.bank.details635Jack HenryUnable to getBankDetails from RTPServerConfirm recipient is on the RTP network and try again later. If the issue persists contact Payments Orchestrator support.
General RTP Errorserror.rtp.failed636Jack HenryTwo possible reasons for this error:
1. The Payments Orchestrator system received a failed status when querying RTP transaction against Jack Henry
2. The payment was rejected by the receiving institution		Ensure valid and active counterparty and try again later.
General RTP Errorserror.invalid.rtp.account.number632Payments OrchestratorRTP Account Number is invalid for counterparty idEnsure counterparty has correct and valid RTP Account Number
General RTP Errorserror.invalid.rtp.due.date633Payments OrchestratorDue date cannot be more than 365 days from current date and it cannot be in the pastEnsure due date is withing the allowed time span and it's correctly formatted as "yyyy-mm-dd".
General RTP Errorserror.invalid.rtp.routing.number640Jack HenryRouting Number does not support RTP payments generally or the specific payment type (Credit Transfer, Refund, Payment Request)Ensure routing number is valid and capable of RTP payments or the specific payment type being executed. If you have validated that the routing number should support RTP and you are still experiencing this error, please reach out to support to ensure configuration is correct on our end.
General RTP Errorserror.bank.not.in.rtp643Jack HenryBank not part of RTP Network/Not signed on to RTP networkEnsure financial institution is capable of RTP payments
General RTP Errorserror.rtp.refund.alreadyExists429Payments OrchestratorTransaction refund already existsEnsure that a refund is not being duplicated.
Did this page help you?
Last updated Mon Jun 29 2026