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
- e31fee7134ea7e52f65f8cf210a3debf864f4a6034d6c5ad9afc0d1543448fc2
- request
- 26427598008a7f0ab0524e3a33e02102c9e07f5523020557991314cfd629533b
- transaction
- d8fcf996125ebd5691aaf148c55bcebe8cbccfcf87652beec60a6a611eeab8a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55253
the chainentry 55253
- sealed to the entry before
- 9f6a91cbd2470b6df6697b7995872855a120641b74423414055262eb4b84d67e
- this leaf
- e9ef9ffee11c53cc7c1ee890c2b690f5baf6fe97e7e47df000dcc55b89c62d0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GOYT600ocorSkXc94eudqfgVV++ROM32sYFPN+FYA4lHOBIflDKdvdluCkOoQMdrHfl1UAqXPewxrdnZ36Y4BA==