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
- df59d6ecb419441e1af51cbc2fb48505d56c5aedda4d47b3b63e688a90686b0e
- request
- d68188561b3f39ec3951c14d094e9aa7e8bbd308613e093c38079f6c0a223031
- transaction
- 271c4aa53cce5af5a315dcefcdb425386c9299dea19acb3e4c71b25edcc02f18computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2320
the chainentry 2320
- sealed to the entry before
- 89d11e8af599a56208635bca125f3048ed9cfef9e46891c05495ecb51a7ecc9d
- this leaf
- 98c7e3e4b4b052e6f58db7e3d2831e098e5d922530c995c46c3bf4a373ed91d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hhTaPIZVbNIjRbSXve8nWD2doVWY8TZh5CdMITXk+2O41eiXuXnCgg2xbvOmnwCRJ5dJ0z0FHBYx0vIL65JrBw==