Course Dashboard
ActiveComprehensive overview of modules, students, and network activity.
Course ID
13cf61af0106efa3ba64ff51cfd847fb8f74538d06cb78b4df04535e
Policy ID
c292279d5552d5a2779cc6a0f1a1c639ee5ac5397df70230dda070c4
Validator Address
addr_test1xrpfyfua24fdtgnhnnr2pudpccu7ukk9897lwq3smks8p3rjflq8ctkef92tz72vjdf6m2tams3k84dvyvhg32ts45fq50fctw
Authorized Teachers
Course Modules
4 Active Modules| Assignment ID | Prerequisites | Learning Targets (SLTs) |
|---|---|---|
|
4c21e2bfbd72f120f80100162fb7e84cafaa57840803cfbe8ad6152e5b211e17
|
-
|
Explain what an API is and describe the request/response pattern used in payment integrations
Read and interpret the fields in a payment API transaction request
Describe the purpose of a sandbox environment and how to use it safely
|
|
fa5ac2eccba40d9488c0e9721cc6cd58a2b7d92a68ff80dc9a399a49b1cf665f
|
-
|
Explain what a payment gateway does and where it sits in the payment network
Describe how an M-Pesa transaction differs from a card transaction
Distinguish between authorization, capture, and settlement
|
|
d6095491ffecb3d33aad4436a0be9a086d896f0718131bf14a26e6de5e235af2
|
-
|
Identify the hardware and software components of a Tracom POS system
Describe the path of a payment transaction from card tap to response
Distinguish between purchase, refund, void, and reversal transaction types
|
|
035086eacba767c1b982797e81fa81b6b5f1c78fc43cad4e96fb32fb961a0d9d
|
-
|
Design the architecture of a POS integration connecting a Tracom terminal to a payment gateway
Map the states a payment transaction moves through from initiation to settlement
Explain what idempotency is and describe how it prevents double-charging customers
|