Payment workflows for regulated fireworks sales.

PyroApex payments are built around an integrated ValorPay gateway path for fireworks ecommerce. At checkout, the application requests a ValorPay client token, loads Passage.JS in the browser, and lets the customer enter card details through the processor flow. The PyroApex server receives a payment token, not the customer's raw card number, then sends the authorized order amount to ValorPay using the sale transaction type for standard checkout.

That architecture matters because fireworks retailers operate in a category that many mainstream processors restrict. Stripe, Square, and other general payment products can introduce account review, delayed onboarding, or outright rejection for fireworks sales. PyroApex does not pretend that risk disappears. Instead, it makes the processor relationship explicit and keeps the checkout integration in the same system as the storefront, cart, tax, shipping, order record, and customer communication workflow.

The implementation stores the transaction identifiers needed for follow-up actions. ValorPay returns a transaction ID, retrieval reference number, and approval code; PyroApex keeps that composite reference so refund, void, and capture-style operations can find the original payment. The normal storefront flow uses sale, which authorizes and captures in one step, while the code leaves room for more advanced flows where a merchant may need to authorize first and capture later.

Transparent rates.

The pricing story separates software fees from processing fees. The PyroApex platform fee is the application fee shown on the pricing tier. The ValorPay processing rate is the merchant processing rate associated with the payment account and underwriting. Those are not the same charge, and the marketing page should not blur them together. A buyer needs to know what PyroApex charges for the software and what the processor charges for card acceptance.

That transparency also helps compare PyroApex to generic high-risk merchant setups. A standalone high-risk account may solve payment acceptance, but it does not automatically connect to a fireworks-ready cart, age gate, order workflow, or shipping quote. PyroApex keeps the merchant account visible while reducing the amount of custom glue needed to make payments work inside the store.

Operator workflows.

Payments are not just a checkout button. Staff need to know whether an order was paid, which reference is needed for a refund, and how the payment status relates to fulfillment. PyroApex keeps those details attached to the order. Refund support can use the saved ValorPay identifiers, and future commerce features such as gift cards can be described as separate workflows instead of being hidden inside processor language.

For a fireworks business, the goal is practical: accept eligible online orders through a processor path that understands the category, keep card data out of the application server, and give staff enough transaction detail to handle the customer after the sale.