1.15. Deposit To Card Transfer

Introduction

Deposit to card transfer (D2C) is a money transfer from Connecting Party bank account (Deposit) to Receiver bank card number (PAN) or tokenized card data (Card Reference ID). Deposit to card transfer is made in three steps:

Initial payment – any transaction type with present cardholder data will work as initial payment - sale, preauth, transfer, etc. It is important to make the initial payment the most secure way in order to guarantee that a real card holder is registering the card.
Card registration – get card-ref-id (Card Reference ID) and register Customer’s card in their profile. Card Reference ID can be used unlimited number of times, while the bank card is active.
Money transfer – run v4/transfer-by-ref/ API command using destination-card-ref-id obtained on previous step.
See terms definitions in Glossary.

Deposit To Card Transfer Flow

@startuml skinparam roundcorner 20 skinparam sequenceArrowThickness 1 skinparam maxmessagesize 1200 skinparam sequenceParticipant underline actor Payer as P participant "Connecting Party" as A participant SBC as B autonumber hnote over P,B : Initial payment ==Card registration== A -> B: api/v2/create-card-ref activate A activate B B --> A: Return card-ref-id deactivate B A -> A: Assign Card Reference ID to Customer's profile deactivate A ==Get card info== group optional A -> B: api/v2/get-card-info/ activate A activate B B -> A: Return Card info deactivate A deactivate B end ==Deposit To Card== A -> B: api/v4/transfer-by-ref/ activate A activate B B --> A: Response with Order ID B -> B: Process\nDeposit group Get Final Status == Receive Connecting Party Callback == A <- B: Callback with Final Status A --> B: HTTP 200 deactivate B == Order Status Request == A -> B: Get Status by Order ID activate B B --> A: Final Status deactivate A deactivate B end @enduml

(1) To implement Card registration and get Card Reference ID see /api/v2/create-card-ref.
(3) Connecting Party assigns Card Reference ID to Customer’s profile, after which Connecting Party shows the page saying that the card registration is successful and initial payment approved.
(4) To implement Card information request by Card Reference ID see /api/v2/get-card-info. The contents of response to this request can be used to show information about previously used card to Payer or to update Connecting Party database. This request can be made anytime if Connecting Party has Card Reference ID.
(6) Connecting Party initiates deposit to card transfer (D2C). To implement deposit to card request see api/v4/transfer-by-ref
(9) To implement callback with final status handling see Connecting Party Callback.
(11) To implement order status request see /api/v2/status/. Status should be requested multiple times with 3-5 seconds interval until final status will be received in response.
(12) Final Status can be sent by Connecting Party based on internal business model or by Receiver’s request.