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 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
During Safer Payments implementation some issues were raised regarding the form SP relates the transaction messages with mandators. In the mandator structure there needs to have Issuers and Acquirers. Most of transactions belong to two mandators, one issuer and one acquirer. Since in the current Safer Payments version, one transaction can only be managed by one only mandator there is an issue. To overcome this situation the request is that SP product enhancement to have multiple ownership of the transactions, without the need to duplicate the transaction. Thus, safer payments should be able to associate a transaction to several entities (issuers, acquirers, merchants), according to data in certain fields. Example: The transaction must be visible to the issuer, acquirer and merchant, according to their respective identification codes, which codes are contained in the message of the transaction.
Do not place IBM confidential, company confidential, or personal information into any field.