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
- 109f41f793d67e68d687bb1d73a50172d22e9ead40b794f60de4e4addad592ff
- request
- d9e8b2f037f706c652762b9abc90a52ac7186ef1eb929a68cc607e980fb5f9fb
- transaction
- 430495b50450ea41ca1336bb0f217e0fa1ee1b69a0b76068e848e939a4e61ea3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70789
the chainentry 70789
- sealed to the entry before
- 1023b3a0c8d9f4b3fb3407ef69187787c0afbffb27f0ddfcc348718610cc3521
- this leaf
- 318a2d04bc5a0e3ea91f80a704b13f8b9fabd7de61eb0af7131d5aa8b2a01fcf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q40i1Y2mMVuBxyUbrGsRWmYBmLQ3gLX8NiVQ9utjHwxRQolH/2D3nYKjv75TMwiYuh8kn/JUaZSmDXHhXWGmBQ==