www.inpay.com Open in urlscan Pro
104.20.74.10  Public Scan

Form analysis
8 forms found in the DOM

<form>
  <fieldset>
    <legend class="visuallyhidden">Consent Selection</legend>
    <div id="CybotCookiebotDialogBodyFieldsetInnerContainer">
      <div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonNecessary"><strong
            class="CybotCookiebotDialogBodyLevelButtonDescription">Necessary</strong></label>
        <div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper CybotCookiebotDialogBodyLevelButtonSliderWrapperDisabled"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessary"
            class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
      </div>
      <div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonPreferences"><strong
            class="CybotCookiebotDialogBodyLevelButtonDescription">Preferences</strong></label>
        <div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
            data-target="CybotCookiebotDialogBodyLevelButtonPreferencesInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
      </div>
      <div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonStatistics"><strong
            class="CybotCookiebotDialogBodyLevelButtonDescription">Statistics</strong></label>
        <div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatistics" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
            data-target="CybotCookiebotDialogBodyLevelButtonStatisticsInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
      </div>
      <div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonMarketing"><strong
            class="CybotCookiebotDialogBodyLevelButtonDescription">Marketing</strong></label>
        <div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketing" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
            data-target="CybotCookiebotDialogBodyLevelButtonMarketingInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
      </div>
    </div>
  </fieldset>
</form>

---

<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span
    class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>

---

<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonPreferences"
    checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>

---

<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonStatistics"
    checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>

---

<form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonMarketing" checked="checked"
    tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>

---

<form class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyContentCheckboxPersonalInformation" class="CybotCookiebotDialogBodyLevelButton"> <span
    class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>

---

POST /news-and-insights/10-ngo-payment-challenges/?utm_medium=email&_hsenc=p2ANqtz--28yNWll9T9dyyWvxa6z4p3Z6-3DGAU4e8h6iXVDWCT_X1C3dOvOqClUDY-pA5Z93bemRFCliMi1QJhQ0OrTme8Oz4XQ&_hsmi=304952510&utm_content=304952510&utm_source=hs_email#gf_4

