TodayPay Docs
  • TodayPay Platform
    • Overview
    • Environments
    • Authentication and connection
    • Payments Overview
    • Initiating Payments via Batch File
      • SFTP File Submission
      • API File Submission
    • Initiating Payments via API
    • Notifying customers
    • Reporting
      • Payment Report File
  • API Reference
    • Payments API
  • Guides
    • Initiating Multiple Payments to Same Customer
    • Sending Payments from the Dashboard
Powered by GitBook
On this page
  • End Customer Experience
  • Uniquely Identifying Customers
  • Information Consistency
  • Example
  1. Guides

Initiating Multiple Payments to Same Customer

Integrators may need to initiate multiple payments to the same customer

Integrators can send multiple payments to the same customer. TodayPay recommends using the notes on payment initiation to associate multiple payments with the same customer. The idempotency_key should be unique for each "intended" payment for a customer.

End Customer Experience

Customers will see the total aggregate sum of payments it their TodayPay account. E.g. if you send 2 $50 payments, the customer will see 2 payments reflected their transaction history and an aggergate balance of $100.

Uniquely Identifying Customers

TodayPay uses phone_number as the the primary key identifier for customers.

Information Consistency

We strongly recommend consistency in sending identifying information. This prevents accidental creation of duplicate customer-facing wallets.

Payments with conflicting information will not fail. We don't provide indication of information inconsistency

We reccomend keeping email and phone_number information consistient across across payments to the same user.

Example

Payment 1 Submission e.g. Initiated January 1

Field
Value

phone_number

+14930494849

email

joe@gmail.com

amount

100.00

idempotency_key

8d691e67-ba4b-4554-a0ad-46834d0519bf

notes

client_account_abc123

Payment 2 Submission e.g. Initiated January 10.

Ensure sending new idempotency_key to uniquely identify the payment

Recommend sending same notes field to uniquely idendity the customer

  • This is helpful in reporting or API connection to "query payments by customer"

Field
Value

phone_number

+14930494849

email

joe@gmail.com

amount

50.00

idempotency_key

32274664-2661-4084-b5f1-8d15e798a43d

notes

client_account_abc123

PreviousPayments APINextSending Payments from the Dashboard

Last updated 3 months ago