Fibonatix gateway guide
| Additional notes |
|---|
| Finger-print & IP are required. |
| Server IP need to be white-listed in order to connect with Fibonatix gateway. |
| Incase of status code is not 30000, enquire must be used to fetch complete details of the transaction. |
Adding Fibonatix gateway
Content-Type: application/json
Authorization: Bearer {access_token}{
"gateway": {
"gateway_type": "fibonatix",
"endpoint": "7263",
"control": "f9c8b910-e63d-40b0-827e-6972b7eca728",
"sandbox": true
}
}{
"gateway": {
"token": "4ZC0AKN0149TN8DFPPMA8GF5VE",
"gateway_type": "fibonatix",
"description": null,
"merchant_profile_key": null,
"sub_merchant_key": null,
"payment_methods": [
"credit_card"
],
"state": "retained",
"created_at": "2025-12-03T07:47:42Z",
"updated_at": "2025-12-03T07:47:42Z",
"name": "Fibonatix",
"endpoint": "7263",
"characteristics": [
"purchase",
"authorize",
"capture",
"credit",
"partial_credit",
"void",
"verify",
"3dsecure_2_mpi_purchase",
"3dsecure_2_mpi_authorize",
"inquire_by_gateway_transaction_id",
"transaction_retry"
],
"credentials": [
{
"name": "endpoint",
"value": "7263"
}
],
"gateway_settings": {},
"gateway_specific_fields": [],
"redacted": false,
"sandbox": true,
"mode": "default"
}
}Note:
Example "token": "4ZC0AKN0149TN8DFPPMA8GF5VE", will be used in Authorization, Purchase etc. in the API end-point.
Enquire End-Point
Content-Type: application/json
Authorization: Bearer {access_token}//Status Code: 201 OK
{
"transaction": {
"on_test_gateway": false,
"created_at": "2025-12-03T08:13:11Z",
"updated_at": "2025-12-03T08:13:14Z",
"succeeded": true,
"state": "succeeded",
"token": "K3xIcTUSWYr3B8yiy1Fs7Xc2Rkd",
"transaction_type": "UpdateTransaction",
"original_transaction_updated": true,
"message_key": "messages.transaction_succeeded",
"message": "Succeeded!",
"gateway_token": "2H12F15KTG9EB80ZBW98BCQMEM",
"gateway_type": "fibonatix",
"original_transaction": {
"on_test_gateway": true,
"created_at": "2025-12-03T08:06:28Z",
"updated_at": "2025-12-03T08:13:14Z",
"succeeded": true,
"state": "succeeded",
"token": "LyaxvRaXcxlTmJm0Ii7PpwpWUKM",
"transaction_type": "Purchase",
"order_id": null,
"gateway_transaction_id": "XvfucEF1",
"message_key": "messages.transaction_succeeded",
"message": "Succeeded!",
"gateway_token": "2H12F15KTG9EB80ZBW98BCQMEM",
"gateway_type": "fibonatix",
"response": {
"success": true,
"message": "Transaction Approved",
"avs_code": null,
"avs_message": null,
"cvv_code": null,
"cvv_message": null,
"pending": false,
"result_unknown": false,
"error_code": null,
"error_detail": null,
"cancelled": false,
"fraud_review": null,
"created_at": "2025-12-03T08:13:13Z",
"updated_at": "2025-12-03T08:13:14Z",
"status": null
}
}
}
}Google Pay
Spreedly supports passing decrypted Google Pay tokens directly to the Fibonatix gateway using server-to-server (S2S) communication. This integration supports both direct API calls and low-code checkouts using Spreedly Composer.
Before processing Google Pay transactions on Fibonatix, ensure the following steps are complete:
- Google Pay Setup: You must have a Google Pay Merchant ID and complete Google's standard web/mobile integration.
- Gateway Provisioning: Contact your Fibonatix account manager to ensure your gateway account is explicitly configured to support Google Pay (
GooglePayment) transactions.
Spreedly Composer Support
If you use Spreedly Composer to manage your checkout forms, you can enable Google Pay within the Composer user interface. When active, Composer automatically handles displaying the Google Pay option on compatible browsers and passing the encrypted payment data to Spreedly, minimizing your backend integration effort.
Gateway Specific Fields
There are currently no supported Gateway Specific Fields for Fibonatix.
To request any gateway_specific_fields or gateway_specific_response_fields, please contact Support with your request and the gateway documentation for the fields of interest.
