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
- 9f0845be343ed8e06b282b0f15e876c2ee937c3d4430e7598f13892da4d590b0
- request
- d882c215979b362c615bb23e6de29f21dc24953fbb122d01bcd980e738377341
- transaction
- 4ab7140db83101b93ad9ff2487ed15e3c08eff02a9cf552e3743338a964413facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3563
the chainentry 3563
- sealed to the entry before
- fd0ffbb944079caa4443c49d217119fef1c9ceaa3d0740a0faef913d43cee28c
- this leaf
- 2c80452f9c38695ebdfecf01081a94ea9f413d5c3d6d1f4e6f95e97c44818e7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OfNhWhR7Cfr5fihJDwwlU8Oka3VLVE9E8bVBP11mcWBJOwI9AhENbXUZQljkD9fGlS0ybtnH4IYYaQDBilWfBQ==