##### Question Design a feature to schedule payments at future timestamps. The system must execute the payment exactly at the scheduled time, update the involved account balances, and skip execution if the source balance is insufficient.

This question evaluates understanding of reliable scheduled job execution, transactional integrity, concurrency control, idempotency, and failure handling in balance-transfer and payment systems within the system design domain.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Take-home Project rounds at HubSpot.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at HubSpot during technical interviews.

Schedule and execute future payments | HubSpot Interview Question

System Design: Scheduled Payments Execution

Context

You are building a balance-transfer service (e.g., an internal wallet). Users can schedule a payment to move funds from a source account to a destination account at a future timestamp.

Requirements

Design a feature that supports the following:

A user can schedule a payment at a future UTC timestamp.
The system executes the payment at the scheduled time.
On execution, the system updates the involved account balances atomically.
If the source balance is insufficient at execution time, the payment is skipped (no balance changes).

Assumptions (minimal to make the problem well-scoped)

Single region deployment; relational database available.
Timestamps are stored and compared in UTC with second-level precision.
Payments are in a single currency (multi-currency handling is out of scope).
“Execute at the scheduled time” means trigger at or immediately after the timestamp (sub-second jitter is acceptable in distributed systems).

What to Deliver

Provide a design that covers:

High-level architecture and components.
Data model and key constraints.
Execution flow (scheduling and run-time) and concurrency control.
Handling of insufficient funds, idempotency, and failure/retry.
Brief API sketch and operational considerations (monitoring, background jobs).

Requirements

Design a feature that supports the following:

A user can schedule a payment at a future UTC timestamp.

The system executes the payment at the scheduled time.

On execution, the system updates the involved account balances atomically.

If the source balance is insufficient at execution time, the payment is skipped (no balance changes).

Assumptions (minimal to make the problem well-scoped)

Single region deployment; relational database available.

Timestamps are stored and compared in UTC with second-level precision.

Payments are in a single currency (multi-currency handling is out of scope).

“Execute at the scheduled time” means trigger at or immediately after the timestamp (sub-second jitter is acceptable in distributed systems).

What to Deliver

Provide a design that covers:

High-level architecture and components.

Data model and key constraints.

Execution flow (scheduling and run-time) and concurrency control.

Handling of insufficient funds, idempotency, and failure/retry.

Brief API sketch and operational considerations (monitoring, background jobs).

Schedule and execute future payments

Quick Overview

System Design: Scheduled Payments Execution

Context

Requirements

Assumptions (minimal to make the problem well-scoped)

What to Deliver

Solution

Submit Your Answer to Earn 20XP

Schedule and execute future payments

Quick Overview

System Design: Scheduled Payments Execution

Context

Requirements

Assumptions (minimal to make the problem well-scoped)

What to Deliver

Solution

Submit Your Answer to Earn 20XP