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
- 2bd31a9746eaf0fe310c47758b2c57201cb5bcbb417681bfc836e3fa34a9eb1d
- request
- d3bf2777ab8ffad7a9bc43659c82d00ba05ac8403be7e4d64969d96980f38cb7
- transaction
- 4504b58fd2349207fac799f7cf12ef92efbfdadfa889f176518fb18e6c5b79facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74104
the chainentry 74104
- sealed to the entry before
- 46998654644f5ca35ea3c33b0294407a1f1d44d79fc8f0711047ebc2755c5230
- this leaf
- 04eb9efab135adb86ea7e232f546452e937d22ac7bfc49a89726eb3ee62d79c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BCoPRzCykLoTnRHa2erDpcsnSSUcMtuZ6Rx1bsF9b7ZimyegHvK1fl8s29aZ4D6BroDAdPzva5WIulxfY66bBQ==