CAFConfirmation of Available Funds – A CBPII begins the Confirmation of Funds journey by registering a request to confirm funds of a PSU. The CBPII must then obtain consent from the PSU in order to authorise the request, enabling it to request the information. Once the request is authorised, the CBPII will be able to invoke Confirmation of Funds API to the confirm availability of funds in the PSU account. requests are created with the selected-language variant of the fundsConfirmationRequestBuilder() method. Once the token request is created, you store it, awaiting a corresponding request-id, which is returned by Token in a response payload. In addition to the request-id, the response payload reflects all the information you included in your original request. Equipped with the request-id, you can redeem the token, thereby receiving the requested confirmation of available funds.
Note: The bank will not prompt the user to select a specific account (regardless of whether the user has one or multiple accounts with the bank). The bank will create an access consent only for the account provided in the token request, so you must capture the specified user account before populating the token request.
Even though it's really quite simple and incredibly secure, accuracy remains paramount vis-à-vis making the right calls with the right information at the right time.
Here's the basic structure of the request.
// Entry point
private static final Member
. . .
// Create a token request to be stored
// set the bankId
// validates the session ID
// use keys in bank authorization metadata from getBanks() response
// Store the request
request-id = cbpiiMember.
The key fields comprising a CAF access token request are defined in the following table.
|accountId||Identifier of the grantor-provided bank account — the user's bank account — e.g., "Main Checking"||Required|
|authorizationMetadata||Needed to capture additional information from the user for initial authorization by the bank, thereby allowing the user to proceed with providing consent for the initiation request. Maps the key-value pairs from the getBanks() response, where key is the name of the field and value is the value of the field.||Required|
|bankId||Must be specified for CAF requests; indicates you wish to bypass the Token bank selection UI and use your own bank selection UI for the request. See Using the getbanks Method||Required|
|callBackState||TPP-specified string that persists state between request and callback||Optional, but recommended|
|customizationId||Identifier for customizing the UI of the Token web app (see Customising the Token Webapp for details)||Optional|
|description||Description of the payment with the following qualifiers:
• description in a subsequent call must match description in originating request
• description omitted in originating request must also be omitted in subsequent calls
• description omitted in subsequent call will be replaced with refId
This description field maps to description in the bank's consentRequest presented to the user.
Warning: If description in a subsequent token request for lookups/changes/updates (retrieve, redeem, or cancel) doesn't match the description in the originating token request, an exception will be thrown.
|grantee||The "To" TPP member placing the access request, which will receive the information upon successful token redemption||Required|
|grantor||User Alias (DOMAIN orEMAIL) of the user member granting access to the specified bank account. To review the methods for finding an alias see Fetching an Alias.||Required|
|receiptRequested||Boolean; requests a receipt be sent to the grantor member's default email address||Optional|
|redirectUrl||Specifies the callback URL where your server will initiate token redemption||Required|
Reference identifier for the token; not to be confused with requestId. RefId maps to tppRefId in the bank's consentRequest. It is needed to match/verify the originating token request with the bank's consent request.
Warning: A description mismatch between the originating token request and subsequent token lookups/changes/updates (retrieve, redeem, or cancel) will throw an exception.
|resourceType||Specifies the type of information for which access permission is requested; in this case, FUNDS_CONFIRMATIONS – confirmation of available funds in the specified account||Required|
|token_expiration||Sets the expiration date and time for the token request (default is 20 minutes); override of default value is not supported by all banks||Optional|
|traceID||TPP-provided unique value captured by Token and sent across to the bank to be stored with the request throughout its lifecycle as an audit-trail aid.||Optional|
After storing the transfer token request, you're ready to construct the redirect URL for authorisation so the customer can authenticate, provide consent, and authorise account information access for funds confirmation as previously outlined in the CAF communication workflow.
Tip: When integrating the Token SDK with a mobile app, you can initiate the token request in WebViewA browser engine that you can insert like an iframe into your native app and programmatically tell it what web content to load. so that the redirect is also in the form of an HTTP 302An HTTP response with this status code will additionally provide a URL in the header field Location. This is an invitation to the user agent (i.e., a web browser) to make a second, otherwise identical, request to the new URL specified in the location field. The end result is a redirection to the new URL.. However, in terms of activity layout, WebView lacks many features found in a fully developed web browser.