Skip to main content

Release Notes

V1.6​

To help improve the speed at which NomuPay can review, underwrite and onboarding merchants, we are updating the merchant onboarding API to all NomuPay reseller clients. With this new release, we have expanded the mandatory field requirement to include 31 additional fields, all of which are designed to help expedite NomuPay’s risk review process.

What’s changed?​

Account entity​

  • The “complianceStatus” field now returns 6 possible updates:

    "1. Application data incomplete"
    "2. Application data received and under review"
    "3. Waiting for additional data"
    "4. Merchant conditionally approved"
    "5. Merchant approved"
    or
    "5. Merchant declined"

    The previous states of:
    “3. Waiting for documents”
    “4. Documents received”
    “5. Documents under review”
    have been deprecated and will no longer be returned.

  • The “fundingCurrency” field has been created to replace the now deprecated settlementCurrency field. The fundingCurrency field is used to send NomuPay the currency type that the merchant will accept funds in into their bank account. It is a mandatory field. View the API spec for more details.

  • The following fields will now be mandatory when "companyType" is not "Sole Proprietor":

    • registrationCountry
    • registrationNumber
    • registrationDate
    • numberOfUBOs

  • The following fields are now mandatory on the Account entity of the merchant onboarding API:

    • accountSubtype
    • companyType
    • contractingEntity
    • fundingCurrency
    • legalName
    • legalAdressCity
    • legalAdressCountry
    • legalAdressPostalCode
    • legalAdressState
    • legalAdressStreet
    • refundPolicy
    • yearsInBusiness

View the Account entity overview for more information on each of these fields. View the Create Account portion of the API spec for additional insight.

Contact entity​

  • The following fields will now be mandatory when "contactClassification" contains "UBO”, “Director” and/or “Signatory”
    • emailAddress
    • phoneNumber

View the Create Contact portion of the API spec for more details.

Opportunity entity​

  • The following fields are now mandatory when Product contains "Ecommerce” model:

    • ecommerceAPMs
    • ecommerceCards
    • numberOfOnlineOutles

  • The following fields are now mandatory when Product contains "In Store” model:

    • inStoreAPMS
    • inStoreCards
    • numberOfPhysicalStore

  • The following fields will now be mandatory on the Opportunity entity of the merchant onboarding API:

    • productDelivery
    • maxTV

View the Opportunity entity overview for more information on each of these fields. View the Create Opportunity portion of the API spec for additional insight.

Pricing entity​

  • The “billingCurrency” field has been created to send NomuPay the currency type will be used for the billing of the Pricing entity that it is associated with. Note: This field is not mandatory. View the API spec for more details.

  • The following fields will now be mandatory on the Pricing entity of the merchant onboarding API:

    • parentID
    • parentType
    • productEntityId
    • effectFrom
    • term
    • percentageFee or flatFee (one must be sent)
    • cbkFee
    • refundFee

View the Pricing entity overview for more information on each of these fields.

View the Create Pricing portion of the API spec for additional insight.

Banking details entity​

  • The following fields are now mandatory when "fIType" contains "BANK_ACCOUNT” model:

    • fICountry
    • fICurrency
    • bankId
    • bankAccountId

  • The following fields are now mandatory when "fIType" contains "BANK_ACCOUNT” and “fICountry” is either “HK” or “TH” model:

    • branchID

Release timeline​

The above-mentioned changes will be released into the sandbox environment on May 24, 2023 and will be available in production June 28, 2023.