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
- 878155acda36745380959eb41cff280963d59262b57e5fa6f54c1dd756017adc
- request
- eeb1f2124b0336bb968a6b9af182e19667218a627174f3dfe07d2631318dcf18
- transaction
- a0caae42c8b69ad5cedc8393c31bc065aecec5d53b7f80032ea6764e2fc349dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9446
the chainentry 9446
- sealed to the entry before
- cccaf20da095d58886bc08f63953520c69c8cb3b1079891cfb649b3bd7f2ce2b
- this leaf
- b954e5f74903c2cdc63d4ae71ea0f711d3520a997179aaa70f753ae250f1467e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bEm0S6WwWhu5hsTEmSJOzLFTiIzTFP/aVq1Yw83K9VkuO8/hAbWS10IZq8ujnGFUF3KUWYnSFw0ME2mePmt6Bg==