One payment API over any payment provider.

Write against [Provider] and which provider takes the money becomes a deployment decision rather than a rewrite. Stripe and iyzico ship with this workspace; a provider that lives elsewhere is a first-class one — implement [Provider], name it with [ProviderId::new]. Everything a caller needs is re-exported here; the bundled adapters are behind features, one each.

kasapay = { version = "0.0.2", features = ["stripe", "iyzico"] }

The one thing to understand first

[Provider::charge] does not mean the money moved. It returns a [Charge] whose [Status] is often [Status::RequiresAction], with a [NextAction] saying what the payer must do — confirm in the browser for Stripe, follow a deep link into iyzico's app for iyzico. Treating a returned Charge as a completed payment is the mistake this crate is shaped to prevent.

Choosing a provider at runtime

use std::sync::Arc;
use kasapay::{Provider, ProviderId};

# #[cfg(all(feature = "stripe", feature = "iyzico"))]
# fn pick(
#     id: ProviderId,
#     stripe: kasapay::stripe::Stripe,
#     iyzico: kasapay::iyzico::in_store::Client,
# )
# -> Option<Arc<dyn Provider>> {
match id {
    ProviderId::STRIPE => Some(Arc::new(stripe)),
    ProviderId::IYZICO => Some(Arc::new(iyzico)),
    _ => None,
}
# }