PAN
CVV
Activate Your Card
Error: {error}
;
if (!widgetToken) return Loading...
;
return (
Your Card
Error: {error}
;
if (!widgetToken) return Loading...
;
return (
Your PIN
Error: {error}
;
if (!widgetToken) return Loading...
;
return (
Set Your Card PIN
Error: {error}
;
if (!widgetToken) return Loading...
;
return (
activity FROZEN --> ACTIVE: Anomalies
resolved ACTIVE --> CANCELLED ACTIVE --> CONVERTED ACTIVE --> DISSOLVED ACTIVE --> MERGED ACTIVE --> SUSPENDED ``` ### Verification status To initiate transactions, an active business must also pass verification (identity and watchlist checks). All states other than `ACCEPTED` are restricted and do not allow most banking operations. | Verification status | Description | | ------------------- | ----------------------------------------------------------- | | `ACCEPTED` | The business is successfully verified. | | `PENDING` | Verification is in progress. | | `PROVISIONAL` | Partially verified or verified with restrictions. | | `REJECTED` | The business was rejected. | | `REVIEW` | Verification ran and identified issues that require review. | | `UNVERIFIED` | Verification has not been completed. | See the [KYC/KYB Verification](/v2/docs/kyc-kyb-verification) guide for how verifications are performed and what the results mean. ## Additional business documentation To mitigate fraud and money laundering, we recommend gathering the following documentation and attaching it to the business with the [Documents API](/v2/reference/createdocument): * **Legal entity organization documentation** — articles of incorporation, partnership agreement, certificate of organization, operating agreement, etc. * **Money Services Business (MSB) status** — whether the entity is a registered MSB and, if so, its FinCEN registration. * **Ongoing re-KYB** (e.g. annually or bi-annually) — required for certain higher-risk accounts subject to the Sponsor Bank's policies, or whenever unusual activity occurs. Higher-risk examples include cash-intensive businesses, non-US businesses, crypto businesses, MSBs, and marijuana-related businesses. ## Best practices
activity FROZEN --> ACTIVE: Anomalies
resolved ACTIVE --> DORMANT: No activity DORMANT --> ACTIVE ACTIVE --> DECEASED ACTIVE --> DENIED: Turned down ``` ### Verification status To initiate transactions, an active person must also pass verification (KYC, watchlists, and other checks). All states other than `ACCEPTED` are restricted and do not allow most banking operations. | Verification status | Description | | ------------------- | ----------------------------------------------------------- | | `ACCEPTED` | The person is successfully verified. | | `PENDING` | Verification is in progress. | | `PROVISIONAL` | Partially verified or verified with restrictions. | | `REJECTED` | The person was rejected. | | `REVIEW` | Verification ran and identified issues that require review. | | `UNVERIFIED` | Verification has not been completed. | See the [KYC/KYB Verification](/v2/docs/kyc-kyb-verification) guide for how verifications are performed and what the results mean. ## Handling sensitive attributes Some information you collect is personally identifiable information (PII) that can identify an individual directly or indirectly. The Synctera platform encrypts all data at rest. Some PII, such as an SSN, is especially confidential and requires further safeguards. Synctera stores those values in a vault to control access. When an endpoint later retrieves a resource containing such protected attributes, they are either omitted from the response or returned masked. ## Best practices
Account programs leverage Spend Controls, rail restrictions and other attributes, and are applied at the template level, to ensure any account created under the given program enforces the necessary controls depending on network, bank or program rules. If Account Programs are required for your use case, Synctera will provide the necessary set up and information. Fintechs must simply pass the correct `account_template_id` provided during Onboarding by your Implementation Manager, which will contain the program level settings required. ## Closing an Account As end customers unenroll from a fintech’s service, their accounts with Synctera will need to be closed. Synctera’s [Initiate Closure](/v2/reference/initiateaccountclosure) API allows fintechs to close a customer account as well as all products in use by the customer and ensure all underlying transactions are handled appropriately, with just one API call. Once closure is initiated - Synctera will: * Check for active disputes and pending transactions, and pause on closure until resolution * Stop further transactions, except for certain allowed scenarios (authorized payments, refunds, etc.) * Deactivate cards and tokens. * End recurring transactions. * Write off negative balances and handle other closure‑related behaviors. * Payout any interest due to the customer. * Transfer remaining funds to a specified destination account. If the destination account is an external account via ACH, the system will wait on a 2 day return window to ensure payout settles to avoid returns to a closed account before closing ### Integrating with Account Closure: The following curl example will walk you through integrating with Synctera’s account closure functionality, via the [Initiate Closure](/v2/reference/initiateaccountclosure) API. This assumes you have set up baseurl and apikey environment variables. See [Base URL](/v2/reference/need-to-know#environments) and [Authentication](/v2/reference/need-to-know#authentication) for instructions. Closing an account requires the following integrations: 1. Integrate with Synctera’s [Initiate Closure](/v2/reference/initiateaccountclosure) API: This API call will start the closure process and the customer account’s status will be set to IN\_CLOSING. The fintech will have to provide a destination account for customer funds to be transferred to. 2. Subscribe to the [Account.UPDATED](/v2/docs/webhooks-guide) webhook: This webhook will transmit updates on the status of the account. Once all system checks pass, any underlying transactions have completed and any products in use have been deactivated, the customer’s account will be set to a status of CLOSED. The following example illustrates how to format an [Initiate Closure](/v2/reference/initiateaccountclosure) request: Call [POST/v2/accounts/](/v2/reference/initiateaccountclosure)[/initiate\_closure](/v2/reference/initiateaccountclosure) to close the account.
Yes. We are able to transfer the funds in multiple payments. 2. **Will the balance transfer happen immediately?**
If there are no transactions on hold and no pending transactions, then the transfer will happen immediately after the Initiate Closure API was called. If there are transactions on hold or pending transactions, then the transfer will occur after these clear and the account will be closed. 3. **What happens if there is a return / refund after the account is closed?**
Synctera will work with your Sponsor Bank to send a check to the last known address for any funds that come in after the account is closed or follow the bank process. 4. **Can customers still raise a dispute after the account is closed?**
Yes, customers can raise a dispute after the account is closed. For card transactions, disputes can be filed up to 60 days from the statement date of the transaction in question. For ACH transactions, disputes can be raised up to 60 days from the settlement date of the transaction in question. If the investigation results in a chargeback, Synctera will manually send a check to the last known address for the transaction amount. 5. **Will a statement be issued after the account is closed?**
Yes a statement will be issued at the end of the month, even after the account is closed. Smart cards will remain IN\_CLOSING, until the customer pays off the balance listed in the statement generated at the end of the month. 6. **Are there any controls to ensure that the funds are sent to a valid recipient?**
Although we enforce industry standard fraud controls in our platform, we do not verify that the recipient is valid. We encourage the fintech to verify the recipient is valid, using its own data and or third party platforms. 7. **If you close an account without any underlying pending transactions or anything else that needs to be closed - how long until you receive the ‘closed’ webhook event?**
You will receive it the next business day. # MRDC Source: https://docs.synctera.com/v2/docs/create-mobile-deposit-guide MRDC - Mobile Remote Deposit Capture is a process that allows users to deposit checks into their accounts without having to go to a branch or ATM. Customers can submit deposits by taking an image of the check and submitting it online using the Synctera platform. Synctera API provides mobile deposit endpoints. As a FinTech you'll have to implement a feature that allows a customer to take a photo of a check to be deposited. ## Steps to submit a deposit The `curl` examples assume you have set up `baseurl` and `apikey` environment variables. See [Base URL](/v2/reference/need-to-know#environments) and [Authentication](/v2/reference/need-to-know#authentication) for instructions. Some examples depend on identifiers generated by previous steps. These are indicated like `{PERSON_ID}`.
Add Payment Card
Error: {error}
;
}
if (!widgetToken) {
return Loading payment form...
;
}
return (
Add Payment Card
to customer activate : Activate card monitor : Monitor card manage : Manage card reissue : Reissue card suspend : Suspend card terminate : Terminate card request --> physical request --> virtual virtual --> present physical --> deliver deliver --> activate present --> monitor activate --> monitor monitor --> manage manage --> reissue manage --> suspend manage --> terminate ``` ## Card Activation Methods There are 3 methods for activating cards: * Activation widget. * `POST /cards/activate` request with a barcode. Refer to [Activate Card](/v2/reference/activatecard) * `PATCH /cards/{card_id}` request . Refer to [Update Card](/v2/reference/updatecard) Typically upon activating a card the user should be prompted to set a PIN on the card. Even virtual cards when used with digital wallets can be prompted for a PIN at a merchant POS. If no PIN is set on a card and a merchant POS requests a PIN, the purchase will be impossible to complete successfully. ### Activation Widget For cards that have the full PAN and CVV printed on them, the customer who receives the card logs into the FinTech app (which uses our widgets described below), selects the option to activate a card, and enters those values to prove that they received the card. These values go to Synctera’s card vendor for card activation. ### Barcode Activation For cards that don’t have the PAN and CVV printed on them (or just have a partial PAN), the card issuer generates a unique barcode value for the card and gives that value to the card fulfillment vendor printing the card. The card printer encodes the barcode string into a code 128 barcode printed on the card or card carrier. The customer receiving the card uses the FinTech app’s section for card activation and scans the barcode. The FinTech converts the barcode back into the string and sends that to the POST /cards/activate endpoint which authenticates card activation through our card vendor. ### PATCH Request Depending on the risk appetite and alternative means of verifying the cardholder has the card in hand, integrators can optionally choose to activate cards using the PATCH /cards/\{card\_id} endpoint. This doesn't require any proof that the customer has the card in hand, so it's up to the integrator to perform any required due diligence to verify and authenticate the user. ## Handling Sensitive Card Information Some card data such as the PAN, CVV, expiration date (EXP) and PIN are sensitive and should be guarded from exposure to anyone except the authorized card holder. This data is exposed not only during card activation, but over the life of the card when the card customer wants to view their card data. To secure sensitive card information, the Payment Card Industry (PCI) Data Security Standard defines steps that must be followed when sending and receiving sensitive information. Your sponsor bank and credit card network require PCI compliance in your application when you handle card business with customers. Getting PCI compliance certification is an involved and expensive process. To provide PCI compliance without you having to go through the compliance process, we provide pre-built widgets and a library that are certified PCI-compliant. These widgets and the library are created by our card vendor, adapted by Synctera to work in our platform, and run within your application to send and receive sensitive data directly between your application and our card vendor. If you are PCI-certified, we also provide direct API access to manage your customers PIN. When your fintech onboards with Synctera, access to the API will be granted upon confirmation of your PCI-certification. ### Initial Card Setup– Synctera provides two PCI-compliant widgets that let your customers activate cards and set up an initial PIN: * The **Activate Card Widget** collects the PAN and CVV from your customer when they activate a card and then securely sends those values to our card vendor. The widget then asks the customer to set a PIN, which it also sends to the card vendor. * The **Set PIN Widget** lets a customer set a card’s PIN and then securely transmits it to our card vendor. This is useful for a barcode-activated card or when a customer wants to reset a PIN. These widgets each display within an HTML iframe element and connect to the card vendor using a single-use token granted for each transaction. If you are PCI-certified the [Card PIN API](/v2/reference/setcardpin) can be used to manage your customer PIN directly. ### Displaying Sensitive Card Data Once a card is active, your customers will want to view information about their cards that includes sensitive card data such as the PAN and CVV. See the [Card Widgets](/v2/docs/card-widgets) guide for more details. ## Resetting PIN Tries If someone incorrectly enters a card’s PIN too many times in a short time period (typically at an ATM or point-of-sale device), our card vendor suspends the card. The card status is set to SUSPENDED, and the card owner will most likely contact your FinTech for assistance. There are several courses of action to take if this occurs: * If you determine that fraud occurred on the card, you should reissue the card. This resets the PIN tries on the new card. * If the customer has forgotten their PIN, they can reset it using the PIN widget in your app. You must update the status of the card from SUSPENDED to ACTIVE so your customer can use the card again. * If the customer remembers their PIN correctly, then you update the status of the card from SUSPENDED to ACTIVE so the customer can use the card again. Note that you can handle status update and card reissuance through the Synctera dashboard if a customer service rep is working with the customer, or you can handle it through the Cards API endpoints if you have your own customer service mechanisms. ## Card Reissuance Scenarios A card may be reissued for many reasons. The card may have expired, the name on the card may need to be changed, or a physical card may be lost or stolen. Each of these scenarios is handled a bit differently to provide the best transition from the existing card to its replacement. These reissuance reasons are defined in the Cards API when you request issuing a replacement card: * **EXPIRATION**: A card is going to expire soon. A new expiration date and CVV are assigned to the replacement card while the PAN remains the same. The old card remains active until the new card is activated or until the expiration date arrives. An expiration reissuance must be requested prior to the actual expiration date. To retrieve cards that are about to expire, you can use the [List Cards](/v2/reference/listcards) endpoint - you can sort cards by expiration date with the `expiration_date` sort argument or filter cards with the `expires_before` filter. From there, you can choose how you want to automate the reissuance. You could, for example, create a background job that reissues cards without any user interaction, or prompt the user to go through a reissuance flow, where they confirm the card shipping address, etc. * **LOST**: The customer has reported the card as lost. The lost card is immediately terminated. The replacement card has a new PAN, CVV, and expiration date, but keeps the same PIN. * **STOLEN**: The customer has reported the card as stolen. The stolen card is immediately terminated. The replacement card has a new PAN, CVV, and expiration date, but keeps the same PIN. * **DAMAGED**: The customer requests a new card to replace a damaged card. A new expiration date and CVV are assigned to the replacement card while the PAN remains the same. The old card remains active until the new card is activated or until the expiration date arrives. * **APPEARANCE**: The customer requests a new card with a different appearance, for example changing the name printed on the card or changing the card's custom image. A new expiration date and CVV are assigned to the replacement card while the PAN remains the same. The old card remains active until the new card is activated or until the expiration date arrives. * **PRODUCT\_CHANGE**: The customer requests converting a card to a different program, specifically debit card to a smart card. A new expiration date and CVV are assigned to the replacement card while the PAN will change since it will be on a new BIN. The old card remains active until the new card is activated or until the expiration date arrives. * **PROGRAM\_CHANGE**: The customer requests converting a card to a different program, specifically debit card to a smart card. A new expiration date and CVV are assigned to the replacement card while the PAN remains the same. The old card remains active until the new card is activated or until the expiration date arrives. In all of these cases, the Synctera platform automatically terminates the old card when it is time for termination. Also, where relevant, Digital wallet tokens are updated automatically, i.e. cardholders to not need to add the new card to the wallet. If the card is already on-file with merchants, cardholders do not need to worry about updating their card-on-file as it is automatically updated. ## Cards API Objects The Cards API works with two primary objects. ### The Card Product Object A card product is a defined set of card features that you can offer to your customers. A card product may define charge limits, foreign transaction fees, reward programs, and other important agreements between you and a customer for card use. When your FinTech onboards with Synctera and works out an agreement with a sponsor bank, if you’re going to use cards, your agreement includes a set of defined card products you can offer to your customers. When we set you up in the Synctera platform, we create a set of Cards API objects, one for each of your card products. Each card product object contains: * The **card product ID**, unique to the card product * The **card product name**. * The **card product form**: whether it’s physical or virtual * **Active/inactive status**, whether the card product is still active or not. Inactive card products can’t be used to request card issuance. When you request a card issuance, you specify a card product by ID so that you and the card issuer know the terms under which the card is issued. ### The Card Object The card object is the Card API’s principal object. Each object defines and tracks a card from issuance request through activation, management, and eventual end of life. A card object has a set of attributes that vary depending on whether the card is virtual or physical. A physical card has to contain information about shipping such as address and shipping status, and for activation of a physical card such as the barcode used for validation. #### Common Attributes Physical and virtual card objects both have these common attributes: * **Card ID** specifies this card object. * **Creation time** specifies the date and time when this card was requested to be issued. * **Last modified time** specifies the date and time when this card object was last modified, whether modified by the integrator or the Synctera platform. * **Form** specifies whether the card is physical or virtual. * **Account, customer, and card product IDs** specify the customer, their account, and the card product associated with the card. * **Embossed name** is the exact name on the card: embossed in the card if physical, just associated with the card if virtual. * **Last four** provides the last four digits of the card’s PAN. * **Expiration month, year, and time** specify at least the standard month and year of expiration and may optionally specify a specific day and time. * **Network** specifies the credit card network that handles the card’s transactions, currently Mastercard. * **Reissue from, to, and reason** provide card reissue information if this is a reissued card: the ID of the card being reissued, the card ID of the replacement (this card), and a reason for the reissuance. * **Metadata** is an optional array of key-value pairs providing additional information about the card. * **Type** specifies whether this is a credit or debit card. It may currently only specify a debit card. * **Status** specifies multiple aspects of a card’s current status: * **Card status** specifies the card’s current stage of life. The platform may set this value as it detects card changes, such as when a card becomes activated. You may also set this status when you find it appropriate. * **Active**: The card is available for full use. * **Unactivated**: The card hasn’t been activated yet and can’t be used. * **Suspended**: The card is suspended and can’t be used again until returned to active status. * **Terminated**: The card may no longer be used. * **Status reason** specifies a code for a defined set of reasons why a card’s status changed. * **Memo** provides your FinTech the option to enter additional details about status change. #### Physical Card Attributes A physical card object has some additional attributes: * **Card fulfillment status** reports whether the card has been issued, ordered, rejected, reordered, or shipped. * **Shipping** provides information about how and where the card should be shipped: * **Address** provides the address to which the card was mailed. If not specified on the issuance request, this defaults to the customer’s shipping address. * **Care of line** is the name of the person who will receive the package on behalf of the recipient. This value is generally used when mailing the card to a location other than the customer’s shipping address. * **Is expedited fulfillment** requests expedited printing of the card by the card fulfillment vendor. Additional fees apply. * **Method** specifies the shipping method and whether or not it’s expedited. If this value is not provided, it defaults to LOCAL\_MAIL. Additional fees apply for all other methods. * **Recipient name** specifies who should receive the card, often used for signature purposes. If not provided, it defaults to the customer’s name. This isn’t the same as the entity specified as “care of,” which is just used as part of the address. * **Tracking number** provides a number used to track a card’s shipment through the carrier. * **Is PIN set** specifies whether the PIN has been set for the card or not. The Synctera platform receives information from the card issuer about shipping status and fills in attributes with received information so you can check on a card’s shipping status by looking at the card object. ## Endpoints The Cards API offers endpoints that handle different aspects of card creation and management. ### Card Products These endpoints provide card product information: * **List Card Products** returns an array of card product objects set up for you when your FinTech onboarded with Synctera. Each object provides a card product ID and card form with optional active/inactive status and card product name. * **Get Details About a Card Product** returns a card product object for a single card product. ### Card Creation These endpoints create an active card for a customer: * **Issue a Card** requests a card for a customer using one of the customer’s accounts and specifying a card product. If a request to this endpoint specifies that this is a card reissuance, the endpoint handles terminating the replaced card. * **Activate a Card** requests the card vendor to activate a physical card using the activation barcode provided by the customer. ### Card Management These endpoints manage a card once it’s issued: * **List Cards** returns an array of card objects representing cards you’ve issued. You can specify query parameters that include customer, account, embossed name, last four digits of the PAN, expiration date, card type, brand, form, card product, and the postal code of the user. Refer to [List Cards](/v2/reference/listcards) * **Get Card** returns a single card object specified by card ID so that you can examine card attributes. Refer to [Get Card](/v2/reference/getcard) * **Update Card** revises a card object’s attributes, limited to attributes that can change over the life of a card. This includes card status, status reason, and metadata stored in the memo attribute. Refer to [Update Card](/v2/reference/updatecard) * **List Card Changes** returns an array of any changes made to a card object’s card status or fulfillment status made either by you or by the Synctera platform. Each change in the array reports the type of change (card or fulfillment), how the change was submitted, optional memo metadata, both the old and new status (card or fulfillment), and the ID of the admin who made the change (if made in the Synctera admin system) and the time the change occurred. Refer to List Card Changes ### Data Security Through Widgets These endpoints provide tokens and connection information for Synctera’s PCI-compliant widgets: * **Get Card Widget URL** returns a URL used by the Synctera Activate Card and Set PIN widgets. * **Get a Client Token** returns a short-term token for use by the syntera.js client library to retrieve sensitive data for display. ## A Typical Card Workflow This workflow is an example of steps covering a card’s life from creation to deactivation. For this example, the card we work with is a physical debit card that activates through a barcode activation value. **Setup:** To create a card, you need a customer that has passed KYC verification and an account that belongs to the customer. ### Requesting Card Issuance 1. You offer a card product to a customer who you think is a promising card candidate. To review the card products available through your FinTech, request a list of them through a request to [List Card Products](/v2/reference/listcardproducts) and note the card product ID of the product you want to offer. 2. The customer signs up for your card product and accepts the card disclosure. Disclosure to the customer is generally handled as part of your account onboarding process, but in some cases may be a separate process. 3. You request a card issuance through [Issue a Card](/v2/reference/issuecard). You specify the customer, the account, the card product, a name to emboss on the card, and optionally provide shipping information for the new card. The endpoint returns the card object, including the card object ID. 4. To check on card issuance status, you regularly request [List Card Changes](/v2/reference/listchanges) to return the card change history of the card object where you can look for new changes. Each change reports shipping and card status changes, so you know when a card was ordered, issued, shipped, or even rejected so you can take action if necessary.
"Activate Card" Synctera Platform->>Card Vendor: Activate card Customer->>FinTech: Set PIN through widget FinTech->>Card Vendor: Widget sends PIN setting Card Vendor->>Card Vendor: Activate card Card Vendor->>Synctera Platform: Card is active Synctera Platform->>Synctera Platform: Card status: ACTIVE ``` ### Reissuing a Card 1. Your customer reports that they lost the card. 2. You request a card reissuance through [Issue a Card](/v2/reference/issuecard). You provide all the information you did when you issued the lost card, and also specify a reason for reissuance and the card ID of the lost card as the card being replaced. (Note that you can also use the Synctera dashboard to perform this task.) 3. The Synctera platform immediately terminates the lost card with the card vendor and sets the card’s status to TERMINATED. 4. The new card is issued and activated just as the lost card was, except for the PIN which is retained from the lost card. ```mermaid mermaid theme={"system"} %%{init: {"fontFamily": "sans-serif"}}%% sequenceDiagram Customer->>FinTech: I lost my card FinTech->>Synctera Platform: "Issue a Card"
to replace lost card Synctera Platform->>Card Vendor: Terminate card Card Vendor->>Card Vendor: Terminate card Synctera Platform->>Synctera Platform: Set card to "TERMINATED" Synctera Platform->>Card Vendor: Issue new card Card Vendor->>Customer: Issue new card with old PIN ``` ### Cancelling a Card 1. The customer cancels the card. 2. You use [Update Card](/v2/reference/updatecard) to change the card’s status to TERMINATED. (Note that you can also use the Synctera dashboard to perform this task.) 3. The Synctera platform notifies the card vendor of termination. 4. The card vendor terminates the card. ```mermaid mermaid theme={"system"} %%{init: {"fontFamily": "sans-serif"}}%% sequenceDiagram Customer->>FinTech: Cancel my card FinTech->>Synctera Platform: "Update Card" to
TERMINATED status Synctera Platform->>Card Vendor: Terminate card Card Vendor->>Card Vendor: Terminate card ``` # Plaid Core Exchange Source: https://docs.synctera.com/v2/docs/plaid-exchange-guide ## Plaid Core Exchange with Synctera Synctera has integrated with Plaid Core Exchange in our v1 API. Please refer to the [v1 guide](/v1/docs/plaid-exchange-guide) for details. # Synctera Platform Source: https://docs.synctera.com/v2/docs/platform-overview You’re a developer about to integrate the Synctera platform with your application. ## A Synctera Platform Overview for FinTechs Before you start, what is the Synctera platform anyway? What does it offer, and how do you work with it? ### The Synctera Platform in a Nutshell The Synctera platform is a comprehensive set of cloud-based financial services that brings three types of businesses together: * **FinTechs** that provide unique financial services to their customers * **Sponsor banks** that provide the necessary legal framework and financial resources to FinTechs to carry out FinTech business * **Service vendors** that team up with Synctera to provide fundamental financial services to FinTechs and sponsor banks.
PIN
Confirm PIN
PIN
Confirm PIN
**Incoming**: Synctera/Bank is RDFI
Whether it is marked as debit/credit is within the frame of reference of the institution receiving the ACH (RDFI). E.g. * Outgoing debit: “I am debiting your account” * Incoming credit: “You are crediting my account” More concretely:
**Outgoing debit**: Originated with Synctera’s ACH API, pulling money from an external account into the Synctera account.
Balance impact: Debit to external account, Credit to Synctera account
**Outgoing credit**: Originated with Synctera’s ACH API, pushing money out of the Synctera account into an external account.
Balance impact: Debit to Synctera account, Credit to external account
**Incoming credit**: Originated at another institution, pushing money from the external account into the Synctera account.
Balance Impact: Debit to external account, Credit to Synctera account
**Incoming debit**: Originated at another institution, pulling money from the Synctera account into the external account.
Balance Impact: Debit to Synctera account, Credit to external account. # We have a few inactive end-customers who would like their accounts closed, what is the process to close their accounts? Source: https://docs.synctera.com/docs/we-have-a-few-inactive-end-customers-who-would-like-their-accounts-closed-what-is-the-process-to-close-their-accounts In order to close an account successfully, you must ensure that the account balance is 0 dollars. To close an account within the Synctera console, go to the customers account and from there in the top right you will see an "Actions" button, click on that and a drop-down menu will pop-up which will give you the option to "close account". You can select that option and the account will be closed. Once the account has been closed, you will be billed one last time for that account only for the month the account was closed on. # We have new employees joining, how do we give them access to the Synctera Console? Source: https://docs.synctera.com/docs/we-have-new-employees-joining-how-do-we-give-them-access-to-the-synctera-console You should have an admin set-up internally within your team and that admin will have the ability to grant and change access for all members of your team. The admin can do this within the Synctera Console here: 1. [https://app.synctera.com/user-management/users](https://app.synctera.com/user-management/users). # We know that direct deposit is a type of ACH. Is there any benefit or difference between setting up direct deposit vs the payer executing an ACH push? Source: https://docs.synctera.com/docs/we-know-that-direct-deposit-is-a-type-of-ach-is-there-any-benefit-or-difference-between-setting-up-direct-deposit-vs-the-payer-executing-an-ach-push-ie-time-for-payment-to-arrive-costs-etc There is essentially no benefit to you. The benefit is for the end-customer or the payroll provider, by having a direct deposit agreement they are allowed to send recurring credits to the same account with customer authorization. The main key benefit is reliability, and also the funds via payroll are considered “safer” since the payroll companies take the money from the employer a few days in advance. A random push of money from an employer is considered more risky. # What are the common reasons why an end customer might be mistakenly flagged as fraudulent? Source: https://docs.synctera.com/docs/what-are-the-common-reasons-why-an-end-customer-might-be-mistakenly-flagged-as-fraudulent Transactions sometimes trigger a false positive if the end-customer attempts multiple transactions in a short period of time or spends outside of their normal activity (i.e. high dollar transactions, unusual merchants, high risk merchants, etc.). These fraud rules are in place to protect customers from unauthorized activity. End-customers can contact you to disclose the purpose of their transaction to further troubleshoot. This will allow you to pair with Ground Control and help the transaction get through. # What are the cutoff times for same-day ACH? Source: https://docs.synctera.com/docs/what-are-the-cutoff-times-for-same-day-ach You can see the cutoff times for same-day ACH in our guide here: [ach-guide](/docs/ach-guide) # What are the different types of statuses for an ACH transaction on the Synctera platform, and how do they relate to the transaction and the network? Source: https://docs.synctera.com/docs/what-are-the-different-types-of-statuses-for-an-ach-transaction-on-the-synctera-platform-and-how-do-they-relate-to-the-transaction-and-the-network There are two types of statuses regarding an ACH transaction: The **transaction status** and the **network status**. Both of these statuses are reflected in the Platform Transaction view. **Transaction status**: The status of the transaction itself. This can be generally understood as the status as it relates to the Synctera ledger. There are three transaction status types you might see in the Platform when viewing an ACH transaction: * **PENDING**: A pending transaction represents a "hold" or "authorization" for the movement of funds in an account. Pending transactions are used whenever we need to guarantee the availability of funds for any multi-step payment flow. The Account Balance includes the Posted Transactions, whereas Available Balance includes pending debits. This means Available Balance is what can actively be spent right now. * **POSTED**: Posted to the Synctera ledger and reflected in both Account Balance and Available Balance. Once a transaction is "posted", it is then considered immutable and cannot be changed. Any adjustments (such as a reversal, for example) would require the creation of a new transaction. * **DECLINED**: ACH transfer failed transaction checks (fraud limits, watchlist, etc) done while in pending transaction state or failed due to a technical issue. This is a final transaction status. **Network status**: The status of the ACH file itself as it relates to the network. The lifecycle of the file itself has a flow that is represented by the following statuses: * **INIT**: The state used in the ledger while Synctera performs transaction checks, prior to sending out the file to the network. The risk\_info field holds details from Synctera’s fraud service and the payload will return with the result of the checks. If approved, the next network status is PENDING. If declined, the next network status will be DECLINED. * **PENDING**: This means that the ACH file has passed the checks from INIT but has not been sent out to the network. * **COMPLETE**: The ACH file has been sent out to the network. This is a final network status. * **DECLINED**: ACH transfer failed transaction checks (fraud limits, watchlist, etc) done while in INIT network state. This is a final network status. # What are the possible account statuses and what do they mean? Source: https://docs.synctera.com/docs/what-are-the-possible-account-statuses-and-what-do-they-mean The list of account statuses and their descriptions can be found in our API reference here: [listaccounts](/v2/reference/listaccounts) # What are the possible errors I might get when attempting to issue a card for an end-customer? Source: https://docs.synctera.com/docs/what-are-the-possible-errors-i-might-get-when-attempting-to-issue-a-card-for-an-end-customer There are myriad of reasons. The list is always subject to change. In general, HTTP 400-499 are client side errors, that require you to remediate before reattempting the request. 500-599 constitutes server side errors, that can be retried later. # What are the processing times for ACH files? Source: https://docs.synctera.com/docs/what-are-the-processing-times-for-ach-files ACH files are sent during ACH Exchange Windows (https://www.frbservices.org/resources/resource-centers/same-day-ach/fedach-processing-schedule.html). Direct ACH payments typically take several business days to appear in the recipient's account. # What are the validations/verifications that checks are subjected to before they are approved? Source: https://docs.synctera.com/docs/what-are-the-validationsverifications-that-checks-are-subjected-to-before-they-are-approved The check standards are as follows : * Endorsement: "For mobile deposit at \[bank name]" and signed by account owner (if the signature is very clearly not the account owner, the check will not be accepted. Keep in mind we do not match signatures) * Date: \<180days * Picture: Is it clear? There are cases where the picture is not clear, but will still come to us. In that case, we will have to reject. * Made out to one party (not signed over) # What can cause an end customer account to go negative? Source: https://docs.synctera.com/docs/what-can-cause-an-end-customer-account-to-go-negative A force-post or charges that settle for a higher amount than authorized (e.g restaurant bills with a tip) can cause an account to go negative. # What formats are accepted for check deposits? Source: https://docs.synctera.com/docs/what-formats-are-accepted-for-check-deposits PNG, JPEG, and TIFF formats are supported. # What happens if an end customer's account goes into a negative balance and how does Synctera handle such situations? Source: https://docs.synctera.com/docs/what-happens-if-an-end-customers-account-goes-into-a-negative-balance-and-how-does-synctera-handle-such-situations When an account goes into a negative balance this can be due to few typical use cases. 1. When the settlement amount of a transaction is greater than the authorized amount e.g. force post or due to a late return 2. Timing issue when the effective date of a transaction is greater than the posted date of the transaction 3. Stand in Processing - allows for the completion of certain transactions when authorization from the service provider is unavailable 4. Fraud - such as when a customer pulls funds, spends the pulled funds, initiates a return with their external bank resulting in a negative balance For Scenario 1, Synctera will monitor account balances on a daily basis. On the day the negative balance is realized, Synctera will debit your Operational account and hold this money in an Allocated Reserve Suspense Account. We will hold this in suspense to allow you to do one of the following: * Work with the end customer to recover the funds * Determine if the account should be closed or frozen * You can choose to cover the cost If the funds are recovered from the end customer, you should notify Synctera and once the funds are received, Synctera will reverse the entry from the Reserve Suspense account back to the Operational Account. If the funds are unable to be recovered after 7 days\* and/or the account is closed or frozen, the Synctera team will then write this off as a loss against the Operational account. You should monitor your Operational account balance and ensure that it is funded in line with your contractual terms on a daily basis. If the Operational account remains in deficit for 7 days, Synctera will instruct an ACH pull from your Operational account with the Bank. However if the Operational balance falls below 75% it must be topped up within 24 hours. \*exceptions to timeframe may apply # What information is required for an end customer to allow their employer to enable/authorize direct deposit? Source: https://docs.synctera.com/docs/what-information-is-required-for-an-end-customer-to-allow-their-employer-to-enableauthorize-direct-deposit The end-customer needs to obtain a direct deposit form from your corresponding sponsor bank and send it to the employer. The direct deposit form must include: Name, Address, Bank name, Account number, Routing number and Signature # What is a contactless card? Source: https://docs.synctera.com/docs/what-is-a-contactless-card A contactless is any card that has the "Tap feature" enabled, allowing you to make purchases by simply tapping the card at the card terminal. # What is the difference between an authorization and pre-authorization? And what are their hold times? Source: https://docs.synctera.com/docs/what-is-the-difference-between-an-authorization-and-pre-authorization-and-what-are-their-hold-times A pre-authorization is typically used to reserve funds with a reasonable estimate of how much will be cleared. An authorization is when the amount is known. Pre-authorizations are used in situations like Automated Fuel Dispensers (AFD), hotel reservations, car rentals, etc. Authorizations are used to reserve funds for a purchase where the merchant does not capture right away, like buying something on amazon where you authorize the amount of the purchase, then it is captured when it ships. Pre-authorizations can be captured for up to 30 days according to MC network rules. For Authorization, it can be up to 7 days. In the absence of any additional messages from the merchant, the hold will automatically be released after 7 or 30 days depending on what type of hold it is. # What is the full list of information to include for each KYC case type? Source: https://docs.synctera.com/docs/what-is-the-full-list-of-information-to-include-for-each-kyc-case-type Full legal name as it appears on government documents (no nicknames, include all last names if you have multiple, etc.) A valid US address that includes: Street Address Apartment number (if applicable) City State Zip code A valid Social Security Number (SSN) A valid email address A valid phone number # What is the process to reverse a card transaction that has already been created? Source: https://docs.synctera.com/docs/what-is-the-process-to-reverse-a-card-transaction-that-has-already-been-created A posted transaction should be negated by either refunds by the merchant (end-customer takes it up with the merchant) or through a dispute. # What should I do if an end-customer has not received their card shipment in the expected timeframe? Source: https://docs.synctera.com/docs/what-should-i-do-if-an-end-customer-has-not-received-their-card-shipment-in-the-expected-timeframe We encourage you to pass the tracking number onto the end-customer so they can track where the package is. If there is an issue with delivery, you can reach out to Synctera support and we can follow-up with our partner, Arroweye, to check for any updates. # What should I do if an end-customer uploads incorrect external card information to the platform, and Tabapay declines eligibility for AFT/OCT? Source: https://docs.synctera.com/docs/what-should-i-do-if-an-end-customer-uploads-incorrect-external-card-information-to-the-platform-and-tabapay-declines-eligibility-for-aftoct You can delete the card and recreate it with correct info. # What should I do if I find out that an end customer couldn't complete a payment because he was flagged for fraudulent behaviour? Source: https://docs.synctera.com/docs/what-should-i-do-if-i-find-out-that-an-end-customer-couldnt-complete-a-payment-because-he-was-flagged-for-fraudolent-behaviour If an end-customer cannot make a payment, it could be for a number of reasons. If you are contacted about an end-customer unable to make a payment, you can review the Synctera console to determine if it was flagged for fraudulent behavior. If so, please verify the transaction with the end-customer. You can add this verification to the fraud case details, which our Ground Control team will then review. Once a case is marked as not-fraudulent, the end-customer will be able to retry the transaction for a limited period of time. It is important to not reveal why fraud rules get fired, including the amount/threshold. This is important as we do not want to enable fraudsters to bypass our system. # What should we do if our end-customer reports that our routing number is not recognized by a third party? Source: https://docs.synctera.com/docs/what-should-we-do-if-our-end-customer-reports-that-our-routing-number-is-not-recognized-by-a-third-party If a financial institution fails to acknowledge a routing number, it is most likely due to their validation system not utilizing the most recent edition of the Federal Reserve's bank routing directory. The instituion will need to update their records in such cases. The best way to get this routing number updated is by contacting the institution directly as their customer. We recommend that your end-customers use the following template to send over to the financial institutions: *Hi \[Institution],* *I’m attempting to link my bank account through your service, but I’m getting an error message of \[insert error message]*. *It seems like your routing number validation system does not recognize the routing number \[insert routing number here]*. *This routing number is valid according to the Federal Reserve's e-payments routing number [directory](https://www.frbservices.org/EPaymentsDirectory/)*. *Could you please help me escalate this to your banking operations team and get this routing number updated?* *Thank you,* *\[your name here]* # When an end customer's account is frozen/suspended, does that automatically freeze his/her card? Source: https://docs.synctera.com/docs/when-an-end-customers-account-is-frozensuspended-does-that-automatically-freeze-hisher-card It does not auto-suspend the card, but part of authorizing a transaction requires that the end-customer and account be in good standing. You should suspend cards when you wish to fully block all authorizations. # When an end customer's customer status is frozen, does that automatically freeze their accounts? Source: https://docs.synctera.com/docs/when-an-end-customers-customer-status-is-frozen-does-that-automatically-freeze-their-accounts Through the UI, if you freeze an end-customer, their accounts will also be frozen. Using the API you must make separate API calls to freeze the end-customer and each account. You can find more details on freezing accounts in our API guide here: [create-a-personal-customer](/docs/create-a-personal-customer#person-status-attributes) # Which types of transactions are subject to holds and how long do the holds last? Source: https://docs.synctera.com/docs/which-types-of-transactions-are-subject-to-holds-and-how-long-do-the-holds-last Outgoing debit ACHs have a 2 day hold on the funds that have been added to the account on Synctera's platform. Incoming checks have a configurable hold (both the amount of time until the hold expires and the amount of funds that are immediately released vs held are configurable per bank). # Why do ACH files get sent out sometimes even when the account has been frozen and the transaction is still in pending status? Source: https://docs.synctera.com/docs/why-do-ach-files-get-sent-out-sometimes-even-when-the-account-has-been-frozen-and-the-transaction-is-still-pending-status If the file has been sent to the network we are not able to then revoke it - in this case a return has to be issued. If the account is frozen prior to the file being sent out, then the transaction can be canceled, but if after, it would have to be handled as a return.If the file has been sent to the network we are not able to then revoke it - in this case a return has to be issued. If the account is frozen prior to the file being sent out, then the transaction can be canceled, but if after, it would have to be handled as a return. # Why do I sometimes not see a network status on ACH transactions? Source: https://docs.synctera.com/docs/why-do-i-sometimes-not-see-a-network-status-on-ach-transactions For Incoming Credits/Debits, a network status will not be trackable. This is because Synctera is not the originator of the transaction so we do not have visibility into the status as it pertains to the file’s state in the network. # Why was our wire returned? Source: https://docs.synctera.com/docs/why-was-our-wire-returned You can view the reason for why the wire was returned in the Synctera console under the specific wire transaction. There will a banner on the left side that will state the reason. # Why would an end customer's account balance be different than the available balance? Source: https://docs.synctera.com/docs/why-would-an-end-customers-account-balance-be-different-than-the-available-balance Account Balance is impacted only by posted transactions, but Available Balance is also impacted by pending transactions. Until a hold is fully posted, only the Available Balance is decreased by the amount of the hold. The Available Balance and the Account Balance can both be negative. # Simulate balance inquiry Source: https://docs.synctera.com/v2/reference/simulatebalanceinquiry openapi-v2.json post /cards/transaction_simulations/financial/balance_inquiry Simulate a `pindebit.balanceinquiry` type transaction by sending a POST request to the `/simulate/financial/balanceinquiry` endpoint. # Create a cash deposit transaction simulation for a barcode Source: https://docs.synctera.com/v2/reference/simulatebarcodesdeposits openapi-v1.json post /cash/transaction_simulations/barcodes/deposits > ⚠️ Sandbox Only > This simulation endpoint is only available in sandbox environments and will not be available in production. Create a cash deposit transaction simulation for a barcode # Retrieve Store Information for Barcode Simulation Source: https://docs.synctera.com/v2/reference/simulatebarcodesstores openapi-v1.json get /cash/transaction_simulations/barcodes/stores > ⚠️ Sandbox Only > This simulation endpoint is only available in sandbox environments and will not be available in production. Retrieve store information for a barcode transaction simulation # Simulate clearing or refund Source: https://docs.synctera.com/v2/reference/simulateclearing openapi-v2.json post /cards/transaction_simulations/clearing Simulate an `authorization.clearing` type transaction by including the `original_transaction_token` and `amount` in your request. To simulate a refund type transaction, set the `is_refund` field to true. # Simulate a network dispute action Source: https://docs.synctera.com/v2/reference/simulatedisputeaction openapi-v2.json post /disputes/simulations/{dispute_id}/actions > 🚧 Beta > This is a Beta endpoint. Feedback from the community is welcome. Any breaking changes to this endpoint will be pre-announced. This endpoint is intended for use only in the testing environment to simulate a network action on a dispute. # Simulate financial Source: https://docs.synctera.com/v2/reference/simulatefinancial openapi-v2.json post /cards/transaction_simulations/financial A "financial" is a transaction message class that includes ATM transactions, PIN-debit transactions, and balance inquiries. Simulate a `pindebit` type transaction by including the `card_token` and `amount` in your request. # Simulate financial advice Source: https://docs.synctera.com/v2/reference/simulatefinancialadvice openapi-v2.json post /cards/transaction_simulations/financial/advice Simulate a financial advice by including the `original_transaction_token` and other authorization details in JSON format in the body of the request. # Simulate L2l3 Source: https://docs.synctera.com/v2/reference/simulatel2l3 openapi-v2.json post /cards/transaction_simulations/clearing/l2l3 > 🚧 Alpha > This is a Alpha endpoint. Feedback from the community is welcome. We may make breaking changes to this endpoint. Simulate a l2l3 type transaction by including the original_transaction_id and enhanced data in your request. L2L3 events enhance the data of a transaction with the `l2l3` details from your request. # Simulate OCT Source: https://docs.synctera.com/v2/reference/simulateoriginalcredit openapi-v2.json post /cards/transaction_simulations/financial/original_credit This Original Credit Transaction (OCT) enables the cardholder to receive funds on the specified card from an external source via the card network. Use this endpoint to simulate a transaction that is similar to a wire transfer and not linked to any purchase. Simulate an OCT by including the `card_token`, `amount`, `mid`, and `type` in your request. # Simulate reversal Source: https://docs.synctera.com/v2/reference/simulatereversal openapi-v2.json post /cards/transaction_simulations/reversal A reversal releases the hold that was placed on account funds by an authorization, thus returning the funds to the account. Simulate an `authorization.reversal` type transaction by including the `original_transaction_token` and `amount` in your request. # Simulate ATM withdrawal Source: https://docs.synctera.com/v2/reference/simulatewithdrawal openapi-v2.json post /cards/transaction_simulations/financial/withdrawal Simulate a `pindebit.atm.withdrawal` type transaction by including the `card_token` and `amount` in your request. # Account linking Source: https://docs.synctera.com/docs/account-linking-products Verify account ownership, identity and account balance when funding new accounts ## Synctera External Account Verification Before funding a new FinTech account via an electronic ACH payment, National Automated Clearing House Association (NACHA) rules require that accounts must be validated for ownership and use prior to processing the debit transaction. Synctera External Account Verification makes it easy for FinTechs to verify external accounts and comply with NACHA rules. ### Benefits **Increase conversion rates:** A seamless experience embedded directly within your app’s flow makes it easy for customers to instantly verify the account **Full visibility:** Track the verification status and view the external accounts customers used for funding **Reduce fraud:** Verify account ownership and identity for all external accounts as part of the customer signup and initial funding process **Remain compliant:** Streamline NACHA compliance to ensure ongoing access to the ACH payment network **Reduce payment errors:** Prevent misdirected and failed payments by ensuring payments are set up correctly and the external account has sufficient funds ### How it works With Synctera External Account Verification, the verification process is streamlined, automating the sequence of steps required to remain compliant and allowing you to easily track the verification status. 1. Validate the external account exists and can be used for ACH payments 2. To help reduce fraud, verify that the account owner information matches the information on file for the customer (if using [Synctera External Account Verification - Identity](/docs/account-linking-products#synctera-external-account-verification-identity)) 3. Confirm that the external account has sufficient funds 4. Create a record of customer information, external funding source, and proof of verification 5. Enforce mandatory re-linking if users update password or add multi-factor authentication criteria ## Synctera External Account Verification - Identity **Use account owner information for linked external accounts to verify customer identities** When you allow your customers to fund their accounts with you from external sources, you will want to take steps to verify that the customer actually owns the external account, and to verify that they are not using a fraudulent identity with you. Synctera External Account Verification - Identity can help prevent fraud and reduce account takeovers by comparing account owner information for linked external accounts to the information the customer gives you. It can help reduce failed, fraudulent, or invalid ACH transfers to and from an external account. In cases where fraud does occur, the account owner information provides an audit trail. NACHA recommends including the external account holder name in your ACH file to help reduce returns due to incorrectly entered account numbers. In cases when an ACH is sent to an external account for which the account number was incorrectly entered, the receiving bank will be able to reduce delays in crediting or debiting the account by using the customer name to match the transaction. ### Benefits * Reduce fraud and help prevent account takeovers: identity data can be used to help prevent an account takeover (ATO) or other transaction fraud, either during onboarding or when the source of funds is switched * Help determine when secondary security features like text message verification should be triggered Example of using Synctera External Account Verification - Identity to trigger secondary security features If a user tries to link an external account but the identity information for that account doesn't match what the user has provided you, you can send a text message to the phone number tied to the external account, or send an email to the address tied to the external account. This helps you confirm it's really the account owner linking the account, and not someone who has stolen their credentials. * Use to personalize forms for onboarding: auto-fill forms with identity data when users link their bank account * Provide a seamless customer experience and help customers link their accounts and start transacting with you faster ### Key features * Performs a check to get the name(s), email(s), address(es), and phone number(s) of the account owner of an external account, and compares the data to what is in the Synctera system in real time * Cannot be used on external accounts verified through microdeposits ## Synctera External Account Transactions **Access detailed transaction history for external accounts** Get up to 24 months of transaction history for external accounts. At your discretion, Synctera partners with either Finicity or Plaid to provide this product. ### Benefits Helps to deliver a seamless in-app experience. Allows your customers to monitor their external bank accounts without leaving your app. Allows you to support personal financial management tools. Allows you to understand customer spending patterns and mitigate risk. ### Key features For ongoing transaction history updates, Finicity updates this information nightly. Plaid updates it 4-6 times per day. Plaid also supports on-demand transaction history refreshes. A user can refresh their transaction history to see if the transaction went through and is appearing in their history. Finicity also allows you to retrieve up to 24 months of historical statements for an external account in PDF format. Use this functionality to verify length of account history, historical balances, and account ownership. Cannot be used on external accounts verified through microdeposits. # Account management Source: https://docs.synctera.com/docs/account-management-products Our proprietary, flexible ledger serves as the operating infrastructure and single source of truth for your customer, account, and transaction data ## Synctera Ledger As the single source of truth, a ledger is a fundamental component of the technology stack for your bank-supported financial product or FinTech app. Most banks and FinTechs manage their accounting processes on inflexible banking systems or basic accounting programs—or they may not have a ledger at all. As a result, related processes like reconciliation can be highly manual and time-consuming. Building a ledger from scratch is complex and can take upwards of a year to complete, while out-of-the-box solutions can be expensive and may require customization. Designed specifically to for bank-supported financial products or FinTech apps, Synctera Ledger is a reliable, flexible, cost- effective alternative, serving as the operating infrastructure and book of record for customer, account, and transaction data. ### Benefits **No core integration required:** Our lightweight platform removes the complexity and costs associated with integrating into the bank’s core system **Complete transparency:** You and your bank partner can gain real-time visibility into your transactions and track the performance of the product(s) they are supporting **Easy reconciliation:** Access transaction information and automate workflows to simplify daily reconciliation processes **Cost-effective:** Compared to other options in the market, we offer the enterprise-grade capabilities that you need at an attractive price point **Accelerate time to market:** Get up and running quickly with easy API integration and system configuration **Ensure the health of your business:** Track your P\&L and account balances to better understand and report on your current position **Streamline operations:** Enable onboarding, support, and operations teams with the data they need to solve issues, serve customers, and reduce manual processes **Flexible:** Build your user interface flow without having to worry about back-end system orchestration ### Key features **Account creation:** Open customer accounts using a template, including valid account and routing numbers that are recognized by other banks and networks **FinTech ledger positions:** Track, display, and post balances across the lead ledger, sub-ledger, and general ledger **Statements:** Provide required data to generate account statements **Partner maintenance:** Define and maintain the relationship with your partner bank, including account setup **Transaction types:** Define transaction types to be posted against the ledger account, including ACH, P2P, internal transfers, and card transactions **Overdraft limits:** Define, assign and track overdraft limits at the customer or account level **Fees and pricing:** Charge fees and calculate interest **Virtual accounts:** Create virtual accounts to support various use cases, such as budgeting **Alerts:** Configure customer notifications for a range of ledger-related activities **Product templates:** Define and configure the features and constraints of a base product **Account lifecycle management:** Change, freeze, and close customer accounts, as required **Account balances:** Track debits and credits and calculate account balances **Operational account management:** Manage your operational account details **Reporting:** Track product health and other key operational metrics **Always-on data:** Engage in real-time with no batch windows, including next-day analytics and AML transaction monitoring ## Synctera Transaction Data Enhancement **Cleanse and enrich transaction data to give you and your customers better understanding and insights** Raw transaction data - such as merchant data for card transactions - is often incomplete and hard to understand. Synctera Transaction Data Enhancement cleanses and enriches financial transaction data to help your customers better understand and manage their spending. It also allows you to glean more customer insights from transaction data. ### Benefits **Enhance customer experience:** Provide detailed, easy to understand transaction data to your customers so that they can quickly see what they purchased, when, and from where. Use classification categories to deliver relevant insights to your customers and power tools that allow them to better assess and manage their spending. **Gain customer insights:** Get a clear view of your customer's financial behaviors, and learn where and how they spend and manage their finances. **Inform marketing strategy:** Develop accurate customer segments and profiles, identify new areas of investment, and engage customers with relevant products and services. ### Key features * Supplements data from your card processor * Uses machine learning technologies and thousands of custom rules to clean and categorize transaction data, translating transactions and assigning relevant merchant data such as logos and location # Account Agreements and Disclosures Source: https://docs.synctera.com/docs/accountagreementsanddisclosures This guide captures the requirements for account agreements and disclosures. **Note your Sponsor Bank may have additional bank-specific requirements to comply with its bank policy. These will be covered during your implementation and final approval. *The below sections are intended as guidance and not legal advice.*** As with any program that offers banking products or services, Synctera’s bank partners require that certain disclosures and agreements be made available, and consented to, during the customer acquisition process. There are a few principles that must be followed for how these disclosures are presented and how a customer consents to them. Primarily, disclosures and agreements must be - * Clearly and conspicuously available, providing the customer a reasonable opportunity to review; * In a form the customer may keep; * In a form in which the customer is able to indicate clear and unequivocal acceptance. ## Consent to Electronic Disclosures (E-Sign) This establishes your ability to provide all disclosures and account information electronically through your platform. In terms of the overall flow of account opening, this should be the first disclosure a consumer views and consents to before moving forward in the customer acquisition process. * A customer must consent to this disclosure before you can share and receive consent for other disclosures with them electronically (such as the account agreement) * Synctera has provided a template for E-Sign consent ## Privacy At account opening, businesses offering financial products must provide consumers with a Privacy Notice explaining their privacy policies and practices. **Privacy Notices must be re-sent at least annually to consumers.** * This includes what information is collected, how it is used and shared, and how it is protected, as well as a statement of rights to opt out of certain types of sharing * Privacy disclosures must be clear, conspicuous, and in a language an average person can readily understand. * Synctera has provided several templates, which fintechs can select depending on their privacy practices. * Sponsor Bank Privacy Notice must also be included ## Terms of Service These are the general terms of service that apply to your platform. * This agreement is between your company and the customer, and it should not include banking terms and conditions. ## Deposit Account Agreement These terms govern the use of your deposit product * This agreement is between the sponsor bank and your end customer * Deposit account agreements should establish a contractual relationship between your bank and your end customer to open up a checking / savings account * Synctera or Sponsor Bank provides a template for deposit agreements * Interest-bearing products must also include a disclosure of the effective interest rate (particularly if it will change) ## Other Product Agreements Other product terms and conditions or agreements may exist depending on the product and services being offered. As an example, this may include a cardholder agreement or a secured deposit account agreement. ## Patriot Act KYC Notice This is a notice that explains the Sponsor Bank’s obligations under the USA Patriot Act. * This notice is required for consumer-oriented products and services, i.e. not any type of business account although separate language may be provided to business accounts. * Consent is not needed, but this notice should be displayed when gathering customer data for verification. # Accounts Source: https://docs.synctera.com/docs/accounts-for-fintechs The Accounts tab of the Synctera Console allows you to view all of your customers' accounts in one place, and to search among your customers' accounts. ## Overview Your operations team can use the Accounts tab to help them address customer service inquiries and fraud/AML investigations. You can use the [Admin tab](/docs/permissions) to add/remove users from the list of those who can view/edit accounts. ## Accounts tab home page Search for accounts by account number, customer first name, or customer last name. Filter accounts by account purpose or status. Click on an individual account to view more information. ## Information displayed after clicking on an individual account Account type: Saving, Checking, Line of Credit * For a Product that has fees, the types of fees can be: * Monthly, Annual, ATM\_Withdrawal, Overdraft, ACH, Wire * Currently Fintech is calculating Fees and using Synctera to post it. * For a product that has Interest rates: * You can mention Interest rate * Interest rate history is maintained so that based on the interest rate for a particular period, the respective interest rate will be calculated daily and applied monthly Account status Account balance Available balance Account owner Creation date Employees who have edit access to account data can: * Open an account for the user - by emulating the FinTech if the user has the permissions to do so * Change the overdraft limit on an account * Freeze / Unfreeze an account * Send funds to another account if the user has passed KYC * Receive funds from another account * Initiate ACH external transfer if the user has passed KYC Employees who have view access to account data can perform following activities specific to External accounts: * View the external accounts of a customer Employees who have edit access to account data can perform following activities specific to External accounts: * Link an external account to the user by providing Routing Number and other details of the account. ### Transactions sub-tab View the most recent pending, posted, and declined transactions. Click on an individual transaction to view more information about that transaction. ### Cards sub-tab View the cards that have been issued to the account. You can issue a new physical/virtual card or re-issue a card. ### Details sub-tab Account purpose Bank ID Partner ID Bank routing number ### Spend monitoring sub-tab The Spend Monitoring feature is described [here](/docs/spend-monitoring). # ACH transaction disputes Source: https://docs.synctera.com/docs/ach-transaction-dispute-cases This guide explains the ACH dispute process, how to initiate, manage and monitor until the dispute is resolved. \[Documentation coming soon] # Adding Sole Proprietorship Source: https://docs.synctera.com/docs/adding-sole-proprietorship This document is intended to list the general requirements from a product and risk and compliance perspective needed to begin supporting sole proprietors in your existing Business onboarding and accounts program with Synctera. ## Adding Sole Proprietorship to a Business Use Case ### Product If a user is using their account for commercial purposes, they are considered a Sole Proprietor. In this case they would be added as a person to the platform, using the [Create Person API](/v2/reference/createperson). Then they would add their business, with [Create Business](/v2/reference/createbusiness), and indicate that the **structure** is a **sole\_proprietorship**, and leave EIN empty ([unless the sole proprietorship has employees - see Risk and Compliance section](/docs/adding-sole-proprietorship#risk-and-compliance)). Then, the ownership of the business would have to be defined using the [Relationship API](/v2/reference/createrelationship) (Beneficial Owner Of).
NOTE: Ground to Canada and Mexico only! | \$15.00 | Yes | | INTERNATIONAL\_PRIORITY | USPS Priority International | \$43.55 | Yes | \*The average charges are based on individual card shipping (not bulk) **Exceptions:** * Other shipping methods may be supported, for example, FinTech may have a shipping method set as a default on the card product with the fulfillment provider * If the shipping method sent in the issuance request does not match the destination, the fulfillment provider’s system will convert it - for example, if USPS Priority is sent for Canada, the system will switch it to USPS Priority International #### Bulk shipping Synctera also supports bulk orders / shipping. FinTechs can use this option to reduce shipping costs for applicable use cases. Supported use cases: * Shipping of multiple cards to a **single** location where the distribution or last mile delivery is handled by a specific distributor/carrier: * This use case is supported through default product settings at the fulfillment provider level - cards are sent in bulk, but **packaged and addressed individually** * FinTech can contact their Synctera representative for this option * Shipping of multiple cards to **more than one** locations: * This use case is supported through [Synctera Bulk Order APIs](/v1/docs/bulk-card-orders) * Cards are sent in bulk, but **NOT packaged and addressed individually**
Jacklyn & Jacqueline
James & Jimmy
Bank, Banque, & Banca
Automovil & Automobile
Vladimir Putin & Владимир Владимирович Путин | | removedPersonalTitle | Partial name match due to the removal of an honorary title within the input name such as (Dr, Mr, Queen, etc.). | Dr Miles & Kevin Miles | | nameInitialized | Name match based on initials | H.B. Hawala & Haji Basir Hawala | | namePhonetic | Name match based on phonetic similarity | Renault & Reneaux | | akaExact | Exact alias match | Joaquin Guzman & Chapo Loera | | akaFuzzy | Fuzzy alias match | Joaquin Guzman & Charo Loeta | | akaEquivalent | Alias match based on the same alias meaning | Peter Tobin & Pat McLaughlin | | akaPhonetic | Alias name match based on phonetic similarity | Ibrahim Anis & Abraham Anees | | dobExact | DOB matches year, month, and day. | 1988-02-23 & 1988-02-23 | | dobFuzzy | DOB is within one year (+/-) from the entered DOB. | 1988-02-23 & 1987-02-24
1988-02-23 & 1987
1988-02-23 & 1988-06-14
1988-02-23 & 1989-02-22 | | dobNotOnRecord | The source does not contain a DOB for the matched entity | | ## Reviewing and decisioning cases ### Mark Case in Review This allows a user to move the case out of the New state so that it is clear to other case reviewers that the case has been initially viewed and is actively under review, even if a final decision is yet to be made. This can be useful in differentiating between new cases that have just been opened and cases that have had a first look or review and are awaiting further input or information before making a final decision. ### Confirm Match This closes the case and marks the watchlist hit as a valid match. Once the hit is investigated and confirmed, this is the action to take to verify the watchlist hit as valid. ### Mark as Not Match This closes the case and marks the watchlist hit as not a match. This may be because the customer shares a similar name and other information with the person actually on the list, but is not in fact the same person. If the hit has been investigated and confirmed as not being for the same person, this is the action to take to mark the match as not valid. ### Reject Customer’s KYC This will change the customer KYC status from its current status into ‘REJECTED’. This should likely be done for any watchlist hit that will be marked as a confirmed match. Once this action is taken the user will not longer be able to transact or open new accounts, and will appear in the system with a KYC status of ‘REJECTED’ meaning they are not a customer that business should be done with. ### Freeze Customer and Related Accounts This will change the customer status and their related account status(es) to ‘FROZEN’ meaning the customer cannot perform any actions and the account(s) cannot perform any transactions. Take this action when confirming the watchlist hit as a match and deciding to no longer do business with the customer and to not allow them to move money on the platform or perform other actions.
**Tasks** will auto scroll you to the corresponding section and task of the Workspace.
**Company info** loads the Admin pages where you save and manage the details of your FinTech and organization. | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ### How to generate an API key for the various environments 1. Make sure you're on the environment for which you want an API key. 2. If your login has ADMINISTRATOR privileges, you will see a link on the bottom left titled "ACCOUNT ADMIN". 3. Selecting the link loads the Admin panel where you can proceed to the Developer Tools left nav item. 4. Here you'll see the API Keys link where you can issue and revoke API keys for the current environment. About API keys Once generated, be sure to capture the unique API key as you won't be able to view it again after dismissing the overlay. ***How to navigate to your API key page*** # Payments Source: https://docs.synctera.com/docs/payments-products Simple, reliable money movement ## Synctera ACH With over 29.1 billion payments last year, the [Automated Clearing House (ACH)](https://www.nacha.org/content/ach-network-volume-and-value-statistics) network is the primary way money moves electronically through the U.S. banking system. With Synctera ACH, your customers can use ACH transfers to fund their accounts, pay bills, and move money. Synctera ACH seamlessly enables your bank partner to manage and execute same-day and non-same-day ACH transfers on behalf of your customers. ### Benefits **Accelerate time to market:** Get your ACH payment program up and running quickly. **Seamless user experience:** The powerful Synctera interface makes ACH payments a breeze. **Complete transparency:** With near real-time visibility into the ACH process, your bank partner can understand your performance and the impact on their balance sheet. **Manage risk:** Enhance fraud controls and ensure outgoing payment volumes align with your bank partner’s risk tolerance. **Streamline operations:** Ensure transactions are flowing correctly to the general ledger and enable support teams to effectively troubleshoot customer inquiries according to NACHA rules (NACHA governs the ACH network). ### Key features **Incoming ACH processing:** Your bank partner receives incoming ACH files that are sent to the Synctera platform to process credits and debits for your customer accounts. **Returns:** Execute returns for ACH payments that fail to be processed by the external bank (e.g., non-sufficient funds, invalid account number, payment stopped, account frozen or closed). **Reversals:** Process incoming payment reversals. **Exception handling:** Troubleshoot payments that cannot be processed and manually resolve these items. **Outgoing ACH processing\*:** Initiate an API call to send money to external accounts and debit customer accounts. With Synctera, you avoid the complexity of having to create an ACH file in NACHA format; instead, only an API call is required. **Account validation:** As a mandatory network compliance requirement, ensure accounts are valid, open, in good standing and that funds are available prior to execution. **Modify/cancel payments:** Review, modify or cancel pending outgoing ACH payments prior to processing. **Pre-scheduled payments:** Create ACH instructions up to three months in advance of the planned execution date. **Recurring payments:** Set up recurring ACH payments on a daily, weekly or monthly basis. **Settlement account:** Create an ACH settlement account to track ACH debits and credits for later settlement. **Partial holds:** If you choose to use ACH for account funding, you can create partial holds for a percentage of the ACH transaction. A percentage of the total transaction amount is released in real time so your customers can use the partially released amount immediately. This feature helps drive customer activation and engagement. **Transaction descriptions for transfers to external accounts:** You can add a transaction description for ACH transfers that go to external accounts. This allows your customers to easily understand why the ACH transfer occurred. It’s particularly useful for transfers that happen automatically (e.g. if your financial product or FinTech app automatically rounds up transactions and then moves the rounded up amount to savings). \*Synctera “Lead” Ledger is required to execute incoming/outgoing ACH transactions. ### How it works #### Incoming ACH payments 1. At the end of each day, your bank partner securely transfers a file with incoming ACH transactions to Synctera. 2. Synctera automatically validates and converts the incoming ACH file to the required format. 3. Validated payment instructions are processed and posted to Synctera Ledger. 4. Your customer accounts are credited and debited with the correct amount. #### Outgoing ACH payments 1. Outgoing ACH payment instructions are validated automatically and posted to Synctera Ledger. 2. Outgoing payment instructions are converted to the outgoing ACH payment file. 3. Several times a day, Synctera securely transfers the outgoing ACH payment file to the bank partner to be sent to the NACHA network. ## Synctera Wire **Give your retail or business customers the ability to make domestic and international high-value transfers in near real time.** Wire transfers are direct point-to-point transfers between any two financial institutions. They’re typically used for higher-value items like property purchases or for settling large institutional transactions. Wire transfers clear immediately. Synctera provides the ability for your customers to send domestic and international wire transfers from their accounts and receive domestic and international wire transfers into their accounts. ### Benefits * Create stickier customer relationships and boost customer lifetime value with your business and high-net-worth retail customers by allowing them to transact via their preferred payment method * Create a new revenue stream by charging a fee, or provide free wire transfers to boost engagement with your other services * Enable cross-border payments for customers ### Key features * Domestic transfers are made via the Fedwire system and are processed by Synctera * Incoming and outgoing wire transfers clear immediately, making them appropriate for time-sensitive transactions * Synctera supports domestic and international wire transfers ## Synctera Remote Check Deposit **Allow your retail and business customers to deposit paper checks without going to a branch or ATM** Paper checks may be declining in popularity as a payment method, but your retail customers may still receive them from time to time, and business customers like doctors and lawyers may receive them quite often. Synctera Remote Check Deposit allows your customers to deposit these checks into their accounts without visiting a branch or ATM. ### Benefits * Allow your customers who receive checks to conveniently deposit and access their funds ### Key features * Your customers capture and upload images of their checks using their mobile phone, tablet, or computer * Customers' funds are generally available between one and seven days from initial deposit, according to your bank partner’s Funds Availability Schedule ### How it works * Using a mobile phone, tablet, or computer, your customer captures images of his/her check and uploads it to your app * You push the images and information to Synctera via API * Synctera sends the image to our Remote Check Deposit provider * Synctera's Remote Check Deposit provider validates the check using optical character resolution (OCR) and returns the outcome to Synctera * If the check is validated, Synctera adds the check deposit to Synctera Ledger * After end of day/cutoff time, Synctera's Remote Check Deposit provider generates anImage Cash Letter (ICL) file and sends it to the Synctera SFTP * Synctera sends the ICL file to your bank partner via SFTP * Your bank partner sends the ICL file to the Fed ## Synctera Fraud **Defend against fraudsters** For companies offering financial products and services, fraud is an unfortunate reality. Fraud—if not managed with proper oversight and controls—can have a significant impact on your bottom line, as fraud losses are your (not your bank partner's) sole responsibility. Synctera Fraud provides FinTechs with a scalable fraud program. Seamlessly integrated with the Synctera platform, Synctera Fraud can be launched quickly and easily, keeping you safe from fraudsters as you scale. ### Benefits **Reduce fraud and remain compliant:** Avoid financial risk and protect your business by identifying and preventing fraudulent events **Increase operational efficiency:** Automate workflows and concentrate resources only on those events flagged for review or rejection ### Key features **Configurable rules and risk models:** Build monitoring rules that align with the risk appetites of you and your bank partner. Create customer risk ratings to enhance accuracy. **Real-time monitoring:** Monitor transactions and money movement in real time with relevant customer information at your fingertips, including KYC outcomes. **Pre-integrated:** Your scalable fraud program works seamlessly with all of Synctera’s regulatory and compliance services. **Proof of compliance:** Track, investigate, and resolve events flagged for review or rejection. Use audit trails and other information to prove compliance with BSA/AML regulations. **Data-driven insights:** Understand overall fraud cases, including opened, current status, and time to close. Identify trends and adjust the program to minimize risk. ### How it works 1. You and your bank partner work with Synctera to implement and configure Synctera Fraud. Rules for event monitoring are configurable by you and your bank partner to address regulations and risk parameters. 2. Once activated, Synctera sends real-time events and customer information for analysis to our fraud partner. 3. Based on pre-configured rules and risk models, each event is permitted or flagged for review or rejection. 4. A case is created within Synctera Cases for each event that is under review or rejected. 5. You investigate and resolve each case, updating customer and account status through Synctera Cases. # Permissions Source: https://docs.synctera.com/docs/permissions ## Permissions demo ## Key concepts Synctera has the following concepts: * **Customers** - Customers of the FinTech that uses Synctera. * **Users** - Employees of the FinTech that uses Synctera. Employees use the Synctera Console to keep track of / manage their customers and their details. ## ## Roles available in the Synctera Console | Role | Description | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Executive | Users with this role have access to view customer, analytics and team data. Users with this role do not have access to view transactions or reconciliation. | | Administrator | Users with this role have access to invite users, administer user accounts, manage notifications, and change account settings. Users with this role do not have access to view customers, accounts, transactions and general user data. | | Operations | Users with this role have access to customer data including accounts and transactions to help resolve customer issues | | Operations Manager | Users with this role have access to customer data and team data | | Case Operations | Users with this role can manage cases and access data needed for case work, including customers, accounts and transactions. Users with this role do not have access to view team data. | | Card Image Reviewer | Users with this role can approve or reject images for custom cards | | Profile Viewer | Users with this role can view FinTech profile information | | Profile Editor | Users with this role can edit FinTech profile information | Each role comes with a set of permissions. The default roles mentioned above cannot be edited / deleted. You also cannot change permissions for default roles. However you can create new roles specific to your FinTech and you can set permissions based on whatever your needs are. Each of these permissions come with View / Edit access. Depending on what permissions are set for the role that the user has, the user will be able to view / edit the respective data of the customer. ## Available permissions | Permission | Description | Other recommended permissions | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Accounts | Account data can be viewed / edited with this permission | Customers / Cards / Sub-ledger | | Admin | Roles with view / edit access to this permission can create API Keys | | | Card Image Reviews | Roles with view / edit access to this permission can view / review / approve the Card Images of the customer | Cases / Cards / Customers | | Cards | Roles with view / edit access to this permission can issue card / activate a card / view card details of the customer | Customers / Cases / Accounts | | Cases | Roles with view / edit access to this permission can act on all types of cases. For Card image review, the user has to have that specific permission along with cases | Customers / Cases / Accounts/ Cards | | Customers | Roles with view / edit access to this permission can view / edit the Customer data | Cases / Accounts/ Cards If the user needs to see transactions, also give Sub-ledger | | Sub Ledger | Roles with view / edit access to this permission can view Transaction data of the customer, perform Reconciliation, or initiate an ACH transaction for the user. | | | Users | Roles with view / edit access to this permission can add users to the Consoleor assign permissions to users. | | | Profile | Roles with view / edit access to this permission can view / edit the Fintech Profile data. | | | General Ledger | Internal to Synctera. You shouldn’t need to use this permission. | | | Notifications | Internal to Synctera. We do not recommend you use this. | | | Waitlists | Internal to Synctera. You shouldn’t need to use this permission | | | | | | # Platform features Source: https://docs.synctera.com/docs/platform-features-fintechs To prevent fraud, Synctera supports the ability to ban identities on our platform. If an identity has been confirmed to be associated with fraud, Synctera Console users can choose to ban that identity with enforcement based on tenant access. ## Banned identities Banning an identity will prevent money movement for all created personal customers matching that identity. Any new personal customers with matching identity information will also enter a banned state, preventing any actions such as KYC that might cause you to incur fees. For accounts associated with banned customers, your operations team should zero out the balance in a suspense account and close the account. ## Restricted accounts and applications FinTechs that want to review and approve an application prior to opening an account can now use Restricted Accounts. With the restricted account flow, a customer submits an application, an operations team member reviews the application in the Synctera Console, and an account is created upon approval of the application. ## Scheduled payments Synctera can manage scheduled payments on your behalf. Customers may want to automatically move money into savings or to automatically send money for a mortgage payment, for example. You can define the expected schedule via API. If necessary, Synctera will recalculate based on business days and automatically initiate the payment. ## Spend controls Synctera Spend Controls provide you with a way to control spend on **account-level** through creation of rules that monitor the flow of funds to or from the account. Spend controls can for example be used to prevent fraud / unauthorized spending on the account or to support budgeting and financial goals. For more details on how to manage spend controls through the Synctera Console, see [this guide](/docs/spend-monitoring). For documentation on the Spend Control API, see the [API Guide](/docs/spend-controls-guide) and [API Reference](/v2/reference/listspendcontrols). ## Statement generation The [Statements API](/docs/statements-guide) allows you to retrieve the transactional information and disclosures needed to generate printable account statements for your customers. # Post-Launch Support Source: https://docs.synctera.com/docs/post-launch-support
Subtypes can indicate a specific use case as defined for the program (e.g. the internal transfer subtype `peer_to_peer` indicates a P2P payment from one customer to another), or can be system generated based on the direction or action taken (e.g. cards subtype `atm_withdrawal` or ACH `incoming_credit`). For more information ACH subtypes, read our FAQ page [here](https://app.mintlify.com/synctera/synctera/~/aa507287-8bdb-4614-95de-149dd26d2ddc). **Top Navigation Options:**
Is it ok with the bank if we use the FinTech company name? | | | 5 | Company identification | | Identical to the 'Immediate origin' used in File Header | | | 7 | Company Entry Description | | Description of the transaction.This may be Printed on the recipient’s bank statement by the Receiving Financial Institution. (i.e. Payroll)
Any specific information that the bank would like to enter? Otherwise we'll leave it up to the FinTech | | | 12 | Originating Financial institution | | We will enter your FI's routing number | | ## Exhibit B ### Information needed to establish cutoff and exchange times | | | | --------------------------------------- | ---------------- | | What is the end-of-day processing time? | Time / Time Zone | | | | | ------------------------- | ---------------- | | ACH Incoming File | Time | | Cutoff | Time / Time Zone | | ACH Outgoing File | | | Same-Day ACH Early Cutoff | Time / Time Zone | | Same-Day ACH Last Cutoff | Time / Time Zone | | Standard ACH Cutoff | Time / Time Zone | | Bank Holidays | Dates | ## Exhibit C ### Information needed to set up SFTP connection to process NACHA files | | | | -------------- | ------- | | Public SSH Key | SSH Key | ## Exhibit D ### Documents required for Mastercard Principal Membership \[coming soon] ## Exhibit E ### BIN tokenization requirements Each Issuer has certain requirements they need to fulfill in order to tokenize their BINs. Google Pay - Every bank needs to execute [Google Pay Click to Accept Agreement](https://support.google.com/faqs/contact/issuers_cta) Apple Pay - Every bank needs to execute: * [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-NDA.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-Third-Party-Program-Managers.docx.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-T\&C.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) Mastercard - Every bank needs to complete the following forms and submit them to [mdes\_administration@mastercard.com](mailto:mdes_administration@mastercard.com). It is recommended that I\&O check Mastercard Connect for the most updated forms in the Help section. [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201222.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201242.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download ## Exhibit F ### MRDC requirements In order for you to support Synctera MRDC functionality for your FinTech partners, you must complete a form for CheckAlt, Sycntera’s MRDC vendor:
Welcome to Synctera's docs
Explore our documentation to learn how to quickly and easily build a FinTech app or embedded banking product with Synctera.
## Get started
Create a Synctera account to get your API key, access our sandbox, and explore the rest of our Console.
Sign up
## Explore our documentation
Learn everything you need to know about integrating with our APIs and how to make your use case come to life.
View the API Guides
Everything you need to make your project come to life can be found here.
View the APIs
## Dive into our APIs
Creates and manages records for personal customers
Creates and manages records for business customers
Creates and manages customer accounts
Issues, activates, and manages cards for customers
Transfer funds between two accounts in real-time
Create and manage scheduled payments for customers
Issue cards, accept payments, and transfer money between accounts
Handles remote deposit capture (RDC) transactions
Create and manage documentation for a customer and run verification checks
Verify documentation for a customer
Handles legally required disclosures to customers
# ACH/Checks/Wires/Ledger
Source: https://docs.synctera.com/docs/achcheckswiresledger
Jacklyn & Jacqueline
James & Jimmy
Bank, Banque, & Banca
Automovil & Automobile
Vladimir Putin & Владимир Владимирович Путин | | removedPersonalTitle | Partial name match due to the removal of an honorary title within the input name such as (Dr, Mr, Queen, etc.). | Dr Miles & Kevin Miles | | nameInitialized | Name match based on initials | H.B. Hawala & Haji Basir Hawala | | namePhonetic | Name match based on phonetic similarity | Renault & Reneaux | | akaExact | Exact alias match | Joaquin Guzman & Chapo Loera | | akaFuzzy | Fuzzy alias match | Joaquin Guzman & Charo Loeta | | akaEquivalent | Alias match based on the same alias meaning | Peter Tobin & Pat McLaughlin | | akaPhonetic | Alias name match based on phonetic similarity | Ibrahim Anis & Abraham Anees | | dobExact | DOB matches year, month, and day. | 1988-02-23 & 1988-02-23 | | dobFuzzy | DOB is within one year (+/-) from the entered DOB. | 1988-02-23 & 1987-02-24
1988-02-23 & 1987
1988-02-23 & 1988-06-14
1988-02-23 & 1989-02-22 | | dobNotOnRecord | The source does not contain a DOB for the matched entity | | ## Reviewing and decisioning cases ### Mark Case in Review This allows a user to move the case out of the New state so that it is clear to other case reviewers that the case has been initially viewed and is actively under review, even if a final decision is yet to be made. This can be useful in differentiating between new cases that have just been opened and cases that have had a first look or review and are awaiting further input or information before making a final decision. ### Confirm Match This closes the case and marks the watchlist hit as a valid match. Once the hit is investigated and confirmed, this is the action to take to verify the watchlist hit as valid. ### Mark as Not Match This closes the case and marks the watchlist hit as not a match. This may be because the customer shares a similar name and other information with the person actually on the list, but is not in fact the same person. If the hit has been investigated and confirmed as not being for the same person, this is the action to take to mark the match as not valid. ### Reject Customer’s KYC This will change the customer KYC status from its current status into ‘REJECTED’. This should likely be done for any watchlist hit that will be marked as a confirmed match. Once this action is taken the user will not longer be able to transact or open new accounts, and will appear in the system with a KYC status of ‘REJECTED’ meaning they are not a customer that business should be done with. ### Freeze Customer and Related Accounts This will change the customer status and their related account status(es) to ‘FROZEN’ meaning the customer cannot perform any actions and the account(s) cannot perform any transactions. Take this action when confirming the watchlist hit as a match and deciding to no longer do business with the customer and to not allow them to move money on the platform or perform other actions.
**Tasks** will auto scroll you to the corresponding section and task of the Workspace.
**Company info** loads the Admin pages where you save and manage the details of your FinTech and organization. | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ### How to generate an API key for the various environments 1. Make sure you're on the environment for which you want an API key. 2. If your login has ADMINISTRATOR privileges, you will see a link on the bottom left titled "ACCOUNT ADMIN". 3. Selecting the link loads the Admin panel where you can proceed to the Developer Tools left nav item. 4. Here you'll see the API Keys link where you can issue and revoke API keys for the current environment. About API keys Once generated, be sure to capture the unique API key as you won't be able to view it again after dismissing the overlay. ***How to navigate to your API key page*** # Payments Source: https://docs.synctera.com/docs/payments-products Simple, reliable money movement ## Synctera ACH With over 29.1 billion payments last year, the [Automated Clearing House (ACH)](https://www.nacha.org/content/ach-network-volume-and-value-statistics) network is the primary way money moves electronically through the U.S. banking system. With Synctera ACH, your customers can use ACH transfers to fund their accounts, pay bills, and move money. Synctera ACH seamlessly enables your bank partner to manage and execute same-day and non-same-day ACH transfers on behalf of your customers. ### Benefits **Accelerate time to market:** Get your ACH payment program up and running quickly. **Seamless user experience:** The powerful Synctera interface makes ACH payments a breeze. **Complete transparency:** With near real-time visibility into the ACH process, your bank partner can understand your performance and the impact on their balance sheet. **Manage risk:** Enhance fraud controls and ensure outgoing payment volumes align with your bank partner’s risk tolerance. **Streamline operations:** Ensure transactions are flowing correctly to the general ledger and enable support teams to effectively troubleshoot customer inquiries according to NACHA rules (NACHA governs the ACH network). ### Key features **Incoming ACH processing:** Your bank partner receives incoming ACH files that are sent to the Synctera platform to process credits and debits for your customer accounts. **Returns:** Execute returns for ACH payments that fail to be processed by the external bank (e.g., non-sufficient funds, invalid account number, payment stopped, account frozen or closed). **Reversals:** Process incoming payment reversals. **Exception handling:** Troubleshoot payments that cannot be processed and manually resolve these items. **Outgoing ACH processing\*:** Initiate an API call to send money to external accounts and debit customer accounts. With Synctera, you avoid the complexity of having to create an ACH file in NACHA format; instead, only an API call is required. **Account validation:** As a mandatory network compliance requirement, ensure accounts are valid, open, in good standing and that funds are available prior to execution. **Modify/cancel payments:** Review, modify or cancel pending outgoing ACH payments prior to processing. **Pre-scheduled payments:** Create ACH instructions up to three months in advance of the planned execution date. **Recurring payments:** Set up recurring ACH payments on a daily, weekly or monthly basis. **Settlement account:** Create an ACH settlement account to track ACH debits and credits for later settlement. **Partial holds:** If you choose to use ACH for account funding, you can create partial holds for a percentage of the ACH transaction. A percentage of the total transaction amount is released in real time so your customers can use the partially released amount immediately. This feature helps drive customer activation and engagement. **Transaction descriptions for transfers to external accounts:** You can add a transaction description for ACH transfers that go to external accounts. This allows your customers to easily understand why the ACH transfer occurred. It’s particularly useful for transfers that happen automatically (e.g. if your financial product or FinTech app automatically rounds up transactions and then moves the rounded up amount to savings). \*Synctera “Lead” Ledger is required to execute incoming/outgoing ACH transactions. ### How it works #### Incoming ACH payments 1. At the end of each day, your bank partner securely transfers a file with incoming ACH transactions to Synctera. 2. Synctera automatically validates and converts the incoming ACH file to the required format. 3. Validated payment instructions are processed and posted to Synctera Ledger. 4. Your customer accounts are credited and debited with the correct amount. #### Outgoing ACH payments 1. Outgoing ACH payment instructions are validated automatically and posted to Synctera Ledger. 2. Outgoing payment instructions are converted to the outgoing ACH payment file. 3. Several times a day, Synctera securely transfers the outgoing ACH payment file to the bank partner to be sent to the NACHA network. ## Synctera Wire **Give your retail or business customers the ability to make domestic and international high-value transfers in near real time.** Wire transfers are direct point-to-point transfers between any two financial institutions. They’re typically used for higher-value items like property purchases or for settling large institutional transactions. Wire transfers clear immediately. Synctera provides the ability for your customers to send domestic and international wire transfers from their accounts and receive domestic and international wire transfers into their accounts. ### Benefits * Create stickier customer relationships and boost customer lifetime value with your business and high-net-worth retail customers by allowing them to transact via their preferred payment method * Create a new revenue stream by charging a fee, or provide free wire transfers to boost engagement with your other services * Enable cross-border payments for customers ### Key features * Domestic transfers are made via the Fedwire system and are processed by Synctera * Incoming and outgoing wire transfers clear immediately, making them appropriate for time-sensitive transactions * Synctera supports domestic and international wire transfers ## Synctera Remote Check Deposit **Allow your retail and business customers to deposit paper checks without going to a branch or ATM** Paper checks may be declining in popularity as a payment method, but your retail customers may still receive them from time to time, and business customers like doctors and lawyers may receive them quite often. Synctera Remote Check Deposit allows your customers to deposit these checks into their accounts without visiting a branch or ATM. ### Benefits * Allow your customers who receive checks to conveniently deposit and access their funds ### Key features * Your customers capture and upload images of their checks using their mobile phone, tablet, or computer * Customers' funds are generally available between one and seven days from initial deposit, according to your bank partner’s Funds Availability Schedule ### How it works * Using a mobile phone, tablet, or computer, your customer captures images of his/her check and uploads it to your app * You push the images and information to Synctera via API * Synctera sends the image to our Remote Check Deposit provider * Synctera's Remote Check Deposit provider validates the check using optical character resolution (OCR) and returns the outcome to Synctera * If the check is validated, Synctera adds the check deposit to Synctera Ledger * After end of day/cutoff time, Synctera's Remote Check Deposit provider generates anImage Cash Letter (ICL) file and sends it to the Synctera SFTP * Synctera sends the ICL file to your bank partner via SFTP * Your bank partner sends the ICL file to the Fed ## Synctera Fraud **Defend against fraudsters** For companies offering financial products and services, fraud is an unfortunate reality. Fraud—if not managed with proper oversight and controls—can have a significant impact on your bottom line, as fraud losses are your (not your bank partner's) sole responsibility. Synctera Fraud provides FinTechs with a scalable fraud program. Seamlessly integrated with the Synctera platform, Synctera Fraud can be launched quickly and easily, keeping you safe from fraudsters as you scale. ### Benefits **Reduce fraud and remain compliant:** Avoid financial risk and protect your business by identifying and preventing fraudulent events **Increase operational efficiency:** Automate workflows and concentrate resources only on those events flagged for review or rejection ### Key features **Configurable rules and risk models:** Build monitoring rules that align with the risk appetites of you and your bank partner. Create customer risk ratings to enhance accuracy. **Real-time monitoring:** Monitor transactions and money movement in real time with relevant customer information at your fingertips, including KYC outcomes. **Pre-integrated:** Your scalable fraud program works seamlessly with all of Synctera’s regulatory and compliance services. **Proof of compliance:** Track, investigate, and resolve events flagged for review or rejection. Use audit trails and other information to prove compliance with BSA/AML regulations. **Data-driven insights:** Understand overall fraud cases, including opened, current status, and time to close. Identify trends and adjust the program to minimize risk. ### How it works 1. You and your bank partner work with Synctera to implement and configure Synctera Fraud. Rules for event monitoring are configurable by you and your bank partner to address regulations and risk parameters. 2. Once activated, Synctera sends real-time events and customer information for analysis to our fraud partner. 3. Based on pre-configured rules and risk models, each event is permitted or flagged for review or rejection. 4. A case is created within Synctera Cases for each event that is under review or rejected. 5. You investigate and resolve each case, updating customer and account status through Synctera Cases. # Platform features Source: https://docs.synctera.com/docs/platform-features-fintechs To prevent fraud, Synctera supports the ability to ban identities on our platform. If an identity has been confirmed to be associated with fraud, Synctera Console users can choose to ban that identity with enforcement based on tenant access. ## Banned identities Banning an identity will prevent money movement for all created personal customers matching that identity. Any new personal customers with matching identity information will also enter a banned state, preventing any actions such as KYC that might cause you to incur fees. For accounts associated with banned customers, your operations team should zero out the balance in a suspense account and close the account. ## Restricted accounts and applications FinTechs that want to review and approve an application prior to opening an account can now use Restricted Accounts. With the restricted account flow, a customer submits an application, an operations team member reviews the application in the Synctera Console, and an account is created upon approval of the application. ## Scheduled payments Synctera can manage scheduled payments on your behalf. Customers may want to automatically move money into savings or to automatically send money for a mortgage payment, for example. You can define the expected schedule via API. If necessary, Synctera will recalculate based on business days and automatically initiate the payment. ## Spend controls Synctera Spend Controls provide you with a way to control spend on **account-level** through creation of rules that monitor the flow of funds to or from the account. Spend controls can for example be used to prevent fraud / unauthorized spending on the account or to support budgeting and financial goals. For more details on how to manage spend controls through the Synctera Console, see [this guide](/docs/spend-monitoring). For documentation on the Spend Control API, see the [API Guide](/docs/spend-controls-guide) and [API Reference](/v2/reference/listspendcontrols). ## Statement generation The [Statements API](/docs/statements-guide) allows you to retrieve the transactional information and disclosures needed to generate printable account statements for your customers. # Platform Reporting and Metrics Source: https://docs.synctera.com/docs/platform-reporting-and-metrics
NOTE: Ground to Canada and Mexico only! | \$15.00 | Yes | | INTERNATIONAL\_PRIORITY | USPS Priority International | \$43.55 | Yes | \*The average charges are based on individual card shipping (not bulk) **Exceptions:** * Other shipping methods may be supported, for example, FinTech may have a shipping method set as a default on the card product with the fulfillment provider * If the shipping method sent in the issuance request does not match the destination, the fulfillment provider’s system will convert it - for example, if USPS Priority is sent for Canada, the system will switch it to USPS Priority International #### Bulk shipping Synctera also supports bulk orders / shipping. FinTechs can use this option to reduce shipping costs for applicable use cases. Supported use cases: * Shipping of multiple cards to a **single** location where the distribution or last mile delivery is handled by a specific distributor/carrier: * This use case is supported through default product settings at the fulfillment provider level - cards are sent in bulk, but **packaged and addressed individually** * FinTech can contact their Synctera representative for this option * Shipping of multiple cards to **more than one** locations: * This use case is supported through [Synctera Bulk Order APIs](/v1/docs/bulk-card-orders) * Cards are sent in bulk, but **NOT packaged and addressed individually**
Is it ok with the bank if we use the FinTech company name? | | | 5 | Company identification | | Identical to the 'Immediate origin' used in File Header | | | 7 | Company Entry Description | | Description of the transaction.This may be Printed on the recipient’s bank statement by the Receiving Financial Institution. (i.e. Payroll)
Any specific information that the bank would like to enter? Otherwise we'll leave it up to the FinTech | | | 12 | Originating Financial institution | | We will enter your FI's routing number | | ## Exhibit B ### Information needed to establish cutoff and exchange times | | | | --------------------------------------- | ---------------- | | What is the end-of-day processing time? | Time / Time Zone | | | | | ------------------------- | ---------------- | | ACH Incoming File | Time | | Cutoff | Time / Time Zone | | ACH Outgoing File | | | Same-Day ACH Early Cutoff | Time / Time Zone | | Same-Day ACH Last Cutoff | Time / Time Zone | | Standard ACH Cutoff | Time / Time Zone | | Bank Holidays | Dates | ## Exhibit C ### Information needed to set up SFTP connection to process NACHA files | | | | -------------- | ------- | | Public SSH Key | SSH Key | ## Exhibit D ### Documents required for Mastercard Principal Membership \[coming soon] ## Exhibit E ### BIN tokenization requirements Each Issuer has certain requirements they need to fulfill in order to tokenize their BINs. Google Pay - Every bank needs to execute [Google Pay Click to Accept Agreement](https://support.google.com/faqs/contact/issuers_cta) Apple Pay - Every bank needs to execute: * [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-NDA.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-Third-Party-Program-Managers.docx.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-T\&C.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) Mastercard - Every bank needs to complete the following forms and submit them to [mdes\_administration@mastercard.com](mailto:mdes_administration@mastercard.com). It is recommended that I\&O check Mastercard Connect for the most updated forms in the Help section. [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201222.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201242.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download ## Exhibit F ### MRDC requirements In order for you to support Synctera MRDC functionality for your FinTech partners, you must complete a form for CheckAlt, Sycntera’s MRDC vendor:
Subtypes can indicate a specific use case as defined for the program (e.g. the internal transfer subtype `peer_to_peer` indicates a P2P payment from one customer to another), or can be system generated based on the direction or action taken (e.g. cards subtype `atm_withdrawal` or ACH `incoming_credit`). For more information ACH subtypes, read our FAQ page [here](https://app.mintlify.com/synctera/synctera/~/aa507287-8bdb-4614-95de-149dd26d2ddc). **Top Navigation Options:**
Welcome to Synctera's docs
Explore our documentation to learn how to quickly and easily build a FinTech app or embedded banking product with Synctera.
## Get started
Create a Synctera account to get your API key, access our sandbox, and explore the rest of our Console.
Sign up
## Explore our documentation
Learn everything you need to know about integrating with our APIs and how to make your use case come to life.
View the API Guides
Everything you need to make your project come to life can be found here.
View the APIs
## Dive into our APIs
Creates and manages records for personal customers
Creates and manages records for business customers
Creates and manages customer accounts
Issues, activates, and manages cards for customers
Transfer funds between two accounts in real-time
Create and manage scheduled payments for customers
Issue cards, accept payments, and transfer money between accounts
Handles remote deposit capture (RDC) transactions
Create and manage documentation for a customer and run verification checks
Verify documentation for a customer
Handles legally required disclosures to customers
# A check was rejected. How can we find out the rejection reason?
Source: https://docs.synctera.com/docs/a-check-was-rejected-how-can-we-find-out-the-rejection-reason
In the Synctera console, open up the check transaction and on the left side there will be a banner which will state the reason for rejection.
# ACH/Checks/Wires/Ledger
Source: https://docs.synctera.com/docs/achcheckswiresledger
NOTE: Ground to Canada and Mexico only! | \$15.00 | Yes | | INTERNATIONAL\_PRIORITY | USPS Priority International | \$43.55 | Yes | \*The average charges are based on individual card shipping (not bulk) **Exceptions:** * Other shipping methods may be supported, for example, FinTech may have a shipping method set as a default on the card product with the fulfillment provider * If the shipping method sent in the issuance request does not match the destination, the fulfillment provider’s system will convert it - for example, if USPS Priority is sent for Canada, the system will switch it to USPS Priority International #### Bulk shipping Synctera also supports bulk orders / shipping. FinTechs can use this option to reduce shipping costs for applicable use cases. Supported use cases: * Shipping of multiple cards to a **single** location where the distribution or last mile delivery is handled by a specific distributor/carrier: * This use case is supported through default product settings at the fulfillment provider level - cards are sent in bulk, but **packaged and addressed individually** * FinTech can contact their Synctera representative for this option * Shipping of multiple cards to **more than one** locations: * This use case is supported through [Synctera Bulk Order APIs](/v1/docs/bulk-card-orders) * Cards are sent in bulk, but **NOT packaged and addressed individually**
Jacklyn & Jacqueline
James & Jimmy
Bank, Banque, & Banca
Automovil & Automobile
Vladimir Putin & Владимир Владимирович Путин | | removedPersonalTitle | Partial name match due to the removal of an honorary title within the input name such as (Dr, Mr, Queen, etc.). | Dr Miles & Kevin Miles | | nameInitialized | Name match based on initials | H.B. Hawala & Haji Basir Hawala | | namePhonetic | Name match based on phonetic similarity | Renault & Reneaux | | akaExact | Exact alias match | Joaquin Guzman & Chapo Loera | | akaFuzzy | Fuzzy alias match | Joaquin Guzman & Charo Loeta | | akaEquivalent | Alias match based on the same alias meaning | Peter Tobin & Pat McLaughlin | | akaPhonetic | Alias name match based on phonetic similarity | Ibrahim Anis & Abraham Anees | | dobExact | DOB matches year, month, and day. | 1988-02-23 & 1988-02-23 | | dobFuzzy | DOB is within one year (+/-) from the entered DOB. | 1988-02-23 & 1987-02-24
1988-02-23 & 1987
1988-02-23 & 1988-06-14
1988-02-23 & 1989-02-22 | | dobNotOnRecord | The source does not contain a DOB for the matched entity | | ## Reviewing and decisioning cases ### Mark Case in Review This allows a user to move the case out of the New state so that it is clear to other case reviewers that the case has been initially viewed and is actively under review, even if a final decision is yet to be made. This can be useful in differentiating between new cases that have just been opened and cases that have had a first look or review and are awaiting further input or information before making a final decision. ### Confirm Match This closes the case and marks the watchlist hit as a valid match. Once the hit is investigated and confirmed, this is the action to take to verify the watchlist hit as valid. ### Mark as Not Match This closes the case and marks the watchlist hit as not a match. This may be because the customer shares a similar name and other information with the person actually on the list, but is not in fact the same person. If the hit has been investigated and confirmed as not being for the same person, this is the action to take to mark the match as not valid. ### Reject Customer’s KYC This will change the customer KYC status from its current status into ‘REJECTED’. This should likely be done for any watchlist hit that will be marked as a confirmed match. Once this action is taken the user will not longer be able to transact or open new accounts, and will appear in the system with a KYC status of ‘REJECTED’ meaning they are not a customer that business should be done with. ### Freeze Customer and Related Accounts This will change the customer status and their related account status(es) to ‘FROZEN’ meaning the customer cannot perform any actions and the account(s) cannot perform any transactions. Take this action when confirming the watchlist hit as a match and deciding to no longer do business with the customer and to not allow them to move money on the platform or perform other actions.
**Tasks** will auto scroll you to the corresponding section and task of the Workspace.
**Company info** loads the Admin pages where you save and manage the details of your FinTech and organization. | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ### How to generate an API key for the various environments 1. Make sure you're on the environment for which you want an API key. 2. If your login has ADMINISTRATOR privileges, you will see a link on the bottom left titled "ACCOUNT ADMIN". 3. Selecting the link loads the Admin panel where you can proceed to the Developer Tools left nav item. 4. Here you'll see the API Keys link where you can issue and revoke API keys for the current environment. About API keys Once generated, be sure to capture the unique API key as you won't be able to view it again after dismissing the overlay. ***How to navigate to your API key page*** # Payments Source: https://docs.synctera.com/docs/payments-products Simple, reliable money movement ## Synctera ACH With over 29.1 billion payments last year, the [Automated Clearing House (ACH)](https://www.nacha.org/content/ach-network-volume-and-value-statistics) network is the primary way money moves electronically through the U.S. banking system. With Synctera ACH, your customers can use ACH transfers to fund their accounts, pay bills, and move money. Synctera ACH seamlessly enables your bank partner to manage and execute same-day and non-same-day ACH transfers on behalf of your customers. ### Benefits **Accelerate time to market:** Get your ACH payment program up and running quickly. **Seamless user experience:** The powerful Synctera interface makes ACH payments a breeze. **Complete transparency:** With near real-time visibility into the ACH process, your bank partner can understand your performance and the impact on their balance sheet. **Manage risk:** Enhance fraud controls and ensure outgoing payment volumes align with your bank partner’s risk tolerance. **Streamline operations:** Ensure transactions are flowing correctly to the general ledger and enable support teams to effectively troubleshoot customer inquiries according to NACHA rules (NACHA governs the ACH network). ### Key features **Incoming ACH processing:** Your bank partner receives incoming ACH files that are sent to the Synctera platform to process credits and debits for your customer accounts. **Returns:** Execute returns for ACH payments that fail to be processed by the external bank (e.g., non-sufficient funds, invalid account number, payment stopped, account frozen or closed). **Reversals:** Process incoming payment reversals. **Exception handling:** Troubleshoot payments that cannot be processed and manually resolve these items. **Outgoing ACH processing\*:** Initiate an API call to send money to external accounts and debit customer accounts. With Synctera, you avoid the complexity of having to create an ACH file in NACHA format; instead, only an API call is required. **Account validation:** As a mandatory network compliance requirement, ensure accounts are valid, open, in good standing and that funds are available prior to execution. **Modify/cancel payments:** Review, modify or cancel pending outgoing ACH payments prior to processing. **Pre-scheduled payments:** Create ACH instructions up to three months in advance of the planned execution date. **Recurring payments:** Set up recurring ACH payments on a daily, weekly or monthly basis. **Settlement account:** Create an ACH settlement account to track ACH debits and credits for later settlement. **Partial holds:** If you choose to use ACH for account funding, you can create partial holds for a percentage of the ACH transaction. A percentage of the total transaction amount is released in real time so your customers can use the partially released amount immediately. This feature helps drive customer activation and engagement. **Transaction descriptions for transfers to external accounts:** You can add a transaction description for ACH transfers that go to external accounts. This allows your customers to easily understand why the ACH transfer occurred. It’s particularly useful for transfers that happen automatically (e.g. if your financial product or FinTech app automatically rounds up transactions and then moves the rounded up amount to savings). \*Synctera “Lead” Ledger is required to execute incoming/outgoing ACH transactions. ### How it works #### Incoming ACH payments 1. At the end of each day, your bank partner securely transfers a file with incoming ACH transactions to Synctera. 2. Synctera automatically validates and converts the incoming ACH file to the required format. 3. Validated payment instructions are processed and posted to Synctera Ledger. 4. Your customer accounts are credited and debited with the correct amount. #### Outgoing ACH payments 1. Outgoing ACH payment instructions are validated automatically and posted to Synctera Ledger. 2. Outgoing payment instructions are converted to the outgoing ACH payment file. 3. Several times a day, Synctera securely transfers the outgoing ACH payment file to the bank partner to be sent to the NACHA network. ## Synctera Wire **Give your retail or business customers the ability to make domestic and international high-value transfers in near real time.** Wire transfers are direct point-to-point transfers between any two financial institutions. They’re typically used for higher-value items like property purchases or for settling large institutional transactions. Wire transfers clear immediately. Synctera provides the ability for your customers to send domestic and international wire transfers from their accounts and receive domestic and international wire transfers into their accounts. ### Benefits * Create stickier customer relationships and boost customer lifetime value with your business and high-net-worth retail customers by allowing them to transact via their preferred payment method * Create a new revenue stream by charging a fee, or provide free wire transfers to boost engagement with your other services * Enable cross-border payments for customers ### Key features * Domestic transfers are made via the Fedwire system and are processed by Synctera * Incoming and outgoing wire transfers clear immediately, making them appropriate for time-sensitive transactions * Synctera supports domestic and international wire transfers ## Synctera Remote Check Deposit **Allow your retail and business customers to deposit paper checks without going to a branch or ATM** Paper checks may be declining in popularity as a payment method, but your retail customers may still receive them from time to time, and business customers like doctors and lawyers may receive them quite often. Synctera Remote Check Deposit allows your customers to deposit these checks into their accounts without visiting a branch or ATM. ### Benefits * Allow your customers who receive checks to conveniently deposit and access their funds ### Key features * Your customers capture and upload images of their checks using their mobile phone, tablet, or computer * Customers' funds are generally available between one and seven days from initial deposit, according to your bank partner’s Funds Availability Schedule ### How it works * Using a mobile phone, tablet, or computer, your customer captures images of his/her check and uploads it to your app * You push the images and information to Synctera via API * Synctera sends the image to our Remote Check Deposit provider * Synctera's Remote Check Deposit provider validates the check using optical character resolution (OCR) and returns the outcome to Synctera * If the check is validated, Synctera adds the check deposit to Synctera Ledger * After end of day/cutoff time, Synctera's Remote Check Deposit provider generates anImage Cash Letter (ICL) file and sends it to the Synctera SFTP * Synctera sends the ICL file to your bank partner via SFTP * Your bank partner sends the ICL file to the Fed ## Synctera Fraud **Defend against fraudsters** For companies offering financial products and services, fraud is an unfortunate reality. Fraud—if not managed with proper oversight and controls—can have a significant impact on your bottom line, as fraud losses are your (not your bank partner's) sole responsibility. Synctera Fraud provides FinTechs with a scalable fraud program. Seamlessly integrated with the Synctera platform, Synctera Fraud can be launched quickly and easily, keeping you safe from fraudsters as you scale. ### Benefits **Reduce fraud and remain compliant:** Avoid financial risk and protect your business by identifying and preventing fraudulent events **Increase operational efficiency:** Automate workflows and concentrate resources only on those events flagged for review or rejection ### Key features **Configurable rules and risk models:** Build monitoring rules that align with the risk appetites of you and your bank partner. Create customer risk ratings to enhance accuracy. **Real-time monitoring:** Monitor transactions and money movement in real time with relevant customer information at your fingertips, including KYC outcomes. **Pre-integrated:** Your scalable fraud program works seamlessly with all of Synctera’s regulatory and compliance services. **Proof of compliance:** Track, investigate, and resolve events flagged for review or rejection. Use audit trails and other information to prove compliance with BSA/AML regulations. **Data-driven insights:** Understand overall fraud cases, including opened, current status, and time to close. Identify trends and adjust the program to minimize risk. ### How it works 1. You and your bank partner work with Synctera to implement and configure Synctera Fraud. Rules for event monitoring are configurable by you and your bank partner to address regulations and risk parameters. 2. Once activated, Synctera sends real-time events and customer information for analysis to our fraud partner. 3. Based on pre-configured rules and risk models, each event is permitted or flagged for review or rejection. 4. A case is created within Synctera Cases for each event that is under review or rejected. 5. You investigate and resolve each case, updating customer and account status through Synctera Cases. # Permissions Source: https://docs.synctera.com/docs/permissions ## Permissions demo ## Key concepts Synctera has the following concepts: * **Customers** - Customers of the FinTech that uses Synctera. * **Users** - Employees of the FinTech that uses Synctera. Employees use the Synctera Console to keep track of / manage their customers and their details. ## ## Roles available in the Synctera Console | Role | Description | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Executive | Users with this role have access to view customer, analytics and team data. Users with this role do not have access to view transactions or reconciliation. | | Administrator | Users with this role have access to invite users, administer user accounts, manage notifications, and change account settings. Users with this role do not have access to view customers, accounts, transactions and general user data. | | Operations | Users with this role have access to customer data including accounts and transactions to help resolve customer issues | | Operations Manager | Users with this role have access to customer data and team data | | Case Operations | Users with this role can manage cases and access data needed for case work, including customers, accounts and transactions. Users with this role do not have access to view team data. | | Card Image Reviewer | Users with this role can approve or reject images for custom cards | | Profile Viewer | Users with this role can view FinTech profile information | | Profile Editor | Users with this role can edit FinTech profile information | Each role comes with a set of permissions. The default roles mentioned above cannot be edited / deleted. You also cannot change permissions for default roles. However you can create new roles specific to your FinTech and you can set permissions based on whatever your needs are. Each of these permissions come with View / Edit access. Depending on what permissions are set for the role that the user has, the user will be able to view / edit the respective data of the customer. ## Available permissions | Permission | Description | Other recommended permissions | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Accounts | Account data can be viewed / edited with this permission | Customers / Cards / Sub-ledger | | Admin | Roles with view / edit access to this permission can create API Keys | | | Card Image Reviews | Roles with view / edit access to this permission can view / review / approve the Card Images of the customer | Cases / Cards / Customers | | Cards | Roles with view / edit access to this permission can issue card / activate a card / view card details of the customer | Customers / Cases / Accounts | | Cases | Roles with view / edit access to this permission can act on all types of cases. For Card image review, the user has to have that specific permission along with cases | Customers / Cases / Accounts/ Cards | | Customers | Roles with view / edit access to this permission can view / edit the Customer data | Cases / Accounts/ Cards If the user needs to see transactions, also give Sub-ledger | | Sub Ledger | Roles with view / edit access to this permission can view Transaction data of the customer, perform Reconciliation, or initiate an ACH transaction for the user. | | | Users | Roles with view / edit access to this permission can add users to the Consoleor assign permissions to users. | | | Profile | Roles with view / edit access to this permission can view / edit the Fintech Profile data. | | | General Ledger | Internal to Synctera. You shouldn’t need to use this permission. | | | Notifications | Internal to Synctera. We do not recommend you use this. | | | Waitlists | Internal to Synctera. You shouldn’t need to use this permission | | | | | | # Platform features Source: https://docs.synctera.com/docs/platform-features-fintechs To prevent fraud, Synctera supports the ability to ban identities on our platform. If an identity has been confirmed to be associated with fraud, Synctera Console users can choose to ban that identity with enforcement based on tenant access. ## Banned identities Banning an identity will prevent money movement for all created personal customers matching that identity. Any new personal customers with matching identity information will also enter a banned state, preventing any actions such as KYC that might cause you to incur fees. For accounts associated with banned customers, your operations team should zero out the balance in a suspense account and close the account. ## Restricted accounts and applications FinTechs that want to review and approve an application prior to opening an account can now use Restricted Accounts. With the restricted account flow, a customer submits an application, an operations team member reviews the application in the Synctera Console, and an account is created upon approval of the application. ## Scheduled payments Synctera can manage scheduled payments on your behalf. Customers may want to automatically move money into savings or to automatically send money for a mortgage payment, for example. You can define the expected schedule via API. If necessary, Synctera will recalculate based on business days and automatically initiate the payment. ## Spend controls Synctera Spend Controls provide you with a way to control spend on **account-level** through creation of rules that monitor the flow of funds to or from the account. Spend controls can for example be used to prevent fraud / unauthorized spending on the account or to support budgeting and financial goals. For more details on how to manage spend controls through the Synctera Console, see [this guide](/docs/spend-monitoring). For documentation on the Spend Control API, see the [API Guide](/docs/spend-controls-guide) and [API Reference](/v2/reference/listspendcontrols). ## Statement generation The [Statements API](/docs/statements-guide) allows you to retrieve the transactional information and disclosures needed to generate printable account statements for your customers. # Platform Reporting and Metrics Source: https://docs.synctera.com/docs/platform-reporting-and-metrics
Subtypes can indicate a specific use case as defined for the program (e.g. the internal transfer subtype `peer_to_peer` indicates a P2P payment from one customer to another), or can be system generated based on the direction or action taken (e.g. cards subtype `atm_withdrawal` or ACH `incoming_credit`). For more information ACH subtypes, read our FAQ page [here](https://app.mintlify.com/synctera/synctera/~/aa507287-8bdb-4614-95de-149dd26d2ddc). **Top Navigation Options:**
Is it ok with the bank if we use the FinTech company name? | | | 5 | Company identification | | Identical to the 'Immediate origin' used in File Header | | | 7 | Company Entry Description | | Description of the transaction.This may be Printed on the recipient’s bank statement by the Receiving Financial Institution. (i.e. Payroll)
Any specific information that the bank would like to enter? Otherwise we'll leave it up to the FinTech | | | 12 | Originating Financial institution | | We will enter your FI's routing number | | ## Exhibit B ### Information needed to establish cutoff and exchange times | | | | --------------------------------------- | ---------------- | | What is the end-of-day processing time? | Time / Time Zone | | | | | ------------------------- | ---------------- | | ACH Incoming File | Time | | Cutoff | Time / Time Zone | | ACH Outgoing File | | | Same-Day ACH Early Cutoff | Time / Time Zone | | Same-Day ACH Last Cutoff | Time / Time Zone | | Standard ACH Cutoff | Time / Time Zone | | Bank Holidays | Dates | ## Exhibit C ### Information needed to set up SFTP connection to process NACHA files | | | | -------------- | ------- | | Public SSH Key | SSH Key | ## Exhibit D ### Documents required for Mastercard Principal Membership \[coming soon] ## Exhibit E ### BIN tokenization requirements Each Issuer has certain requirements they need to fulfill in order to tokenize their BINs. Google Pay - Every bank needs to execute [Google Pay Click to Accept Agreement](https://support.google.com/faqs/contact/issuers_cta) Apple Pay - Every bank needs to execute: * [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-NDA.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-Third-Party-Program-Managers.docx.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) \* [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Tokenization-Apple-T\&C.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [](https://docs.google.com/document/d/128RaYBB-9zFCcxhqwxA1Z5Im0Eb7C9y3/edit?usp=sharing\&ouid=108955235655309595630\&rtpof=true\&sd=true) Mastercard - Every bank needs to complete the following forms and submit them to [mdes\_administration@mastercard.com](mailto:mdes_administration@mastercard.com). It is recommended that I\&O check Mastercard Connect for the most updated forms in the Help section. [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201222.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download [Click here](https://cdn.document360.io/dce2753c-5559-4810-a779-e02cfa7763f7/Images/Documentation/Mastercard%20MDES%20Form%201242.pdf?sv=2022-11-02\&spr=https\&st=2025-02-21T08%3A21%3A14Z\&se=2025-02-21T08%3A31%3A14Z\&sr=c\&sp=r\&sig=v7k3teorg%2FdngLP35ltn62KyfmAgcJOO0iyUnsIbQ00%3D) to download ## Exhibit F ### MRDC requirements In order for you to support Synctera MRDC functionality for your FinTech partners, you must complete a form for CheckAlt, Sycntera’s MRDC vendor: