External Payment Processors
External payment processors are third-party services, such as Stripe or Adyen, that Raytio connects to for payment capture and processing. FXM keeps the processor configuration separate from the credentials used to connect to it, so credentials can be rotated without changing the processor itself.
Processor registration
Each payment processor is registered as a named provider. A processor registration identifies the provider and whether it operates as a payment gateway or direct processor.
| Field | Purpose |
|---|---|
| Processor name | The human-readable name, such as "Stripe" |
| Processor type | Whether the provider is used as a gateway or direct processor |
| Provider party | The organisation represented by the processor |
Gateways route transactions to acquiring banks. Direct processors handle more of the transaction lifecycle themselves.
Default setup
Raytio can provide a default gateway processor for a tenant. Additional processors depend on the tenant's payment configuration and the integrations enabled for that tenant.
Processor credentials
API keys and secrets for each processor are managed separately from the processor registration. Credentials can apply at tenant level or to a specific merchant, depending on how payment processing is configured.
Credentials may include:
- credential type, such as API key or secret key
- environment, such as test or production
- merchant scope, where a credential belongs to one merchant
- public/private classification, which controls whether the credential can be shown to client applications
Credential visibility
FXM supports different credential views for different audiences:
- Administrative view - shows the credential details needed by administrators to configure and maintain processor integrations.
- Merchant public view - shows only active publishable credentials for merchant-facing or browser-based payment flows.
Secret credentials are not exposed through the merchant public view.
Access control
Registering a processor is an administrative activity. Merchant users can manage the payment credentials and publishable details that apply to their own merchant configuration when the tenant's access settings allow it.