Skip to content

Logo

Creedo.Capital

Supports in this guide: Payments, Payouts

Note

No independently verifiable public website could be confirmed for this provider. Contact your account manager for onboarding details.

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

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

Prerequisites: get from Creedo.Capital

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

  • MID -> Corefy field mid.
  • Secret key -> Corefy field secret_key.

Local payment methods: BDT (bKash, Nagad), PKR (Easypaisa), ARS (Mercado Pago).

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Creedo.Capital in the provider directory and press Connect at Creedo.Capital Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • MID
  • Secret key
  • Currency / Features -> choose values available for your account (BDT, PKR, ARS)

Success

You have connected Creedo.Capital Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Creedo.Capital's hosted payment page.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "83020cb4-79a4-4745-8c4c-782ceeced0f3",
      "service": "bkash_limited_bdt_hpp",
      "currency": "BDT",
      "amount": 200
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "83020cb4-79a4-4745-8c4c-782ceeced0f3",
      "service": "bkash_limited_bdt_hpp",
      "currency": "BDT",
      "amount": 200,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "phone": "+8801911111111",
        "email": "name@example.com",
        "metadata": {
          "ip": "203.0.113.1"
        }
      }
    }
  }
}

Important

customer is entirely optional - any field you don't send either falls back to a matching Constant (see below) or is simply omitted. customer.metadata.ip, if neither sent nor set as a Constant, falls back further to the IP address Corefy itself recorded for the request.

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

Constants (fallback fields)

Constants are static values that Corefy can send to Creedo.Capital 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_ID -> customer.reference_id
  • CUSTOMER_NAME -> customer.name
  • CUSTOMER_PHONE -> customer.phone
  • CUSTOMER_EMAIL -> customer.email
  • CUSTOMER_IP -> customer.metadata.ip
  • CUSTOMER_TYPE -> no API field - this one is Dashboard-only; there is no customer.* request field for it, so it must be set as a Constant if you want to send it at all (one of Trusted, FTD, MTD, YTD, Others)

Refunds

Creedo.Capital does not support refunds.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice, sending funds to the recipient's wallet/account.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1c9f6a0-2d5e-4a7b-9b1e-6a3f0d8c7b2a",
      "service": "bkash_limited_bdt",
      "currency": "BDT",
      "amount": 400,
      "fields": {
        "account_number": "111111111111"
      }
    }
  }
}

Important

fields.account_number is required for every payout service (bKash, Nagad, Easypaisa, Mercado Pago alike).

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1c9f6a0-2d5e-4a7b-9b1e-6a3f0d8c7b2a",
      "service": "bkash_limited_bdt",
      "currency": "BDT",
      "amount": 400,
      "fields": {
        "account_number": "111111111111"
      },
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "phone": "+8801911111111",
        "email": "name@example.com",
        "metadata": {
          "ip": "203.0.113.1"
        }
      }
    }
  }
}

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

Constants (fallback fields)

Same priority rule as on Payments.

Currently available constants (constant -> Corefy API field)

  • CUSTOMER_ID -> customer.reference_id
  • CUSTOMER_NAME -> customer.name
  • CUSTOMER_PHONE_NUMBER -> customer.phone
  • CUSTOMER_EMAIL -> customer.email
  • CUSTOMER_IP -> customer.metadata.ip
  • CUSTOMER_TYPE -> no API field - Dashboard-only, same as on Payments

Refunds

Creedo.Capital does not support refunds.

Additional info

  1. Active reconciliation is available on both Payments and Payouts - Corefy can poll Creedo.Capital's status endpoints in addition to receiving its callbacks.
  2. A payment can succeed even if the customer sends a different amount than requested - Creedo.Capital reports this as its own distinct status, which Corefy maps to a successful payment, not a failure.
  3. No recurring - this connector does not support saving/charging a token through Corefy.
  4. Each local payment method (bKash, Nagad) supports two underlying network types on Creedo.Capital's side (customer-to-merchant and merchant-to-customer wallet transfer); both map to the same Corefy service, so there is nothing to choose on your end.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the MID and Secret key
  • Invalid signature -> the Secret key configured in Corefy must match the one issued by Creedo.Capital exactly
  • Payment rejected for invalid phone number -> confirm customer.phone is a valid number for the selected payment method's country
  • Payout rejected for missing fields -> fields.account_number is required for every payout service
  • Currency or service is not supported -> confirm allowed currencies/features in your Creedo.Capital account and in Corefy
  • Refund fails -> Creedo.Capital does not support refunds through Corefy

Question

Still looking for help connecting your Creedo.Capital account? Please contact our support team!