Gateway Configuration
Each organization can configure multiple gateways and set defaults per payment method.
Gateway Fields
| Field | Description |
|---|---|
| Provider | MOCK, KOBANA, or PAGARME |
| Name | Display name |
| Environment | SANDBOX or PRODUCTION |
| Active | Whether the gateway is enabled |
| Credentials | Provider-specific settings (encrypted) |
| Default for card | Whether it is the default gateway for card payments |
| Default for boleto | Whether it is the default gateway for boleto |
| Default for PIX | Whether it is the default gateway for PIX |
Default Gateway
Each organization defines one default gateway per payment method:
- One default gateway for card
- One default gateway for boleto
- One default gateway for PIX
When setting a gateway as default, the previous default is automatically unset. The system uses transactions to ensure consistency.
Operations
Create Gateway
- Select the provider
- Enter the credentials
- Choose the environment (sandbox/production)
- Define whether it will be the default for any method
Kobana: Requires OAuth authorization before activation Pagar.me: Requires a connection test before activation Mock: Activated automatically
Update Gateway
Update name, credentials, status, or default configuration. Masked values are filtered to prevent accidental overwriting.
Delete Gateway
Only if there are no associated payments.
Monitoring
For each gateway, the system tracks:
- Total gateways (active/inactive)
- Count by provider
- Payments processed per gateway
- Consecutive delivery failures