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
- a28c48985bff57d4322d02b3c1f2941557c842c8c8bc51ee3599c95bb9be9582
- request
- f56e56d2af800e5db28c71ceded2780fcaeb66ead7b318b8cb9f9409f50f3e85
- transaction
- e6e4e112bab604991c94a26462e543cd2811badfc105f8a97c505c49c64e91edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36452
the chainentry 36452
- sealed to the entry before
- bf4d5d93f7d3ecc17ce6f13218f83f8faaf459f1afcd37645120f066afce9f26
- this leaf
- fc255e4e189fc98e0b038413fe54f508afbc6f82407275ecb1a4e1eaf8799c4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wCZlATdWEWYCpD21o3Ve2B8qDsnr0S1gs6si7PezhyZ6Zhb0HJlvkFDubdMJspVAMw5OCKvsWZ+GpabQ+OfvCA==