Integration of the Pledg payment solution

# Transfer mode

# Use case

See here.

# Sequence diagram

# Integration

This mode is particularly simple to deploy as there is strictly no configuration to be completed on the merchant backend or merchant PSP.

# Result

The general principles of the result sent to the merchant frontend are detailed there.

The JSON contains the details of the transfer to be completed.

The structure of the JSON is the following:

{"purchase": {"meta_data": {"departure-date": "2022-03-30"},
              "reference": "PLEDG_6500735432411",
              "uid": "pur_c9299823-810e-4e8b-a7c3-bde856e6840c"}
}

# Notification

The general principles of the notification sent to the merchant backend are detailed there.

The JSON contains the details of the transfer to be completed.

The structure of the JSON is the following:

{
   "reference":"purchase_reference",
   "created":"2020-09-17 15:00:02.052177",
   "transfer_order_item_uid":"tri_fasdkfiasfsd234nfs7f5d",
   "merchant_uid":"mer_e821ccca-7a16-45a7-8b00-0a6015e16123",
   "purchase_uid":"pur_6c48d42b-f29b-4f84-bee8-3cb2b964b600",
   "amount_cents":10000
}

If there is a secret in the configuration of the merchant, it is used to sign the notification body with JWT.

{
    "signature": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyZWZlcmVuY2UiOiJwdXJjaGFzZV9yZWZlcmVuY2UiLCJjcmVhdGVkIjoiMjAyMC0wOS0xNyAxNTowMDowMi4wNTIxNzciLCJ0cmFuc2Zlcl9vcmRlcl9pdGVtX3VpZCI6InRyaV9mYXNka2ZpYXNmc2QyMzRuZnM3ZjVkIiwiYW1vdW50X2NlbnRzIjoxMDAwMH0.6ZhlvdcPgjwwBfxCrRpzaBGoRxTCoqtWJzFhB8pw4Ys"
}

← Refunds →