When transactions are generated using this method, they incorporate a standardized transaction description that is crafted based on the inputs specified during the funding request. This ensures that all transactions are uniformly documented, providing clear and consistent information regarding the nature and purpose of the transaction. The standardization enhances transparency and simplifies record-keeping, making it easier for users to track and reconcile transactions associated with card funding activities.
Initiate card funding
post
Path parameters
customerIdstringRequired
Header parameters
authorizationstringOptional
Authorization header containing your API Token
x-alg-noncestringOptional
Nonce used to generate the payload signature
x-alg-signaturestringOptional
Payload signature
datestringOptional
Date of the request un UTC/GMT
Body
amountnumberRequired
Amount of the funding in minor units (e.g., for £1.29 enter 129).
Example: 129
idempotencyKeystring · uuidRequired
Idempotency key to prevent duplicate funding operations.
Example: 1483d25d-3f00-4d39-90ce-2379a130becd
externalReferencestring · uuidRequired
External reference identifier provided by partner.
Example: 550e8400-e29b-41d4-a716-446655440000
phasestring · enumRequired
Phase of the card transaction.
Example: AUTHORIZATIONPossible values:
typestring · enumOptional
Type of the card transaction. Optional but recommended for accurate reference generation.
Example: CARD_PAYMENTPossible values:
transactionTokenstring · uuidRequired
Unique reference for the card transaction, to logically group multiple events.
