SAP Mobile Platform Review

Great transaction processing with good stability and very helpful technical support


What is our primary use case?

We have implemented SAP Mobile Platform into two to three banks. We are one of their OEM partners.

There are multiple types of customer onboarding. There are multichannel platforms like mobile apps, where you have an Agent and Salesforce app. From there, users can onboard the customer or the customers can do self-onboarding from ATM machines.

There are multiple types of transactions. We have mobile wallet transactions, including bill payments and telco-based top-ups, or we have QR code-based payments and we have integration with third-party agents as well. With the telco companies, the customers can walk into any of the telco agents and they can do cash-ins/outs.

What is most valuable?

SAP's Mobile Platform when has a lot of technical features, however, the way they have written the transaction processing is really smart and we're using it very successfully in terms of scalability and in terms of stability.

The initial setup is not overly complex.

The solution offers good scalability.

So far, the stability has been good.

We've found the technical support to be helpful.

What needs improvement?

There are multiple functionalities within the design however they're not, actually, a hundred percent available on the UI in SAP's platform. If they can work more on the UI platform or maybe they change the framework on which the UI is written. That would be great. Right now, it is older technology with older frameworks. It's not purely on microservices. They could transform it onto microservices in order to benefit us as a partner.

The licensing model is a bit dated.

For how long have I used the solution?

We started working with the solution in 2015. AT this point, it's been six years. It's been a while.

What do I think about the stability of the solution?

The solution is stable. It doesn't crash or freeze. It doesn't have bugs or glitches. It's reliable.

What do I think about the scalability of the solution?

The solution scales well. It's designed very smartly and can scale really well.

The solution works well for small, medium, or large organizations.

How are customer service and technical support?

We have been getting support from SAP on the technical aspects, however, we don't normally require much technical support as our team is fully enabled now. That said, whenever we need it, we have our support agreement with SAP and they provide us with support for that product.

They have good technical support services for the most part. They have a very streamlined process and the support is good. The people in support know the product. Sometimes there are incidents where we have gotten the support we needed a little late, however, overall, it's good.

How was the initial setup?

The initial setup is not overly complex. It's pretty straightforward. A company shouldn't have too much trouble with the process.

There are a lot of integrations involved when it comes to the deployment of the mobile wallet platform as it involves multiple integrations with central units, such as telcos, bill payment aggregators, and third-party agents.

When it comes to the maintenance, usually the maintenance is required on the integration part. Otherwise, from the engine point of view, there are a couple of queries every six months or so. We don't require support from SAP very often.

What about the implementation team?

We provide implementation services to our clients. We are the OEM partners. We have bundled our products and integrated them with the SAP platform and we are selling it with our proprietary name. This is our product which is built on the SAP platform. We have also implemented SAP's platform to a couple of banks, as well, without bundling any module.

What's my experience with pricing, setup cost, and licensing?

The industry has evolved now. In 2015, it wasn't that expensive. However, at this point in time, there is a lot of competition in the industry on the mobile wallet platform. There are multiple mobile platforms available and they are offering multiple pricing models. However, we are with SAP on their pricing model with a number of accounts.

It could be more competitive in the market if we could have different pricing models for the platforms. SAP needs to adjust how they license.

What other advice do I have?

We are implementors. We have some partnerships with Microsoft. In terms of the technology stack, we are using Microsoft, Oracle, and SAP, not IBM.

For the local industry, we have done some customizations on the solution and that's how we are using it.

We have implementations on both cloud and on-premises currently. We are using on-premises deployments as the industry where we have implemented it - the central bank - doesn't allow cloud-based implementations at this point in time.

I'd rate the solution at a nine out of ten. We've mostly been quite satisfied with the capabilities of the platform.

Which deployment model are you using for this solution?

On-premises
**Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Find out what your peers are saying about SAP, IBM, Temenos and others in Mobile Development Platforms. Updated: July 2021.
522,281 professionals have used our research since 2012.
Add a Comment
ITCS user
Guest