Overview

While you complete sandbox testing and work through the sandbox checklist, your team submits a set of deliverables for review. We use these deliverables to determine your eligibility for production access.

Deliverable requirements vary by use case. Not every item in this guide may apply to your program or use case. Your Implementation Manager confirms which deliverables you need to submit; these are also listed in your Integration Checklist, under the Sandbox tab.

Please submit all deliverables directly in your Integration Checklist.

When in doubt about next steps for production approval, always review your sandbox checklist.

Required Deliverables

Successful Transfer IDs

For each approved use case and payment flow your program intends to launch Astra, you will be required to submit a corresponding Transfer ID for review. Astra reviews each ID to compare against the pre-approved flow of funds to ensure your program remains in compliance with Astra.

If your integration supports multiple use cases or user types, our team will need to receive a successful Transfer ID for each.

• Example A: if your program is integrating with Astra for deposits and withdrawals, Astra will need to receive one successful Transfer ID for the deposit and one successful Transfer ID for the withdrawal.

• Example B: if your program is integrating with Astra for deposits, but plans to allow both Personal and Business User to initiate deposits, Astra will need to receive one successful Transfer ID for the deposit from a Personal User and one successful Transfer ID for a deposit from a Business User.

• Example C: if your program is integrating with Astra for deposits, and plans to use two payment solutions to accomplish this, such as Card-to-Account and Account-to-Account, Astra will need to receive one successful Transfer ID for the Card-to-Account Deposit and one successful Transfer ID for the Account-to-Account Deposit.

Demo Videos

All Integrations are required to submit a Sandbox Demo Video. Depending on your program's use case, the steps below may not be applicable. Generally speaking, the Sandbox Demo Video needs to capture the following:

Onboarding

• End-User account creation, including the information required for KYC/KYB, such as name, address, date of birth, and SSN

Authorizing & Authentication

• Mobile Two-factor authentication or biometric authentication

• User agreement to Astra's Terms of Service and Privacy Policy

Linking A Payment Instrument

• Adding a debit card or bank account

Initiating a Routine / Transfer

• This may include, but not be limited to deposits, pay-ins, on-ramps, withdrawals, pay-outs, off-ramps.

Test cases

All Integrations are required to complete Test Cases as part of the Sandbox deliverable package, which are curated to the specifics of your program's use cases and payment flows. Your program's test cases are located in the Integration Checklist in a tab to the left of the Production Checklist. Once all cases have been submitted, an Astra Technical Account Manager will review. General timelines for review are 1 to 2 business days.

API Log Review

At the end of each integration phase, your designated Astra Technical Account Manager will review your Sandbox API logs to confirm your implementation is working as expected before you move to the next phase. Although there is not an explicit deliverable here, there are guidelines your program must adhere to, outlined in the following: What to Expect in Your Sandbox Log Review. Your program may be required to make revisions based on the outcome of this review.

Use Case Specific Deliverables

GET Balance Endpoint
This deliverable applies to program's using Astra's Account-to-Card Gross Debit solution, where the source of funds is unique to each User, or is a DDA account. This resource is designed as an additional pre-flight check ahead of a User withdrawing their funds to ensure they don't withdraw more than they have. This aids in preventing return codes for your program. For more information, please review the following guide: Balance Update Endpoint.

Ultimate Receiver and Ultimate Sender IDs

Depending on the specifics of your program's flow of funds, you may need to submit evidence by way of a Transfer ID that your team has implement an Ultimate Receiver ID, and or Ultimate Sender ID via the payload of the parent Routine request. For more information, please review the following guide: Ultimate Sender vs. Ultimate Receiver.

Optional Program Deliverables

KYC/KYB Delegation Submission
If applicable to your program's use case, and if your program is eligible, your program may apply for KYC/KYB delegation. If these conditions are met, Astra's Compliance Team will share a secure KYC/KYB Delegation folder by email with your compliance team. Once all materials have been submitted, Astra's compliance team will schedule and conduct a formal review. The review timeline is generally 1 to 2 weeks.

Trusted Authentication Application
Depending on your program's use case and the flow of funds, your program may be required to perform a Mobile 2FA or equivalent per User, which we refer to as "Authentication". Astra's provides this service out-of-the-box through our WebSDK, which can be embedded in an iFrame. If your program would prefer to own the scope of authentication, you can apply for Trusted Authentication. If interested, please notify your Astra Implementation Manager and they will share an application with you. For more information, please review the following guide: Trusted Authentication.

S3 Bucket Setup
If your integration uses an S3 bucket, set this up as part of your sandbox deliverables. For more information, please review the following guide: S3 Report Set Up Guide.

MVV
Applicable to programs using AFTs and or OCTs. If you have an incentives program with Visa, please share your MVV (Merchant Verification Value) with Astra. If you do not have an incentives program with Astra, Astra will proceed with creating a Card Acceptor ID (CAID) and Merchant Transaction Identifier (MTI) for your program.