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
- 0e5d855e5be3a8ab48af6543ee0dbbdc148751d6ac20b95fe4c2dc511e314c6a
- request
- 217d5c97d3fca010002eccda5ae4ddbec85dd17ff3fc9094d4d1c0fc7c774dc8
- transaction
- 7c68614f4028e9a32a63bd42ec5c6eea8a24918874a72dfca6006a3463bcde6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18642
the chainentry 18642
- sealed to the entry before
- 433a45885deaf601e3513a2ecb70ff073a865f20324e6276ea1ae841d7878fc5
- this leaf
- b6cdf0da619942e383edea77d8222b2528590ee6131b14c6827450dcc47c9729
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UPhAWPvv+CaWCWo5fbU7tYaVcoAb5HVxuvz+DrZVpn4ld3JQ2N00UUz1I0n8/rrrXPpSzVqzVQoaXRkBf6Y5AQ==