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
- d36d70809d7183af55359278b48a12e40571e40e77d16906bf0279402c3bed5d
- request
- c6708a7a74cd8b3f07d602ef058e4e9f4e5cb067aa40004da660255c0074c784
- transaction
- 39f761cd62f17e3bdad1eacbb2c6b5b780d2e084c4a4adc924a43ff29cc5a9a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28843
the chainentry 28843
- sealed to the entry before
- fc43e55c19509c27c002c95a66de4c2e8e25d05aad7ba4bdc389c58be99a33c4
- this leaf
- ac7ef271c7899bcd9854586857d35bc4f97905c4c961ef7d0bf4eef536378f8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LMcrGNQL/H1zOF/UtifvPB4tzyNeRAcZ2y3ZP0oVoReRUGHQEqF58rIw35gvvAW0BnfiVxmK21y6znSVbD24Aw==