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
- 914f9ca177dd5639225e0d9d375885e702b61d0997e23b42e631fcc9fc25c838
- request
- c6cd1c2b504b04b94ec836a8affca5d151ef309c146d8d250c4cdcd7251e1166
- transaction
- 9d70ac36d9088999337a7f1fbd382ed70a4e72d19f52dcf2e2438534bc20f661computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34986
the chainentry 34986
- sealed to the entry before
- 4103fecd11b8fcc95970f8ed3277261b70d4afe06f927eeceea469b8045df8f3
- this leaf
- e4f0a3176d1b68618c6fa24e1454dc408ba107a4c194bd5fdd78aa58901dbcbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D4VaW3SYSpWwBhtOTzbZ60sVMjwgYyFO2yzXXbS3uKCK4EKYge5FMPCIU5FI7KsG4AwcTB0vje+wJZkO7yjrCg==