why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 69c2a50ebcf74ab0ef7e0640f71e02467d194dd5e63c1ffc9c53667799b2f079
- request
- c4cabd88e5e88159b771737b6df4c0f23b7bdd84c76d8668e031e11f7381008a
- transaction
- b929ee9ff0340ba0581ebe8f69f7eda7400bba226cf0bc5096f5b7db5594ac7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24519
the chainentry 24519
- sealed to the entry before
- 12d6413126aa2a34b5cb62ea5a9031e32cd670b84bb80cad9a35f2e21fc4d127
- this leaf
- 90046152e2108d913932dfe88f7609bdb209a7e6d70687bf682391c0c4fa222a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ncUs2VKrktqqH8rnF8DmU0+w/Ucdxy1iiv2QvAtcli0PMURlE94oqx5AmBEB8bzC4uYVcxdPzn6oElc72PbACw==