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
- d8b2c4a4a0612ec5ddd77a58f15852c1cf7856eca43547e8535e2fcb03ec07cb
- request
- 80f79006f0328b666ac17b4f939faabaae91cfaa4db2c99e089b618dbace722c
- transaction
- d4e39070a6ced2365aa9fc2c83fc7cf933186934df3500675936b01072758dcecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1420
the chainentry 1420
- sealed to the entry before
- 1a80aae7f6e2073ce2409cf353d2ce5aa409ce6344d21a1ab4269fb6d8fb3d2b
- this leaf
- bf15040531ff8caaa62f91a45b1d0dff0a3b42ded6c420b7b2cc8c1d6bcb65c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GOv8QE+gheM7GjD/ZRPLiNM8pU0B5Vgiv/d3WdopAC1SOLQxdWc3lYQsDtcAfDMlwrnPhBsBthhhlb1R++/9Bw==