FinCode supports multiple payment methods to facilitate transaction funding. This guide details the integration flows for Card Payments (Hosted Checkout) and Open Banking.Documentation Index
Fetch the complete documentation index at: https://docs.fincode.technology/llms.txt
Use this file to discover all available pages before exploring further.
Supported Payment Methods
To retrieve the available payment methods for a specific transaction, use thesupported-payment-methods endpoint. This endpoint returns the payment options configured for your tenant and the specific corridor.
Get Supported Methods
Get Supported Payment Methods
Response Schema
The response includes a list ofpaymentMethodsMetadata, each containing specific details for that provider.
Card Payments (Hosted Checkout)
We support hosted card checkout flows via providers like TrustPayments (Secure Trading) and PayCross.- TrustPayments (Secure Trading)
- Other Providers (e.g. PayCross)
HTML Form Injection
TrustPayments requires a hidden HTML form to be constructed and submitted from the client side.Integration Flow:- Initiate Transaction: Create a transaction and call
supported-payment-methods. - Select Provider: Choose
SECURE_TRADING. - Construct Form: Create a hidden HTML form using all key-value pairs from the
paymentDetailsobject. - Auto-Submit: POST the form to
https://payments.securetrading.net/process/payments/choice. - Redirect: User is redirected to the secure payment page.
- Watch for Redirect: Listen for the callback URL (e.g.,
http://remitter.test.remitjunction.io/) to detect completion.
Open Banking
Open Banking payments are facilitated via providers like Volume and Volt. This flow typically uses a deep link or a redirect URL.Integration Flow
- Initiate Transaction: Create a transaction and get the supported payment methods.
- Select Provider: Choose the
ONLINE_BANK_PAYMENTprovider (e.g.,VOLUME). - Redirect User: Use the
hosted_gateway_urlfrom thepaymentDetailsto redirect the user.- Web: Redirect the browser window.
- Mobile: Launch the URL, which may open the user’s banking app via deep link.
- Completion: After payment, the user is redirected back to your application (configured via the callback URLs).
Example Response Data
Webhooks & Status Updates
Since these are hosted flows, your application will not receive the payment result synchronously in the response. You must listen for Webhooks to update the transaction status.- Success: The provider calls the
allurlnotification(or configured webhook URL). FinCode processes this and updates the transaction status toPAIDorPROCESSING. - Failure: If payment fails, the status will be updated to
FAILEDorCANCELLED.
Webhooks Guide
Learn how to subscribe to transaction status events.
