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
- 4caba23cb4523d61e468a57053ef3a15ca7eaed8e3c50c83df927bceb4351773
- request
- b5c92577dcef2ca9f9d812da92a8e58c3837e617188444c9d1c9c3c99078f18b
- transaction
- f8fef2b40353975e3bee72fa818f9b5a7aed1983f6661be44d6b190a51232c05computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11837
the chainentry 11837
- sealed to the entry before
- e615195d086ae74e1b783818fd2ed183f544212eb8410c1b038fee8e60ba0342
- this leaf
- cb49f712313f028b2969ff83a2f1c3211f26f4e775eaa2ad71b944c97662d9f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oEQMOo4jiun10hvU4ydykuHxX3ahF4Npp5gKmijojXnRZqmcpZ9Dsvs+Zx2Qqsz/djgglCqd58Ta/dZm7noLAw==