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
- ed5dd657a5550e84cb8e8d9b604f88abaddcd25b03a77bebf61dcb23f6a6b0ce
- request
- 7468433458d5c3d1a197d444fe18941cc41ba9b1e6b2b6c978e7966238773165
- transaction
- 232b754112daf6eb445bed1fe30ee800f741154cfc3166b47b7b7fab925fc15ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1215
the chainentry 1215
- sealed to the entry before
- cd7a8f300a4917a4ad9443ea2d7139ccede7da302817ec3eaaee7c0a62d48f14
- this leaf
- d106a8debb3ddb076b6801a6dd7d2aa05c0bc0f802ebfaa51894e928279b93ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U0fzt2E8wRzoI8ZIbuBvq2qx4LFs4ScXoh3mWJOpTZvKmI7JyGp81Yj7WudyqqToOWBrz+igyCNgWMDQTFwBBQ==