Generate payment request template JSON files for X9.150 specification testing.
npx skills add https://github.com/carlosnetto/x9.150-py --skill x9-template
Please help me install this Agent Skill. Skill: x9-template Source: https://github.com/carlosnetto/x9.150-py/tree/main/.claude/skills/x9-template Command: npx skills add https://github.com/carlosnetto/x9.150-py --skill x9-template
This Skill streamlines the creation of standardized payment request template JSON files, essential for testing and validating the X9.150 secure payment specification.
Generate a new payment request template for a restaurant scenario with tip options.
High-intent search queries and answers about installing and using this skill.
You can generate a payment request template for X9.150 specification testing by creating partial JSON payloads for predefined scenarios like restaurant tips or deferred invoices, which are then validated against the OpenAPI schema. The generated files follow specific naming conventions for organization.
The X9.150 payment template generation supports scenarios including restaurant tips, deferred invoices, marketplaces, and multi-currency payments. These predefined scenarios help test how payment applications handle dynamic calculations and various transaction types.
Yes, the generated payment template JSON validates directly against the OpenAPI schema. This ensures that all generated payloads strictly follow the X9.150 secure payment specification structure before being used for testing.
Yes, you can test dynamic tip calculations by generating a restaurant payment scenario template. The template includes specific tip options within the PaymentRequest payload to evaluate how your payment application processes dynamic additions.
No external dependencies are required to create X9.150 payment request JSON files. The template generation operates independently to produce the necessary JSON payloads for your specification testing workflows.
The best way to organize X9.150 payment template files is by following the specific naming conventions provided during generation. This ensures the partial PaymentRequest JSON payloads remain structured and accessible across various testing scenarios.
carlosnettoValidate JSON payloads against the X9.150 OpenAPI schema with Python and jsonschema.
carlosnettoParse EMVCo QR strings, validate CRC-16 checksums, and extract X9.150 payment URLs.
Basis-Theory-LabsGenerate a JSON mapping file for a payment service provider from its API documentation.
cafe3310Generate standardized project and product documentation from reusable markdown templates.
