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
- ff4bd4d7daa5929316dabee32ee5c01c03b05a195b75c0eb98e3bd1b63b8fbaf
- request
- b4aa8d2af32360b492de3bf1962aafd942edb868eeb01d291b20c04934011e7b
- transaction
- 79e76cccef710f847169e76db7bd08dddf2ed946573645be423d0260f49999d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63668
the chainentry 63668
- sealed to the entry before
- e12cffba2d409ac9ba8ff951c6d15a847a80abc90e00456f76bdb90cf452d632
- this leaf
- 99fafe80e7c1f9aa83bf60c56781b876b9c0f085fbd0bfe68f85ec6eb0513843
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0gXqfnZLSS8eb2cL7TftUyYmo5xe59WDvJBhW1RwPMfaTRIr0ur/u5kCKzj2vc/ndBX6LnwiGNKJaHtlYLvaAg==