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
- ec92b76f244bd261b015ca1a542cbb3ec7b8a788df6a1dffbeb931979ad0c532
- request
- 9be7ee0f8829356d91a4fb271f2e535acef9c1399d91dfa132e24436367a5664
- transaction
- e1b6a2130c22af2dc6e519d37a78478c5127046a300baf8497f358e9d4a9a1c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60402
the chainentry 60402
- sealed to the entry before
- 09caf4684b831c91f130a397466559224ce600f9d098969ae16d6afdff9ccb5d
- this leaf
- bbfc58b33d9e9ea7eab0157d580530077201fb5a907e2e677df42dbd7bc68836
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rIenCad8xrkBoW/icS9p1yb748s9eOAXijlZHa3KSBWMWylkBaXhUDt4+ed5JrMfet61RWQ6ud8YB32msaKtCA==