Skip to main content

Payment API

This document provides a comprehensive migration guide for transitioning from FedNow to PIPA (PayCenter Instant Payments API) Payment API functionality.

It highlights all essential changes including endpoints, headers, request/response structures, identifiers, and error handling to ensure a smooth migration process.

1. Endpoint & Header

API Endpoint

AreaFedNowPIPA
HostNameSandbox : fedwag01.eagle.jhapaycenter.com
Production: fedwag01.tango.jhapaycenter.com
Sandbox : ipa01.eagle.jhapaycenter.com
Production: ipa01.tango.jhapaycenter.com
URL/v1/institutions/{senderrtn}/environments/{envname}/products/paycenter/networks/fednow/credit-transfers/v2/paycenter/institutions/{senderrtn}/environments/{envname}/products/pipa/credit-transfers
HeaderFedNowPIPA
X-Request-ID• Renamed as OriginatorReferenceId
Optional
• Unique per request
• Must follow UUID format
Required
• Unique per request
• Must follow UUID format
• Returned in all response headers

2. Request Body

Debtor

FieldFedNowPIPA
NameOptionalRequired
AccountNumberRequiredRequired
AccountTypeRequired
Allowed types: Checking, Savings, MICR
Required
Allowed types: Checking, Savings, MICR
UltimateDebtor.NameOptionalOptional

Creditor

FieldFedNowPIPA
NameRequiredRequired
RoutingNumberRequiredRequired
AccountNumberRequiredRequired
UltimateCreditor.NameOptionalOptional

CreditTransferDescription

FieldFedNowPIPA
AmountRequiredRequired
TransferFeeNot AvailableOptional
OriginatorTypeRequired
Allowed types: CONSUMER, BUSINESS, GOVERNMENT
Required
Allowed types: CONSUMER, BUSINESS, GOVERNMENT
UserNameRequiredRequired
NotesOptionalOptional
For more details:

3. Response Body

AreaFedNowPIPA
StructureNested within CreditTransfer ObjectFlattened structure with primary identifiers at the top level
Primary IdentifierCreditTransfer.IdPmtHubTrakId
StatusCreditTransfer.StatusStatus
For more details:

4. Error Response

AreaFedNowPIPA
StructureSimple object inside CreditTransferStandard PIPA error schema (consistent across all APIs)
Key FieldsMessage, Error (Code, Description)ResponseCode, Description, MessageSource, Details[], LogId
CodeError.CodeDetails[].Code
DescriptionError.DescriptionDetails[].Description
For more details:

5. Duplicate Error Response

AreaFedNowPIPA
Original Transaction IdentifierCreditTransfer.OriginalTransactionDetails.IdOriginalTransactionDetails.PmtHubTrakId
StatusCreditTransfer.OriginalTransactionDetails.StatusOriginalTransactionDetails.Status
For more details:

6. EES & Events

AreaFedNowPIPA
Primary IdentifiersNetworkPrimaryReferenceId, TrnRcptId, PmtHubTrakId, X-Request-ID, PaymentIntegratorCode, PmtRailTypeNetworkPrimaryReferenceId, TrnRcptId, PmtHubTrakId, X-Request-ID, PaymentIntegratorCode, PmtRailType
EventsOutbound - DrPmt/Acpt,DrPmt/Rej
Inbound - CrPmt/Acpt
Outbound - DrPmt/Acpt,DrPmt/Rej
Inbound - CrPmt/Acpt
For more details:

Migration Checklist

Quick Migration Steps
  1. Update endpoints → Switch to PIPA hostnames and updated API paths.
  2. Update headers → Use required X-Request-ID (UUID, unique per request) instead of optional OriginatorReferenceId.
  3. Add required fields → Ensure Debtor.Name and Debtor.AccountType are provided as required in PIPA.
  4. Handle new response → Use the flattened PIPA structure and read identifiers from PmtHubTrakId.
  5. Update error handling → Implement the PIPA standard error schema (ResponseCode, Description, MessageSource, Details[], LogId).