Providers

Defines the PesaLink provider connections (mfi.pesalink.provider) - endpoint URLs, credentials, signing keys and transfer limits used to reach the interbank network. A correctly configured provider is what lets the transfer wizard and transactions communicate with the rail. Administrators manage sandbox-versus-production toggles here.

Providers
Providers — live screen from the BridgeERP MFI Suite.

Workflow

  1. Open Providers under PesaLink Configuration.
  2. Create or edit a provider entry with its endpoint and credentials.
  3. Set the environment toggle to sandbox or production.
  4. Enter signing keys and per-transaction limits.
  5. Save and run a connection test before going live.

Fields reference

Every field on this screen, drawn from the live data model.

FieldTypeRequiredDescription
Base URL
base_url
TextYese.g. https://uat.jengahq.io or https://sandbox.stanbicbank.co.ke
Token Endpoint Path
token_endpoint
Text—Path appended to base_url for OAuth2.
Public Callback URL
callback_url
Text—Full HTTPS URL where the sponsor bank POSTs camt.054 notifications. Should point to /pesalink/webhook on this BridgeERP.
Merchant/Account Code
merchant_code
Text—Configured on the sponsor-bank side for signature canonicalisation.
RSA Signing Key (PEM)
signing_key_pem
Long text—Merchant private key used to sign outbound payloads.
HMAC Secret
hmac_secret
Text—Shared secret used to verify inbound webhook signatures.
Funding Savings Account
funding_account_id
Link → mfi.savings.account—Account whose balance is debited for outbound transfers (your MFI float held at the sponsor bank).
Default Provider
is_default
Yes/No—At most one provider should be default.
Name
name
TextYesName
Sponsor Bank
sponsor_bank
Choice: DTB Jenga API, Stanbic Bank Kenya (sandbox), Generic ISO 20022YesSponsor Bank
Environment
environment
Choice: Sandbox, ProductionYesEnvironment
Has Message
has_message
Yes/No—Has Message
Sequence
sequence
Number—Sequence
Company
company_id
Link → res.company—Company
Initiate Transfer Endpoint Path
initiate_endpoint
Text—Initiate Transfer Endpoint Path
Query Status Endpoint Path
query_endpoint
Text—Query Status Endpoint Path
Client ID
client_id
Text—Client ID
Client Secret
client_secret
Text—Client Secret
API Key
api_key
Text—API Key
Sponsor Bank BIC
funding_account_bic
Text—Sponsor Bank BIC
Sponsor Bank Account Number
funding_account_number
Text—Sponsor Bank Account Number
Active
active
Yes/No—Active
Last Token At
last_token_at
Date & time—Last Token At
Last API Call
last_audit_at
Date & time—Last API Call
Transaction Count
transaction_count
Number—Transaction Count
Dispute Count
dispute_count
Number—Dispute Count

Actions & buttons

Buttons available on this screen and what they do:

  • Test Connection

Notes & rules

  • Credentials and signing keys authenticate every outbound message.
  • Sandbox/production toggle isolates testing from live settlement.
  • Transfer limits enforced here cap individual transactions.
  • Only administrators should edit production provider records.

Technical model: mfi.pesalink.provider · Record: Pesalink Sponsor-Bank Provider

Was this page helpful?