Thursday, May 21, 2026

MPP's core SDKs now expose typed payment hooks for client and server payment flows. Use them to record what happened around an MPP request without rewriting your payment handler.

Why hooks matter

MPP puts the payment flow close to the request flow in REST APIs and MCP servers. That makes basic integration simple, but becomes fragile when used in production applications and existing tech stacks.

Hooks give you a typed place to attach that visibility:

• Monitoring and observability: Count Challenges, successful payments, failed Credentials, and paid retry responses, then attach Challenge IDs, method names, intents, amounts, currencies, and Receipt references to traces.
• Logging: Record enough context to debug a failed payment without logging secrets.
• Support: Connect a user-facing request to the payment attempt that authorized it.

What changed

Server hooks observe issued Challenges, successful payments, and rejected Credentials. Use typed helpers for common events, canonical strings for direct event names, or * for a single catch-all handler:

import { Mppx, tempo } from 'mppx/server'
 
const payment = Mppx.create({
  methods: [tempo.charge()],
})
 
const log = (event: string, data: Record<string, unknown>) => {
  console.log(event, data)
}
 
payment.onChallengeCreated(({ challenge, request }) => { 
  log('payment.challenge.created', {
    amount: request.amount,
    challengeId: challenge.id,
  })
})
 
payment.on('payment.success', ({ receipt, request }) => { 
  log('payment.success', {
    amount: request.amount,
    reference: receipt.reference,
  })
})
 
payment.onPaymentFailed(({ challenge, error, request }) => { 
  log('payment.failed', {
    amount: request.amount,
    challengeId: challenge.id,
    error: error.name,
  })
})

What's next

This release starts with core lifecycle events of the MPP request flow. If there is an event or payload field which you would like to monitor, please leave feedback on GitHub.