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
- ae8dbde2fff0af1be8dc1e90fc30ec818192ce8ab70e60c50d596c6763446692
- request
- 3861091c9db67e95388371a9be6b80e075cbca7282e165903f14a66841fcafd0
- transaction
- 60f2eef14c88e7aa478c90a6330e26c464acd3200049a7ae1be4275e747c0b2bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52067
the chainentry 52067
- sealed to the entry before
- 4bed355c1126881fb56efff449ee1fcf011823392e1dd6cd4d0fc980d8cd9b15
- this leaf
- 86c40b9835a02de2c1f3c37a9c2f31ad1ff6f9c5397b6c2968d55d04ddc2b779
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +w26X4eViWNiy0D+TCbim1rYO5u+WjUvhn7LbTDrdo4+DeRn+5PK8EsOCkDGnK0f2Z18w6aJp67D7Yion/VhDg==