Payment Tokens

tokens create an additional layer of security for sensitive customer information, such as bank accounts, allowing them to be stored securely within monoovas system and referenced using a token the tokenization system is designed so that the generated token has no mathematical or algorithmic link to the original data instead, the token is a randomly generated guid currently, the system supports two types of payloads australian bank account numbers bpay crn and biller code securely generating a token tokens are most secure when the underlying payment information never passes through your server to enable this, monoova allows you to generate docid 0nc5 xf7d6vx6mjztivli that can be embedded in a web form, allowing you to call our api without exposing your sign in account credentials this flow can be used for capturing new payment details using the docid\ x jgojqb6lbuzcpmg3hbd endpoint, or for maintaining an existing token using the docid 44gj mw9xuc1ve33lo5mo endpoint docid 6i8ccg4pwm7lu 35jkhkl display a form to capture bpay or account details on your application call the docid\ x jgojqb6lbuzcpmg3hbd endpoint using the security token instead of your sign in account credentials using tokens for payment bank account tokens can be used for direct debit transactions by specifying the paymentsource as "token", and for bpay or direct credit by specifying the disbursementmethod as "token" by passing the token id in the token object, the system will retrieve the payment details and transact to or from the target account sample direct credit payment to a token { "totalamount" 100, "paymentsource" "token", "token" "00000000 1111 0000 0000 000000000000", "disbursements" \[ { "disbursementmethod" "token", "totoken" "11111111 0000 0000 0000 000000000000", "lodgementreference" "monoova 123", "amount" 100, "description" "direct credit to beneficiary using tokenized system" } ], "description" "token based credit transfer for service payment" }{ "durationms" 28, "status" "ok", "statusdescription" "operation completed successfully", "transactionid" 1022, "feeamountexcludinggst" 0 08, "feeamountgstcomponent" 0 008, "feeamountincludinggst" 0 088, "calleruniquereference" "dctoken123", "feebreakdown" { "transactionfee" { "feeamountexcludinggst" 0 08, "feeamountgstcomponent" 0 008, "feeamountincludinggst" 0 088 } } } retrieving token details to retrieve the details of a single existing token you can call the docid\ itwd9f0vpubk01iyu3gje endpoint, which returns the token id, hint, description, and token type the underlying payment details are not exposed if you require the details for all tokens under your account you can call the docid\ fpquay47bb luhyajqd9x endpoint, which returns the same information in an array deleting a token tokens can be deleted by calling the docid\ m0ntkyhgbo5hp3nwgtpkg endpoint with the token id if you are exposing tokens as a saved payment method for users of your application, it's recommended to also provide this as an option to allow users to self service their payment options validating a token if you want to validate that the token id you have stored exists in our system you can call the docid\ imv1jbchx59t7vhmejlq0 endpoint this is a lightweight endpoint that returns either a 200 response if the token exists, or a 404 response if the token can't be found this can be used to verify a token has been deleted