deema BNPL Integration Guide

This is a Technical guide explains the step-by-step process to integrate deema Buy Now, Pay Later (BNPL) into your online store using the standard integration flow.

⚙️ 1. Overview

Integrating deema BNPL allows your customers to pay later while you receive payment instantly. The process starts in the Sandbox environment for testing, then moves to the Live environment once approved.

All merchants must complete setup and testing before accepting real customer transactions.


🧰 2. Integration Channels

deema provides several integration options to suit your business setup and technology stack. Choose one of the following official integration channels to get started:

Each channel includes detailed documentation and examples to help your developers integrate quickly and securely.


🧪 3. Sandbox env and Testing

Before going Live, every merchant must complete the Sandbox testing phase to ensure their system can communicate with deema successfully.

Steps:

  1. Access the Sandbox
    • Use the credentials shared after initial registration.
    • Log in to the Merchant Portal.
  2. Perform the Required Tests
    • Complete one successful transaction in Sandbox.
    • Test order cancellation and refund operations through the portal.
    • Verify that your system receives Webhook notifications for each order update.
  3. Validate Results
    • Make sure your system updates order status correctly based on deema notifications.
    • Ensure the customer flow (checkout → payment → success/failure page) is smooth.

🔔 4. Webhook Configuration

Webhooks allow deema to automatically notify your system when an order's payment status changes.

Setup Process:

  1. Log in to your Merchant Portal.

  2. Open the Webhook section from the sidebar.

  3. Click Create New Webhook +.

  4. Fill in the following fields:

    • Webhook Name (for example, "My Store Orders")
    • Webhook URL (your system endpoint to receive updates)
    • Headers (Add a secret Key,Value pair for the Header)
  5. Save the configuration.

Test the Webhook

  • Confirm your system receives it correctly and returns 200 OK.

Webhook Settings Page



💳 5. Widget Implementation

The deema Widget provides the official payment experience for your customers.

How to Implement:

  1. Add the deema payment option to your checkout page.
  2. When the customer selects deema, the widget securely shows to them deema payment options and the steps to proceed with their payments.
  3. After completing the payment, the customer is redirected to your success or failure page automatically.
  4. The widget ensures the checkout flow meets deema's compliance and user experience standards.

Widget Interface



🧾 6. Integration Summary

Below is the complete overview of how the integration operates:

  1. Customer chooses deema at checkout.
  2. Your system initiates a checkout session and redirects the customer to deema.
  3. The customer completes payment on deema's page.
  4. The customer returns to your website (success or failure page).
  5. deema sends an automatic Webhook notification to update your system.
  6. You can view, cancel, or refund orders from your Merchant Portal as needed.

🚀 7. Go Live Checklist

Before requesting Live activation, confirm that you've completed all the following:

✅ RequirementDescription
Successful Sandbox TestOne full transaction tested (including cancel and refund)
Webhook WorkingNotifications received and processed correctly
Widget Integrateddeema checkout visible and functional on your Live website
System ValidationYour system updates order statuses automatically
Portal Access VerifiedYou can view and manage orders in the Merchant Portal

🌐 8. Go Live Activation Steps

Once testing is complete:

  1. Switch your system configuration from Sandbox to Live.
  2. Contact the deema Support Team to request Live activation.
  3. Use your new Live credentials.
  4. Perform one small Live test transaction.
  5. Confirm that your Webhook receives Live payment updates.
  6. Start accepting real payments from customers.

📘 9. Key Resources


💡

Tip: Always keep separate configurations for Sandbox and Live environments to prevent real transactions during testing.