Bibliothek / Finanzen, Rechnungen & Buchhaltung
Finanzen, Rechnungen & Buchhaltung
Qersh-Wallet-Überweisungen aus Webhooks protokollieren und verifizieren in Google Sheets
Empfängt signierte Qersh-Wallet-Überweisungs-Webhooks, weist ungültige Signaturen ab und protokolliert jede Zahlung als Zeile in Google Sheets; verdächtige Fälschungen werden bei Eingang markiert.
Was sie bewirkt
## Log wallet transfers to Google Sheets ### How it works The Qersh app on the merchant's phone posts every incoming wallet transfer (Vodafone Cash, Orange Cash, e& money, InstaPay) to the Webhook node as a signed JSON delivery. The Code node checks the signature on the raw body with the connection key and refuses anything else with 401. A valid delivery is answered with 200 at once, the connection test is left alone, and each transfer becomes one row in your sheet: time, amount, payer, transaction id, wallet, risk. A later "suspected forgery" verdict marks the row. Repeated deliveries (the phone retries until it gets a 2xx) are found by delivery_id and not logged twice. ### Setup 1. In Settings, replace the placeholder with the connection key the phone shows after you add the wallet (paste it only here). 2. Create a Google Sheet with a header row: received_at, amount, currency, payer_number, payer_name, provider_txn_id, wallet, risk, auto_confirm_ok, transfer_id, delivery_id, status. Select it and your Google credential in the three Google Sheets nodes. 3. Activate the workflow and copy the Webhook node's Production URL into the Qersh app (More, Wallets, Add wallet, "your store URL"). "Test connection" on the phone must say the signature was verified. Self-hosted n8n needs NODE_FUNCTION_ALLOW_BUILTIN=crypto for the Code node; n8n Cloud allows it. ### Customization tips Add columns to the append node as you like (balance_after, payer handle). Keep "Send sender details" on "full name and number" in the wallet, or the payer number arrives masked. The phone retries a failed delivery for days, so a Sheets outage loses nothing. Qersh (Qersh Pay) is a wallet notification relay, not a payment service provider. Docs: https://qersh.cfd/en/integrations/n8n
Die Schritte
- Webhook
- Settings
- Verify the Qersh signature
- Is the signature valid?
- Reply 401 to a bad signature
- Reply ok at once
- Is this the connection test?
- Is this a new transfer?
- Nothing to log for the test
- Look the delivery up in the sheet
- Is the delivery new?
- Append the transfer row
- Is it a forgery verdict?
- Mark the row as suspected forgery
Insgesamt 16 Schritte.
Ähnliche Automatisierungen
Sicherheit & ComplianceBlacklist-Status einer Tron-Wallet über Telegram prüfen18 SchritteMonitoring, Betrieb & StörungenUSDT-Wallet-Guthaben mit Etherscan und Telegram überwachen19 SchritteMonitoring, Betrieb & StörungenUSDT-Wallet-Guthaben mit Etherscan und Telegram überwachen7 SchritteSicherheit & ComplianceBlacklist-Status von Tron-USDT-Wallets über Telegram prüfen6 Schritte