Marketplace Capabilities
Payments
ALEFBA payment documentation describes marketplace checkout principles and the boundary between ALEFBA, sellers and payment providers.
Documentation
Payment principles
- Use provider-hosted or provider-approved payment experiences.
- Never collect raw card data through undocumented ALEFBA API fields.
- Verify payment completion server-side before fulfilling an order.
- Use idempotency for operations that could otherwise be repeated.
- Record provider references without logging secret credentials.
- Keep refunds and payment status changes auditable.
Marketplace lifecycle
- The buyer confirms the cart and checkout details.
- A payment provider securely handles the payment interaction.
- The backend verifies the provider result.
- The order is updated only after trusted server-side confirmation.
- Refunds and disputes follow marketplace policy and provider rules.
Public API availability
This portal does not declare a standalone public Payments API endpoint. Use only payment routes and webhook events explicitly published by ALEFBA.
Security: Never place payment-provider secret keys in front-end JavaScript, documentation examples or public repositories.