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
- 833bb0cde31e568488e7b3bf39e574ebf6dce9dd6131b3887161aa451bac9f97
- request
- b195bd24f959435c4954d019744cde11cc09cb83e6e68fe75826f2011b5a577f
- transaction
- 4dca6ae524814eece3b00075f0c31b30f16fe47500a58462822dfd72fab8bf4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75293
the chainentry 75293
- sealed to the entry before
- d9f8470d5d00d4f72066d1b77fdf2131935a624f019d106be83a58217321bb3f
- this leaf
- a634188cb1fa07f67bcbe350b6da57ec6c1adf7a127fcfdf7d35aff622faeb04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gqq8fFqTdnAxTl52Uz83hM+t5L45oFcoMC5roh3eaFli6LmvT4t7Jhz7PzIkeK+eO7Hqr/eEO3LWOQmMQmVGDA==