Skip to content

Logo

MyFatoorah

Online payment solutions designed for business success

Supports in this guide: Payments

Provider website: myfatoorah.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from MyFatoorah)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from MyFatoorah

Contact your MyFatoorah account manager to get your account verified and receive the following credentials.

  • Merchant ID -> Corefy field merchant_id.
  • API Token -> Corefy field api_token -> used as a bearer token to authenticate every request.
  • Webhook Secret Key (optional) -> Corefy field webhook_secret_key -> used to verify callback notifications from MyFatoorah, if your account requires it.
  • API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.

Note

MPI API Key, Acquirer BIN, Acquirer Merchant ID, Acquirer Country Code, and Acquirer Country Code Source are also available as optional fields - they're only needed if your account uses the Use External MPI option (see Options below); ask your account manager whether this applies to you.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open MyFatoorah in the provider directory and press Connect at MyFatoorah Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • Merchant ID
  • API Token
  • Webhook Secret Key (optional)
  • API URL (optional)
  • MPI API Key (optional)
  • Acquirer BIN (optional)
  • Acquirer Merchant ID (optional)
  • Acquirer Country Code (optional)
  • Acquirer Country Code Source (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected MyFatoorah H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. MyFatoorah may return a 3D Secure challenge redirect depending on the card. CVV is always required - non-CVV sales aren't supported.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

This connector also supports EUR, AED.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

Important

customer.name is never sent to MyFatoorah directly - the name MyFatoorah receives always comes from the card's own embossed name, falling back to the CUSTOMER_NAME constant if that's unavailable. customer.email falls back to the EMAIL constant; no other customer field is used by this connector.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

  • use_external_mpi -> optional, boolean - if enabled, Corefy handles 3D Secure itself using the acquirer credentials above instead of MyFatoorah's own 3D Secure solution; Acquirer BIN and Acquirer Merchant ID are required in that case.
  • is_service_charge_on_customer -> optional, boolean - when processing a refund, controls whether MyFatoorah's own service charge for the refund is deducted from the customer or absorbed by you.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

  • CUSTOMER_NAME -> used only if the card's own embossed name isn't available (see the important note above - customer.name itself is never used)
  • EMAIL -> customer.email

Refunds

MyFatoorah supports partial and multiple refunds against the same payment.

Additional info

  1. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in MyFatoorah's own back-office.
  2. No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

  • Sale fails with a 3DS/MPI-related error -> if Use External MPI is enabled, double-check Acquirer BIN and Acquirer Merchant ID are both set - they're required in that case
  • Unexpected or missing customer name on MyFatoorah's side -> customer.name isn't used by this connector - the embossed card name or the CUSTOMER_NAME constant is sent instead
  • Invalid credentials / auth error -> verify Merchant ID/API Token for the selected environment
  • Currency or service is not supported -> confirm allowed currencies/features in your MyFatoorah account and in Corefy

Question

Still looking for help connecting your MyFatoorah account? Please contact our support team!