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
- b90611109671d86ae21cdb227d388612fae80fa50e2fd94a0d7928177aa17cbf
- request
- 172833ba7c39633d511f78270197e36ddffc274d1bf99bdedfa121ed4650813e
- transaction
- eb96036f9383ced68d68e5c0a58526291a9766bada5aa69ea9c6b3412c24d262computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30285
the chainentry 30285
- sealed to the entry before
- c41fedfb43885f5489da06a7b7586ee25e0dae2a82d12fee807603f40734229f
- this leaf
- d796364cf2fb37ad1fca798f8342154f3bbfdc28e69a8a55517c373507787165
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sLP5akCrxp2IvAxh6HhwW6nCoijUcs0YlAiVRPBddSvb6QDY0v/bsJwl562nBscYxtf2Vd9DcIsl5scy46KjCA==