Paymentez is not the Nuvei package. A Paymentez account has application codes and app keys; a Nuvei global REST API account has a Merchant ID, Site ID and Secret key. Confirm with Nuvei which platform your account is on.
How it works
- The adapter asks Fire spark to prepare the charge (
prepare). Fire spark calls Paymentezinit_referencewith the tender amount and answers thereference. - Your template’s bridge opens
PaymentCheckoutwith that reference. - The customer pays. The checkout answers
{ transaction: { status, id, status_detail } }. - The adapter asks Fire spark for the status (
status). Fire spark reads the transaction from Paymentez and accepts it only if it is this attempt’s (dev_reference) and for the tender amount.
Requirements
- A Paymentez server application per environment: application code and app key. The Nuvei/Paymentez team provides them (sandbox ones start with
NUVEISTG-). - The customer email on the order, or pass it in
email: Paymentez requires it. - Pages served over https.
Activate it
- In the dashboard, create a payment with the Paymentez provider and the
CARDmethod. - In Connection Settings, fill in:
- Optional, per store: in Store settings set the store
application_codeandsecret_app_key. Fire spark uses the store pair only when both are set; otherwise it uses the Connection Settings pair. - In Paymentez, set the callback URL to
https://<your-api-host>/api/webhooks/payments/paymentez.
Use it in the SDK
Web bridge
Load the checkout and open it from the pay button click: browsers block the popup when it opens from another callback.React Native (kiosk and app)
Run the same checkout in areact-native-webview with an https page that loads the script, opens PaymentCheckout with the reference and sends the answer with window.ReactNativeWebView.postMessage. Turn the message into the bridge outcome: onResponse → { type: "response", response }, onClose → { type: "closed", by: "user" }. Test the WebView in sandbox before production.
Charge states
Webhooks
POST /api/webhooks/payments/paymentez settles charges the channel did not confirm. Fire spark checks the stoken (HMAC-SHA256 with the app key, or the legacy MD5), reads the transaction again from Paymentez and only applies what matches the attempt and the amount.
Refunds
Paymentez voids and refunds run on the Fire spark server.order.cancel() and order.refund() work as with any method: the device does nothing with a paid Paymentez tender and the server refunds it in the same call.
- In Ecuador Paymentez refunds whole transactions. A partial refund fails in the ledger and is done by hand in the Paymentez dashboard.
- A
pendinganswer from Paymentez counts as accepted; the webhook confirms the refund.