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
- 5ed0659ac5a720afe13c7d1a0693f1811e298b8adfebd5a83f44ff2aba1be30f
- request
- df7af0189f92b0a3d106f28837158f19b2485a0fe099e69800cfc41ca2f761aa
- transaction
- 99637a2e255698c317bb59039f3c79b4dbdece45240876ffb955d3f2520783b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9524
the chainentry 9524
- sealed to the entry before
- e6c240ed07d5373a67ba6d15213c72f14a89b2e87ce4befcaa7541880b197060
- this leaf
- 0bb2308422ada50545f9fca15cfae5d4a8c65d79f59a62853d4b8b66072a531a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 77hQDoFhhLr34agTjfj5NR2r6kRSykn9h6W3kqET994yXA7nEOp8hZ+3exAKm3DDXQr03cIPhUIRxMzmwjAbBQ==