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
- f35302e9d6e39bb9e41ad478cfd4b9162291550b9ee759ed5fbad88c2624c94e
- request
- 18b116c382a5472ea20e0ef91b62a7ce77c69aa6b906380ab35b39ae8057cdcd
- transaction
- f6549307627d0f2c208b3dd18ed04755e1971aac929b4786219c2cad4aec8a61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1110
the chainentry 1110
- sealed to the entry before
- da2553d8f7f9ed30a093523d7ec25366ec1bea45021144ff2eb0955500706916
- this leaf
- 4d39f5943ede17f210ab29c7e3675a26fdfc20492d2251684ab98fd2927fd8c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wYuntN2jwf2CRFpsUrtmr6zNYQnmIrULucfdN+HkDwphY7hAvfKLNEsKzQXU8o2noC+zLfviN2FR5DSE5j9BCg==