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
- 6fcca00ef8b055fd4e7add062343ebde3d168cfabd2a8141fb057c27021b4d1b
- request
- aa1f318a7b2d0124bac0c23480d54c37a23761986083b8fadb3b3230d3546811
- transaction
- 136a63ad51eb2d1fcf98727db81945f012210ba0255c5a89d4869bac23d42ba6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36397
the chainentry 36397
- sealed to the entry before
- f1b7e1485325cc99bfe8c0e7cfc1f5d384a476edf1634a462ee956173e3978c3
- this leaf
- 0f933fa212dfefc563f0636f480f0a52dea1bd1fc02d5b3a8a9644d0b73affee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1T4OV+8SsDxXC85cRrFXugw3AemczBCLVdkml5IZaftmmMRjp/J3JUfp5u6apEVC/1ynp2CQZPIoC2Uh8SbvCQ==