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
- 84fd26edd4fb00670764a1f94ab1e2ed2043f3d12448ccf567f7dc2d4fcab1e7
- request
- e73dab5e945b1edefd6c7cca7057cf6b871cc9e03d9c784cb21d91ab5d06515c
- transaction
- e590dc2f23a5da5f6f4a453d883a40bca2bdda1f83fc6e20e736711b2ad63c6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32442
the chainentry 32442
- sealed to the entry before
- 333e399e9b1bcfb1727638cdc086e5189266b2c1273593b219dffaabe946d5e4
- this leaf
- 5b8d03bb33e766770395b6efd26fee1333d048bedf83c9b6ed2b16dd1a55282e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZHD/16HbNukAuu2BrwyZKNvwEXEY3leVpK1wb4t/Zxu2kv/Ybuacps0QXOsnIFuk8PB33QwHU4o0oa2GGT+lAw==