<form method="post" enctype="multipart/form-data" target="gform_ajax_frame_4" id="gform_4"
  action="/news-and-insights/10-ngo-payment-challenges/?utm_medium=email&amp;_hsenc=p2ANqtz--28yNWll9T9dyyWvxa6z4p3Z6-3DGAU4e8h6iXVDWCT_X1C3dOvOqClUDY-pA5Z93bemRFCliMi1QJhQ0OrTme8Oz4XQ&amp;_hsmi=304952510&amp;utm_content=304952510&amp;utm_source=hs_email#gf_4"
  data-formid="4" novalidate="" class="recaptcha-v3-initialized">
  <div class="gf_invisible ginput_recaptchav3" data-sitekey="6Lf-MxkpAAAAAPXhdQrcZgdCuTZozj_LYNfVLW5y" data-tabindex="0"><input id="input_73a32564cb408802bce8489c68359e82" class="gfield_recaptcha_response" type="hidden"
      name="input_73a32564cb408802bce8489c68359e82" value=""></div>
  <div class="gform-body gform_body">
    <div id="gform_fields_4" class="gform_fields top_label form_sublabel_below description_below">
      <fieldset id="field_4_1" class="gfield gfield--type-name gfield--width-half field_sublabel_hidden_label gfield--no-description field_description_below hidden_label gfield_visibility_visible" data-js-reload="field_4_1">
        <legend class="gfield_label gform-field-label gfield_label_before_complex">Name</legend>
        <div class="ginput_complex ginput_container ginput_container--name no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name gform-grid-row" id="input_4_1">
          <span id="input_4_1_3_container" class="name_first gform-grid-col gform-grid-col--size-auto">
            <input type="text" name="input_1.3" id="input_4_1_3" value="" aria-required="false" placeholder="Your name">
            <label for="input_4_1_3" class="gform-field-label gform-field-label--type-sub hidden_sub_label screen-reader-text">First</label>
          </span>
        </div>
      </fieldset>
      <div id="field_4_3" class="gfield gfield--type-email gfield--width-half field_sublabel_below gfield--no-description field_description_below hidden_label gfield_visibility_visible" data-js-reload="field_4_3"><label
          class="gfield_label gform-field-label" for="input_4_3">Email</label>
        <div class="ginput_container ginput_container_email">
          <input name="input_3" id="input_4_3" type="email" value="" class="large" placeholder="Your company email" aria-invalid="false">
        </div>
      </div>
      <fieldset id="field_4_4" class="gfield gfield--type-consent gfield--type-choice gfield--input-type-consent field_sublabel_below gfield--has-description field_description_below hidden_label gfield_visibility_visible" data-js-reload="field_4_4">
        <legend class="gfield_label gform-field-label gfield_label_before_complex">Consent</legend>
        <div class="ginput_container ginput_container_consent"><input name="input_4.1" id="input_4_4_1" type="checkbox" value="1" aria-describedby="gfield_consent_description_4_4" aria-invalid="false"> <label
            class="gform-field-label gform-field-label--type-inline gfield_consent_label" for="input_4_4_1"></label><input type="hidden" name="input_4.2" value="" class="gform_hidden"><input type="hidden" name="input_4.3" value="13"
            class="gform_hidden"></div>
        <div class="gfield_description gfield_consent_description" id="gfield_consent_description_4_4">I agree to receiving occasional marketing communication from Inpay, including updates on our products and services. I am aware that I can withdraw
          this consent at any time by contacting Inpay or unsubscribing via email. I have read and agree to Inpay processing my personal data in accordance with its <a href="/privacy-policy">Privacy Policy</a>.</div>
      </fieldset>
    </div>
  </div>
  <div class="gform_footer before"> <input type="submit" id="gform_submit_button_4" class="gform_button button" value="Submit"
      onclick="if(window[&quot;gf_submitting_4&quot;]){return false;}  if( !jQuery(&quot;#gform_4&quot;)[0].checkValidity || jQuery(&quot;#gform_4&quot;)[0].checkValidity()){window[&quot;gf_submitting_4&quot;]=true;}  "
      onkeypress="if( event.keyCode == 13 ){ if(window[&quot;gf_submitting_4&quot;]){return false;} if( !jQuery(&quot;#gform_4&quot;)[0].checkValidity || jQuery(&quot;#gform_4&quot;)[0].checkValidity()){window[&quot;gf_submitting_4&quot;]=true;}  jQuery(&quot;#gform_4&quot;).trigger(&quot;submit&quot;,[true]); }">
    <input type="hidden" name="gform_ajax" value="form_id=4&amp;title=&amp;description=1&amp;tabindex=0&amp;theme=gravity-theme">
    <input type="hidden" class="gform_hidden" name="is_submit_4" value="1">
    <input type="hidden" class="gform_hidden" name="gform_submit" value="4">
    <input type="hidden" class="gform_hidden" name="gform_unique_id" value="">
    <input type="hidden" class="gform_hidden" name="state_4"
      value="WyJ7XCI0LjFcIjpcImRlNTE1YTJjMmI2NTQ4YmViNmZkZjM3YzE4YTNhZTQ0XCIsXCI0LjJcIjpcImU1NGVkYTYyYTM4ZDQ0MGYyZTlkMmY3MDc4ZTU2N2M4XCIsXCI0LjNcIjpcImUwMDg4ZmM4YWMzNjY0YWFmM2Y2MjZkMWZhZDQyMDE2XCJ9IiwiYzYyMjBlMzZlOWM3NzIzMDE0ODdkZjRjZDUzNjNhM2UiXQ==">
    <input type="hidden" class="gform_hidden" name="gform_target_page_number_4" id="gform_target_page_number_4" value="0">
    <input type="hidden" class="gform_hidden" name="gform_source_page_number_4" id="gform_source_page_number_4" value="1">
    <input type="hidden" name="gform_field_values" value="">
  </div>
</form>

---

POST /news-and-insights/10-ngo-payment-challenges/?utm_medium=email&_hsenc=p2ANqtz--28yNWll9T9dyyWvxa6z4p3Z6-3DGAU4e8h6iXVDWCT_X1C3dOvOqClUDY-pA5Z93bemRFCliMi1QJhQ0OrTme8Oz4XQ&_hsmi=304952510&utm_content=304952510&utm_source=hs_email#gf_8

