Question 1

What does Entrant DPS actually do?

Accepted Answer

Two halves of one engagement. Advisory covers strategy, business analysis, and architecture for payment and banking programmes. Delivery builds the software and infrastructure and then operates it. Most clients buy both, which is the point — the team that designed the platform is the team that runs it.

Question 2

How does an engagement start?

Accepted Answer

With a scoping conversation, not a proposal. We look at the platform you already run, where the programme is stuck, and whether the problem sits inside our domain. If it does not, we say so in that first call.

Question 3

Who do you work with?

Accepted Answer

Banks, fintechs, enterprises, and government programmes — organisations running regulated payment or banking infrastructure. The common thread is a platform that has to clear an audit, not a product still looking for its first users.

Question 4

How long does a typical platform take?

Accepted Answer

A scoped integration runs six to twelve weeks. A full switch or issuing platform is measured in quarters, delivered in stages so something is live and useful well before the last milestone.

Question 5

Do we have to replace what we already run?

Accepted Answer

Usually not. Most engagements start by integrating with the core, the switch, or the card management system already in place. A replacement is a decision we make with you after the assessment, never the opening assumption.

Question 6

How are security and compliance handled?

Accepted Answer

As architectural constraints from week one, not as an audit item at the end. PCI DSS and ISO 27001 requirements shape the design; what that means in practice depends on your regulator and card schemes, which we work through before the design is fixed.

Question 7

Where does our data live?

Accepted Answer

Wherever your regulator requires — on your infrastructure, in your cloud tenancy, or in a region you nominate. We hold no production cardholder data of our own, and access for our operations team is scoped and logged.

Question 8

What does managed operations cover?

Accepted Answer

24/7 monitoring, incident response against an agreed severity model, patching, and capacity planning, with a named escalation path rather than a shared inbox. Response and resolution targets are set in the service agreement before handover.

Question 9

Who is on the team, and are they dedicated?

Accepted Answer

A core team assigned to your programme — architecture, engineering, and business analysis — with specialists brought in for defined pieces of work. The people in the design sessions are the people who write the code.

Question 10

Where do you operate?

Accepted Answer

Cairo is the headquarters and Kigali is our East African delivery base. Both sit in the same time zone, so the two offices share a working day rather than handing work across a gap.

Question 11

How is the work priced?

Accepted Answer

Advisory and scoped delivery are fixed-price against a defined statement of work. Longer builds run on a dedicated-team basis, and managed operations is an annual service agreement. You get the shape of the number in the scoping call, not weeks later.

Question 12

What if we want to take the platform in-house?

Accepted Answer

You get the documentation, the credentials, and a handover. We would rather you stay because the operation is good than because leaving is painful.

Frequently asked questions

Still have a question?