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
- b3d51e57c02ac6a16f701265b6b26839cf4b0f323c2094715151c2f1416188a2
- request
- 1117947ff919abeac1f9916473955e6556ad00e508c842f8c58ef74a524d0dbd
- transaction
- 1c20c34e3b80d4ee2db701101634c156904723fa1ec0e8b42f1d7ff6deb1a946computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69606
the chainentry 69606
- sealed to the entry before
- 06e0d869c8e4e4cbe39571bfcdc2a05873fc7b0bd5c635649a9d99bb611c1597
- this leaf
- 032209908af94e99460a66f1c9d384c2e1d1394028292f75d3e3dfe2d16132cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W/j4qdyrPhiA8ST2nU6bUCyXE7rS9pDQCNPBjaOX+kxy5AK4v/22rhX1F4s9OW6XMb0VOsijFM38eyJ9j9sZCg==