We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Client requirement is to make file limit checking. We can go with transaction limit, making number of days 0. It works, but it is impossible to make this monitor overrideable (tried changing risk error code with no effect). Also, next to suspendab...
Gateway Server should be able to process batches concurrently.
The best TPS we got in gateway server was 150. Our largest file from a customer has around 600k transactions. With the current throughput from Gateway server it woulld take around 1 hour and 7 minutes to ingest those payments. As a result, we woul...
CPA005 Transaction Rejected in FTM Base but Accepted by Gateway in PFS layer (Refer WorkItem Work Item 114946)
During AFT application development, we found that FTM Base rejected transactions where getting accepted by Gateway in PFS i.e. FTM Base Rejections are not considered by Gateway for updating a payment's status. We raised a RTC defect 114946 for thi...
No Audit Trail available for state/column change for a Payment/Item in FTM for CPS PFS layer
As per our analysis, we could find audit trail for transmission and batches. But there is no Audit trail for a payment/item. For example when does a payment's state change from Received to Accepted, From Accepted to Cancelled, from not-posted to p...
FTM CPS : UI should not allow Manual Return of Transaction with all available Return Reason Codes irrespective of its Record Type (PMR# TS004455925)
Whenever we try to manually return a transaction from UI it allows us to return the transaction with all the available reason codes irrespective of the record type(Credit/ Debit). According CPA Rules, UI should allow Debit and Credit records to be...
FTM CPS : Manual Returns from UI : Should be validating CPA rules for time limits for Returns. (Ref PMR TS004363369)
CPA Rule for Returning an AFT Transaction requires below date-time range validation. -> for credit transaction, the difference should not be more than 90 days. -> for personal debit transaction, the difference should not be more than 90 days...
As part of AFT application, we found issues with Automatic Distribution of Outound Transmissions by the distribution scheduler. We raised PMR# TS004448402 for the same. As per the PMR updates, the product is working as designed and required by ACH. But we see there is some scope of improvement here as mentioned in details in the PMR.
On doing test-cases surrounding "Automated Distribution" issue, we found that if a processing batch is "Not Ready For Distribution" and all the transactions inside that batch are either in Held or Rejected status, then Distribution Scheduler works...
Need a mechanism to hold an individual transaction for vetting by Safer Payments, while allowing other transactions to pass
This would work with Safer Payments to allow valid transactions to flow through FTM for processing, while only holding back individual transactions requiring more time for Safer Payments/fraud team to investigate.
Do not place IBM confidential, company confidential, or personal information into any field.