May 23, 2023

Link a corporate customer to an individual customer is a new feature for Spend Management and Payroll Management use cases. You can now link an individual customer, or employee, to their corporate customer and create that hierarchy in the system.

Note: For details on how to link a corporate customer to an individual customer or the Spend and Payroll Management feature, refer to the Platform tab.

• Spend Management: assigns a card to an employee linked to a corporate account. You can issue cards using the Add Card V2 API to provide the customer details as mentioned below:

  • customerHashId: the customerHashId of the corporate customer
  • walletHashId: the unique walletHashId of the corporate customer
  • childCustomerHashId: the customerHashId of the individual customer

  The card is issued to a corporate customer and is linked to an individual customer.

  You can fetch the childCustomerHashId with the Card Details V2 and Card List APIs. The query parameters are enhanced to include the clientHashId, customerHashId, walletHashId, and childCustomerHashId to help filter the results.

• Payroll Management: assigns a card to an employee for their own account. You can issue cards using the Add Card V2 API to provide the customer details as mentioned below:

  • customerHashId: the customerHashId of the corporate customer
  • walletHashId: the unique walletHashId of the corporate customer
  • childCustomerHashId: NULL

  The card is issued to an individual customer.

Card List V2 API retrieves a list of all cards issued to a wallet using the walletHashId and the customerHashId path parameters.

• The API structure mirrors the structure of all other Card V2 APIs with logical tags.
• The API shows the delivery address on file, the address where the card is delivered, and its embossing details.
• Card List V1 API is deprecated and becomes unsupported on December 31, 2023.

A transaction is declined if the Know Your Customer (KYC) verification process is in the pending status. This change is in accordance with compliance regulations. All cards associated with the customer and their wallet are also temporarily blocked until the status changes to verified.

• Link a corporate customer to an individual customer is a new feature for Spend Management and Payroll Management use cases. You can now link an individual customer, or employee, to their corporate customer and create that hierarchy in the system. Only an individual customer can be linked to a corporate customer. The opposite isn’t true.

  To establish a connection or relationship between the individual customer and the corporate customer, you need to configure the relationship with the childMustHaveParent parameter set to true. If this flag is false, you have the option to establish the connection, but the hierarchy is not enforced by the system.

  • Spend Management clients need to be configured with the billingAddressAsCorporate parameter set to true. This parameter allows the billing address of an Individual customer to be the same as the business address of a corporate customer.
  • Payroll Management clients need to be configured with the billingAddressAsCorporate parameter set to false.

  To setup the hierarchy, you need to onboard the corporate customer first and then onboard the individual customer using the Unified Add Customer API. The fields below have been impacted:

  • parentCustomerHashId: A new required parameter has been added if the childMustHaveParent flag is set to true.
  • kycMode: accepts MANUAL_KYC value if the billingAddressAsCorporate parameter is set to true.
  • billingAddress: details are optional if the billingAddressAsCorporate parameter is set to true.

  You can fetch the parentCustomerHashId for an individual customer with the following enhanced APIs:

  • Customer List V3 API: allows all individual customers to have the parentCustomerHashId parameter value available. You can fetch all the Individual customers linked to a corporate customer by providing the parentCustomerHashId parameter as a part of the query parameter.
  • Customer Details V2 API: the parentCustomerHashId parameter, in the individual customer details section, provides the customerHashId of a corporate customer to which the individual customer is linked.

• Transaction management is enhanced with the update of the following APIs to include the transactions that individual customers make on the cards issued to corporate accounts:

  • Transactions API: The childCustomerHashId parameter is added for all the transactions. The value includes the customerHashId of the individual customer for the applicable transactions. The childCustomerHashId can be used as a query parameter in this API.
  • Client Transactions API: The childCustomerHashId parameter is added for all the transactions. The value includes the customerHashIdof the individual customer for the applicable transactions. The childCustomerHashId can be used as a query parameter in this API.

Electronic document verification, or E_DOC_VERIFY, is now available as an option in kycMode for Know Your Customer (KYC) applicants in all regions. Corporate customers in Australia (AU), Singapore (SG), and the United States (US) previously completed the applicant KYC verification process via MANUAL_KYC, which delays the approval process. Using E_DOC_VERIFY, customers can now complete the KYC verification process for non-resident applicants following the redirect URL of Nium's KYC vendor and uploading documents on the vendors' UI resulting in real-time approvals. E_DOC_VERIFY is also available for Electronic Know Your Business (eKYB) and manual KYB. E_DOC_VERIFY is also available for European Union (EU) and United Kingdom (UK) applicants.

Enable E_DOC_VERIFY by passing the businessDetails.applicantDetails.kycMode=E_DOC_VERIFY object in the Onboard Corporate Customer API. Refer to Region-specific KYB requirements to see the available applicant and stakeholder KYC modes. Refer to the applicant KYC information on the following pages to learn how to integrate: AU, SG, US

Customer account statement generates a statement that gives a list of all transactions your customer makes on the platform, including deposits, withdrawals, spending, fees, payments, and refunds. You can give your customers an account statement periodically or based on their specific requests to help them keep the information for their records or to reconcile their transactions. You can now generate an account statement for your customers via the Account Statement API as a PDF or a CSV document. Contact your Nium representative to use this feature.

Customer List V3 API features a new query parameter, named customerType, so you can fetch your customer list based on your customer type. The accepted values are INDIVIDUAL or CORPORATE.

Unified Add Customer API makes the new customer onboarding delivery address parameters listed below optional. You can now choose to use the fields but they’re not required.

• deliveryAddress
• deliveryAddress2
• deliveryCity
• deliveryCountry
• deliveryLandmark
• deliveryState
• deliveryZipCode