Skip to main content

SATIM Summary Wrap-Up

1. End-to-End Outcome​

SATIM integration is complete when:

  • backend reliably registers, acknowledges, and persists payment flow states
  • frontend respects SATIM IHM/UX requirements and return-page behavior
  • receipt actions and multilingual requirements are covered
  • certification checklist items are all validated

2. Backend Wrap-Up​

  • payment_attempts is the source of truth for traceability
  • raw register/acknowledge request and response payloads are stored
  • status lifecycle is consistent (initiated -> registered/registered_failed -> acknowledged/acknowledge_failed)
  • transactions is always persisted and linked to payment_attempts
  • acknowledge mapping sets gateway_success_message / gateway_error_message consistently
  • logs are audit-ready in case SATIM requests evidence during certification/support

3. Frontend Wrap-Up​

  • payment pages are SSL/TLS secured
  • final amount is clearly emphasized
  • captcha and CIB/EDAHABIA branding are present
  • terms and conditions are visible and accepted before payment
  • redirection opens in an independent browser context
  • return page messages follow SATIM accepted/rejected conditions
  • receipt print/download/email is available in all supported platform languages

4. Team Coordination Wrap-Up​

  • frontend and backend align on response mapping, statuses, and messages
  • shared end-to-end testing is executed before SATIM review
  • release readiness is validated jointly with the certification checklist
  1. Run full payment path with SATIM test cards.
  2. Verify DB trace (payment_attempts + transactions) for success and failure cases.
  3. Verify return-page outputs for accepted and rejected conditions.
  4. Verify receipt actions and multilingual rendering.
  5. Submit for SATIM validation with logs available on request.