Accept Fincra
without building the integration
Fincra is a cross-border payments provider connecting African markets with the UK, EU and US. It issues virtual named accounts in GBP, EUR and NGN, so an African business can be paid as though it held a local account in its customer's country — which is the hard part of cross-border collection.
- NGN
- GHS
- KES
- UGX
- ZAR
- ZMW
- GBP
- EUR
- USD
- Region
- Africa / Europe
- Methods
- 3
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Fincra in summary
- Coverage
-
- Nigeria
- Ghana
- Kenya
- Uganda
- South Africa
- Zambia
- United Kingdom
- United States
Among the markets Fincra serves — their own list is authoritative (opens in new tab).
- Currencies
-
- NGN
- GHS
- KES
- UGX
- ZAR
- ZMW
- GBP
- EUR
- USD
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by Fincra, and published on their pricing page (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab) · Developer docs (opens in new tab)
Written against Fincra's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, Fincra's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Virtual accounts
Named accounts in GBP, EUR and NGN for local collection
Bank transfer
Local bank rails in each supported market
Cards
Card collection where enabled
What PaymentHood handles for you
A direct Fincra integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- API key and business identifier, held server-side in PaymentHood
- Webhook security
- Signed collection webhook, validated before an order is released
- Payment verification
- Server-side transaction status re-check against the Fincra API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Fincra is unreachable
- One reconciliation view across Fincra and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use Fincra on your platform
Install the free PaymentHood plugin for your store, then enable Fincra in your dashboard.
Connecting Fincra takes three steps
Open your Fincra account
Register directly with Fincra and complete their onboarding. Funds settle from Fincra into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Fincra API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and Fincra appears as a payment option. Test in sandbox, then switch to live.