Skip to main content
After initiating a card request and receiving a transaction_id, you call this endpoint to confirm the order and complete the purchase. Wasl processes the payment reference you provide and returns the actual card codes and card numbers that you deliver to your customers. This is the final step in the card order flow.
You must call Initiate Card Request first and use the transaction_id it returns. Attempting to confirm an order without a valid transaction_id from a prior initiation will fail.

Endpoint

Base URL (Development)

Request Headers

Request Body

string
required
The transaction ID returned by the initiate-card-request endpoint. This links the confirmation to the earlier reservation.
double
required
The total monetary amount for the order. This should match the value of the cards being confirmed.
string
required
Your internal payment reference identifier. Use this to correlate the Wasl transaction with your payment records.

Example Request

Request
cURL

Response

On success, Wasl returns an array of card objects under the data key. Each object contains a redeemable code and a card number corresponding to one of the cards in your order.
boolean
true when the order was confirmed successfully.
string
A response code for the operation. "11111" indicates success.
array
An array of card objects — one entry per card in the order.

Example Response

Response
Deliver card codes to your customers promptly after receiving them. Card codes have monetary value — treat them as sensitive data in transit and at rest. If a card turns out to be faulty or unredeemable, use the Cards Console Panel to request a replacement from Wasl support.
The number of objects in the data array will match the quantiry value you specified during the initiate step. Verify the count before delivering codes to customers.