Skip to Main Content
IBM Data and AI RegTech Ideas Portal

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 offering manager 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.


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

ADD A NEW IDEA

FILTER BY CATEGORY

FTM for Digital Payments

Showing 24

Zelle - Alerting the client when a contact (recipient) is added or updated.

We need to send an alert to our clients when a contact (recipient) is added or updated. We are seeing a lot of fraudulent activity around this. We need to alert the clients when changes are made to ensure that the client was the party that request...
12 months ago in FTM for Digital Payments / Alerting & Notification 1 Delivered

Request to add PAYMENT_ID field/value to the JMS_TEXT in our logs. Also, to be clear, one of our main goals it to be able to count and/or omit H50 payment ids so we are looking to see the full payment id/orig seq number added to the JMS_TEXT.​

HUNTINGTON BANK - Business Justification - Idea Submission TS004601479 - HOPS ZELLE - Request to add PAYMENT_ID field/value to the JMS_TEXT in our logs We are looking to use our log entries to calculate and track payment SLAs while excluding certa...
over 1 year ago in FTM for Digital Payments / Transaction Processing - Ingestion 2 Delivered

Recipient Management

Recipient management should provide a UI for maintenance of recipient data. There currently is no UI that can allow an Ops user to maintain this information UI come up read only in 3.2.5, we need UI for editing
almost 2 years ago in FTM for Digital Payments / Transaction Processing - Distribution 1 Delivered

Adding dual approval process to the schedule management

discussed on the call with Craig on 9/18/2020 the following change is needed in FTM for Dual Approval: Life-cycle management of scheduled payments Record list of approvers, approver decision, approval deadline On reaching approval deadline, the fu...
almost 2 years ago in FTM for Digital Payments / Transaction Processing - Distribution 1 Delivered

Update schedule – there is a set of fields which we need to store while setting up schedules

update schedule – there is a set of fields which we need to store while setting up schedules and current FTM API does not allow to send those fields during schedule update. Missing Field List: Payer account Memo Purpose
almost 2 years ago in FTM for Digital Payments / Transaction Processing - Distribution 2 Delivered

Recurrent payments of any type

ability to schedule a recurrent payment for wires or any other payment type(payment-independent feature)
about 2 years ago in FTM for Digital Payments / Transaction Processing - Distribution 3 Delivered

API for business rules

Provide CRUD API for managing Business Rules
about 2 years ago in FTM for Digital Payments / Administration & Configuration 1 Delivered

Payee management

provide CRUD APIs for management of Payees

scheduled payment independent of payment type

provide ability to schedule future dated payment this feature should not be dependent on the payment type
about 2 years ago in FTM for Digital Payments / Transaction Processing - Distribution 1 Delivered

FTM for TCH - Considers weekends as holidays by default - Remove this default configs to allow clients to make the decision

Huntington has used the out of the box Product Deadlines provided by IBM for TCH Receive (TCHI – Product Code). This setup indicates that Saturday and Sunday are to be treated as business days. These days are not treated as business days by busine...