Embedded Acquisition

In-app acquisition stands as an effective approach for acquiring users within your primary platform and seamlessly converting them into active vendors within your embedded payments ecosystem, thereby significantly boosting the adoption of your white-label payment solution.

At UNIPaaS, we recognize the transformative power of this strategy and have developed a sophisticated smart infrastructure - Embedded Acquisition - to facilitate this process. Our aim is to empower businesses to easily acquire users and employ innovative marketing strategies to ensure user adoption, enhance the value proposition of the platform, cultivate user loyalty and stickiness, and unlock the revenue potential inherent in users' transactional activities.

Benefits

UNIPaaS Embedded Acquisition provides a range of benefits for platforms looking to employ the innovative marketing strategies, based on ML, segmentation and personalization. These benefits include:

Enhanced user acquisition: Streamlined processes and targeted strategies result in more efficient acquisition of users, expanding the payment solution's user base.

Leveraging personalized experiences, tailored marketing messages, and strategic segmentation enables platforms to unlock new revenue streams, maximize the value of each user, foster deeper connections with the platform, and drive business growth through higher conversion rates.

Data-driven Insights: Advanced analytics provide valuable insights into user behavior and preferences, enabling data-driven decision-making and continuous optimization of marketing strategies.

Competitive advantage: By implementing cutting-edge marketing technologies and strategies, platforms gain a competitive edge in the market, positioning themselves as leaders in user acquisition and engagement for embedded payment solution.

These benefits collectively contribute to the overall success and growth of platforms leveraging UNIPaaS Embedded Acquisition.

Implementation

The primary interface for user engagement and marketing is UNIPaaS UI Web-Embeds. Prior to a vendor registering with your platform's payment solution, they encounter the "Zero state" of the UI Web-Embeds, presenting personalized messages and highlighting the specific benefits for their business, tailored to their industry, payment history, monthly turnover, and other pertinent parameters.

UNIPaaS collaborates closely with your team, aligning UI design, language style, and marketing strategies with your platform's vision and preferences. What distinguishes the Embedded Acquisition tool is its infrastructure, which gathers and analyzes user data, establishes segmentation and personalization, and facilitates simple integration with your platform, exponentially boosting adoption rates for payment products.

To implement the Embedded Acquisition tool, three main steps are involved:

UI Web-Embeds implementation:This step entails integrating UNIPaaS UI web embeds into your platform. These embeds serve as the primary interface for user engagement and marketing. To create a personalized experience for non-registered users who don't have a vendor ID yet, UNIPaaS requires a user (vendor) reference on your platform to be passed, along with basic user data, each time embeds are loaded.

Invoice data sharing and updating for non-registered users:
Dedicated endpoints are established to facilitate the sharing of invoice data with non-registered users who have not yet been assigned a vendor ID. The shared data serves as the foundation for crafting personalized messages tailored to each user's preferences and potential benefits with your payment solution.

New registered vendor creation with vendor reference:
Upon completion of the registration process, new vendors are created within the platform's ecosystem. It is crucial to include a vendor reference during this step to establish a direct connection between pre-registration data sharing and post-registration integration. This ensures seamless continuity and enables businesses to leverage insights gathered during the pre-registration phase to enhance the vendor's experience and drive adoption of the payment solution.

UI Web-Embeds

Authorization

To implement UI Web-Embeds, including Embedded Acquisition, into your platform, an authorized API call is required in your backend. This call should include a non registered vendor object, with a reference and user data, instead of vendor ID, to generate the UNIPaaS access token.

Generate UI components access token

curl -X POST "https://sandbox.unipaas.com/platform/authorize" \
  -H "accept: application/json" \
  -H "Authorization: Bearer <PLATFORM_SECRET_KEY>" \
  -H "Content-Type: application/json" \
  --data-raw '{
    "scopes": ["portal_read","portal_write","onboarding_write","invoice_read","invoice_write"],
    "vendor": {
      "reference": "uniq-id-1",
      "email": "[email protected]",
      "name": "John Doe",
      "type": "individual",
      "category": "MISC_AND_RETAIL_STORES",
      "categoryDescription": "Miscellaneous and Specialty Retail Stores"
    }
  }'

Vendor's object for non-registered users

NameTypeRequiredDescription
referenceStringYESA unique user reference on your platform
emailStringNOUser's email
nameStringYESUser's contact name
typeEnumYESUser's business type:
company
individual
categoryEnumYESUser business' industry
(Please use this mapping: https://docs.unipaas.com/docs/mcc-codes)
categoryDescriptionStringNODetailed user business' industry description

Learn more about UI Web-Embeds implementation

Invoice data

Dedicated endpoints have been specifically designed to facilitate the sharing of invoice data for non-registered users who have not yet been assigned a vendor ID.

Post invoice

POST/platform/vendors/reference​/{vendorReference}​/invoices

The invoice object example

{
  "reference": "INV-1234",
  "currency": "GBP",
  "totalAmount": 81,
  "vatAmount": 9.9,
  "dueDate": "2022-12-12T08:42:52.933Z",
  "paymentStatus": "unpaid",
  "totalPaid": 0,
  "vendor": {
    "reference": "uniq-id-1",
    "email": "[email protected]",
    "name": "John Doe",
    "type": "individual",
    "category": "MISC_AND_RETAIL_STORES",
    "categoryDescription": "Miscellaneous and Specialty Retail Stores"
  },
  "customer": {
    "reference": "customer-uniq-id-1"
  },
  "lineItems": [
    {
      "description": "line 1",
      "unitPrice": 10.6,
      "quantity": 4
    },
    {
      "description": "line 2",
      "unitPrice": 19.3,
      "quantity": 2
    }
  ],
  "isRecurring": true,
  "external":true,
  "publicUrl": "http://yourcompany.com/invoice.pdf",
  "invoiceObject": {}
}

Learn more about invoice creation

Update invoice

PATCH/vendors/reference​/{vendorReference}​/invoices​/{invoicesId}

The invoice object example

You may only update the values that have been changed.

In this example, the invoice was subject to a partial payment of 60 GBP, leading to a change in the payment status.

{
  "id": "6391fd42a38e34b15b118d9b", 
  "totalPaid": 60.0,
  "paymentStatus": "partially_paid"
}

Learn more about invoice updates

Newly registered vendors

To ensure seamless integration and continuity of data shared before and after a vendor's registration with your payment solution, it is imperative to include a vendor reference in the initial POST/vendors call.

This step serves to close the loop and establish a direct connection between the pre-registration data sharing process and the subsequent registration and integration phases.

Including vendor reference

POST/vendors

curl --location --request POST 'https://sandbox.unipaas.com/platform/vendors' \
--header 'accept: application/json' \
--header 'Authorization: Bearer <PLATFORM_SECRET_KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "businessName": "Better Delivery",
    "type": "company",
    "firstName": "John",
    "lastName": "Doe",
    "email": "[email protected]",
    "country": "GB",
    "reference" : "uniq-id-1", 
    "createOnboardingLink": true
    }'

Learn more about vendor creation