# Checklist

Before initiating live payments, our integration team needs to verify your integration to ensure all essential steps are completed accurately.&#x20;

This verification involves a 30-minute call where we'll explore the following areas:

* [ ] **User Onboarding and KYC:** Describe your approach to onboarding new users and conducting Know Your Customer (KYC) checks.
  * [ ] How do you handle PAD pre-authorized-debits for EFT and ACH?
* [ ] **Transaction Idempotency:** Explain your methods for preventing duplicate transaction processing to maintain data integrity.
* [ ] **Transaction Failures:** Outline your strategy for managing transactional errors and ensuring error resilience.
  * How do you handle failures, specifically late failures for EFT and ACH?
* [ ] **Webhooks Implementation:**
  * How do you manage webhook delivery failures?
  * What security measures have you implemented for webhooks, such as HMAC signatures or IP restrictions?
  * Have you configured email notifications to be alerted about failed webhook events?
* [ ] **Wallet Balance Management:**
  * Have you set up email notifications to alert you when wallet balances become negative?
* [ ] **Production Account Limits:** Confirm your awareness and understanding of the current limits on your production account.
* [ ] **Zūm Rails API Usage:** Confirm which Zūm Rails APIs your system interacts with and the frequency of these calls.
* [ ] **Status Page Subscription:** Confirm your subscription to our status page to stay informed about system updates and issues.

This discussion will help ensure a robust and secure integration.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zumrails.com/go-live/checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
