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
- ca1197ddc996b82b4917195ccda7f74452dd330084ecf7dd828896fbca7aa6b4
- request
- b87760f2d5ac1743e835650301199db0e8c85be44093e8eaba29a64df401c873
- transaction
- d76a53453287aaf4e0f475ecd1fea9df5c0137a5d5c1665b5d8564cec9c5ab1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31247
the chainentry 31247
- sealed to the entry before
- f7a4757fd71beb1cef06710cbaf02a8eba487d2a8138c315ef24f3e0aeb6ee0f
- this leaf
- 51ad06c3fd40575874e46ff0088326962c8309cc2b6b89d051f1556bcc74a0cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HreafguTavEBaz18uvUQMYEigoZ7ZeozPv0C1OfcHJ7bME/FI8sFVxixjbWB3CUIO6BKNfdHghoX57s8tWfSCg==