Backend Engineer
Adding Risk Scoring and Regional Controls to Payment Integrations
Implemented Accertify risk scoring alongside configurable country and currency controls for merchant-specific payment eligibility.
Details are intentionally generalized to respect confidentiality.
- Timeline
- 2025–2026
- Domain
- Merchant integrations, risk scoring, payment eligibility controls
- Impact
- Added provider-based risk scoring and merchant-configurable country and currency controls across IndiGo and Air India payment work.
Architecture
System boundary map
The diagram preserves the major responsibilities and handoffs while omitting proprietary implementation details.
Risk Controls & Provider Integrations
Integrated Accertify risk scoring and delivered merchant-configurable country and currency allow/deny controls that can be evaluated consistently during payment processing.
Context
IndiGo and Air India payment work required integration-specific risk capabilities in addition to the core payment flow.
Risk scoring and regional controls must be configurable enough for merchant needs while staying understandable and safe for the shared platform.
Problem
Risk-provider integration had to fit the existing payment lifecycle without turning every merchant requirement into bespoke branching.
Merchants also needed explicit country and currency controls over which payment contexts were allowed to proceed.
Constraints
Provider decisions and control checks needed predictable behavior in the transaction path.
Configuration had to remain merchant-specific without leaking across integrations.
Controls needed clear defaults and auditable decisions for production support.
My Role
Implemented Accertify risk-scoring integration as part of IndiGo and Air India payment work.
Delivered merchant-configurable country and currency allow/deny controls and integrated their evaluation into relevant payment flows.
Technical Design
Integrated provider risk scoring into payment decision points with explicit request, response, and failure handling.
Modeled country and currency controls as merchant configuration rather than hard-coded integration rules.
Applied the controls consistently against transaction context so eligibility decisions remain explainable.
Kept the work compatible with existing payment paths and operational support requirements.
Tradeoffs
Configuration-based controls require validation and clear defaults, but avoid repeated code changes for merchant policy updates.
Provider integrations add decision-path complexity, so integration behavior must remain observable and contained.
Impact
Added Accertify risk scoring across merchant payment work for IndiGo and Air India.
Gave merchants configurable, explicit control over allowed country and currency contexts.
What I learned
Eligibility controls are most reliable when policy is data-driven and evaluated at explicit transaction boundaries.
A provider integration is useful only when its failure behavior and operational visibility are designed with the same care as its happy path.