Payment Security
Payment security is the set of controls that stop money and payment data from being stolen, changed or misused while a payment is created, sent and settled. It covers the data (card numbers, keys, account details), the transfer itself, and the checks on who is paying and who is being paid.
Where card payments are exposed
A card payment passes a reusable secret, the card number, through merchants, gateways, processors and banks. Every party that stores it is a target, which is why merchants must follow PCI DSS, the card industry's data security standard. Card payments can also be reversed long after the sale. In Amboss's iGaming comparison, a card chargeback can arrive up to 120 days later.
How Lightning changes the risk
A Lightning payment does not carry a reusable credential. The payee creates an invoice that contains a payment_hash. When the payment reaches the payee's node, the payee reveals the secret preimage that hashes to that value. The preimage settles each hash time-locked contract along the route, and it also acts as proof of payment for the payer. The merchant never holds the customer's funds in escrow.
Two further properties follow:
- No card data. There is no card number for a merchant to store or leak.
- Finality. A completed Lightning payment cannot be reversed through a card chargeback. Refunds are separate payments that the business sends under its own refund policy.
Security work moves to the places that remain: API keys, webhook handling, key storage and counterparty checks.
Threats that remain
- Forged or repeated webhooks. Verify the signature on every webhook before you update an order. Webhook delivery is at-least-once, so deduplicate repeat deliveries.
- Key theft. Whoever holds the private keys controls the funds. See self-custody.
- Risky counterparties. Sanctions screening and wallet address screening check who is on the other side of a payment.
- Fraud on the order side. Final payments remove chargeback fraud, but refund abuse and account takeover still need fraud detection.
How Amboss handles payment security
- Funds stay with you. Amboss Payments is self-custodial. In Amboss's words, it does not hold, receive or proxy your funds. Amboss operates with scoped credentials on a node you control, not with your private keys.
- Limited permissions on Rails. Rails keeps funds in your own self-hosted Lightning node. Amboss manages the node with strictly limited permissions: receive Lightning, open channels and close channels.
- API integration. The Payments API authenticates with an API key. Requests accept an
idempotency_keyfor safe retries, and webhook signatures are verifiable. - Screening tools. Amboss's own compliance tool, Reflex, runs IP node screening and OFAC channel checks. It is being integrated into Rails.
- Clear responsibilities. Amboss Payments is B2B software. Amboss does not run KYC or AML screening on a customer's end users. A business that processes payments for its own users stays responsible for that screening.
