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
- abb880933eef5f8ba30f6e4065d0d156b103a0d747a64e3344d855a78efd3d0e
- request
- 265c63de10ce13ac83111c0baa530a5ef3dc43b1979047dea910f20249b090b5
- transaction
- 23192d6b26f06026d46ab113eb1e4af7396532daafccf4e4524be107a9c657b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38207
the chainentry 38207
- sealed to the entry before
- babea38849f0d5feaa8a50208bb11065601204bab9f9d23bc5d3d194012a4338
- this leaf
- 0d4dbe4f186382b0f10902459bcaf8c948e5f88ac80f2b2b7544be350bac1efd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oOZHkr42xcRVgdJejjoSNjy6OpQGoDofOJY5vsORBrSYe1L+IqM2makZjZFPfYEp81weJS/wpkiXKJ0ZF38lAQ==