IBM Support

PH06129: IF RECIPIENT EXISTS FOR UNKNOWN PAYMENT BEFORE TOKEN CREATED ON RECEIVING SIDE, ORIG PAYMENT WONT CANCEL IF RECEIVER RESTRICTED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • When a payment is being sent to an unknown recipient, then
    saving the recipient.  When the token registers with Zelle, it
    is being registered with a bank that is restricted to the
    customer.  An error is being caused by the Match Recipient call
    done when updating the recipient.  We need to catch the thrown
    exception and continue processing thru until the payments
    associated with the token are cancelled.
    
    
    WQE is setup with EWS as a restricted bank. A payment was
    created to an Unknown recipient using the mobile app, which also
     creates a recipient record. The recipient's token was then
    registered on CXC as a WQE user. When FTM receives the
    OnTokenChangeNotification, it fails with "160500: Failure while
    calling CXC Match Recipient with reason connection-not-allowed"
    but does not fail the payment. This is due to the recipient, and
     cannot be created if the payment is added via SOAP without
    adding a recipient also. The following error will occur if the
    recipient does not exist, but the payment will fail correctly:
    
    
    [10/17/18 21:31:48:439 UTC] 00000c56 CXCServiceBea 3 Exit:
    matchRecipient
    
    [10/17/18 21:31:48:439 UTC] 00000c56 CXCPaymentBea E CXCEN528S:
    Database Accessor Exception. 122200: connection-not-allowed,
    Connection from Organization [Id=HI1, name=H Bank] to
    Organization [Id=WQE, name=W Bank WQE] is not allowed
    at this time. {1}
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R
    com.ibm.fxh.zel.ui.ejb.cxcservice.CXCServiceException: 122200:
    connection-not-allowed, Connection from Organization [Id=HI1,
    name=H Bank] to Organization [Id=WQE, name=W Bank WQE]
    is not allowed at this time.
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.CXCPaymentBean.callCXCMatchRec
    ipient(CXCPaymentBean.java:3261)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.CXCPaymentBean.updateUnknownIn
    formation(CXCPaymentBean.java:5230)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.CXCPaymentBean.handleUnknownPa
    yment(CXCPaymentBean.java:778)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.CXCPaymentBean.continueUnknown
    Payment(CXCPaymentBean.java:727)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.EJSLocal0SLCXCPaymentBean_c4a2
    1fa8.continueUnknownPayment(EJSLocal0SLCXCPaymentBean_c4a21fa8.j
    ava)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcpayment.CXCPaymentManagement.continueU
    nknownPayment(CXCPaymentManagement.java:165)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcnotification.CXCNotificationBean.proce
    ssTokenChange(CXCNotificationBean.java:1359)
    
    [10/17/18 21:31:48:446 UTC] 00000c56 SystemErr R at
    com.ibm.fxh.zel.ui.ejb.cxcnotification.CXCNotificationBean.onTok
    enStatusChange(CXCNotificationBean.java:348)
    

Local fix

Problem summary

Problem conclusion

  • Code change to allow a payment to be cancelled when the payment
    was made to an unknown recipient.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH06129

  • Reported component name

    ACH SERVICES FT

  • Reported component ID

    5725S7630

  • Reported release

    306

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-05

  • Closed date

    2019-01-25

  • Last modified date

    2019-01-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    ACH SERVICES FT

  • Fixed component ID

    5725S7630

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"306","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
14 October 2021