x9-jws

Implement JWS signing and verification for X9.150 payment transactions in Python.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/carlosnetto/x9.150-py --skill x9-jws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x9-jws
Source: https://github.com/carlosnetto/x9.150-py/tree/main/.claude/skills/x9-jws
Command: npx skills add https://github.com/carlosnetto/x9.150-py --skill x9-jws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and reference implementations for securing X9.150 payment requests and responses using JSON Web Signatures (JWS), ensuring authenticity, integrity, and non-repudiation.

Core Features & Use Cases

  • JWS Signing & Verification: Detailed explanations and code examples for creating and validating JWS tokens.
  • Certificate Management: Guidance on certificate discovery via JWKS, embedded certificates (x5c), and thumbprints (x5t#S256).
  • Header Validation: Enforcement of critical headers like iat, ttl, and correlationId for security and replay prevention.
  • Use Case: A developer needs to implement the JWS security layer for an X9.150 payment gateway. They can use this Skill to understand how to correctly sign outgoing payment responses and verify incoming payment requests, including handling various certificate discovery methods and freshness checks.

Quick Start

Use the x9-jws skill to understand how to sign a payment response payload with a given private key and correlation ID.

Frequently Asked Questions about x9-jws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement JWS signing for X9.150 payment responses in Python?

JWS signing for X9.150 payment responses requires constructing the header, selecting a valid algorithm, and signing the payload with your private key and a correlation ID to ensure authenticity and non-repudiation.

What is the best way to validate X9.150 JWS certificate freshness and discovery?

Validating X9.150 JWS certificates involves discovering certificates via JWKS, embedded x5c certificates, or x5t#S256 thumbprints, while enforcing critical headers like iat and ttl for payment freshness and replay prevention.

Can I use embedded x5c certificates and x5t#S256 thumbprints for JWS verification?

Yes, you can use embedded x5c certificates and x5t#S256 thumbprints for JWS verification. The implementation supports multiple certificate discovery methods to securely authenticate X9.150 payment transactions.

Why does my JWS verification fail when critical headers are missing in X9.150?

JWS verification fails when critical headers are missing because the X9.150 security layer strictly enforces headers like iat, ttl, and correlationId to guarantee payment freshness and prevent replay attacks.

What are common pitfalls in X9.150 JWS header construction and algorithm selection?

Common pitfalls in X9.150 JWS header construction include improper algorithm selection and failing to enforce critical headers, which can compromise payment security by allowing replay attacks or signature bypass.