US 11,783,387 B2
Software development kit (SDK) for non-profit layer data capture for online donation transactions
Raymond J. Gary, Jr., Dallas, TX (US)
Assigned to iDonate LLC, Plano, TX (US)
Filed by iDonate LLC, Plano, TX (US)
Filed on Aug. 16, 2022, as Appl. No. 17/820,037.
Application 17/820,037 is a continuation of application No. 17/460,136, filed on Aug. 27, 2021, granted, now 11,430,021.
Claims priority of provisional application 63/071,914, filed on Aug. 28, 2020.
Prior Publication US 2022/0391953 A1, Dec. 8, 2022
Int. Cl. G06Q 30/02 (2023.01); G06Q 30/0279 (2023.01); G06F 16/958 (2019.01); G06Q 20/38 (2012.01); G06Q 30/01 (2023.01)
CPC G06Q 30/0279 (2013.01) [G06F 16/958 (2019.01); G06Q 20/389 (2013.01); G06Q 30/01 (2013.01)] 32 Claims
OG exemplary drawing
 
1. A method of conducting a donation transaction associated with a non-profit, the method comprising:
receiving, at a software development kit (SDK) and from a web browser via a network and an embeddable form displayed using the web browser:
a unique token associated with payment data from a donor to the non-profit; and
non-profit layer data formed by a first combination of payment metadata;
wherein the payment metadata is associated with the payment data from the donor to the non-profit;
wherein the embeddable form has been customized to collect the first combination of payment metadata from a plurality of different combinations of payment metadata; and
wherein the first combination of payment metadata is specific to the donation transaction with which the non-profit is associated so that the non-profit layer data customizes attributes of the donation transaction;
wherein the first combination of payment metadata comprises data related to a recurring donation;
wherein the data relating to the recurring donation comprises a time interval;
and
wherein the first combination of payment metadata further comprises data related to:
a campaign identifier;
a tribute gift;
an anonymity preference;
a fund designation; or
any combination thereof;
executing, by the SDK, the donation transaction in accordance with:
the unique token associated with the payment data, and
the payment metadata associated with the payment data;
storing, by the SDK, the unique token associated with the payment data and the payment metadata associated with the payment data;
determining, by the SDK, that the time interval has passed;
after determining, by the SDK, that the time interval has passed, accessing, by the SDK:
the stored unique token associated with the payment data, and
the stored payment metadata associated with the payment data;
executing, by the SDK, another donation transaction, wherein the another donation transaction is made in accordance with:
the unique token associated with the payment data, and
the payment metadata associated with the payment data;
and
recording, by the SDK, the another donation transaction on a server associated with the SDK.