<form method="post" enctype="multipart/form-data" target="gform_ajax_frame_8" id="gform_8"
  action="/news-and-insights/10-ngo-payment-challenges/?utm_medium=email&amp;_hsenc=p2ANqtz--28yNWll9T9dyyWvxa6z4p3Z6-3DGAU4e8h6iXVDWCT_X1C3dOvOqClUDY-pA5Z93bemRFCliMi1QJhQ0OrTme8Oz4XQ&amp;_hsmi=304952510&amp;utm_content=304952510&amp;utm_source=hs_email#gf_8"
  data-formid="8" novalidate="" class="recaptcha-v3-initialized">
  <div class="gf_invisible ginput_recaptchav3" data-sitekey="6Lf-MxkpAAAAAPXhdQrcZgdCuTZozj_LYNfVLW5y" data-tabindex="0"><input id="input_04beee060f6fcbb0256cf55c52eefd80" class="gfield_recaptcha_response" type="hidden"
      name="input_04beee060f6fcbb0256cf55c52eefd80" value=""></div>
  <div class="gform-body gform_body">
    <div id="gform_fields_8" class="gform_fields top_label form_sublabel_below description_below">
      <div id="field_8_1" class="gfield gfield--type-email gfield_contains_required field_sublabel_below gfield--no-description field_description_below gfield_visibility_visible" data-js-reload="field_8_1"><label
          class="gfield_label gform-field-label" for="input_8_1">Email<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
        <div class="ginput_container ginput_container_email">
          <input name="input_1" id="input_8_1" type="email" value="" class="large" placeholder="Email" aria-required="true" aria-invalid="false">
        </div>
      </div>
      <div id="field_8_3" class="gfield gfield--type-text gfield_contains_required field_sublabel_below gfield--no-description field_description_below gfield_visibility_visible" data-js-reload="field_8_3"><label class="gfield_label gform-field-label"
          for="input_8_3">First Name<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
        <div class="ginput_container ginput_container_text"><input name="input_3" id="input_8_3" type="text" value="" class="large" placeholder="First Name" aria-required="true" aria-invalid="false"> </div>
      </div>
      <div id="field_8_4" class="gfield gfield--type-text gfield_contains_required field_sublabel_below gfield--no-description field_description_below gfield_visibility_visible" data-js-reload="field_8_4"><label class="gfield_label gform-field-label"
          for="input_8_4">Last Name<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
        <div class="ginput_container ginput_container_text"><input name="input_4" id="input_8_4" type="text" value="" class="large" placeholder="Last Name" aria-required="true" aria-invalid="false"> </div>
      </div>
      <div id="field_8_5" class="gfield gfield--type-textarea gfield_contains_required field_sublabel_below gfield--no-description field_description_below gfield_visibility_visible" data-js-reload="field_8_5"><label
          class="gfield_label gform-field-label" for="input_8_5">Message<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></label>
        <div class="ginput_container ginput_container_textarea"><textarea name="input_5" id="input_8_5" class="textarea small" placeholder="Message" aria-required="true" aria-invalid="false" rows="10" cols="50"></textarea></div>
      </div>
      <fieldset id="field_8_7" class="gfield gfield--type-consent gfield--type-choice gfield--input-type-consent gfield_contains_required field_sublabel_below gfield--has-description field_description_below gfield_visibility_visible"
        data-js-reload="field_8_7">
        <legend class="gfield_label gform-field-label gfield_label_before_complex">Consent<span class="gfield_required"><span class="gfield_required gfield_required_text">(Required)</span></span></legend>
        <div class="ginput_container ginput_container_consent"><input name="input_7.1" id="input_8_7_1" type="checkbox" value="1" aria-describedby="gfield_consent_description_8_7" aria-required="true" aria-invalid="false"> <label
            class="gform-field-label gform-field-label--type-inline gfield_consent_label" for="input_8_7_1"></label><input type="hidden" name="input_7.2" value="" class="gform_hidden"><input type="hidden" name="input_7.3" value="21"
            class="gform_hidden"></div>
        <div class="gfield_description gfield_consent_description" id="gfield_consent_description_8_7">I agree to receiving payment news and trends from Inpay, including updates to our products and services. I am aware that I can withdraw this
          consent at any time by contacting Inpay or unsubscribing via email. I agree to Inpay processing my personal data in accordance with its <a href="/privacy-policy">Privacy Policy</a>.</div>
      </fieldset>
    </div>
  </div>
  <div class="gform_footer top_label"> <input type="submit" id="gform_submit_button_8" class="gform_button button" value="Submit"
      onclick="if(window[&quot;gf_submitting_8&quot;]){return false;}  if( !jQuery(&quot;#gform_8&quot;)[0].checkValidity || jQuery(&quot;#gform_8&quot;)[0].checkValidity()){window[&quot;gf_submitting_8&quot;]=true;}  "
      onkeypress="if( event.keyCode == 13 ){ if(window[&quot;gf_submitting_8&quot;]){return false;} if( !jQuery(&quot;#gform_8&quot;)[0].checkValidity || jQuery(&quot;#gform_8&quot;)[0].checkValidity()){window[&quot;gf_submitting_8&quot;]=true;}  jQuery(&quot;#gform_8&quot;).trigger(&quot;submit&quot;,[true]); }">
    <input type="hidden" name="gform_ajax" value="form_id=8&amp;title=&amp;description=1&amp;tabindex=0&amp;theme=gravity-theme">
    <input type="hidden" class="gform_hidden" name="is_submit_8" value="1">
    <input type="hidden" class="gform_hidden" name="gform_submit" value="8">
    <input type="hidden" class="gform_hidden" name="gform_unique_id" value="">
    <input type="hidden" class="gform_hidden" name="state_8"
      value="WyJ7XCI3LjFcIjpcImRlNTE1YTJjMmI2NTQ4YmViNmZkZjM3YzE4YTNhZTQ0XCIsXCI3LjJcIjpcImU1NGVkYTYyYTM4ZDQ0MGYyZTlkMmY3MDc4ZTU2N2M4XCIsXCI3LjNcIjpcIjNiNTkxZjU5MGUyNGVjYjgwN2E0MzI0YTcwN2ZhNjg5XCJ9IiwiNDBhMDU2OWY1NGNmNjM2ZTRjZjJmYjc5ODQ1NjBlY2YiXQ==">
    <input type="hidden" class="gform_hidden" name="gform_target_page_number_8" id="gform_target_page_number_8" value="0">
    <input type="hidden" class="gform_hidden" name="gform_source_page_number_8" id="gform_source_page_number_8" value="1">
    <input type="hidden" name="gform_field_values" value="">
  </div>
