Required for all Assembly customers

Know Your Customer (KYC)

KYC is the process of a business identifying and verifying the identity of its clients. The objectives of KYC guidelines is to prevent Assembly from being used, intentionally or unintentionally, by criminal elements for illegal activities.

KYC controls typically include, but are not limited to:

  • Collection and analysis of basic identity information such as government issued identity (individual) or registration (business) documents
  • Name matching known parties from Sanctions lists
  • Determination of the customer’s risk in terms of propensity to commit money laundering, terrorist finance, or identity theft

Assembly requires the collection of KYC information for a merchant to begin transacting normally on your platform. More information on the required KYC information can be found here.

Underwriting

Underwriting is the assessment of pre-payment risk that is posed by a user. Assembly conducts a multi-stage process where all users undergo continuous review, and can revert to prior verification states if they are flagged.

These reviews are conducted to mitigate the impact associated with the pre-payment risk Assembly Payments (and your platform) may be exposed to from disputable transactions that can result in a financial loss including, but not limited to; wire transfers, electronic funds transfers, credit cards payments, ACH pull, BPAY transaction and Direct Debits.

Underwriting reviews are conducted in the background of the transaction life cycle, and are largely unnoticed by end users unless they are flagged, and Merchant Identification is required.

Merchant Identification

In the event that a user provides inconsistent KYC information, is suspected of being involved in a fraudulent event, or poses a credit risk, Assembly may request a copy of applicable government identification to provide to verify their identity.

Assembly may defer payout/restrict access to funds to a user until request has been fulfilled.

Defend Basic

Fraud Detection

Assembly employs multiple tools that are designed to deliver real-time, multi-tiered protection which results in instant decisions on transactions.

As part of our Defend Basic offering, Assembly employs a basic set of rules that are designed to either Accept or Deny a transaction. These rules are very broad, and designed to identify and deny only the riskiest of transactional behaviour.

Manual Review

As the fraud detection rules for Defend Basic are Accept/Deny only, there are no manual reviews undertaken.

Secondary Transaction Verification

As the fraud detection rules for Defend Basic are Accept/Deny only, there is no secondary transaction verification undertaken.

Chargeback Management

In the event that we receive a chargeback, our team will notify you of the chargeback, and Direct Debit/ACH Pull the amount of the chargeback from you, plus a chargeback fee. If you wish to challenge the chargeback, you may provide evidence to us that the transaction is legitimate. 

If we determine that we have sufficient evidence to challenge the chargeback, we will then represent this data through our acquirer. Should our representment be successful, we will credit you the transaction amount, and you will only be charged the chargeback fee.

If the amount of chargebacks received becomes excessive, Assembly may require you to take further measures to mitigate chargeback volumes, or your production account may be de-activated.

Banning of users

In the event that a chargeback is received, the user is permanently banned.

Defend Plus

Fraud Detection

Assembly employs multiple tools that are designed to deliver real-time, multi-tiered protection which results in instant decisions on transactions.

As part of our Defend Plus offering, Assembly will employ a set of rules that are designed to detect fraudulent transaction common to your industry and your geolocation. These rules are based on historical data from fraudulent events detected with comparable merchants, and are updated as trends change and new data is received.

Manual Review

You are required to include a step in your payment flow that accounts for our Payment Held state. The ideal point in our payment workflow is between 'Purchaser Initiates Payment' and 'Funds Held In Secure Escrow Vault', and you can test this flow in Pre-Live using available credit card test data. A notification would ideally pop up for both the Purchaser and the Merchant whenever a transaction hits one of our fraud rules and enters into a Payment Held state.

This will prevent fraudulent transactions from continuing without approval, and avoid issues where Merchants complete work and subsequently don't get paid from that fraudulent transaction. While the payment exists in this state, we will complete a manual review, which will result in the transaction being approved, rejected, or kick off the Secondary Transaction Verification.

Secondary Transaction Verification

Secondary Buyer Verification is conducted when we are not satisfied that the transaction is legitimate after a manual review. We will contact the purchaser via email requesting an image of their card with the middle 8 digits hidden to ensure that they have physical possession of the card and satisfy our concerns. If a user refuses to provide this image, or we suspect that the image has been manipulated in any way, we will refund the transaction as part of our process, however you retain the right to override this process as the financial liability sits with you.

Chargeback Management

In the event that we receive a chargeback, our team will notify you and/or the sub-merchant of the chargeback, and Direct Debit/ACH Pull the amount of the chargeback from the sub-merchant, plus a chargeback fee. If for any reason we are unable to recover the funds from the sub-merchant, we will Direct Debit/ACH Pull from your account or pull the funds from your digital wallet.

If you and/or the sub-merchant wish to challenge the chargeback, our team may request from certain pieces of evidence required for us to challenge the chargeback through the card schemes. This information will only be what we cannot collect ourselves through our system. If we determine that we have sufficient evidence to challenge the chargeback, we will then represent this data through our acquirer. Should our representment be successful, we will credit the transaction amount, and only the chargeback fee will be applicable.

If the amount of chargebacks received becomes excessive, Assembly may require you to take further measures to mitigate chargeback volumes, or your production account may be de-activated.

Banning of users

In the event that a chargeback is received, that user will be banned. However you retain the right to override this process as the financial liability sits with you.

Defend Premium

Fraud Detection

Assembly employs multiple tools that are designed to deliver real-time, multi-tiered protection which results in instant decisions on transactions.

As part of our Defend Premium offering, Assembly employs a tailored set of rules that are designed to profile the fraud trends specific to your platform.These rules are based on historical data from fraudulent events detected on your platform, and are updated as trends change and new data is received.

Manual Review

You are required to include a step in your payment flow that accounts for our Payment Held state. The ideal point in our payment workflow is between 'Purchaser Initiates Payment' and 'Funds Held In Secure Escrow Vault', and you can test this flow in Pre-Live using available credit card test data. A notification would ideally pop up for both the Purchaser and the Merchant whenever a transaction hits one of our fraud rules and enters into a Payment Held state.

This will prevent fraudulent transactions from continuing without approval, and avoid issues where Merchants complete work and subsequently don't get paid from that fraudulent transaction. While the payment exists in this state, we will complete a manual review, which will result in the transaction being approved, rejected, or kick off the Secondary Transaction Verification.

Secondary Transaction Verification

Card Requests are conducted when we are not satisfied that the transaction is legitimate after a manual review. We will contact the purchaser via email requesting an image of their card with the middle 8 digits hidden to ensure that they have physical possession of the card, and satisfy our concerns. If a user refuses to provide this image, we will refund the transaction. We retain the right to refund a transaction at any time if we suspect or have confirmed that a transaction is fraudulent, and we do not pay out to Merchants on fraudulent tasks if we still hold those funds.

Chargeback Management

In the event that we receive a chargeback, our team may request from you certain pieces of evidence required for us to challenge the chargeback through the card schemes. This information will only be what we cannot collect ourselves through our system. We require this information to challenge any chargebacks we feel are genuine, however regardless of the outcome, you are not financially liable. Exceptions are if you don't provide the information we require within a timely manner.

Banning of users

In the event that a chargeback is received, that user will be banned, unless there is a compelling reason why they should be allowed to continue transacting. This is at our discretion, as we wear the financial liability.

Did this answer your question?