Paymob
Egypt-focused payment gateway integration profile.
Checkout request mapping, callback verification, idempotency, reconciliation and saved-card behavior are implementation-specific.Open profile →Provider registry
Profile providers
without pretending they are enabled.
These profiles document integration questions, ownership boundaries and verification requirements. They are not a live inventory of configured providers.
Stripe
Global payment platform integration profile.
PaymentIntent or Checkout choices, webhook verification, idempotency and local payment-method support depend on the project.Open profile →Bosta
Shipping and fulfillment integration profile.
Shipment creation, city/zone mapping, labels, tracking, cancellation and exception handling require implementation verification.Open profile →ERP / CRM
Business-system synchronization profile.
Source-of-truth ownership, identifiers, field mapping, retries and auditability must be defined per implementation.Open profile →No provider profiles match that filter.
Provider registry JSON
The public descriptor contains category, implementation status semantics and links—never credentials or private endpoints.
Open provider-registry.v9.json →Use the integration contract
Provider-specific pages complement the normalized payment, shipping and business-system contract model.
Integration contracts →