• User Documentation 
  • Amaryllis Release Notes 
  • For Developers 

  • User Documentation 
  • Amaryllis Release Notes 
  • For Developers 

Heartland - Dev Portal

  • folder icon closed folder iconIntroduction
  • folder icon closed folder iconAuthentication
  • folder icon closed folder iconManagement
    • Getting Started
    • Platform Accounts Management
      • Get Platform Account Configuration
      • Get Platform Account
      • Create Platform Account
      • Update Platform Account
      • Objects Reference
    • Sub-Accounts Management
      • Get Sub-Account Configurations
      • Get Sub-Account
      • Create Sub-Account
      • Update Sub-Account
      • Objects Reference
    • Users Management
      • Get User by User Id
      • Get User by Username
      • Create User
      • Update User
      • Objects Reference
    • Underwriting Management
      • Get Application
      • Get Application Template
      • Get Application Fields Statuses
      • Get Application Status
      • Get Linked Sub-Accounts
      • Get Resubmission
      • UMS IFrame Authentication
      • UMS IFrame
      • UMS IFrame Authentication in Resubmission Mode
      • UMS IFrame in Resubmission Mode
      • Create Application
      • Update Application
      • Update Application Fields Statuses
      • Update Application Status
      • Objects Reference
      • Response Codes
  • folder icon closed folder iconTransactions Processing
    • Getting Started
    • Credit Card Transactions
      • 3D-Secure
      • Authorization
      • Void
      • Capture
      • Charge
      • Refund
      • Credit
      • Verify
      • Chargeback
      • Cancel
    • Update
    • Adjustment
    • Recurring
    • ACH
    • Response
    • Response Codes
    • Objects Reference
  • folder icon closed folder iconTransactions Echo
    • Getting Started
    • Credit Card Transactions
      • Authorization
      • Void
      • Capture
      • Charge
      • Refund
      • Credit
      • Verify
      • Chargeback
      • Cancel
    • Update
    • Adjustment
    • ACH
    • Echo Response
    • Response Codes
    • Objects Reference
  • folder icon closed folder iconTokenization
    • Processing with a Token
      • Getting Started
      • Processing with Tokenization
    • Tokenization iFrame
      • iFrame Integration
      • iFrame Customization
      • iFrame Testing
      • Response Example
    • Tokenization API
      • Getting Started
      • Tokenization Request
      • Tokenization Response
      • Response Codes
  • folder icon closed folder iconPayouts
    • Getting Started
    • Payout Transactions
    • Response
    • Objects Reference
  • folder icon closed folder iconReports
    • Getting Started
    • Reports API
      • Account Balances
      • Payouts
      • Payouts Reconciliation
      • Transaction Details
      • Settlements
      • Account Summary
      • Transactions
      • Transactions Summary
      • Fees Summary
      • Incoming Fees
      • Expected Future Revenue
      • Profitability Analysis
      • Reconciliation Summary
      • Reconciliation Records
      • Chargeback Analysis
      • Tokens
      • Sign-up Summary
    • Status Codes
  • folder icon closed folder iconErrors
  • folder icon closed folder iconResponse Codes
  1. Home
  2. Docs
  3. Heartland – Dev Portal
  4. Management
  5. Underwriting Management
  6. UMS IFrame
Updated on June 9, 2023

