Instant digital issuance

A system comprising:

• at least one memory comprising computer-readable instructions stored thereon;
• and
• at least one first processor associated with a gateway and at least one second processor associated with a software development kit to provision a payment source, wherein the at least one first processor and the at least one second processor executes the computer-readable instructions to:
• receive, by the gateway, a first request from an issuer application on behalf of a cardholder for a list of entities comprising merchants or pay wallets that are eligible to receive the payment source;
• send, by the gateway, the list of entities to the issuer application for display to the cardholder for selection of an entity from the list of entities;
• receive, by the software development kit and from the issuer application, the selected entity;
• prepare, by the software development kit, pass-through data for sending to the issuer application to request provisioning of the payment source to the selected entity;
• receive, by the gateway, a second request from the issuer application in response to sending the list of entities to the issuer application, wherein the second request comprises the pass-through data, an asset identifier associated with the selected entity, and user data associated with the cardholder;
• prepare and transmit, by the gateway, a response to the issuer application upon receiving the second request, wherein depending upon a type of a token service provider or the selected entity, the response comprises (a) an encrypted payload obtained by encrypting, by the gateway, at least the entity identifier and the user data;
• or (b) a receipt identifier;
• receive, by the software development kit, the response from the issuer application;
• redirect, by the software development kit, from the issuer application to an entity application associated with the selected entity, wherein the redirection includes sending the encrypted payload or the receipt identifier to the entity application to allow the entity application to send the encrypted payload or the receipt identifier to the token service provider to request a new token for the payment source from the token service provider;
• receive, by the software development kit, a result from the entity application indicating whether the entity application successfully received the new token from the token service provider;
• and
• determine, by the software development kit and based on the result, whether the request for the provisioning of the payment source is successful.

A method comprising:

• receiving, by at least one first processor associated with a gateway and at least one second processor associated with a software development kit for provisioning a payment source and executing computer-readable instructions stored on at least one memory, a first request from an issuer application on behalf of a cardholder for a list of entities comprising merchants or pay wallets that are eligible for receiving the payment source;
• sending, by the gateway, the list of entities to the issuer application for display to the cardholder for selection of an entity from the list of entities;
• receiving, by the software development kit and from the issuer application, the selected entity;
• preparing, by the software development kit, pass-through data for sending to the issuer application to request provisioning of the payment source to the selected entity;
• receiving, by the gateway, a second request from the issuer application in response to sending the list of entities to the issuer application, wherein the second request comprises the pass-through data, an asset identifier associated with the selected entity, and user data associated with the cardholder;
• preparing and transmitting, by the gateway, a response to the issuer application upon receiving the second request, wherein depending upon a type of a token service provider or the selected entity, the response comprises (a) an encrypted payload obtained by encrypting, by the gateway, at least the entity identifier and the user data;
• or (b) a receipt identifier;
• receiving, by the software development kit, the response from the issuer application;
• redirecting, by the software development kit, from the issuer application to an entity application associated with the selected entity, wherein the redirection includes sending the encrypted payload or the receipt identifier to the entity application to allow the entity application to send the encrypted payload or the receipt identifier to the token service provider to request a new token for the payment source from the token service provider;
• receiving, by the software development kit, a result from the entity application indicating whether the entity application successfully received the new token from the token service provider;
• and
• determining, by the software development kit and based on the result, whether the request for the provisioning of the payment source is successful.