Digital Wallet Token Simulations

Digital Wallet Token Request Body

Provisioning

Fulfillment Sub-Object

Token Service Provider Sub-Object

Example Request

Example Response

Success

Error

Create a Digital Wallet Token Simulation

Introduction

Treasury Prime Developer Documentation

Start building today with Treasury Prime's APIs for banking.

Overview

This is a checklist that a fintech can run through before launching to assess overall readiness

Pre-launch Checklist

This guide will cover the basics of applying to open new bank accounts (both business and personal) as well as funding those accounts with an initial deposit.

This guide describes how to add authorized users to existing accounts and issue them debit cards. Authorized users do not require the same amount of KYC as account owners, and as such adding them to accounts requires permission from the bank.

Adding Authorized Users

In the normal course of maintaining a deposit offering, it may become necessary to lock a customer's account to block certain activity while an investigation or remediation takes place. This is usually done to prevent fraudulent activity after an event of suspected fraud.

Locking an Account

Closing an account is done primarily when an account owner no longer wishes to use their account. Upon account closure, a paper check will be issued with the remaining balance if the fintech does not zero the account. To the extent you, as the fintech, are seeking to initiate the close because you suspect fraud or nefarious conduct, always use the lock functionality and not the close functionality. See the  guide for details.

Closing an Account

This guide describes how to create and file a 1099-INT for an account.

Creating and Filing a 1099-INT

By default, debit cards issued using the Treasury Prime platform will have access to withdraw cash from any ATM which operates on the Pulse or Mastercard network (look for the logos). Use of these ATMs will incur a usage fee for the cardholder.

Card Issuing and Fulfillment

Cards provide a mechanism to easily conduct transactions with merchants both online and in-person. Using our API, the entire card lifecycle—from issuing, to activation, to deactivation—can be managed programmatically. With the ability to issue virtual cards, you can get to market quickly while providing incredible digital experiences for your customers.

Issuing a Card

There are a number of scenarios which may require you to take additional actions on a specific card after it has been issued to a cardholder including activation, renewal, suspension, and termination. Each of these scenarios is outlined below with accompanying examples.

Card Management

Card Events and  are the two main elements involved in the lifecycle of a card payment on the Treasury Prime platform. Card Events are dispatched via webhook callback to provide notification that a specific type of message was received from the card network. In response to these messages, Treasury Prime also creates Transactions on the related account, which impacts the current and available balance.

Card Events

Declined card transactions are represented as  with a  of . Card events in this status will contain a value in the  field which outlines the reason the transaction was declined. The example below shows a card event that was declined due to “Card Not Active.”

Card Declines

A great way to reduce fraud exposure is to notify your cardholders when someone has attempted to add their card to a Digital Wallet such as Apple Pay™. If you are integrated with Marqeta through Treasury Prime, the  allows you to know when a card was attempted to be added to a Digital Wallet so that you can notify the cardholder.

Digital Wallet Notifications

The  allows you to accept or reject a card transaction at the time of authorization based on your business logic. To accomplish this, you assign the Card Auth Loop Endpoint to the Card Product whose card authorization requests you want to monitor. From there, any time a new authorization or refund authorization request is received for a card created using that Card Product, you will receive a callback at the URL specified in the Card Auth Loop Endpoint object.

Managing Card Authorizations

Testing your card implementation is essential to ensuring the successful rollout of any new card program. While initial testing can be completed in the sandbox environment, it is highly recommended that production testing be performed to ensure that all elements of the card implementation are functioning as expected before launching your program with customers.

Testing Cards

Digital wallets allow users to store and use their cards without carrying a physical card with them. This guide describes how to provision cards using Apple Pay.

Apple Pay

ACH transfers created using the  endpoint are referred to as “API originated” ACH transfers as they are originated by the Treasury Prime platform. They support both credit and debit transfers, allowing funds to be sent (credited) to a recipient's account, or pulled (debited) from another account. Beyond this, originated ACH transfers support two levels of service— and —which impacts the amount of time required for the transfer to settle.

An Automated Clearing House (ACH) transfer is an electronic funds transfer between two accounts at different banks. It allows for for credits (sending money) and debits (receiving money), and is generally cheaper when compared to other available methods, but also most-often slower. This guide will examine the process of sending money  another account using ACH (also known as a credit), though you can also receive money  an account (a debit) using this same method.

ACH Transfers

The ACH Network supports the ability to return ACH payments for a number of reasons. Commonly, returns are initiated because the payment can't be completed due to reasons like insufficient funds, account closure, or inaccurate account details.

ACH Returns

While ACH transfers provide a relatively simple way to transfer funds between two accounts at different banks, we recommend that you understand and test the various scenarios you may encounter while using this payment rail before launching your application.

Testing ACH

A book transfer is an electronic funds transfer between two accounts at the same bank; such as transferring funds from a checking account to a savings account. While book transfers are the fastest and cheapest type of transfer, they are restricted to accounts held at the same bank.