Heartland - Dev Portal

  • folder icon closed folder iconIntroduction
  • folder icon closed folder iconAuthentication
  • folder icon closed folder iconManagement
    • Getting Started
    • Platform Accounts Management
      • Get Platform Account Configuration
      • Get Platform Account
      • Create Platform Account
      • Update Platform Account
      • Objects Reference
    • Sub-Accounts Management
      • Get Sub-Account Configurations
      • Get Sub-Account
      • Create Sub-Account
      • Update Sub-Account
      • Objects Reference
    • Users Management
      • Get User by User Id
      • Get User by Username
      • Create User
      • Update User
      • Objects Reference
    • Underwriting Management
      • Get Application
      • Get Application Template
      • Get Application Fields Statuses
      • Get Application Status
      • Get Linked Sub-Accounts
      • Get Resubmission
      • UMS IFrame Authentication
      • UMS IFrame
      • UMS IFrame Authentication in Resubmission Mode
      • UMS IFrame in Resubmission Mode
      • Create Application
      • Update Application
      • Update Application Fields Statuses
      • Update Application Status
      • Objects Reference
      • Response Codes
  • folder icon closed folder iconTransactions Processing
    • Getting Started
    • Credit Card Transactions
      • 3D-Secure
      • Authorization
      • Void
      • Capture
      • Charge
      • Refund
      • Credit
      • Verify
      • Chargeback
      • Cancel
    • Update
    • Adjustment
    • Recurring
    • ACH
    • Response
    • Response Codes
    • Objects Reference
  • folder icon closed folder iconTransactions Echo
    • Getting Started
    • Credit Card Transactions
      • Authorization
      • Void
      • Capture
      • Charge
      • Refund
      • Credit
      • Verify
      • Chargeback
      • Cancel
    • Update
    • Adjustment
    • ACH
    • Echo Response
    • Response Codes
    • Objects Reference
  • folder icon closed folder iconTokenization
    • Processing with a Token
      • Getting Started
      • Processing with Tokenization
    • Tokenization iFrame
      • iFrame Integration
      • iFrame Customization
      • iFrame Testing
      • Response Example
    • Tokenization API
      • Getting Started
      • Tokenization Request
      • Tokenization Response
      • Response Codes
  • folder icon closed folder iconPayouts
    • Getting Started
    • Payout Transactions
    • Response
    • Objects Reference
  • folder icon closed folder iconReports
    • Getting Started
    • Reports API
      • Account Balances
      • Payouts
      • Payouts Reconciliation
      • Transaction Details
      • Settlements
      • Account Summary
      • Transactions
      • Transactions Summary
      • Fees Summary
      • Incoming Fees
      • Expected Future Revenue
      • Profitability Analysis
      • Reconciliation Summary
      • Reconciliation Records
      • Chargeback Analysis
      • Tokens
      • Sign-up Summary
    • Status Codes
  • folder icon closed folder iconErrors
  • folder icon closed folder iconResponse Codes

UMS IFrame

Select Html to display code samples
  1. Request an authorization token via UMS IFrame Authentication method.
  2. Add the provided script reference to your application HTML page (parent page in the external system).
  3. Add Underwriting amaryllis-application custom element container (with required parameters) to your application HTML page (parent page in the external system).
  4. Add async submit() method to your application HTML page (parent page in the external system), a specific responses will be received – see attached implementation example.
Component Properties
Select Html to display code samples
NameRequiredDescription
template✓Id of the application template to display specific underwriting application form in the external system.
provider✓Id of the Service Provider that is related to application template in the configuration.
name✓Generated or pre-defined name of the Underwriting Application form.
email✓Merchant contact email.
token✓Token that is taken via get authentication token method.
configurationoptionalPre-filled form information.
Component properties rendering logic
Select Html to display code samples
NameRequiredDescription
name✓Name of the field.
valueoptionalValue of the field.
isHiddenoptionalThe flag defines whether the field is hidden or not.
  • Single fields (one parameter in Template = one field in Application) can be hidden, if set “isHidden”:true
  • Group fields (one parameter in Template = a few fields in Application, named as block of parameters in the description) can be hidden, if set block name “isHidden”:true.
    • List of group fields:
      • businessDetails.businessAddress
      • businessDetails.corporateAddress
      • bankingDetails.bankAccount
      • contactDetails.address
      • businessProfile.gstExempt
      • businessProfile.shippingRequired
      • businessProfile.pciCompliance
      • businessFinancials.volumeProjection
      • businessFinancials.annualVolumeProjection
      • businessFinancials.monthlyVolumeProjection
      • businessProcessingHistory.volumeHistory
      • businessProcessingHistory.monthlyVolumeHistory
      • businessProcessingHistory.annualVolumeHistory
