Skip to main content

Get Payment API

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

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

1. Endpoint & Identifier

API Endpoints

AreaRTPPIPA
HostNameSandbox : wag01.eagle.jhapaycenter.com
Production: wag01.tango.jhapaycenter.com
Sandbox : ipa01.eagle.jhapaycenter.com
Production: ipa01.tango.jhapaycenter.com
URL (Path Parameter)/v1/institutions/{senderrtn}/environments/{envname}/products/paycenter/networks/rtp/credit-transfers/{Id}

Id – Primary identifier returned in CT response.
/v2/paycenter/institutions/{senderrtn}/environments/{envname}/products/pipa/credit-transfers/{PmtHubTrakId}

PmtHubTrakId – Primary identifier returned in CT response.
URL (Query Parameter)/v1/institutions/{senderrtn}/environments/{envname}/products/paycenter/networks/rtp/credit-transfers?OriginatorReferenceId={OriginatorReferenceId}

OriginatorReferenceId - Client-provided reference to track the original request.
/v2/paycenter/institutions/{senderrtn}/environments/{envname}/products/pipa/credit-transfers?X-Request-ID={X-Request-ID}

X-Request-ID - Client-provided reference to track the original request.

2. Response Body

AreaRTPPIPA
TransferFeeNot AvailableIncluded

3. Error Response

AreaRTPPIPA
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

4. Authentication Error Response

AreaRTPPIPA
StructureReturned in XML formatReturned in JSON format

Migration Checklist

Quick Migration Steps
  1. Update endpoints → Switch to PIPA hostnames and updated API paths.
  2. Update Path parameters → Use PmtHubTrakId instead of Id values for path-based lookups.
  3. Update query parameters → Use X-Request-ID instead of OriginatorReferenceId for query-based lookups.
  4. Update error handling → Implement the PIPA standard error schema (ResponseCode, Description, MessageSource, Details[], LogId).
  5. Update authentication error handling → Expect JSON format instead of XML for authentication errors.