Book Transfer

FedNow is the Federal Reserve's instant payment service that enables financial institutions to provide safe and efficient instant payment services.

FedNow

Treasury Prime has partnered with  to offer our customers a seamless solution for sending ACH payments to authenticated bank accounts.

Plaid Payments Integration

Remote Deposit Capture (RDC) allows banks and their customers to deposit checks electronically by capturing images of the checks and submitting them through a mobile device or scanner. Treasury Prime’s RDC API streamlines this process, enabling seamless integration of RDC functionality into your banking or financial application.

Check Deposit

Rutter Integration

This documentation provides step-by-step instructions for integrating with these services through Treasury Prime's platform, including API endpoints, authentication methods, and example use cases.

Deposit Sweeps

Live and Test Environments 

Authentication

Ledger & Core Direct Products

Testing In Sandbox

Health Check

Idempotency

Request and Response Payloads

Undocumented Fields

Filtering

Pagination

Errors

**Fix: Improvement For Statement Generation**

04/25

April 25th

**Fix: Remote Deposit Check Processing Update**

03/24

March 24th

03/19

March 19th

**Fix: Account Enrollment Type Configuration, Account Specific Interest Rates**

03/18

March 18th

02/14

February 14th

**Feature: Signatory Name Now Available for Printed Checks**

02/11

February 11th

**Fix: Webhook Delivery For Incomming ACH Updates, Error Messaging For Issued Checks, Support For Other Delivery Methods**

**Feature: Additional Check Deposit Status, Additional Key Points About Invoice Account Numbers**

01/28

January 28th

**Feature: Enhanced Shipping Methods For Issued Checks**

01/27

January 27th

**Fix: Search Filtering Added To The NEW Console**

01/20

January 20th

01/17

January 17th

**Feature: Enhanced 1099-Ints Generation (Tax Documents)**

12/18

December 18th

**Feature: Enhanced Statement Generation**

12/04

December 4th

10/25

October 25th

**Feature: Ability To Split Balanced Ach Return File**

10/09

October 9th

**Fix: Voiding Outgoing Wires with Fees**

09/17

September 17th

**Feature: Voiding Outgoing Wires, Returning Incoming Wires**

09/16

September 16th

09/12

September 12th

**Feature: Originated ACH Email Notifications**

**Feature: Addenda Record Option For Ach Origination Using WEB SEC Code**

09/11

September 11th

**Feature: Introducing The Console And New Features**

09/04

September 4th

**Fix: Update To [Update An Account] Endpoint**

08/15

August 15th

08/02

August 2nd

**Fix: Early Posting for Incoming ACH Credits, Check Deposit Status Conversion**

08/01

August 1st

**Feature: Returning/Voiding Wires Capabilities, Returning Incoming Wires**

07/30

July 30th

**Fix: International ID Numbers, Check Deposit Status Conversion**

07/29

July 29th

06/21

June 21st

**Feature: Returning Incoming ACH, Invoice Account Numbers**

06/07

June 7th

**Fix: Updates To Rdc Api Responses, Account Closure Checks Funds Flow, Prime Data**

04/17

April 17tg

02/21

February 21st

**Fix: Statements, Support For ARC SEC Code For Incoming ACH, Manage Enhanced FDIC Insurance For Foreign Entities Without US-TINs**

Parameter	Type	Required?	Description
card_id	string	Required	ID of the card to use as the source for simulated tokens.
fulfillment	object		An object that defines additional fields for fulfillment of the token.
token_service_provider	object		An object that defines additional fields for requestor of the token.

Parameter	Type	Description
token_requestor_name	string	Name of the token requestor within the card network. One of `APPLE_PAY` or `ANDROID_PAY`.
token_requestor_id	string	Unique numerical identifier of the digital wallet token requestor within the card network. These IDs map to a token_requestor_name. `50110030273` for Apple Pay, `50120834693` for Google Pay, and `50139059239` for Samsung Pay.

Introduction

Account

Account Opening

Cards

Payments

Testing

Utilities

Introduction

Digital Wallet Token Simulations

Create a Digital Wallet Token Simulation

Digital Wallet Token Request Body

Provisioning

Fulfillment Sub-Object

Token Service Provider Sub-Object

Example Request

Example Response

Success

Error

Introduction

Account

Account Opening

Cards

Payments

Testing

Utilities

​Digital Wallet Token Simulations

​Create a Digital Wallet Token Simulation

​Digital Wallet Token Request Body

​Provisioning

​Fulfillment Sub-Object

​Token Service Provider Sub-Object

​Example Request

​Example Response

​Success

​Error

Digital Wallet Token Simulations

Create a Digital Wallet Token Simulation

Digital Wallet Token Request Body

Provisioning

Fulfillment Sub-Object

Token Service Provider Sub-Object

Example Request

Example Response

Success

Error