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
- 97ef2207965ac2a3ce0292f12ccfea89ef418f9bbdadbb8e77122097ae99bc68
- request
- a68df5e201c1438d7e5bf2fa1cb4a0a01fd0947b19152152f5c45ef9b46d8fb9
- transaction
- 6e227e956d8784d1a16134b3c672f4b80ea90cc0eedb6fe52d8a6a4f39bf7eafcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48702
the chainentry 48702
- sealed to the entry before
- d10546dcf40632df9f1adb2cb39ffbb9df39e8cead0a44810ec900b62d12e632
- this leaf
- 5bf5d9f12e204f7fda3c6d73a1170166010f64f8bfd2205e36903893dfe00746
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7ec7dhv8vs9AAoETBzn2OHrjZ4v7R8NHvxQQ78hqbipfYD/MEBiBAzdrvD+lNKADIxXYMu0n7dtuD3ImQZj3Aw==