Payments and Compliance
Check cards, bank details and names before money moves: Luhn and BIN lookups without widening PCI scope, IBAN, SWIFT and routing validation, sanctions screening with an audit trail, and one explainable risk score.
Payments and Compliance badgeComplete all 4 lessons to earn it. About 2.3 hours.
0 of 4 lessonsStart course
What you'll be able to do
- Run Luhn checks locally and use BIN lookups for card facts without handling full card numbers
- Validate IBANs, SWIFT/BIC codes and US routing numbers with field-level errors before a payout
- Screen people and companies against sanctions lists, route fuzzy matches to review and keep an audit record
- Combine contact, network, card and sanctions signals into a weighted risk score with reasons
- Tune allow, review and block thresholds from logged outcomes instead of guesses
This course is one of three skill areas on exam APV-200, APIVerve Certified Developer: Verification: 10 of its 30 questions. See the full path
Syllabus
- Check a card with Luhn validation and BIN lookupStart hereValidate card numbers with the Luhn check and look up the BIN for brand, debit or credit, prepaid and issuing country, without widening your PCI scope.
- Validate bank details before you pay outValidate IBAN checksums, look up SWIFT/BIC codes and US routing numbers through an API, and catch bad payout details before a transfer bounces or goes astray.
- Screen names against sanctions listsScreen customers and payees against OFAC and other sanctions lists with an API, handle fuzzy matches and false positives, and keep an audit trail.
- Build an explainable risk scoreCombine email, phone, IP, VPN, BIN and sanctions checks into one weighted fraud risk score with reasons, allow/review/block thresholds and logs you can tune.