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
- 6765bbb666d539853641eca626fffe7444b29ed19a48a51f62c2124ecb41a7ec
- request
- c52de5fad0dc6ca98bcb101fdb6fb4836129b3e69b4912f86aca4956e5f8214a
- transaction
- da58847e7d5f3898bd01d03ef97bcba792d9acecb4c8a50e45f2578adda57f8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68030
the chainentry 68030
- sealed to the entry before
- 547752ea7b6959ce0ab6cd1a3cae0f4e3115fafdad19804bcae5f9acd7b7acd2
- this leaf
- f6d5adc150b885485cd2a7ec62681f3951b017a48c291577addcf8bfa0bdc73d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CIjzneIIq1krELfci3XzFJNtT2E1VktnbfQPHr3OazOgXAl+mFcyIP/bzwd6R0Zw1jE3e/rR7L7UggFTydkfDg==