What are the best practices for testing mobile applications with different payment and billing systems?

Isso envolve selecionar softwares e frameworks que sejam compatíveis com a variedade de sistemas operacionais móveis, gateways de pagamento, e modelos de cobrança utilizados pelo aplicativo. Ferramentas que oferecem automação de testes, simulação de transações de pagamento em ambientes seguros, e a capacidade de imitar diversas condições de rede e dispositivos são particularmente valiosas. Essa seleção cuidadosa permite realizar testes abrangentes, identificar problemas de compatibilidade, e garantir que o processo de pagamento funcione de maneira fluida e segura para os usuários, em diferentes dispositivos e contextos.

An example I have seen when we were developing an EPOS app to handle customer order and then push the ticket to an embedded payment page within the device was a simple process. Purely because the integration was on a local device. (pax a920). Which was really cool to develop because it came with a test device with test payment cards etc..however I am seeing more complex systems nowadays where you will need to download 2 apps on the device (IOS or Android) and locally integrate the payment page to the second app where it will be able to handle NFC payment on the enabled device.. it’s a great solution for contactless payments and there are test applications available via softpos (Mastercard has introduced one)providers out there

Testar os aspectos de segurança e conformidade é crucial ao desenvolver aplicativos móveis que envolvem sistemas de pagamento e cobrança, garantindo que as transações dos usuários sejam seguras e estejam em conformidade com as normas regulatórias, como PCI DSS para pagamentos com cartão e GDPR para proteção de dados na Europa. Isso inclui a realização de testes de penetração para identificar vulnerabilidades, a implementação de testes de conformidade para verificar a aderência às leis e regulamentos aplicáveis, e a análise de segurança do código para detectar falhas que possam comprometer dados sensíveis.

When it comes to a payment enabled device all the security protocols are available hardcoded within the device, however if you are building an app that needs to communicate with a external payment gateway or processing system, then I would suggest its authentication protocols are secured and also when it’s an external payment page which is accessed via a link and not an embedded app sitting on the device it gets more complex because then you need to be aware of screen jacking scams etc. It’s not particularly the PCI Certification that is more important at this stage because that’s the gateways responsibility and most of processors would have that in place to process any payment. I would suggest having an app to app integration

Testar a interface e a experiência do usuário (UX) é essencial para assegurar que os aplicativos móveis, especialmente aqueles com sistemas de pagamento e cobrança, sejam intuitivos, fáceis de usar e visualmente agradáveis. Isso envolve a avaliação da navegabilidade do aplicativo, a clareza dos elementos visuais e instruções, a rapidez e eficiência dos processos de pagamento, e a adaptabilidade do design em diferentes tamanhos de tela e orientações. A implementação de testes de usabilidade, que podem incluir sessões de teste com usuários reais, permite identificar pontos de fricção na jornada do usuário e oportunidades de melhoria.

I would have a few pilot customers that will use the app for testing purposes to get the feedback from them and develop accordingly. Some of the apps I see out there are beautifully designed but when it comes to usability in a real word environment it’s not that helpful sometimes, so it’s best to mock up something that’s works and have used by some pilot customers to get a better insight of what and how you can develop further

This would also be down to the kind of audience you are targeting, is it an app for individual persons to use or SME or corporate enterprises ? Because it varies widely of how it is used and every user has different needs, so would narrow the audience and see what your feedback looks like and develop accordingly.

This would be again down to the pilot beta users you want to try it with, and according to the feedbacks and systems in place to log the performance and crash logs etc. You will have a better idea of the performance. Also it’s a good way to layout your system in a way that it auto increases performance behind scenes (AWS is good at this). Where you can increase backend tech capabilities. As the demand is increasing