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
- b2d8090f88bcc5952c51f5fcfaa4f746e11030df4ec9981b5c01bd44b3e6aca7
- request
- d53beb0d4180b7fe68a8c5d22a3be4154d5f370a8ade4fcff9cbab773b6e3979
- transaction
- ad31abbda6ca9ac33792cd8c287bc4ad66d7ed46fe2a3ae767ab4741357fb476computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13590
the chainentry 13590
- sealed to the entry before
- fca0150a3a91726fc0ab458630afe84a9a9e0e1fa792b411ffde36a55e8cf303
- this leaf
- 45e58f68e4bcfdaaab19c9fb2f701372330ec1a1852554c120b8648116fcdff9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CdA8E0flEkMTvApMYGoPWEMjklCCY+647K3OqlMVMfKx7ym8MU8fjNumxNZ6YvClcOzRa4TBpFzTRA4ge/gnAA==