One separate field from group cannot be hidden, only full group.
 

There are two types of pre-filled information representation:

  • Hidden fields: hidden in the UMS custom element. Fields contain pre-filled data that cannot be overridden and are represented by the following parameters
    • name
    • isHidden flag="true"
    • pre-populated value is saved after submit action from the external system
  • Visible fields with pre-filled data: displayed in the UMS custom element and contain pre-filled data that can be overridden. Fields are represented by the following parameters
    • name
    • isHidden flag="false"
    • pre-populated value OR the user input is saved after submit action from the external system
Available Fields

As each application is based on a specific Template (see list of Component Properties earlier in this section), application fields depend on the related fields in the Template.

  • In case fields are marked as visible, then they are not required;
  • In case fields are marked as required, then they are required and fields values must be populated in the form at the moment when the submit() method is called
  • Enumeration field type value is defined via enum number according to Validation rules – see below
Available Fields Validation Rules
NameTypeDescription
businessDetails.namestringMax length = 255 symbols.
businessDetails.legalnamestringMax length = 255 symbols.
businessDetails.registrationNumberstringMax length = 255 symbols.
businessDetails.ownershipTypeenum
Available Values:
 
  1. Individual
  2. Partnership
  3. Corporation
  4. LLC
  5. Medical
  6. Legal
  7. Association
  8. Estate
  9. Trustcompany
  10. NotForProfit
  11. GovernmentMunicipalEntity
  12. GovernmentFederalEntity
  13. GovernmentProvincialEntity
businessDetails.taxIdstringLength must be equal to 9 digits.
businessDetails.giinstringMax length = 19 symbols
1st and 2nd parts – Numbers and uppercase letters only
3rd part – Uppercase letters only
4th part – Numbers only
businessDetails.incorporationDatedatetimeDate format: US pattern mm/dd/yyyy
businessDetails.businessAddressblock of
parameters
See examples for additional reference
businessDetails.businessAddress.countrystringCountry from the list of available values
businessDetails.businessAddress.stateCodestringMax length = 3 symbols
States from the list of available values for country = “US” or “CA”or “Australia”:
businessDetails.businessAddress.citystringMax length = 50 symbols
businessDetails.businessAddress.streetstringMax length = 38 symbols
businessDetails.businessAddress.apartmentstringMax length = 38 symbols
businessDetails.corporateAddress.zipstring

If businessDetails.businessAddress.country = “US”,

max length = 5 or 9 symbols
If businessDetails.businessAddress.country != “US”,

max length = 15 symbols

