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
- b1fc8c34fa0ec85cc8531a66cbb0289e20d7d3945e319eff671cccde6f7077a3
- request
- 8bc9e0d14605afd0a9d767bff12d74934ed8116bf6ba1d38e581cea8f46c03ba
- transaction
- d53a5d09ab7fa752bfc79194994cdb78cddafac21063dc59c163bb1ca810c9b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25975
the chainentry 25975
- sealed to the entry before
- db83eee21b6ccedcca05981a4dff883df1decf6cc7a8f9c8e6b28410e02dd744
- this leaf
- c29a3b7ac3b2a61073f3f1dda05631a2c686ec2be597c2722a778ad2801fbccb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gSKrBF2RQFTe3jw/sOEfNj+53pmmSgH49erAUP2Kx82lwofpqPccgPXnurfmgZVtE+Yb5XYDwSCGGUJb9gT1Bg==