ESEN
Let’s talk

Payments connected to your operations.

A transaction needs to appear in the sale, at the payment provider and in your internal records. We define the complete flow: request, response, confirmation, reversals and reconciliation, with clear ownership for resolving discrepancies.

Tell us about your project
  1. Customerinitiates the transaction
  2. ChannelPOS · web · application
  3. Integrationrequest · response · events
    AcquiringGateway · PSP
    SINPEProvider · participating institution
  4. Operationsrecords · reconciliation

PSPs, acquiring and payments

Integration of payment service providers (PSPs), acquiring and payment channels: e-commerce, POS, tap-to-phone, links and buttons.

Ask about this service
Technical decisions
Authorization, confirmation, reversals, settlement and reconciliation. We review how the channel and provider connect with sales, accounting and customer support.
Our work
The payment flow map, application programming interfaces (APIs), event notifications (webhooks) and error handling. We coordinate requirements and testing with providers and technical teams.
What we validate
Approved, declined and pending payments; duplicate notifications, refunds and reconciliation differences. Tests cover scenarios supported by each provider.

SINPE services

Managing integrations with SINPE services through providers and participating institutions, for transfer flows and their operational records.

Ask about this service
Technical decisions
The required service, accounts, authorizations, individual or batch transfers and status enquiries. Capabilities and conditions depend on the selected service and provider.
Our work
Integration requirements, data structures, confirmations and reconciliation references. We coordinate environments, access, tests and production rollout owners.
What we validate
Data and destination accounts, transfer states, rejections, retries and reconciliation records, within the available interfaces and services.

Clear scope for every team.

Deliverables are agreed within scope. BE IN leads definition and project management; each team implements and validates its assigned components.

Your team

Defines channels, payment rules, internal records and owners for reconciliation and incident handling.

BE IN

Designs the transaction flow and coordinates requirements, integrations, tests and project dependencies.

Providers and specialists

Provide payment or connectivity services, documentation, test environments and operating conditions.

Decisions that matter

Are payment confirmation and reconciliation the same?

Confirmation reports an operation’s status. Reconciliation compares provider records with sales and internal movements to identify discrepancies. The design should cover both processes and how pending cases are handled.

What if confirmation arrives later or more than once?

We define pending states and status enquiry or webhook mechanisms according to the provider. We also agree on identifiers and duplicate controls so a retry is not treated as a new operation.

How is SINPE integrated into the project?

Connectivity is coordinated with the provider or participating institution. We review enabled services, interfaces, limits, applicable operating hours and confirmations. BE IN leads integration and testing within that scope; the corresponding participant provides the financial service.

Keep exploring

Connect onboardingSee how identity, signature and the customer record form one journey.See how we workUnderstand how we organize owners, dependencies and execution.

Tell us what you want to solve.

Share the current process, the systems involved and your objective. We assess what needs to be defined, integrated or validated to move forward.

Tell us about your project