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
- 40fb36992b01f69887c6bcf85d29cb151410a509d1fe4eb7770c511d6aae2c57
- request
- c07915d09141170d4e86a1d3d7a89d116cdacba94d90503d61fe5c983db1b60b
- transaction
- 1b6ec76715ddbf2fad9481d9815142b45eb77995eca379f44fb9eced0b53dd6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54688
the chainentry 54688
- sealed to the entry before
- a75da96ca308218c3e784c4f046f7f0e616040f816b2ec51e4a9c47cfaf2e255
- this leaf
- 0263e205efa88e1b1da0b632a4e97cfb70fa79bae3fe5b6ebeac67cc7d9a4d56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zBnux8ZasBDvr/YtYMAhMtrBYYmEC/kWc/ZoIKzihcsGQgdgpOxUHGqRnlTfJtGpW5KIQi5HcXkmGpc+KTrRDg==