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
- e71ca7c473de1f3118323b18c0b4a86cb6487fb5ae00df38e2cd978b1ca7acd5
- request
- 343adab3decdf0e7ae34d57cbb8d6ed77b06e176a81ce802570594e98eb778b2
- transaction
- eb23adfc9af2fb2280846fab0af209b994b159f5b5a1a6c757884903ae425fc2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59770
the chainentry 59770
- sealed to the entry before
- 456df72fb4fc681480218712a251e840e2ad07489def4f3f96de34ae27831255
- this leaf
- bdc10136ac0cd6e0ff9d073fa3a0b7fd8562ea7f7f1af890e40df1fc72bcc382
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /lA6aFBwQ7Nfd9KNO7PPMBfT8DegQ4ZI2lE7xDebfzx0FNCFYJoGl2MtDhagfymTnS1/6HASnpcAfSatoxKLCA==