businessDetails.companyWebsiteUrlstringWeb address
URL address should be started with http(s)://
businessDetails.dbaNamestringMax length = 255 symbols
businessDetails.dbaWebsiteUrlstringWeb address
URL address should be started with http(s)://
businessDetails.dynamicDescriptorstringMax length = 255 symbols
businessDetails.descriptionstringMax length = 4000 symbols
businessDetails.customerServicePhonestringMax length = 50 symbols
Regular expression:
/^([+ ]+)?(\d[\d- ]+)?(([\d- ]+))?[\d- ]+\d$/
businessDetails.customerServiceEmailstringEmail
Regular expression:
/^(?=[a-zA-Z0-9])[a-zA-Z0-9.!#$%&’+/=?^_`{|}~-]a-zA-Z0-9@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]{2,})$/
businessDetails.faxstringMax length = 50 symbols
Regular expression:
/^([+ ]+)?(\d[\d- ]+)?(([\d- ]+))?[\d- ]+\d$/
businessDetails.agreementboolean
Available Values:
 
true
false
businessDetails.customField1stringMax length = 255 symbols
businessDetails.customField2stringMax length = 255 symbols
businessDetails.customField3stringMax length = 255 symbols
bankingDetails.bankAccountblock of
parameters

See examples for additional reference

If there is external bank validation (‘External Bank Validation’ = ‘PLAID’ in Template),
then bank account fields (bankingDetails.bankAccount.accountNumber, bankingDetails.bankAccount.accountType, bankingDetails.bankAccount.accountHolderName, bankingDetails.bankAccount.entityType, bankingDetails.bankAccount.routingNumber , bankingDetails.bankAccount.bankName)
must be excluded from config and Account Number will be validated via PLAID wizard in iFrame.
If there is no external bank validation in Template,
bank account fields (bankingDetails.bankAccount.accountNumber, bankingDetails.bankAccount.accountType, bankingDetails.bankAccount.accountHolderName, bankingDetails.bankAccount.entityType, bankingDetails.bankAccount.routingNumber , bankingDetails.bankAccount.bankName)
are available for configuration

bankingDetails.bankAccount.accountNumberstringValue restrictions:
digits;
min.length=3
max.length=17
bankingDetails.bankAccount.accountTypeenum
Available Values:
 
Checking1
Savings2
 
bankingDetails.bankAccount.ccountHolderNamestringlength= 120
bankingDetails.bankAccount.entityTypeenum
Available Values:
 

personal – 0

business – 1
bankingDetails.bankAccount.routingNumberstring
digits;
length = 9
bankingDetails.bankAccount.bankNamestringMax length = 255 symbols
businessProfile.industryenum

String with IndustryType enumeration value.

Available Values:
 
InformationTechnology1
Telecommunication2
Manufacturing3
BankingServices4
Consulting5
Finance6
Government7
Delivery8
Entertainment9
NonProfit10
Other11
businessProfile.categoryenum

String with the CategoryType enumeration value.

Available Values:
 
Retail1
ECommerce2
POS3
businessProfile.privacyPolicyUrlstringWeb address
URL address should be started with http(s)://
businessProfile.returnsPolicyUrlstringWeb address
URL address should be started with http(s)://
businessProfile.tcPolicyUrlstringWeb address
URL address should be started with http(s)://
businessProfile.gstExemptboolean
Available Values:
 
true
false
businessProfile.gstNumberstringIn case
businessProfile.gstExempt = true, then businessProfile.gstNumber is required
businessProfile.gstExempt = false, then businessProfile.gstNumber should be empty.
businessProfile.descriptionOfGoodsstringMax length = 4000 symbols
businessProfile.seasonalBusinessboolean
Available Values:
 
true
false
businessProfile.shippingRequiredbooleanIf businessProfile.shipping.shippingRequired = false, then following values should be empty:
businessProfile.shipping.inventory
businessProfile.shipping.deliveryTimePercentage.oneToSevenDays
businessProfile.shipping.deliveryTimePercentage.eightToFourteenDays
businessProfile.shipping.deliveryTimePercentage.fifteenToThirtyDays
businessProfile.shipping.deliveryTimePercentage.moreThanThirtyDays
Available Values:
 
true
false
businessProfile.inventoryboolean
Available Values:
 
true
false
businessProfile.deliveryTimePercentage.oneToSevenDaysinteger0 >= Value <= 100
In case
businessProfile.shipping.shippingRequired = true parameter is required
businessProfile.shipping.shippingRequired = false parameter is not required
businessProfile.deliveryTimePercentage.eightToFourTeenDaysinteger0 >= Value <= 100
In case
businessProfile.shipping.shippingRequired = true parameter is required
businessProfile.shipping.shippingRequired = false parameter is not required
businessProfile.deliveryTimePercentage.fifteenToThirtyDaysinteger0 >= Value <= 100
In case
businessProfile.shipping.shippingRequired = true parameter is required
businessProfile.shipping.shippingRequired = false parameter is not required
businessProfile.deliveryTimePercentage.moreThanThirtyDaysinteger0 >= Value <= 100
In case
businessProfile.shipping.shippingRequired = true parameter is required
businessProfile.shipping.shippingRequired = false parameter is not required
businessProfile.pciComplianceblock of
parameters
See examples for additional reference
businessProfile.pciCompliance.pciLevelenumIn case
businessProfile.pciCompliance.isEnabled = true parameter is required
businessProfile.pciCompliance.isEnabled = false parameter is not required
Available Values:
 
DSS Level 11
DSS Level 22
DSS Level 33
DSS Level 44

businessProfile.pciCompliance.

storesSensitiveData

booleanIn case
businessProfile.pciCompliance.isEnabled = true parameter is required
businessProfile.pciCompliance.isEnabled = false parameter is not required
Available Values:
 
true
false

businessProfile.pciCompliance.

dataCompromised

booleanIn case
businessProfile.pciCompliance.isEnabled = true parameter is required
businessProfile.pciCompliance.isEnabled = false parameter is not required
Available Values:
 
true
false
businessProfile.customField1stringMax length = 255 symbols
businessProfile.customField2stringMax length = 255 symbols
businessProfile.customField3stringMax length = 255 symbols
businessProfile.mccCodestring,
Max 255
MCC code.
businessProfile.merchantBillingTypeenum

Merchant Billing Type details.

Available Values:
 
Debit
Remit
businessProfile.merchantPricingModelenum

Merchant Pricing Model details.

Available Values:
 
DailyDiscount
MonthlyDiscount
businessFinancials.volumeProjectionblock of
parameters
See examples for additional reference
businessFinancials.volumeProjection.visastringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.volumeProjection.mastercardstringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.volumeProjection.americanExpressstringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.volumeProjection.discoverstringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.volumeProjection.localDebitCardstringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.annualVolumeProjectionblock of
parameters
See examples for additional reference
businessFinancials.annualVolumeProjection.visastringMax length = 255 symbols
In case parameter “annualVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.annualVolumeProjection.mastercardstringMax length = 255 symbols
In case parameter “annualVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.annualVolumeProjection.americanExpressstringMax length = 255 symbols
In case parameter “annualVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.annualVolumeProjection.discoverstringMax length = 255 symbols
In case parameter “annualVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.annualVolumeProjection.localDebitCardstringMax length = 255 symbols
In case parameter “annualVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.monthlyVolumeProjectionblock of
parameters
See examples for additional reference
businessFinancials.monthlyVolumeProjection.visastringMax length = 255 symbols
In case parameter “monthlyVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.monthlyVolumeProjection.mastercardstringMax length = 255 symbols
In case parameter “monthlyVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.monthlyVolumeProjection.americanExpressstringMax length = 255 symbols
In case parameter “monthlyVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.monthlyVolumeProjection.discoverstringMax length = 255 symbols
In case parameter “monthlyVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.monthlyVolumeProjection.localDebitCardstringMax length = 255 symbols
In case parameter “monthlyVolumeProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.avgTicketPriceProjectionstringMax length = 255 symbols
In case parameter “Volume Projection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.highestTicketPriceProjectionstringMax length = 255 symbols
In case parameter “highestTicketPriceProjection” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.isAnnualAmexVolumeExceedMillionDollarsstringMax length = 255 symbols
In case parameter “isAnnualAmexVolumeExceedMillionDollars” = ‘Required’ under Underwriting Template the parameter is required
businessFinancials.customField1stringMax length = 255 symbols
businessFinancials.customField2stringMax length = 255 symbols
businessFinancials.customField3stringMax length = 255 symbols
businessProcessingHistory.volumeHistoryblock of
parameters
See examples for additional reference
businessProcessingHistory.volumeHistory.visastringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.volumeHistory.mastercardstringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.volumeHistory.americanExpressstringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.volumeHistorydiscoverstringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.volumeHistorylocalDebitCardstringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.monthlyVolumeHistoryblock of
parameters
See examples for additional reference
businessProcessingHistory.monthlyVolumeHistory.visastringMax length = 255 symbols
In case parameter “monthlyVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.monthlyVolumeHistory.mastercardstringMax length = 255 symbols
In case parameter “monthlyVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.monthlyVolumeHistory.americanExpressstringMax length = 255 symbols
In case parameter “monthlyVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.monthlyVolumeHistory.discoverstringMax length = 255 symbols
In case parameter “monthlyVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.monthlyVolumeHistory.localDebitCardstringMax length = 255 symbols
In case parameter “monthlyVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.annualVolumeHistoryblock of
parameters
See examples for additional reference
businessProcessingHistory.annualVolumeHistory.visastringMax length = 255 symbols
In case parameter “annualVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.annualVolumeHistory.mastercardstringMax length = 255 symbols
In case parameter “annualVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.annualVolumeHistory.americanExpressstringMax length = 255 symbols
In case parameter “annualVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.annualVolumeHistory.discoverstringMax length = 255 symbols
In case parameter “annualVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.annualVolumeHistory.localDebitCardstringMax length = 255 symbols
In case parameter “annualVolumeHistory” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.avgTicketPriceHistorystringMax length = 255 symbols
In case parameter “Volume History” = ‘Required’ under Underwriting Template the parameter is required
businessProcessingHistory.previousBankruptcyboolean
Available Values:
 
true
false
businessProcessingHistory.previousPersonalBankruptcyboolean
Available Values:
 
true
false
businessProcessingHistory.highestTicketPriceHistorystring,
Max 255
 
businessProcessingHistory.customField1stringMax length = 255 symbols
businessProcessingHistory.customField2stringMax length = 255 symbols
businessProcessingHistory.customField3stringMax length = 255 symbols
businessProcessingHistory.customField3stringMax length = 255 symbols
businessProcessingHistory.customField3stringMax length = 255 symbols
businessProcessingHistory.customField3stringMax length = 255 symbols
				
					//1. Request an authorization token via UMS IFrame Authentication method.

//See UMS IFrame Authentication section 




//2. Add script reference to your application HTML page 

//sandbox environment
<script src= "https://sandbox.4levers.com/underwritingiframe/amaryllis-application.js"></script>
<script src="https://ajax.googleapis.com/ajax/libs/webfont/1.6.16/webfont.js"></script> 

//production environment
<script src= "https://underwriting.4levers.com/amaryllis-application.js"></script>
<script src="https://ajax.googleapis.com/ajax/libs/webfont/1.6.16/webfont.js"></script>


//3. Add Underwriting amaryllis-application custom element container. 

<div id="container">
<amaryllis-application-create 
  template="application template id" 
  provider="Service Provider Id" 
  name="underwriting application form name" 
  email="merchant contact email"
  configuration='[{"parameterName":"text","value":"text","isHidden":"true"}]'
  token="Token that is taken via Get Authentication Token method">
</amaryllis-application-create>
</div>

//4. submit() method example

<script type="application/javascript">
         async function submitApplication(){
         try {
         var applicationElement = document.querySelector('amaryllis-application-create');
         var appId = await applicationElement.submit();
         document.body.removeChild(document.getElementById('container'));
         alert("Your application ID is: " + appId);
         } catch (e) {
         alert("Please complete all the steps and required fields");
         }
         }
      </script>
//Iframe example

<html lang="en">
   <head>
      <meta charset="UTF-8">
      <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.6.16/webfont.js"></script>
      <script src="https://sandbox.4levers.com/underwritingiframe/amaryllis-application.js"></script>
      <script type="application/javascript">
         async function submitApplication(){
         try {
         var applicationElement = document.querySelector('amaryllis-application-create');
         var appId = await applicationElement.submit();
         document.body.removeChild(document.getElementById('container'));
         alert("Your application ID is: " + appId);
         } catch (e) {
         alert("Please complete all the steps and required fields");
         }
         }
      </script>
   </head>
   <body>
      <div id="container">
         <amaryllis-application-create
            template="application template id"
            provider="Service Provider Id"
            name="underwriting application form name"
            email="merchant contact email"
            configuration='[{"parameterName":"text","value":"text","isHidden":"true"}]'
            token = "Token that is taken via Get Authentication Token method"
            >
         </amaryllis-application-create>
      </div>
      <div>
         <button onclick="submitApplication()">Submit</button>
      </div>
   </body>
</html>				
			
Still stuck? How can we help?
Was this page helpful? Yes No

How can we help?

© Amaryllis Payment Solutions, 2022  All rights reserved.