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
- 15ff6bd43c1007a1eee483e319dcc146a3821026575e76e7d1d91927e85a5132
- request
- 4c84b624000131dfff498711dbdd5c48b8fb406098efa4e488f933840836ae6f
- transaction
- 66d187436cd2c004924db9fb5cf36356e5ada89e331a059bc6ea48111f75a5d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21029
the chainentry 21029
- sealed to the entry before
- 372d3936719d74bf06961dc60df994e9c8d93d8a02e70d2170752f3e613a16d1
- this leaf
- 17fb30bc99c3af26185812ab76f64b4be15f10b4f18547309fb09f3cddd7ac05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wnV2LG+2aCDnVK8oLe9vvDNWuAGFlGWKWYztLWaz20BGq7jT6nU3MFUOFtMMwXReHhOVTXHZrYivwFqQFKvIAA==