</form>

---

Text Content

Powered by Cookiebot
 * Consent
 * Details
 * [#IABV2SETTINGS#]
 * About


THIS WEBSITE USES COOKIES

We use cookies to personalise content and ads, to provide social media features
and to analyse our traffic. We also share information about your use of our site
with our social media, advertising and analytics partners who may combine it
with other information that you’ve provided to them or that they’ve collected
from your use of their services. If you want to choose between each of the
cookies used, please click on the fan “Details“ above.

Consent Selection
Necessary

Preferences

Statistics

Marketing

Show details
 * Necessary 13
   
   Necessary cookies help make a website usable by enabling basic functions like
   page navigation and access to secure areas of the website. The website cannot
   function properly without these cookies.
    * Cookiebot
      2
      Learn more about this provider
      1.gifUsed to count the number of sessions to the website, necessary for
      optimizing CMP product delivery.
      Expiry: SessionType: Pixel
      CookieConsentStores the user's cookie consent state for the current domain
      Expiry: 1 yearType: HTTP
    * Google
      3
      Learn more about this provider
      test_cookieUsed to check if the user's browser supports cookies.
      Expiry: 1 dayType: HTTP
      rc::aThis cookie is used to distinguish between humans and bots. This is
      beneficial for the website, in order to make valid reports on the use of
      their website.
      Expiry: PersistentType: HTML
      rc::cThis cookie is used to distinguish between humans and bots.
      Expiry: SessionType: HTML
    * LinkedIn
      2
      Learn more about this provider
      li_gcStores the user's cookie consent state for the current domain
      Expiry: 180 daysType: HTTP
      bscookieThis cookie is used to identify the visitor through an
      application. This allows the visitor to login to a website through their
      LinkedIn application for example.
      Expiry: 1 yearType: HTTP
    * hubspot.com
      vimeo.com
      zoominfo.com
      
      6
      __cf_bm [x3]This cookie is used to distinguish between humans and bots.
      This is beneficial for the website, in order to make valid reports on the
      use of their website.
      Expiry: 1 dayType: HTTP
      _cfuvid [x3]This cookie is a part of the services provided by Cloudflare -
      Including load-balancing, deliverance of website content and serving DNS
      connection for website operators.
      Expiry: SessionType: HTTP

 * Preferences 0
   
   Preference cookies enable a website to remember information that changes the
   way the website behaves or looks, like your preferred language or the region
   that you are in.
   
   We do not use cookies of this type.

 * Statistics 20
   
   Statistic cookies help website owners to understand how visitors interact
   with websites by collecting and reporting information anonymously.
    * Google
      6
      Learn more about this provider
      collectUsed to send data to Google Analytics about the visitor's device
      and behavior. Tracks the visitor across devices and marketing channels.
      Expiry: SessionType: Pixel
      _gaRegisters a unique ID that is used to generate statistical data on how
      the visitor uses the website.
      Expiry: 2 yearsType: HTTP
      _ga_#Used by Google Analytics to collect data on the number of times a
      user has visited the website as well as dates for the first and most
      recent visit.
      Expiry: 2 yearsType: HTTP
      _gatUsed by Google Analytics to throttle request rate
      Expiry: 1 dayType: HTTP
      _gidRegisters a unique ID that is used to generate statistical data on how
      the visitor uses the website.
      Expiry: 1 dayType: HTTP
      tdRegisters statistical data on users' behaviour on the website. Used for
      internal analytics by the website operator.
      Expiry: SessionType: Pixel
    * Hotjar
      3
      Learn more about this provider
      _hjSession_#Collects statistics on the visitor's visits to the website,
      such as the number of visits, average time spent on the website and what
      pages have been read.
      Expiry: 1 dayType: HTTP
      _hjSessionUser_#Collects statistics on the visitor's visits to the
      website, such as the number of visits, average time spent on the website
      and what pages have been read.
      Expiry: 1 yearType: HTTP
      _hjTLDTestRegisters statistical data on users' behaviour on the website.
      Used for internal analytics by the website operator.
      Expiry: SessionType: HTTP
    * Hubspot
      4
      Learn more about this provider
      __hsscIdentifies if the cookie data needs to be updated in the visitor's
      browser.
      Expiry: 1 dayType: HTTP
      __hssrcUsed to recognise the visitor's browser upon reentry on the
      website.
      Expiry: SessionType: HTTP
      __hstcSets a unique ID for the session. This allows the website to obtain
      data on visitor behaviour for statistical purposes.
      Expiry: 180 daysType: HTTP
      hubspotutkSets a unique ID for the session. This allows the website to
      obtain data on visitor behaviour for statistical purposes.
      Expiry: 180 daysType: HTTP
    * LinkedIn
      1
      Learn more about this provider
      AnalyticsSyncHistoryUsed in connection with data-synchronization with
      third-party analysis service.
      Expiry: 30 daysType: HTTP
    * Sleeknote
      2
      Learn more about this provider
      sn_global_countdown_last_reset_timestampSets a timestamp for when the
      visitor entered the website. This is used for analytical purposes on the
      website.
      Expiry: PersistentType: HTML
      SNSSets a unique ID for the session. This allows the website to obtain
      data on visitor behaviour for statistical purposes.
      Expiry: SessionType: HTTP
    * analytics.sleeknote.com
      tr-rc.lfeeder.com
      
      2
      (unnamed) [x2]Registers statistical data on users' behaviour on the
      website. Used for internal analytics by the website operator.
      Expiry: SessionType: Pixel
    * www.inpay.com
      2
      ziwsSessionCollects statistics on the user's visits to the website, such
      as the number of visits, average time spent on the website and what pages
      have been read.
      Expiry: SessionType: HTML
      ziwsSessionIdCollects statistics on the user's visits to the website, such
      as the number of visits, average time spent on the website and what pages
      have been read.
      Expiry: SessionType: HTML

 * Marketing 22
   
   Marketing cookies are used to track visitors across websites. The intention
   is to display ads that are relevant and engaging for the individual user and
   thereby more valuable for publishers and third party advertisers.
    * Meta Platforms, Inc.
      3
      Learn more about this provider
      lastExternalReferrerDetects how the user reached the website by
      registering their last URL-address.
      Expiry: PersistentType: HTML
      lastExternalReferrerTimeDetects how the user reached the website by
      registering their last URL-address.
      Expiry: PersistentType: HTML
      _fbpUsed by Facebook to deliver a series of advertisement products such as
      real time bidding from third party advertisers.
      Expiry: 3 monthsType: HTTP
    * Google
      6
      Learn more about this provider
      IDEUsed by Google DoubleClick to register and report the website user's
      actions after viewing or clicking one of the advertiser's ads with the
      purpose of measuring the efficacy of an ad and to present targeted ads to
      the user.
      Expiry: 1 yearType: HTTP
      pagead/landing [x2]Collects data on visitor behaviour from multiple
      websites, in order to present more relevant advertisement - This also
      allows the website to limit the number of times that they are shown the
      same advertisement.
      Expiry: SessionType: Pixel
      pagead/1p-conversion/#/Pending
      Expiry: SessionType: Pixel
      pagead/1p-user-list/#Tracks if the user has shown interest in specific
      products or events across multiple websites and detects how the user
      navigates between sites. This is used for measurement of advertisement
      efforts and facilitates payment of referral-fees between websites.
      Expiry: SessionType: Pixel
      _gcl_auUsed by Google AdSense for experimenting with advertisement
      efficiency across websites using their services.
      Expiry: 3 monthsType: HTTP
    * Hubspot
      1
      Learn more about this provider
      __ptq.gifSends data to the marketing platform Hubspot about the visitor's
      device and behaviour. Tracks the visitor across devices and marketing
      channels.
      Expiry: SessionType: Pixel
    * LinkedIn
      4
      Learn more about this provider
      bcookieUsed by the social networking service, LinkedIn, for tracking the
      use of embedded services.
      Expiry: 1 yearType: HTTP
      li_sugrCollects data on user behaviour and interaction in order to
      optimize the website and make advertisement on the website more relevant.
      Expiry: 3 monthsType: HTTP
      lidcUsed by the social networking service, LinkedIn, for tracking the use
      of embedded services.
      Expiry: 1 dayType: HTTP
      UserMatchHistoryUsed to track visitors on multiple websites, in order to
      present relevant advertisement based on the visitor's preferences.
      Expiry: 30 daysType: HTTP
    * Sleeknote
      3
      Learn more about this provider
      _sn_aImplements pop-up advertisement on the website.
      Expiry: 1 yearType: HTTP
      _sn_mImplements pop-up advertisement on the website.
      Expiry: 1 yearType: HTTP
      _sn_nImplements pop-up advertisement on the website.
      Expiry: 1 yearType: HTTP
    * sc.lfeeder.com
      5
      _lfaUsed in context with Account-Based-Marketing (ABM). The cookie
      registers data such as IP-addresses, time spent on the website and page
      requests for the visit. This is used for retargeting of multiple users
      rooting from the same IP-addresses. ABM usually facilitates B2B marketing
      purposes.
      Expiry: 1 yearType: HTTP
      _lfa_test_cookie_stored [x2]Used in context with Account-Based-Marketing
      (ABM). The cookie registers data such as IP-addresses, time spent on the
      website and page requests for the visit. This is used for retargeting of
      multiple users rooting from the same IP-addresses. ABM usually facilitates
      B2B marketing purposes.
      Expiry: SessionType: HTTP
      _lfaUsed in context with Account-Based-Marketing (ABM). The cookie
      registers data such as IP-addresses, time spent on the website and page
      requests for the visit. This is used for retargeting of multiple users
      rooting from the same IP-addresses. ABM usually facilitates B2B marketing
      purposes.
      Expiry: PersistentType: HTML
      _lfa_expiryContains the expiry-date for the cookie with corresponding
      name.
      Expiry: PersistentType: HTML

 * Unclassified 2
   Unclassified cookies are cookies that we are in the process of classifying,
   together with the providers of individual cookies.
    * js.zi-scripts.com
      1
      _zitokPending
      Expiry: 1 yearType: HTTP
    * www.inpay.com
      1
      unifiedScriptVerifiedPending
      Expiry: SessionType: HTML

Cross-domain consent[#BULK_CONSENT_DOMAINS_COUNT#] [#BULK_CONSENT_TITLE#]
List of domains your consent applies to: [#BULK_CONSENT_DOMAINS#]
Cookie declaration last updated on 30-04-2024 by Cookiebot



[#IABV2_TITLE#]

[#IABV2_BODY_INTRO#]
[#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#]
[#IABV2_BODY_PREFERENCE_INTRO#]
[#IABV2_LABEL_PURPOSES#]
[#IABV2_BODY_PURPOSES_INTRO#]
[#IABV2_BODY_PURPOSES#]
[#IABV2_LABEL_FEATURES#]
[#IABV2_BODY_FEATURES_INTRO#]
[#IABV2_BODY_FEATURES#]
[#IABV2_LABEL_PARTNERS#]
[#IABV2_BODY_PARTNERS_INTRO#]
[#IABV2_BODY_PARTNERS#]


Cookies are small text files that can be used by websites to make a user's
experience more efficient.

The law states that we can store cookies on your device if they are strictly
necessary for the operation of this site. For all other types of cookies we need
your permission.

This site uses different types of cookies. Some cookies are placed by third
party services that appear on our pages.

You can at any time change or withdraw your consent from the Cookie Declaration
on our website.

Learn more about who we are, how you can contact us and how we process personal
data in our Privacy Policy.

Please state your consent ID and date when you contact us regarding your
consent.


Do not sell or share my personal information
Use necessary cookies only Allow selection Customize

Allow all cookies
Powered by Cookiebot by Usercentrics

Home
Solutions

Services

Money Out

Instant, 24/7 global payouts

Money In

Open Banking enabled cardless pay-ins

Sectors

Financial Services
iGaming
Corporates
NGOs
Fintech Partnerships
About
About Us

Who we are, what we do & the purpose that drives us

Careers

Join the people transforming global payments

News & Insights
Contact Us
Get started

Home
Solutions

Services

Money Out

Instant, 24/7 global payouts

Money In

Open Banking enabled cardless pay-ins

Sectors

Financial Services
iGaming
Corporates
NGOs
Fintech Partnerships
About
About Us

Who we are, what we do & the purpose that drives us

Careers

Join the people transforming global payments

News & Insights
Contact Us
Get started


10 NGO PAYMENT CHALLENGES, CAUSES AND POSSIBLE CURES

2 April 2024

WE EXAMINE THE TEN BIGGEST PAYMENT PAIN POINTS FOR NGOS AND SUGGEST POSSIBLE
CURES.



Diagnosing payment problems and understanding the causes can help NGOs seek the
right treatment and potential cures.

1. COVERAGE

Challenge: Cross-border payments are harder to organize than domestic ones.

Cause: To achieve global coverage, banks rely on a network of correspondent
banking relationships, which link their different domestic systems together.
Great in theory, but difficult to implement in practice across different
countries, currencies, time zones and IT protocols.

Cure: Alternatives to SWIFT wire transfers for cross-border payments exist to
make global payment as quick and simple as local bank transfers. Some payment
service providers have developed their own global pay-in/pay-out networks.
That’s in addition to the technical and regulatory rails behind the scenes to
make global payments happen.

2. TRANSPARENCY

Challenge: Payments get stuck or go missing altogether.

Cause: Account-to-account cross-border payments are often processed by SWIFT.
While this is a great method for sending money around the world, it offers very
little transparency as to the route and status of the payment. With the
equivalent of world GDP moved across the SWIFT network every three days, things
may not always go smoothly.

Cure: Consolidating relationships into the right payment partner gives access to
a global network. And pre-funding transactions in bulk helps ensure more
right-first-time payments.

3. TRACEABILITY

Challenge: Payments can’t be tracked easily.

Cause: Based originally on telex, SWIFT has long been a single message system
with no response. This is why there’s historically been limited trackability.

Cure: By contrast, modern real-time payment systems are designed to confirm or
reject each transaction individually to both sender and recipient. Payments are
irrevocable, so both parties know whether payments have been successful within
seconds, which leads to better traceability and fewer exceptions.

4. SPEED

Challenge: Payments take too long.

Cause: Cross-border payments can take days, weeks or even months, due to legacy
technology platforms and a lack of standardization, among other reasons.

Cure: Some payment service providers can receive funds in any currency and pay
out locally in real-time 24x7x365. That’s in countries with an instant payment
infrastructure, or offer near-instant settlement elsewhere.

5. PRICE

Challenge: NGOs don’t necessarily know the price of sending a payment in
advance.

Cause: The more banks involved in a SWIFT chain, the more expensive the transfer
is likely to be. But it’s not always possible to know up front exactly how many
banks are involved, or which ones. Deductions also depend on who pays the
transfer fee: the sender, the recipient or both parties.

Cure: Some payment providers, like Inpay, can offer consistent fees, known
up-front with no deductions. That’s irrespective of the transaction amount,
originating country or currency, whether it’s a one-off, bulk or recurring
payment.

6. COST

Challenge: Payments cost too much.

Cause: For high volume currency pairs, such as US dollar to British pound, fewer
intermediary banks are involved. Hence shorter chains, quicker processing times
and lower costs. However, for less common currency pairs, the opposite is true.

Cure: Complex, ever-changing pricing and FX models are a no-no. International
transfers can be as cost-effective as domestic ones. Some payment service
providers can support scores of local currencies. That’s in addition to
simplifying the logistics of multi-currency operations.

7. SUPPORT

Challenge: NGOs don’t know where to turn for advice.

Cause: Domestic banks don’t provide the true consultative service that NGOs
desperately need – because they’re not necessarily set up to do so. They’re not
experts on other countries’ banking infrastructure. Or on specific payment
corridors and what’s needed to move transactions along.

Cure: Specialization is key. The right payment service provider has NGO sector
expertise and experience. They can offer guidance on the documentation required,
the questions likely to be asked, the quickest and most cost-effective way to
route payments to pre-empt problems.

8. COMPLIANCE

Challenge: Complex, dynamic regulations can be difficult to navigate.

Cause: Regulatory requirements, including sanctions regimes, know you
customer/anti-money laundering checks (KYC/AML) and the need for documentation,
differ country to country and change frequently.

Cure: NGOs need financial partners who understand their sector and will guide
them through the maze of regulatory requirements as quickly and cost-effectively
as possible. And if this is backed by an industry-leading compliance framework
and advanced screening capabilities, so much the better.

9. RECONCILIATION

Challenge: Back-office reconciliation can be complex and resource-intensive.

Cause: With so many payment corridors, currency pairings and transfer
timeframes, international payments can quickly become complex – and
reconciliation even more so. NGOs want operational efficiencies, particularly
around repetitive admin tasks which are not their core business.

Cure: Consolidating funds into a single, easy-to-reconcile format simplifies
admin on the back end. Payment providers should also be able to provide a simple
user interface to view all payments in one place, which helps with
reconciliation but also improves decisioning and speeds up issue resolution.

10. SCALABILITY

Challenge: Adding new payment corridors and growing payment volumes through
existing ones can be tough.

Cause: Scaling operations cross-border is hard because every country is
different. There are cultural and compliance differences, plus language,
logistics and localization challenges. Not all banks have the appetite to
service hard-to-reach countries.

Cure: A unified payments platform packaged in a single API will help NGOs expand
their important work. When the pay-in/pay-out solution comes from one place,
NGOs can manage payments end-to-end on a single contract. And avoid the
multi-supplier headaches of different providers for different payment corridors
or regions.

HOW INPAY CAN HELP

While they are generally the default entry point into financial services, banks
may be unwilling or unable to deal with everyday NGO challenges. Fortunately,
other options are available.

Modern cross-border payment solutions providers, like Inpay, are making the flow
of global payments faster, easier and more cost-effective. They have the right
reach to link NGO destination and origin countries and may already be accepted
by governments as regulated entities.

When it comes payment speed, trackability, cost-effectiveness and service,
alternative providers can certainly rival traditional ones. This means real-time
pay-outs, absolute traceability, cost advantages and domain expertise.

Covering 70% of the top 17 countries receiving humanitarian aid via local bank
transfer, and the remainder via international wire, Inpay helps the financial
inclusion of societies otherwise cut off from the global economy.

Contact us at sales@inpay.com to find out how we could help support your
important work.


STAY AHEAD OF PAYMENT TRENDS WITH INPAY’S NEWSLETTER

Name
First
Email

Consent

I agree to receiving occasional marketing communication from Inpay, including
updates on our products and services. I am aware that I can withdraw this
consent at any time by contacting Inpay or unsubscribing via email. I have read
and agree to Inpay processing my personal data in accordance with its Privacy
Policy.


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of
Service apply.


OPPORTUNITIES AND THREATS: THE IMPACT OF OPEN BANKING 

Mon 29 April 2024

On the face of it, regulatory and technical frameworks may not sound very
exciting. And payment infrastructure perhaps even less so. But what if we were
to talk about better bank payments, more joined-up money and personalized
services?

Read more about Opportunities and threats: the impact of Open Banking 


10 NGO PAYMENT CHALLENGES, CAUSES AND POSSIBLE CURES

Tue 2 April 2024

We examine the ten biggest payment pain points for NGOs and suggest possible
cures. Diagnosing payment problems and understanding the causes can help NGOs
seek the right treatment and potential cures.

Read more about 10 NGO payment challenges, causes and possible cures


HOW NGOS CAN CRACK THE INTERNATIONAL PAYMENT CODE

Mon 25 March 2024

Trying to navigate the maze of requirements to send funds abroad can seem like
Mission Impossible for NGOs. Know-your-customer (KYC) and anti-money laundering
(AML) checks differ from country to country. As do sanctions regimes and
documentation requirements.

Read more about How NGOs can crack the international payment code

×


SPEAK TO US

Let’s connect. Whatever your payments challenge, get in contact with a member of
our team to see how we can help.

Email(Required)

First Name(Required)

Last Name(Required)

Message(Required)

Consent(Required)

I agree to receiving payment news and trends from Inpay, including updates to
our products and services. I am aware that I can withdraw this consent at any
time by contacting Inpay or unsubscribing via email. I agree to Inpay processing
my personal data in accordance with its Privacy Policy.


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of
Service apply.


LET'S CONNECT

Contact Us

Denmark:
Toldbodgade 55B
1253, Copenhagen

 

United Kingdom:
1 Poultry
EC2R 8EJ, London

 

info@inpay.com
Phone: +45 88 610 600

SOLUTIONS

 * Money Out
 * Money In

SECTORS

 * Financial Services
 * iGaming
 * Corporates
 * NGOs
 * Fintech Partnerships

OTHER

 * About Us
 * News & Insights
 * Compliance
 * Careers
 * Contact Us

© 2024 Inpay. All rights reserved.

 * Privacy Policy
 * Cookie Policy

Cookie Settings


Notifications